Add the ability to create outlets

[pulkitsinghal]

Motivation

I want to be able to take a data dump and mimic customer environments for testing. This often requires populating similar products which requires populating similar taxes and outlets and such.

Requirement

It would be a good start to get a POST endpoint to create outlets so we can begin the journey to one day seamlessly copy a subset of customer account for testing in our vend subdomain before delivering solutions.

cc @ysg410 @szeber

[ablears]

Sounds great. Also could be used for staging/live environments.

[pzurek]

This is something we hear from time to time but it's a dangerous thing to open.
Retailers on certain plans have no limit in the amount of allowed outlets/registers. Since they are getting billed on a per register basis, an integration creating a number of registers unintentionally could mean a huge unexpected bill. It's a dangerous situation.
It's not to say that this is never going to happen, but there's more decisions to be made here than just committing resources to do the implementation. I'll keep this around to see how many people react with 👍.

[pulkitsinghal]

Is there room for middle ground:

• By default API posts to create outlets and other pricing sensitive entities should fail. A flag must be toggled by the owner of the subdomain before POST API requests for that price-sensitive entity are allowed?
• I understand this means extra UI work that you probably really really don't have the bandwidth to do but if it gets done then everyone wins?

[pzurek]

I was thinking in more general terms about a specific OAuth scope which would enable that. Apps requesting this scope could get a very strong warning.
Of course, that means we have to implement scopes. :-)