Inventory effects

On this page

• What moves where, per transition
• Why “incoming” matters at the destination
• Multi-location forecasting
• Checking historical transfer sync
• See also

What moves where, per transition

Transition	Origin	Destination	Shopify push
Draft → Sent	available decreases by planned quantity	incoming increases by planned quantity	yes
Sent → Partially Received	unchanged	incoming → available (per received line)	yes
Partially Received → Received	unchanged	remaining incoming → available	yes
Sent or Partially Received → Cancelled	sent quantity added back to available	remaining incoming zeroed; already-received quantity removed from available	yes
Received or Partially Received → Sent or Draft (revert)	sent quantity added back to available	already-received quantity removed from available, received counts reset to 0	yes
Draft → Cancelled	no effect	no effect	no
→ On Hold / Resumed	no effect	no effect	no
Received / Partially Received → Completed	no inventory change: unlocks reconciliation tools	no inventory change	no

Notes:

• At Send time, the planned quantity is what moves; there’s no separate “shipped quantity” you enter at dispatch.
• Cancelling or reverting only undoes what the system itself pushed to Shopify. Leaving Received or Partially Received pulls the already-received quantities back out of the destination’s available stock and resets each line’s received count to 0, so the lines can be received again.
• Logistified writes Shopify’s available quantity. Shopify’s on-hand figure follows automatically, because on-hand is derived from available plus committed and the other tracked states.
• Editing the shipping date or carrier doesn’t push to Shopify; those are app-only details.
• This table is for TOs with a destination location. A TO shipped to a supplier (Elevate) still decrements origin available at Send, but nothing happens on the destination side in Shopify at any transition; there’s no Shopify incoming push and no destination available change, because the destination isn’t a Shopify location at all.

Note

3PL-managed available stock. If your fulfillment partner owns Shopify available inventory at the origin and/or destination, turn off the matching Update source / destination location available in Shopify switch in TO settings → Preferences. The available changes in the table above on a turned-off side (origin decrement on Send with the source switch off; destination move-in on Receive with the destination switch off) are left to your 3PL; Logistified still pushes the incoming changes and keeps its own tracking in sync on both sides. Typical setup: source switch on, destination switch off; you send from your own warehouse, the 3PL’s system books the arrival.

Turning off incoming updates. The same card has a third switch, Sync incoming to Shopify (on by default). Turned off, transfer orders skip every incoming change in the table above: sending no longer raises incoming at the destination, and receiving adds the received units directly to destination available (when that side’s switch is on) instead of moving them out of incoming. With both destination-facing switches off, transfer orders leave Shopify untouched at the destination entirely. Logistified’s own in-transit tracking and forecasts keep working either way.

Why “incoming” matters at the destination

Even before the goods arrive, Logistified marks them as incomingIncoming quantityUnits expected to arrive from open purchase orders and in-transit transfer orders. Shopify maintains its own incoming counter; Logistified updates it from PO/TO workflow, and Incoming Reconciliation may require a manual apply if the two drift. Read more → at the destination. This lets the forecast at the destination see the upcoming stock, so reorder suggestions there don’t ask for more than you need.

Multi-location forecasting

When you have a TO in Sent state:

• The destination’s “Days of stock with all incoming” reflects the in-transit units.
• The origin’s stock dropped at Send time, so it shows accurate available stock.

Note

TOs and POs both contribute to a location’s “incoming” total. The forecast adds them up so reorder suggestions take both into account.

Checking historical transfer sync

An assistant with read access can inspect Logistified’s recorded transfer sync state, including historical lines whose product variant is now missing or deleted. This inspection makes no inventory changes and does not recreate products.

A Completed transfer can still have unresolved sync work. An in-flight amount means Logistified recorded a claim awaiting confirmation; it does not confirm what happened in Shopify or Assemblified. A hold marker applies to the line; it does not identify which movement or acknowledgement is held, and other outstanding changes can coexist with it. Even zero outstanding totals do not prove that both systems or physical stock agree.

Before deciding on a correction, compare the transfer’s history with Assemblified’s delivery and application records, Shopify’s inventory history at both locations, and any physical movement or count evidence. Keep the historical product identifiers when asking support to investigate. The inspection does not authorize a retry, acknowledgement release, reversal, or reopening of a Completed transfer; historical repair needs a separate decision after that evidence is reviewed.

See also

• Inventory → Incoming reconciliation: fixing drift between Logistified and Shopify.
• Forecast → Locations & multi-location math: how the destination’s forecast sees TOs.
• Ship to a supplier: what changes on the destination side when a TO ships to a supplier instead of a location.

Last updated: 30 October 2026