Stock and order sync in e-commerce: when a sold product is not in stock

A customer places an order, pays and the next day receives an email saying “your order has been cancelled because the product is out of stock”. Stock and order synchronization means that every product sold in e-commerce is reflected in its stock record and that the store, the ERP and the marketplaces all look at the same stock information; when this breaks, the product that was sold does not come off the shelf.

In this article we explain how the problem arises, why it repeats and which questions need answering when setting up synchronization. We give our examples through the ERP and marketplace connections in the YazSis Smart E-Commerce platform. The subject is not only a technical transfer matter; it also concerns how the sales, warehouse and customer service teams work together.

How does a wrong sale happen?

The problem often comes not from a single mistake but from several small delays stacking up. At no step has anyone done anything wrong; but the gap between the steps is enough for the same product to be sold twice. The chain below is the most familiar example of this:

1. The last two items in the warehouse are shipped with a marketplace order and the stock in the ERP drops to zero.
2. The store site still shows “in stock” because its stock information is updated at intervals or by hand.
3. A customer adds the same product to the cart and completes the payment.
4. When the warehouse starts to prepare the order, it cannot find the product in the shelf record.
5. Customer service starts the cancellation and refund process and sends the customer an apology message.
6. The customer has neither received the product nor kept their trust; the refund process has also created extra work for the team.

The cost of this chain is not limited to the cancelled order. The time of customer service, the processing load of the payment refund, the service score dropping on the marketplace and the customer who never shops again are the invisible items. That is why stock accuracy is less a warehouse topic than a sales and reputation topic.

Why does synchronization break?

• Stock does not flow from a single source. The store, the ERP and the marketplaces each keep their own stock count; it is unclear which one is “real” and everyone trusts their own number.
• The update is delayed. If data is transferred at intervals or by hand, a product sold between two transfers can be sold twice. The shorter the interval, the lower the risk, but it never disappears completely.
• The number of channels grows. As marketplaces, dealers and corporate sales are added to the store, the same stock is drawn down from more places and every new channel means a new point of delay.
• Events are defined incompletely. If events that affect stock, such as cancellations, returns, transfers and partial shipments, are not reflected in the system, the difference grows quietly and only shows up at the count.

Even when the stock number is not wrong, it can produce a wrong sale because it was seen at the wrong time.

Six questions to answer during setup

Synchronization is not a matter of switching on a connection and walking away. The questions below should be put in writing before setup and approved together by sales, the warehouse and IT:

1. Which is the source of stock? The ERP, warehouse management or the store? The other systems should be fed from this source and should not draw down stock on their own.
2. Which events affect stock? Orders, payments, cancellations, returns, transfers and count corrections should be considered together; if one is forgotten, the difference builds up there.
3. Does an order awaiting payment hold stock? If so, for how long? If not, you have accepted the chance of two people taking the last item at the same time.
4. Will quotas be set aside for channels? Will every channel sell from the same pool, or will there be a limit per channel?
5. Which warehouse will be visible? In a multi-warehouse setup, which warehouse’s stock will the customer see, with which delivery time?
6. Who will be notified if something goes wrong? There should be an alert mechanism so the team notices when a transfer fails.

What to look at in daily operation

Synchronization is not a feature you set up once and leave; it is a process that is monitored. A few checks the operations team can glance at every day let you catch the problem before the customer complains: products that are out of stock but still appear for sale, the reasons for cancelled orders, transfers that ended in error and products that look different between the warehouse and the store. When this list is kept short, it really gets looked at; when it is long, nobody looks.

The approach in YazSis Smart E-Commerce

YazSis Smart E-Commerce is built so that the store is not left detached from the rest of the company. The ERP and marketplace connections aim to keep product, stock, price, order and delivery data in sync. Multi-warehouse, stock and lead-time visibility and shipping and delivery status notifications are in the same data flow. Before going live, product, customer and order data is verified and critical scenarios are tested; the answers to the questions above form the scope of these tests.

To bring your stock and order data into a single flow between the store, the ERP and the marketplaces, you can look at the Smart E-Commerce page.