Expected supplier stock is appearing as received stock

Expected, incoming, and received are different facts

An accepted supplier confirmation records what the supplier has agreed to supply, in what quantity, and on what date. Dispatch evidence — a supplier ship notice or a transfer leaving the origin — records that goods were sent. A receiving event records that goods arrived and were counted. An acceptance records that someone authorized those units into sellable inventory. These are separate records made by different parties at different steps, and any of them can disagree in quantity, which is why systems model them separately. Shopify's inventory transfer workflow distinguishes drafting a transfer, committing stock at the origin, showing it as incoming at the destination, and receiving it; received inventory is what becomes available at the destination. Each platform stage is itself a record to verify against evidence, not physical proof that the next step occurred.

When a report shows expected units as received, candidate causes include a process that recorded a receipt that never physically occurred, or a report summing an earlier stage — a draft, an expectation, or an incoming quantity — into a column someone reads as on-hand. Other causes are possible, and the repair is different in each case, so the first task is identifying which stage actually produced the number.

Find which stage produced the figure

Take one product where the discrepancy is visible and trace the number backward. Identify the exact report, screen, or export showing the units as received, and read its field definition or configuration rather than inferring meaning from a column heading. Then locate the underlying records: open purchase orders, transfer records with their statuses, and any receiving entries for that product.

Check the arithmetic the report performs. A view that totals purchase order quantities alongside received quantities will show supply twice: once as a plan and once as a fact. Do not count planned and received quantities as separate new supply, and do not subtract an incoming quantity from an on-hand figure that never included it. Each correction has to name the stage it is correcting.

Trace the inbound path in order

For each affected product, walk the chain. Start with the supplier's documented confirmation: the purchase order or accepted confirmation, its quantity, and its expected date. Then the dispatch evidence: a supplier ship notice or a transfer leaving the origin. Then the arrival evidence: a receiving count made at the dock or warehouse, created at the time, not reconstructed later. Then acceptance: the entry that moved counted units into inventory, by whom, and when.

A status in the chain is not physical proof of the next step. A dispatched transfer does not prove arrival, and a screen showing a received status does not by itself prove the units were counted; verify the underlying event record and the physical count where one exists. Where the chain breaks — a dispatch with no arrival, an arrival with no acceptance — the units past the break are a dependency to track, not stock to allocate.

Decide what the business can actually allocate

Only accepted, received units support allocation to orders or availability on the storefront. Expected units support a purchasing conversation and, at most, a clearly labeled incoming display — they do not support promising shipment dates or answering a capacity question. Where orders were already taken against phantom stock, list them and the shortfall they represent, and route the fulfillment decision through the merchant's normal process rather than quietly waiting for the shipment and hoping.

Ownership of the decision is split and should be named. The receiving lead verifies what physically arrived and was counted. The inventory owner authorizes what enters available stock and approves any correction to a wrongly recorded receipt. If the inflation comes from an integration writing supplier confirmations directly into inventory, the integration owner repairs the feed — after its actual behavior is confirmed, not assumed.

Hold the boundary going forward

Keep the stage separation visible in whatever the team reads daily: distinct fields or columns for expected, incoming, received, and available, with dates, so no one has to reconstruct which number means what during a busy week. Where a supplier shipment is received partially, record the received quantity against the open expectation rather than closing it, so the remainder stays visible as still owed.

If the root cause is how the storefront or its inventory integrations are configured and you want that concern scoped, a Prism consultation can discuss the setup you describe. Summarize the stages and the discrepancy without sending supplier files or internal exports through the public form, and confirm scope, responsibilities, fees, and terms before any work begins.

Receiving-stage separation worksheet

Complete one sheet per affected product. Every quantity must name its source record and date; a quantity with no event record behind it is an expectation, not stock. The allocation decision at the end applies only to accepted units.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.