Inventory effects
On this page
Section titled “On this page”- What moves where, per transition
- Why “incoming” matters at the destination
- Multi-location forecasting
- See also
What moves where, per transition
Section titled “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.
Why “incoming” matters at the destination
Section titled “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
Section titled “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.
See also
Section titled “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.