Services
Custom SoftwareCRMs, portals, dashboards + internal tools. Automation + IntegrationsWorkflows, APIs + business logic. DataScraping, enrichment + monitoring. AIAgents, assistants + knowledge systems. WebWebsites, performance + conversion.
Company
AboutWorkJournal
Start a project →

How to Sync Stock Levels With Your Online Store

A unit can still be on the shelf after your trade desk has promised it. Check what your shop receives and what happens when both channels try to sell it.

NM
Written byNathan MackenzieFounder · ZappFlow
Practical notes on software, automation, data, web and AI.

To sync stock levels with your online store, send the quantity you can still sell, not the quantity sitting on the shelf. If your trade desk reserves the last unit for a customer, the warehouse still has one unit on hand, but the website should have none available to sell.

Check what quantity your connector sends before paying for faster updates. A faster connector can publish the wrong number more often. Even when it sends the right number, a web order can arrive before the shop receives the update. If both channels need to sell the last unit safely, they should ask the same inventory system to reserve it before either confirms the order.

The idea in one viewVISUAL GUIDE
THE FORM IS ONLY THE STARTCONNECTED WEBSITE

How a trade reservation changes online stock

Online shopLIVE
WHAT THE VISITOR SEES

Stock shown for sale

The shelf still holds one unit, but a trade reservation means it is no longer available for the website to sell.

Trade desk reserves last unitReserved
WHAT HAPPENS NEXT
Behind the page
Stock system
Deducts reserved units from sellable stock
Shop connector
Sends sellable stock to the website
Online shop
Shows no units available to buy
CONNECTED OUTCOME
One unit on the shelf, but none offered for sale online
Sellable stock

1. Decide which system calculates stock available to sell

Choose one system to calculate sellable availability for the stock that the website and trade desk share. That could be your warehouse system, order management software or shop platform, provided it can account for the commitments made by both channels. The warehouse count tells you what is physically there. Sellable availability deducts active reservations and any other units you cannot sell, such as damaged goods.

Check what the fields actually mean in your software. For example, Shopify distinguishes on-hand, available and committed inventory. Its inventory developer documentation explains that placing an order moves units from available to committed, while fulfilment reduces the committed quantity. That describes Shopify’s order flow; it does not tell you whether a trade order entered elsewhere reaches Shopify in time.

2. Trace a trade order from reservation to cancellation

Pick one product sold through both channels. Match its SKU and variant in both systems, then check which warehouse or location supplies web orders. A connector can send the right type of quantity from the wrong location.

Ask someone at the trade desk to enter a test order as they normally would. Record the action that actually reserves stock: saving the order, confirming it or a separate reservation step. If staff can promise stock before that action happens, changing the connector schedule will not close the gap. Then edit the quantity and cancel the order before dispatch. The system should release only the units that were still reserved against that order. Since those units never left the shelf, cancellation should not increase the physical count.

3. Check what your connector sends and when it arrives

For the test product, compare the source system’s on-hand and available quantities, the connector’s outgoing update if you can see it, and the quantity stored against the shop variant. Check what the customer can buy at checkout too. The most useful comparison is immediately after a reservation, when on-hand and available quantities differ. If the connector sends one when availability is zero, check the field mapping. If it sends zero but the shop stays at one, check delivery, the destination variant and the location.

Note when the reservation was saved, when the connector picked it up and when the shop applied the update. Repeat for cancellation. Find out whether the connector sends changes as they happen, checks on a schedule or waits for a manual run. If logs are available, check whether staff can spot a failed update and retry it without applying the same adjustment twice. A late reservation update should not overwrite a newer cancellation update. Assign someone to compare shop quantities against the source and correct discrepancies after a failure.

WHAT HAPPENS WHEN SOMETHING GOES WRONGBACKUP PLAN

When the last unit is reserved

01 · PROBLEM
Shop count is stale

Trade reserves the last unit, but the website still shows one. A web order may be confirmed twice.

→
02 · FALLBACK
Pause the web order

If checkout cannot reserve shared stock, hold the order and check its status. Do not trust the displayed count.

→
03 · RECOVERED
Cancellation releases stock

Cancellation before dispatch takes reserved to zero and available to one; the shop updates afterwards.

OUTCOME
Keep the exception visible: check the held web order before confirming.
Check before confirming

4. Run the last-unit test before changing the setup

Illustrative test sheet: Use a test product with one unit on hand in a single shared location, no buffer and no other holds. Run it in a test environment or with a product hidden from customers. Record the time, order reference and actual values beside each expected result. Here, “online” means the quantity held by the shop, even if shoppers only see an in-stock label.

  • Baseline: Physical stock 1; reserved 0; available 1; online 1. Either channel can claim the unit.
  • Trade desk reserves the unit, before the shop update: Physical stock 1; reserved 1; available 0; online may still show 1. The trade order holds the unit even though it is still on the shelf.
  • A web order arrives before the shop updates: Physical stock 1; trade reservation 1; available 0; online still shows 1 just before checkout. If checkout must reserve stock in the same system before confirming, the web order cannot be confirmed. If checkout relies on its local count alone, it may confirm a second order. Record that as a failed test, even if the shop shows zero a moment later.
  • The reservation update arrives: Physical stock 1; reserved 1; available 0; online 0. A new web order should not be confirmed. This update does not undo a duplicate promise already made.
  • The trade order is cancelled before dispatch: Assuming the web order was not confirmed, physical stock stays at 1; reserved falls to 0; available rises to 1; online returns from 0 to 1 after the release update. If the web order was confirmed in the previous test, resolve that commitment and reset the test before checking cancellation in isolation.

Repeat with the website claiming the unit first and the trade desk trying to reserve it before its screen refreshes. Then try both at nearly the same time. The pass condition is one confirmed order at most: the shared system must check and reserve the unit as a single operation. If the reservation request fails or times out, hold the order for a status check rather than confirming it on the strength of the displayed count.

Before rolling out to more products, test order edits, failed payments and returns separately. Their stock rules need not match trade cancellation. For example, WooCommerce’s Hold Stock setting applies to unpaid orders in Pending payment status, not orders marked On hold. Check which status your own process creates and which system is responsible for releasing or restoring stock so that both systems do not add it back.

5. Decide whether to fix the connector, use a buffer or build a connection

Keep the existing connector if it can send sellable availability from the right location and reliably handle changes and releases. Fix the field mapping and reservation workflow first. If the remaining problem is a delay, faster updates can narrow the window for overselling, but they cannot guarantee that two orders will not claim the same unit.

Consider a buffer if the channels cannot reserve against the same stock and you can accept showing fewer units online. For example, withholding the final unit from the website can leave it for the trade desk under normal operation, but it also prevents an online sale when no trade customer wants it. Judge the trade-off using your order patterns, observed update delays and the cost of unwinding a duplicate promise. A buffer reduces risk; it does not repair a failed sync.

Consider a custom connection when the existing connector cannot support a required reservation or release, and the underlying systems can. If both channels must be able to sell the final unit, ask a supplier to demonstrate that checkout and the trade desk can reserve against the same stock before confirming. Where the systems cannot support that behaviour, a custom quantity feed alone will not solve the problem. When scoping automation and integrations for this workflow, include who handles failed reservations, retries, stock discrepancies and changes to the software interfaces. Use the last-unit test as the acceptance check, rather than asking only how often the stock feed runs.

ZappFlow · practical next step

Is your online shop selling stock already promised?

Tell ZappFlow which shop and stock systems you use, where staff take trade orders and what happened when both channels wanted the last unit. We can help you assess whether a connector setting will fix it or whether both channels need a different way to reserve stock.

Discuss your stock integration