Organized
This commit is contained in:
@@ -0,0 +1,16 @@
|
||||
reliable "change sku" API endpoint that corrects the SKU assigned to one or more individual_product entries owned by the same user.
|
||||
|
||||
## What usually causes the problem:
|
||||
|
||||
**Not confident to choose/verify SKU**: While receiving and checking in packages from someone like Moses, there we receive one or more items we can't confidently match to one of his products. Then, either:
|
||||
|
||||
a) We choose an "AUTO-" sku or "add unexpected item", and type a description of what we have.
|
||||
b) We make a guess or a mistake, and and it turns out to be incorrect.
|
||||
|
||||
On the employee-facing side of the portal, we have a tool for fixing this from the [[Refurbishment Panel]] and also [[Item Manager]]. Customers like Moses who want to correct the SKU chosen for an item seem to lack an intended, easy-to-use way to accomplish that.
|
||||
|
||||
## Benefits and Tradeoffss about AUTO SKUs and our receiving procedures
|
||||
|
||||
### Our intention should be maximal truth within a predictable timespan and price, pertaining to all handling of inventory. That includes confirming and documenting we received somethinmg addressed to the customer, even if it wasn't expected by anyone.
|
||||
|
||||
AUTO skus are usually left in a "non-final condition" like [[Customer Service Needed]] until somebody does something about it. In practice, we have a persistent rumor that setting "CSN" notifies customers, most customers decide they don't want the items, and Danny is the person who deals with that.
|
||||
Reference in New Issue
Block a user