Shopify Flow : New triggers for inventory transfer completed and inventory transfer ready to ship.

What changed : Shopify Flow now supports inventory transfer status triggers

Shopify Flow is Shopify’s workflow automation tool. It lives in your Shopify admin and lets you stitch together “when this happens, do that” automations without custom code.

And the “when this happens” part matters more than people think. Triggers are the moment something becomes real operationally. If your trigger is late, the team is late. If it’s vague, the workflow turns into noise.

Shopify Flow now includes two new triggers tied specifically to inventory transfers :

• Inventory transfer ready to ship
• Inventory transfer completed

If you run multiple locations, this is a big quality of life update.

Quick clarity before we go deeper. An inventory transfer in Shopify is just stock moving between your business locations. Warehouse to retail store. Store to store. 3PL to your main warehouse. Anywhere you track inventory separately and need products to physically move.

The practical problem these triggers solve is simple, and kind of annoying.

A lot of teams find out about transfer changes too late. Someone marks a transfer “ready,” but nobody in shipping sees it until they check the transfer list. Or receiving closes a transfer, and merchandising still thinks the store is out of stock for another day. Or updates sit in someone’s internal spreadsheet, not where the rest of the team actually works.

So in this post, I’m going to cover what each trigger means, where it fits in real operations, and a handful of workflows you can build right away to make transfers feel less… manual.

Shopify POS Editor: Find Every Setting (Fast)

Learn how the new Shopify POS Editor centralizes all your configurations in one single interface to eliminate menus scavenger hunts and ensure settings consistency.

EnovaiZakia

A quick refresher : inventory transfers and business locations in Shopify

Most growing Shopify businesses end up multi location, even if they didn’t plan to.

Common setups look like :

• Distribution center or warehouse → retail store
• Store → store (coverage for a stockout, seasonal demand, or an event)
• 3PL → warehouse (or 3PL → store, depending on how you operate)
• Warehouse → pop-up location (temporary but still needs tracking)

The transfer lifecycle at a high level usually follows something like :

1. Created
2. Ready to ship
3. In transit (some teams use this step, some don’t, depends on process)
4. Received / Completed

Where the handoffs happen is the real story :

• Picking and packing happens at the origin location
• Carrier pickup or dispatch happens when it actually leaves
• Receiving happens at the destination
• Then shelf stocking (or putaway) and sometimes a quick cycle count for sanity

Transfer status visibility matters because it affects everything downstream.

Inventory accuracy, obviously. But also customer promises. If your online storefront is using location based inventory and you’re planning to replenish a store, your timing affects what customers can buy and when staff can confidently say “it’ll be here tomorrow.”

It also affects replenishment planning. If transfers get stuck in limbo, you reorder too early or too late. Both hurt.

Trigger 1 : “Inventory transfer ready to ship” (what it means and when it fires)

In plain language, ready to ship means the sending location has prepared the transfer and queued it for shipment. The products are supposed to be picked and packed, or at least committed to that next step. It’s the moment where the transfer stops being “a plan” and becomes “something we need to move.”

This trigger fires when the transfer is marked ready to ship.

Operationally, this is the perfect moment to start outbound logistics workflows, like :

• Create or print a shipping label
• Schedule carrier pickup
• Assign a picker and packer
• Notify the destination location that something is coming (especially if they need to make room, plan labor, or expect high value items)

Data you will likely want to include in actions

When you build a notification or a task, the details matter. Usually you want :

• Transfer ID or reference
• Origin location
• Destination location
• Line items (SKUs, product titles, quantities)
• Notes (especially if your team uses notes for priority, carrier instructions, or receiving hours)

Even better if you include a direct admin link to the transfer record so nobody has to hunt.

Common pitfalls to avoid

A few ways “ready to ship” automations can get messy :

• Notifying too early or too late : if your team marks ready to ship before it’s actually packed, then the trigger is technically correct but operationally misleading. That is a process issue, but the automation will expose it fast.
• Sending to the wrong team : shipping alerts belong with shipping. receiving heads ups belong with receiving. sounds obvious, but it’s the most common mistake.
• Not including destination details : if the message doesn’t say where it’s going, people ask. then you’ve basically automated nothing.

If you think of it as “start workflows on inventory status change for outbound logistics,” you’ll design it the right way.

Trigger 2 : “Inventory transfer completed” (what it means and when it fires)

