Appearance
The journey of a stock number
This page follows one stock number from the warehouse to the marketplace. Each step has its own page in this section if you want the detail.
The journey at a glance
From the moment the PIM changes, the trip takes at most about 15 minutes, and usually less. Almost all of that is waiting for the next PIM reading; sending itself takes seconds. See When things happen.
The same journey, in time order
The flowchart shows the decisions. This diagram shows who talks to whom, and in which order.
A worked example
Here is a real-looking morning. Product 123456 is a jacket, SKU K50K510943-BAX, size M. It is offered on two accounts:
| Account | Mode | Lead-time limit | Offer | Published |
|---|---|---|---|---|
| eMAG RO | Live | No limit | 123456, Linked, In sync | 3 |
| Fashion Days RO | Preview | No limit | 123456, Linked, In sync | 3 |
10:15. A delivery arrives. The warehouse system tells the PIM: available 5, on hand 6. Neither marketplace knows yet.
10:22. The regular PIM reading runs. It asks the PIM for everything that changed since the previous reading at 10:07. Product 123456 is among the 214 products it sees; 37 of them really changed. The reading shows up in Activity → Sync runs as a PIM reading with "214 seen · 37 changed".
A second later, Stock Sync looks for every offer of product 123456 and recalculates each one:
| Account | PIM available | Stock to publish | Published | Result |
|---|---|---|---|---|
| eMAG RO | 5 | 5 | 3 | Waiting to send |
| Fashion Days RO | 5 | 5 | 3 | Waiting to send |
Straight after, a Sending round runs for each account:
- eMAG RO is Live. Stock Sync sends "offer 123456: 5". eMAG answers that it accepted it. The offer becomes In sync with Published 5. On the offer's page the history shows Stock to publish changed, then Published, and the exact request and answer.
- Fashion Days RO is in Preview. Nothing is sent. The offer stays Waiting to send, with Stock to publish 5 and Published 3. The account's status banner now counts it in "Going Live would send … stock updates now." When the account goes Live, this is exactly what will be sent.
Overnight, a customer buys one jacket on eMAG. The marketplace lowers its own stock to 4, but the PIM still says 5 because the order has not reached the warehouse system yet.
04:41 next morning. The daily Offer import reads every offer on eMAG RO. It sees Marketplace shows 4 where we last published 5. That difference is called drift. The offer goes back to Waiting to send and Stock Sync sends 5 again, because the PIM is the source of truth. When the order reaches the PIM and it says 4, the next reading sends 4.
What can change the journey
| Situation | What happens instead | Read more |
|---|---|---|
| The product's lead time is longer than the account's limit | Stock to publish is 0; the offer shows Eligible: No | How the quantity is calculated |
| The offer id is not a PIM product id | The offer is Not linked and never touched | Matching offers to products |
| The marketplace is busy or times out | Retried after 30 seconds, 1 minute, 2 minutes … up to 30 minutes; Failed after 8 tries | Sending stock to the marketplace |
| The offer is in a marketplace campaign | Rejected (campaign lock), retried every 6 hours for up to 14 days | Sending stock to the marketplace |
| The marketplace refuses the password | The whole account is Suspended | Account health and pausing |
| The account is in Preview or paused | Calculated but not sent | Preview and Live |
| The PIM cannot be reached | The reading fails and the next one catches up; the Overview warns after 20 minutes | When things happen |