Multichannel inventory needs a clear mapping between the item you hold, the listings that offer it and the orders that reserve or consume it. Start by naming the quantity states each channel uses. Then assess how a representative order and an exception travel between the records, including the point where someone must investigate a difference.
Which item does each listing represent?
Create an item-to-listing map before discussing synchronisation. Give the internal item a stable reference, then list each channel’s product and variation references beside it. Ask the team to identify which differences are merely presentation and which describe a genuinely different stock item.
WooCommerce describes a simple product as one item without variations. WooCommerce allows each variation to have its own SKU and stock level. The WooCommerce product guide makes product type and variation identity useful questions for that mapping exercise.
For a hypothetical training catalogue, use a mug offered in two colours across two channels. Give each colour a synthetic item reference. The proposed exercise is to follow an order for one colour without changing the other colour’s quantity. Record the actual behaviour when the configured integration is assessed.
WooCommerce grouped products allow each constituent item to be added to the cart individually. If a channel groups items on one page, ask the implementer how each constituent maps to the internal item. A shared display should not silently become an assumption that several items share the same quantity record.
What do the quantity states mean?
Shopify defines on-hand quantity as the sum of committed, unavailable and available inventory at a location. Shopify excludes incoming inventory from its available quantity. The Shopify inventory-state guide supplies explicit definitions for interpreting that platform’s quantities.
Shopify’s committed inventory includes units reserved in a draft order. Shopify’s unavailable inventory can include units held for damage, quality control or safety stock. Use the documented meanings to write a channel-state dictionary. Keep the source platform named in each entry and ask the implementer to explain how its states map to the internal system.
For the training mug, prepare examples of a unit ready to sell, a unit already committed and a unit held for a named reason. Ask the assessor to locate each quantity in the configured records. Record the source of the quantity and the event that last changed it.
Do not compare two headline totals until their scope is clear. A location-specific available quantity and a combined physical quantity answer different questions. The reconciliation worksheet should include item, location, state and observation time so a difference can be investigated meaningfully.
Which system owns each change?
Shopify requires inventory information and active tracking to determine its inventory states. Before assessing any synchronisation, ask which system is responsible for item identity, physical count corrections, reservations and order fulfilment. Keep those decisions separate; the same application need not own every part of the process.
Draw the intended path of one training order. Identify its channel reference, the internal order reference, the item quantity affected and the component expected to transfer the event. Ask how the receiving side identifies a repeated message and how staff can find an event that has not been accepted.
Use a deliberately delayed update in the proposed exercise. Record what each side shows before and after the delay, and who is expected to investigate it. This produces a bounded observation of the chosen implementation instead of an unsupported promise of instant synchronisation.
Agree how a manual correction enters the process. The operator should be able to explain why it was made and which record was treated as authoritative. A correction without that basis can leave the next person unable to distinguish a deliberate adjustment from an integration fault.
How should cancellations and listing changes be assessed?
Include a cancelled training order and ask which quantity state changes in each system. Check the actual event sequence and references. Record an unresolved reservation as an exception with an owner rather than silently editing the headline quantity until the screens agree.
WooCommerce provides bulk editing for changes to multiple products. If staff use bulk editing, identify which fields they are authorised to change and whether the connector is expected to act on them. Inspect the actual integration behaviour separately from the documented product editor.
WooCommerce provides built-in options to duplicate or delete products. Include a copied training listing in the identity review. Ask the operator to demonstrate whether it should map to an existing internal item or a new one, and retain the resulting mapping decision. A convenient duplicate action should not decide the stock relationship on its own.
Prepare a retirement procedure for a listing that should no longer accept orders. Specify the intended action on the channel and the handling of work already accepted. Ask the assessor to inspect that boundary using a training listing before it becomes an operational requirement.
What belongs in a multichannel reconciliation worksheet?
Use this original item-state-event matrix to assess the relationship between records. It is a proposed review tool; the selected connector still needs to demonstrate which evidence it actually exposes.
| Boundary | Record to keep | Question to resolve |
|---|---|---|
| Item identity | Internal item and channel variation references | Do the listings represent the same stock item? |
| Quantity meaning | Location, state and observation time | Are the compared quantities equivalent? |
| Order acceptance | Channel and internal order references | Has the intended order been recorded once? |
| Reservation | Event reference and resulting state | Which units are committed to this work? |
| Delayed update | Observed positions on both sides | Who investigates the incomplete handoff? |
| Cancellation | Order event and quantity change | Has the intended reservation been released? |
| Listing change | Authorised edit and mapping decision | Does the stock relationship remain correct? |
Ask another authorised colleague to investigate a deliberately chosen discrepancy using only the worksheet and the available system evidence. Record where they need additional information. Those gaps identify practical requirements for the integration or operating procedure.
For a disputed mapping, attach the two listing references and ask the catalogue owner to decide whether they represent interchangeable units. Keep that identity decision separate from the technical choice of which message or field the connector will use.
Keep reconciliation observations in sequence rather than overwriting the earlier position. A later matching total can close a question only when the team understands the events that produced it. The assessment should leave a clear owner for each unresolved item and an agreed point for checking it again.
For the storefront context, see online stores. For connector requirements, see web development or send Spout a representative item and order path.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.