Completed means the transfer is fully received and closed and inventory is updated at the destination location.

Shopify notes something important here : completed can reflect the transfer being fully received in a way that’s accepted or rejected. So completion is not always “everything perfect,” it’s “the receiving step is finalized.”

This trigger fires when the transfer is marked completed.

Operationally, this is the moment to :

• Confirm stock arrival
• Update internal records and dashboards
• Reconcile discrepancies
• Kick off shelf stocking and putaway
• Update merchandising assumptions (availability, allocations, replenishment timing)

Data to include in downstream notifications

For completion, the receiving context is everything. Helpful fields typically include :

• Destination location
• What was received (quantities by SKU)
• What was expected (so variances can be spotted)
• Notes or exceptions (damages, missing cartons, partial receipts, rejection reasons)

Why it’s ideal : it reduces manual follow-ups. Nobody has to ask “did that transfer arrive ?” and then wait for someone to check. The workflow just tells you, and then starts the next step.

Shopify Balance Domestic Wire Transfers (No Guesswork)

Discover what domestic wire transfers mean within Shopify Balance, how they work for US merchants, and how they differ from ACH and card payments.

EnovaiZakia

Where these triggers fit best : practical use cases by team

These two triggers hit different teams at different moments, which is exactly what makes them useful.

Warehouse and shipping team

• Notify the shipping lead when a transfer is ready to ship
• Create a packing checklist
• Assign a picker/packer
• Start a carrier pickup task

Receiving team at the destination

• Auto alert when a transfer is completed so they can start shelf stocking
• Trigger a quick cycle count task for certain product types
• Notify store staff for high priority items (new launches, backordered products)

Ops and finance

• Kick off reconciliation tasks after completion
• Track variances and shrink patterns by lane (warehouse to store vs store to store)
• Maintain an audit trail without chasing people on Slack

Customer support and merchandising

• Update availability assumptions once stock is completed at the store
• Reduce “it should be there” responses that are really just guesses

Management

• Lightweight alerts for high value transfers
• Or feed an internal dashboard so leadership can see transfer health without reading message threads all day

Workflow examples you can build in Shopify Flow (step-by-step outline)

Below are a few patterns that are easy to implement and usually immediately useful. I’m using Slack/Teams and common task tools as examples, but the structure stays the same.

Example A (Ready to ship) : Slack or Teams message to shipping channel

Trigger : Inventory transfer ready to ship

Conditions (optional) :

• Origin location is “Main Warehouse”
• Destination location is in a set of retail stores
• Quantity over X, or includes “priority” SKUs

Actions :

• Send message to Slack/Teams channel #shipping or #warehouse-ops

Message template fields to include :

• Transfer reference/ID
• Origin → destination
• Item summary (top SKUs, total units)
• Notes
• Admin link to the transfer

What this replaces : the “hey is this ready yet ?” loop.

Example B (Ready to ship) : Create an internal task for carrier pickup

Trigger : Inventory transfer ready to ship

Conditions (optional) :

• Destination location is "Store 12" (pilot lane)
• Transfer has a tag like "LTL" or "Carrier Required"

Actions :

• Create task in Asana/Trello/ClickUp : "Schedule pickup for transfer {ID}"
• Assign to shipping coordinator
• Set due date to same day, or next business morning depending on cutoffs

Task fields to include :

• Transfer ID and link
• Destination address or contact (if your process stores this in notes or a shared doc)
• Preferred carrier or service level
• Any delivery window notes

Example D (Completed) : Update a logistics dashboard or Google Sheet

Yes, I'm skipping C because in real life your workflows won't be perfectly numbered either.

Trigger : Inventory transfer completed

Conditions (optional) :

• Only for transfers to retail locations
• Only for transfers created in the last X days (if you want to avoid legacy noise)

Actions : Add or update a row in Google Sheets (or whatever dashboard you use) with the following fields :

• Transfer ID
• Origin
• Destination
• Completed timestamp
• Status : Completed

This is boring, and that's why it's powerful. It creates a passive record you can sort and report on.

Example E (Completed) : Create a reconciliation task if received differs from expected

Trigger : Inventory transfer completed

Conditions :

• Received quantity does not equal expected quantity
• Transfer includes certain SKUs that must be exact (high value, regulated, serialized, or whatever matters to you)

Actions :

