Stocks Upload
The task reports your stock into the Shopify shop, and nothing else. It is separate from Products Upload, because stock changes far more often than a product does: that way a change in stock does not drag the whole product record along.
What gets transferred
For each product already present in the shop the stock quantity goes over, namely to a particular location in the shop. Shopify keeps stock not on the article but per location, and this task is the place where your stores meet the shop's locations.
This task creates no product, it only changes what is there.
How the transfer plan is built
One plan with two sections.
| Section | What sits in it |
|---|---|
| Selection | Which products get reported and how TRADElube recognizes the counterpart in the shop |
| Stock | One tab per shop location, with Location and Quantity |
The Stock section is empty out of the box, and without it the task transfers nothing. Through the button Add you create a tab, and the bin symbol on the tab removes it again. The tabs are numbered.
Such a tab carries two rows. Location is a fixed value and is picked from a drop-down TRADElube fetches from the shop when opened. Without a standing connection it therefore stays empty. Quantity lists your stores as sources, one per store. So you decide per location which of your stores it is to see. Where you keep several and one location is to see their total, enter that as a script.
One tab per location is the right construction even where you keep a single store: Shopify needs to be told which location the quantity sits at, and without it the shop would not know where the goods are.
Selection carries two rows. Condition decides which products get reported. Existing Item decides how TRADElube recognizes the article in the shop: through the product number as SKU, through the manufacturer product number as barcode, or through the EAN as barcode. The rows New Item and Removed Item are absent, because this task neither creates nor deletes anything in the shop.
Special features and limits
The task behaves differently depending on whether Products Upload sits on the same channel. Where it does, the execution skips the parent articles, because in Shopify their stock hangs on the variants. Where it does not, this task looks the article up in the shop itself and says so explicitly when it does not find it, so that a shop without stock does not look like a silent failure.
The product numbers have to match on both sides. TRADElube finds the article in the shop through its channel mapping and then checks whether its SKU is still the product's product number. If it differs, that product's transfer stops with a message instead of overwriting somebody else's stock.
Further reading
- Shopify: prerequisites, connection, mappings and the other five tasks
- Products Upload (Shopify): the task transferring the products themselves
- Stock (concepts): where stock comes from and what it says
- Stores (reference): the stores appearing as sources in the Stock section
- Transfer plan (concepts): plan, section and assignment, plus the three ways to determine a value