Check Shopify inventory at the variant, location and quantity-state level, then inspect the variant’s out-of-stock selling policy. A physical stock total cannot by itself establish what customers can buy. Use a controlled order and hold exercise to see how available, committed and unavailable quantities change before relying on a stock report or integration.
The useful outcome is an explanation that both the stock team and the store administrator can repeat. They should be able to identify the item, name the location, explain the quantity state and show the selling-policy decision. Shopify’s developer documentation supplies the model for those checks; the worksheet below turns it into a practical acceptance exercise.
Why should the check start with a location?
A Shopify inventory level connects one inventory item to one location. The InventoryLevel reference describes quantities by named state at that location. Keep the inventory item and location identifiers alongside the familiar product name in a technical handover. This helps an implementer show exactly which record a report is reading.
For a business with a stockroom and a shop, request separate rows even if the current report shows a combined total. Ask the demonstrator to explain the source of each figure. A movement or adjustment at one location should be investigated using that location’s record, rather than hidden inside a plausible business-wide total.
Use a single product variant first. If the product has several sizes or other options, choose one and record it explicitly. Expanding the exercise to every variant before establishing the record relationships makes it harder to tell whether a discrepancy concerns the physical count, the selected item or the location mapping.
Which quantities mean physically present and sellable?
Shopify describes on-hand quantity as the sum of available, committed, reserved, damaged, safety-stock and quality-control quantities. Incoming Shopify inventory is not available to sell until it is received and changed to available. These definitions in the inventory-management guide explain why “we have stock” needs a more precise meaning.
Write both the physical-count question and the selling question on the test sheet. A unit held for inspection may be physically present while being intentionally excluded from sale. A delivery expected tomorrow is a different state again. Ask the team to name the state it intends for each case before comparing the software output.
Shopify describes the reserved state as on-hand units temporarily set aside. Inventory reserved on a Shopify draft order is represented as committed. Those statements use similar everyday language but refer to different documented cases. Give the demonstration a specific event, such as an inspection hold or a draft-order reservation, so “reserve it” cannot conceal the distinction.
| Business question | State or setting to inspect | Interpretation to confirm |
|---|---|---|
| What is physically at this location? | On-hand and its component states | Which units the physical count includes |
| What can be sold from the recorded stock? | Available | Which held or committed units are excluded |
| What is still arriving? | Incoming | Receipt and state change before availability |
| What belongs to an unfulfilled order? | Committed | Order reference responsible for the commitment |
| What has been set aside? | Reserved or another relevant unavailable state | Specific reason and release responsibility |
| Can an out-of-stock variant still be purchased? | Inventory policy | Intentional selling rule for that variant |
For the broader business vocabulary, see inventory control. Establish the meaning of each report column before using it to make a replenishment or customer-service decision.
What changes when an order is placed?
For an order, Shopify reduces available quantity and increases committed quantity. Shopify reduces committed quantity after the order is fulfilled. The documented lifecycle makes an order reference a useful companion to a quantity snapshot: it explains why the state changed.
Ask for a before-and-after view in a suitable test setup. Record the selected variant and location, then follow the specific test order. Have the demonstrator explain the actual result against the documented lifecycle. If order assignment or fulfilment involves additional configuration, retain that configuration with the test instead of assuming the sum across locations explains the order’s treatment.
The Shopify Admin API cannot adjust or move inventory quantities in the committed state. An integration proposal should respect that boundary. If a planned correction involves an order commitment, ask which supported order action is responsible for it. Do not treat a generic quantity-adjustment call as a substitute for explaining the order state.
Keep the acceptance test away from live customer orders. Name the person responsible for preparing the test data and cleaning up the exercise through supported processes. A demonstration should leave a clear record of what happened, including any unresolved assignment or fulfilment question.
Does an out-of-stock total necessarily stop purchases?
The CONTINUE inventory policy allows purchase of an out-of-stock variant. The DENY inventory policy prevents purchase of an out-of-stock variant. Shopify defines these values in its inventory-policy reference. Inspect the chosen variant’s policy as a separate acceptance item; the quantity report alone does not describe that decision.
Agree the intended commercial behaviour before configuring the test. If continued selling is intended, ask how the business will communicate and manage that choice. If it is not intended, request evidence for the selected policy and a controlled out-of-stock purchase attempt. Record the actual observed result rather than describing the policy as a guarantee against every possible discrepancy.
Store availability and regional business constraints remain separate questions. Use Shopify in Zambia for that wider selection discussion. This article’s test concerns the documented inventory model and the behaviour of a proposed configuration.
Original two-location state ledger
Consider a hypothetical variant with eight units at the shop and five at the stockroom, initially all available in the exercise. A test order needs three shop units, and two other shop units are to be held for inspection. These are illustrative quantities chosen to make the state transitions easy to explain.
Draw the opening ledger. Give each location a row and show on-hand, available, committed and the relevant unavailable states. Keep incoming stock separate. Record the variant, starting time and test configuration. Ask a second person to check that the opening figures describe the same physical scenario.
Follow the order. In the exercise’s assumed shop allocation, the three-unit order should be explained through available and committed quantities. Request the actual order reference and inspect the result. Keep the stockroom row visible to confirm the demonstration is not merely substituting a combined total for a location-level explanation.
Follow the inspection hold. Ask the operator to use the supported process for the intended hold. Inspect the relevant state and the remaining available quantity. Record who can release those units and what evidence would support release. Do not label this a draft-order reservation unless that is the action actually being demonstrated.
Test the selling rule separately. Use a controlled out-of-stock case for the same variant policy. Record the selected policy, attempted action and observed outcome. Keep this evidence separate from the physical count so a correct total cannot obscure an unintended selling rule.
Inspect the integration evidence. Changes to committed, reserved, damaged, safety-stock and quality-control states do not trigger inventory webhooks. This documented limitation deserves a specific question: how does the proposed integration obtain the state information its report needs? Request a demonstrated retrieval and reconciliation approach rather than assuming every change arrives as a notification.
Shopify documents referenceDocumentUri for identifying the system and document behind an inventory adjustment. Where an integration uses the documented adjustment mutations, ask it to show the reference and the resulting evidence. Retain those details with the ledger so another person can investigate a difference.
For the wider project, visit online stores. To discuss an inventory brief, get started with the variant, location map, intended selling policy and completed ledger.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.