All inventory guides

Sync lag vs. real stock drift: how long to wait

Measure how long your own inventory updates take and use a second reading to decide when a mismatch needs attention.

You spot a mismatch between the store and the warehouse. It could be the time it takes for a normal update to arrive, or the quantity could be stuck. Start with the timestamps and whether the compared quantities represent the same inventory. There’s no single wait time that applies to every connector or store. Use your own stock changes to set the point at which you check again.

Start with reads you can compare

Pick a single SKU that’s stocked as a normal unit. Record the warehouse location or group, the matching store location and the quantities at both. Work out the quantity your connector should send after any configured buffer and other adjustments. Note when each number was read and whether it came from a live screen or an export. If it was an export, keep the timestamp it covers when that’s known.

Take both reads close together. If there was a stock event between them, write it down and take a fresh pair when you can. The manual reconciliation guide explains how to choose comparable fields and locations. A persistent difference between mismatched locations can look like a broken sync indefinitely.

Measure normal lag using completed updates

Find several ordinary stock changes you can trace. Use the types of changes you expect to drive updates, such as a warehouse receipt or a stock adjustment. Record when the change first appeared in its source system, when you expected the connector to pick it up and when the destination first reflected it. If you only check the destination at intervals, you have a range for the delay. A change first seen at 10:10 was already there by then, and it may have arrived earlier.

If your connector shows run times or errors, keep them beside the readings. Shopify’s inventory adjustment history can help trace quantity changes on the store side. If your warehouse reported a receipt at a different time from when that stock was ready to sell, record the event that should drive the sync. Collect examples from both quiet and busy periods if your store behaves differently during promotions. Shopify inventory adjustment history

Choose a window your team can explain

Start with the schedule or update expectations for your connector and compare those with the late end of the normal delays you observed. Pick a wait that leaves room for an ordinary update to finish. Include the time it takes to get a fresh reading. Document which changes and locations you measured. If little data is available, call the first window provisional and revise it as you collect more examples.

Suppose, for illustration, that expected updates usually arrive within 10 minutes in the examples you traced, and you only check every five minutes. You might use 15 minutes as a provisional wait. If a midday receipt bumps the warehouse quantity at 12:00 and the store is still lower at 12:05, compare a fresh pair after the normal window. The 15 minutes belong to this example. Your own observations and the order risk should determine what you do.

Start the clock from a defined event. For a warehouse receipt, that could be when the units become eligible for sale. For a sweep you run on a schedule, you might only know when you first observed the gap. In that case, record the first observation as your starting point so the recheck can be reproduced.

Treat the second read as a decision point

If the numbers now agree and the timing fits the update you were waiting for, record the original gap as likely lag. If they still disagree on the same comparable SKU and stock pool, investigate. Check whether fresh events occurred between reads. A new order can create a new gap while the original gap is already closed. Look for the event you expected to be reflected and check whether it reached the destination. If the connector shows which run processed the change, include that detail in the handoff.

An unresolved gap is a reason to investigate, and either reading may still be wrong. Review the main causes of inventory drift before making an adjustment. If the systems agree and a customer order still can’t be picked, ask the warehouse for a count. Two matching records can repeat the same mistake.

Escalate sooner when shoppers can buy the extra units

A wait for diagnosis doesn’t have to be a wait for action. If an item with little stock is selling fast and the store is showing more units than the warehouse can ship, tell the person who can review the listing now. Give them the quantities, timestamps and any open orders you can confirm. Let your team choose whether to pause the listing or change the promise while the issue is checked. A discrepancy that hides stock from sale can also matter, especially during a launch.

Keep a short record of the wait used and the result of each follow-up. Revisit the window when you change the connector, add locations or find that routine updates repeatedly exceed it. For a planned second read and alert when the difference persists, you can register interest in the pilot.