Resources · 62

Inventory: verify availability, reservations and concurrency

Distinguish physical, sellable, reserved and incoming stock, then test concurrent purchases, cancellations and channel synchronisation.

· 4 min

Empty electronics and component assurance laboratory bench AI-generated editorial illustration

What this guide helps achieve

  • Define states
  • Connect units and locations
  • Exercise reservations
  • Test concurrency

Quick check

  • Is an on-hand unit always sellable?
  • Does a refund always release inventory?
  • How should the last unit be checked?

Step-by-step method

  1. 01

    Define states

    Name physical, available, committed, unavailable and incoming units. Shopify documents these distinctions; the vocabulary is a reference here, without assuming all tools implement identical transitions.

    Deliverable: state dictionary per tool.

  2. 02

    Connect units and locations

    Identify variant, location and channels allowed to sell. Choose the authoritative availability source. A shared total can hide a warehouse unable to fulfil a buyer’s order.

    Deliverable: allocation and synchronisation rules.

  3. 03

    Exercise reservations

    Define when a unit is held and how it returns to availability. Test pending payment, abandonment, refusal, cancellation and refund. Do not release a unit on an ambiguous event alone.

    Deliverable: transitions and business events.

  4. 04

    Test concurrency

    Using a fictional last unit, send two simultaneous requests and replay a notification. Check business outcome, final stock and the unsuccessful buyer’s message. Reserve and confirm under the system’s actual guarantees; an assumed lock needs testing.

    Deliverable: simultaneous and repeated-trial evidence.

  5. 05

    Reconcile differences

    Compare movements, reservations and physical counts. Identify synchronisation delays and manual adjustments. Incoming stock is not necessarily sellable; preorders need an explicit availability and delivery policy.

    Deliverable: discrepancy report and correction procedure.

Four situations for testing the method

Fictional teaching cases. Each situation connects a signal, a check and a decision bounded by evidence; none represents a client outcome.

Fictional situationConcrete checkDecision and limit
Import available stock rather than an ambiguous total — A file lists ten physical units, with four committed and one unavailable, but the store offers all ten for sale.Define each state, reconcile variant identifiers and check actual availability on a sample. In this model, ten minus four minus one leaves five.Fix definitions and mapping before another import. Successful file parsing does not establish correct displayed stock.
Reconcile inventory states during migration — A redesign preserves products and images but turns reserved units into available units.Compare variants, locations and quantities by state before and after. Replay an open order and cancellation in a controlled environment.Pause cutover for affected items until reconciled. A catalogue migration must preserve business states as well as product records.
Separate advertised and sellable marketplace inventory — Two sellers use the same product name, but their variants, lead times and available units are not interchangeable.Retain offer, seller and variant identity through ordering. Simulate delayed updates and unavailable offers.Show the conditions of the selected offer. An aggregate total should not conceal separate stock and fulfilment commitments.
Replay two sales of the last unit — A store and website both show the last unit as available and try selling it almost simultaneously.Test reservation, confirmation, expiry and cancellation with the responsible system owners. Observe the authoritative state and update timing.Define conflict handling and customer communication. A snapshot of synchronised stock does not demonstrate control of concurrent sales.

Reusable worksheet

Complete with your authorised observations. These fields are a working template, not observed results.

FieldInformation to record
Item / locationVariant, warehouse and channel
TransitionEvent and expected state
ConcurrencyRequests, reservation and unique effect
DifferenceMovement, observation and correction

Worked example

Illustrative situation

Fictional example: two channels display the last unit during a synchronisation delay.

Decision and expected evidence

The test verifies one valid allocation, an explicit message for the other order and documented inventory convergence.

Distinguish the mechanisms

MechanismPurposeCheck or limitation
Physical stockCount present unitsDo not equate it with sellable stock
ReservationAvoid double allocationDefine release and expiry
Incoming stockPrepare replenishmentDo not promise availability without an explicit rule

Management indicators

IndicatorWhat it measuresFirst action
Stock discrepanciesExpected versus observed stateConnect each correction to a movement
Stuck reservationsUnits held outside the ruleInspect cause before release
Synchronisation delayLag between source and channelName affected journeys

Common pitfalls

  • Do not equate it with sellable stock
  • Define release and expiry
  • Do not promise availability without an explicit rule

Frequently asked questions

Is an on-hand unit always sellable?

No. It may be committed, damaged or held at a location unable to fulfil the order.

Does a refund always release inventory?

No. Physical return and quality matter; separate financial decisions from inventory movements.

How should the last unit be checked?

Exercise two concurrent purchases using fictional data and inspect orders, allocation and final stock.

Official references

References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.