Stock transfers with Shopify Flow: notifications and control

Shopify Flow can start automations when an inventory transfer is ready to ship or its receipt is completed. These events help coordinate locations and systems. A trigger does not mean you should add stock again: transfer and receipt are already part of the inventory process.

Before creating the flow, decide who maintains the operation. If Shopify records the transfer and an ERP also updates quantities, a poorly designed automation can duplicate movements even when each system works separately.

What each event means

The official Flow update describes both events. “Ready to ship” does not prove a carrier has collected the goods. “Completed” does not imply every unit was accepted and ready to sell: rejection may be included.

Design a simple first flow

1. Choose a transfer between two test locations.
2. Select the event matching the moment you need to coordinate.
3. Add filters for origin, destination or available data where relevant.
4. Prepare an internal notification identifying the transfer and pending task.
5. Test accepted quantities, partial receipt and rejection.
6. Confirm the automation does not create a second stock update.

A useful notice includes the reference, origin, destination and next action. It need not repeat the whole product page. If the destination must review a rejection, staff should be able to open the correct operation and identify its owner.

Partial receipts and exceptions

A completed-transfer flow should not replace tracking individual partial receipts. Check which event and data Shopify offers for the specific case you need to control. The trigger reference identifies available objects and actions.

Define what happens when fewer goods arrive, products are damaged or a unit is rejected. Automation can create a task or communicate the incident; accepting, returning or replacing must follow the business procedure.

If connecting an ERP or logistics tool

• Retain a shared identifier linking the transfer in both systems.
• Define which creates and which updates the operation.
• Avoid processing the same event twice.
• Log errors and retries, with someone responsible for review.
• Do not translate receipt status directly into availability without reviewing its rules.

Flow is available on Basic, Grow, Advanced and Plus. Some actions have their own requirements; HTTP requests, for example, are supported from Grow. Check connectors and permissions before deciding how to send information externally.

How to test without changing a real transfer

Use Flow testing tools to review logic and data, followed by a controlled operation when you need to verify an external result. A test that does not execute modifying actions cannot prove the ERP received an update.

Include two often-forgotten cases: repeated events and a temporarily unavailable destination system. The flow should show what was processed and what needs recovery rather than failing silently.

What to measure in operation

Observe pending incidents, time until staff learn of an exception and necessary manual corrections. No saving percentage or “real-time” latency is guaranteed for every store.

If automation helps staff see the next task and keeps inventory consistent, it is serving its purpose. Add complexity only after demonstrating the first rule works and someone can maintain it.

Continue working on your store

Define and generate automations with Sidekick · Test flows before activating them · Review inventory adjustment history.

If you need to turn these options into a work plan, our Shopify consulting reviews your operations and dependencies before recommending an implementation. Tell us what your store needs.

Sources and review

• New Flow transfer triggers.
• Inventory transfer completed.
• Shopify Flow.

Editorial review: the Migraciones.io team · 30 October 2026. Features, plans and availability are checked against the linked sources.