From warehouse to store—two new triggers have been added to Flow that can automatically launch workflows for notifications, record updates, and follow-up tasks the moment an inventory transfer between locations changes status.
Whether a transfer was ready to ship or had arrived was something staff had to check on screen. Updating records and sending notices after receipt also had to be done by hand.
Flow detects "ready to ship" and "received" and launches automatically. You can build notifications, dashboard updates, and follow-up tasks with no code.
When it fires : When a transfer is prepared and marked "ready to ship."
Use cases the article mentions
When it fires : When a transfer is fully received at its destination (whether accepted or rejected).
Use cases the article mentions
* The example actions on the right list the use cases mentioned in the article. Which action components you can actually use depends on the actions Flow supports.
Notify the destination store or warehouse the moment shipment is ready, so they can prepare to receive it ahead of time.
Use "ready to ship" as a trigger to push the status to your internal logistics visibility dashboard.
Use receipt completion at the destination as a trigger to automatically update internal records and ledgers.
Automatically alert the responsible team that "stock has arrived" to shorten the lead time before they start handling it.
Use receipt completion as the cue to kick off follow-up tasks for shelf stocking.
Automatically launch follow-up reconciliation tasks, such as matching received quantities against transferred quantities.
| Item | What the article states |
|---|---|
| Feature category | New Shopify Flow trigger (tags: Feature / Apps) |
| Target object | Inventory transfer = moving inventory between your own locations |
| Trigger timing | ① Ready to ship / ② Completed (whether accepted or rejected) |
| Supported plans / countries | Not stated |
| Required apps / prerequisite features | Not stated(Presumably requires the use of Flow, but this is not explicitly stated) |
| Handling via API / Webhook | Not stated(See the documentation for details) |
These are event-driven triggers that catch the moment an inventory transfer's status changes. Setups that monitored inventory transfers via polling can potentially be replaced by these two triggers.
"Ready to ship" is the sending side, an advance-notice type; "completed" is the arrival side, a closing type. Since both the notification destination and the processing differ, design the workflows as two separate ones in principle.
The completed trigger runs whether the transfer is accepted or rejected. If you build reconciliation or record updates, always evaluate the result (accepted / rejected) with conditional branching.
The article does not document the specification of the fields the trigger passes to the workflow (source and destination locations, items, quantities, etc.). Verify which fields are available in the documentation before building conditional branching or external integrations.
Most of the example use cases in this post (updating a logistics dashboard, updating internal records, sending notifications) assume connecting from Flow to an external WMS, Slack, or an internal database. Taking inventory transfer events as the starting point, Flow can be positioned as an automation hub for internal operations. The specific action components for each integration target depend on what Flow currently supports.