• Create task : "Reconcile transfer discrepancy {ID}"
• Assign to ops lead or inventory control
• Include variance details and request photos or notes if your SOP requires it

Task fields to include :

• Destination location
• Expected vs. received summary
• Notes and exceptions
• Admin link

This workflow is the difference between "we'll look at it later" and "we actually catch issues while they're still fresh."

Suggested conditions and filters to keep your automations clean

If you turn on triggers and notify everyone about everything, people will mute it. Fast.

A few clean filters that usually help :

• Filter by origin/destination location — for example, only automate warehouse → stores, not store → store.
• Filter by SKU, vendor, or product type — for example, only alert on "Launch" items or key vendors.
• Threshold rules — only notify if total units exceed 50, or total value exceeds $2,000 if you track value elsewhere and can reference it.
• Time-based follow-ups — if a transfer is ready to ship but not completed after a set number of days, ping ops. This is optional but acts as a useful "nothing fell through the cracks" safety net.
• Message hygiene — avoid duplicate alerts by watching for overlapping workflows, and always include a direct link to the transfer record in admin.

Shopify Analytics Insights: What They Mean + What to Do

You know that moment when you open analytics and it’s… a lot. Charts, tables, date ranges, filters. Useful, sure. But it still leaves you doing the real work in your head. What changed ? Where ? Is it good or bad ? And what do I do with it ?

EnovaiZakia

Benefits you should expect (and how to measure impact)

The nice thing about transfer automation is it's measurable. You can feel it immediately, but you can also prove it.

Expected benefits :

• Faster handoffs between shipping and receiving
• Fewer missed stock arrivals and less "who owns this next ?" confusion
• Better inventory accuracy because reconciliation happens on time, not weeks later
• More reliable internal records through automatic dashboard updates

Metrics worth tracking :

• Time from ready to ship → shipped (or dispatched, depending on your process)
• Time from shipped → completed
• Number of discrepancies caught and time to resolution
• Reduction in manual messages or check-ins about transfer status

Even one month of data is enough to see if you're improving.

Implementation notes : where to find the triggers and get official help

In Shopify Flow, you’ll find these triggers in the trigger selection list when building a new workflow. Look for inventory transfer related events, then pick :

• Inventory transfer ready to ship
• Inventory transfer completed

For the official reference, Shopify points to the Flow documentation for trigger and action details, plus the event fields you can pull into messages, tasks, and updates.

If you run into edge cases, the Shopify Flow community is genuinely useful. It’s where you’ll see real templates, weird behavior reports, and how other merchants handle things like partial receipts or location specific rules.

One strong recommendation : validate these triggers in a test workflow first. Run a couple of transfers end to end and confirm the timing matches how your team actually works.

A simple rollout approach is to start with one lane, like warehouse → one store, then expand once the signal to noise ratio is right.

A simple rollout blueprint (so you don’t over-automate on day one)

Over-automation is real. You want momentum, not a notification flood.

Phase 1 : Ready-to-ship notifications + basic dashboard update

• Workflow 1 : ready to ship → message shipping channel
• Workflow 2 : ready to ship → log to sheet/dashboard

Keep it simple. The goal is visibility.

Phase 2 : Completed notifications to receiving + shelf-stocking checklist task

• completed → message destination receiving channel or store manager
• completed → create task “Putaway and shelf stocking for transfer {ID}”

Now you’re tightening the loop at the destination.

Phase 3 : Reconciliation automation for discrepancies + exceptions routing

• completed + variance detected → create reconciliation task
• optionally route to a specific owner based on location or product type

This is where you start saving real money, not just time.

Governance basics (don’t skip this)

• Define an owner for each workflow
• Maintain a tiny change log (even a Google Doc is fine)
• Review notifications monthly. prune what people ignore.

Conclusion

These two new Shopify Flow triggers are simple on paper, but they hit a very real operations gap.

• Inventory transfer ready to ship helps you start the outbound work right when the transfer becomes actionable.
• Inventory transfer completed helps you finish the loop at receiving, update records automatically, and catch discrepancies before they turn into mystery shrink.

If you do multi-location inventory at any real volume, this is one of those changes that makes Shopify feel more like an ops system, not just an ecommerce admin.

Start with one lane, one or two workflows, and make the messages actually useful. Then expand.

FAQs (Frequently Asked Questions)