Why do two inventory screens disagree about available stock?
Format: Article.
Two stock screens can disagree because they answer different questions. One may show all units at a site. Another may show only units still for sale. Before changing a count, match the item, site, unit, state, and time. If you skip that check, you could turn a harmless gap between screens into a real stock error.
Start with the terms below. They follow Shopify's stock states, not rules for every warehouse tool. In Shopify, on-hand stock is the sum of committed, unavailable, and available units. Incoming stock is separate. [S02] An ERP, the system that holds business records such as orders and stock, may use other names or rules.
A stock-state dictionary
| Term | Question it answers | What it must not imply |
|---|---|---|
| On hand | How many units are recorded at this location? | All units can be promised to a new customer |
| Available | How many units are available to sell under this system's rules? | Every physical unit is included |
| Committed | How many units are already set aside under the documented commitment rules? | Those units have left the building |
| Unavailable | How many units are held from sale, such as quality holds or damaged stock? | The units are missing |
| Incoming | How many units are on their way to this location? | Staff have received and released them |
Do not treat another tool's “reserved” field as Shopify's “committed” field just because they sound alike. Ask what sets stock aside and what frees it. Does the rule cover orders, drafts, transfers, or internal holds? Write down the answer for each tool before you link the fields.
Hypothetical example: the counts both make sense
A fictional merchant checks one variant at its east warehouse. The warehouse screen shows 48 units on hand. The store screen shows 31 available. The review finds 12 committed units and five units on a quality hold. Another 20 units are incoming from a supplier.
Under the stated example definitions, 31 available plus 12 committed plus five unavailable equals 48 on hand. The incoming 20 are not part of that total. Neither screen needs a correction merely because 48 and 31 differ.
A salesperson asks if the team can promise 40 units. The on-hand total does not answer that. Check how many are still free to sell and when the customer needs them. Do not lift the quality hold or take another order's stock just to make the screen show enough.
Investigate in this order
- Identity: Match the SKU, or item code, plus size, color, and batch where needed. A total for all colors cannot tell you how many blue units remain.
- Location: Does each screen show one warehouse or several? Can each site ship new orders?
- Unit: Compare single units with single units. If one screen uses cases, show the approved units per case beside that count.
- Meaning: Save the exact column label. Write what it means in this tool. Does it count stock on hold or set aside for orders?
- Time: Note when you read each source and when it last changed. A morning file and a current screen may not show stock at the same point in time.
- Movement: Check what came in, left, moved, or went on hold since the earlier count. Check manual stock edits too.
- Physical evidence: If the gap is still unclear, ask for a count under the warehouse's rules.
These checks help show why the counts differ. It may be the field meaning, the read time, or the stock itself. None of these checks grants permission to edit stock. Send any proposed change to the person who can approve it.
Keep a discrepancy note that another shift can use
Copy this record into the review queue:
Item and variant / location / selling unit / source A value, state, time / source B value, state, time / mapping rule / movements checked / unresolved difference / reviewer / next check.
Keep both first readings. If one was stale, say which one and how you know. Add the new reading beside it. Do not replace the old value in the note. Staff need it to see why the screens did not match.
Treat an unknown quantity as unknown, not zero. Treat an unavailable feed as unavailable, not “out of stock.” Both distinctions matter when support is drafting a customer message from the review.
Define the useful software output
The useful result shows what each count means and what still needs a check. It is not one “true stock” number made by averaging screens. A proposed view could keep the states apart and flag old reads or counts from different sites. Staff can then see why the figures may not match.
Core Agentic builds custom AI software to fit current tools. A stock view needs approved access and a clear match between each tool's fields. Test it with your real rules for stock holds. Your staff still decide what can be sold and what to promise a customer. This is not a live stock service or a forecast.
Bring a pair of conflicting stock views, with private details removed, to discuss the right comparison. Book a Demo.
Sources
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.