Supplier stock sync: how to avoid showing the wrong availability

Key points

• Keep your own stock separate from supplier availability.
• Match the product and variant before updating.
• Decide what you show when the last update is too old.

The problem starts when two stocks look like the same thing

A customer orders a product shown as available, and your team then finds out it exists only at the supplier. A phone call follows, then a check and a changed delivery date. Automation should reduce this kind of surprise, not just copy a number into a field.

Define separately the quantity in your own warehouse, the reserved quantity and external availability. Tell customers whether the product ships from your stock or after restocking. Do not promise a delivery time just because the supplier reports a positive quantity.

How to choose the source and match products

Check what the supplier provides: an API, a periodic file or another authorized interface. Ask for a description of the fields, the update frequency and what availability means. Some sources give exact quantities, others only states such as in stock or available to order.

Match products using verified codes, manufacturer identifiers or other consistent keys. A similar name is not enough for technical variants. Build a list of unmatched products and send it for review instead of updating based on a guess.

Which business rules must be written down before the integration

If the same product is offered by several suppliers, decide how you choose the availability you display. Price, lead time and restocking terms may differ. Do not add quantities together automatically if the sources may describe the same stock or if you cannot order from all of them at once.

Also decide when a product can be ordered. You can allow orders with later confirmation or limit sales to guaranteed stock. The rule depends on your business model and must be explained to the customer before checkout.

• The official source for each field.
• The rule for your own stock and reservations.
• Supplier priority and estimated lead time.
• The condition that stops a sale or sends it for review.

What happens when the source does not respond

Keep the date of the last successful update and distinguish a missing response from zero stock. An empty or incomplete file should not wipe the entire catalog without a check. Set alert thresholds for unusual changes and for products that disappear from the source.

Decide how long you accept old data and what you show once that window has passed. One option is to ask for availability confirmation. The person responsible must see the error and the affected products, not just a technical message in a log nobody reads.

How to test with real products

Pick products with variants, your own stock, external stock and no availability. Check every update in the catalog, in the cart and in the order sent to your team. Simulate a delayed source, an unknown code and a sudden drop in availability.

Regularly compare quantities and reservations across the relevant systems. Update frequency does not fix a wrong rule on its own: you can update the wrong information very often. First check what the data means, then choose the pace you need.

How to start without connecting the whole catalog at once

Start with one supplier and one group of products whose identifiers have been verified. Track the orders that needed an availability correction and the time spent checking. Extend the integration once exceptions have a clear procedure.

Webmate connected the online store, the WMS and the ERP/CRM in the Center Electric project. For an integration with your suppliers, we need the source documentation and product samples. Each supplier's terms must be checked before we can promise synchronization.

Frequently asked questions