Back to Blogs
Shopify
Nov 14, 2026
By The Shoptimity Team
1 min read

Shopify Flow Fulfillment Event: Track Carrier Updates

Shopify Flow Fulfillment Event: Track Carrier Updates cover art

Shopify Flow Fulfillment Event workflows can react to tracking updates from third-party fulfillment services. They are not interchangeable with a workflow that starts when an order is manually fulfilled, and an event on one shipment may not describe the entire order.

Understand the feature and its limits

Shopify's Fulfillment event created trigger starts when a change occurs in an existing order's fulfillment status. The documentation identifies third-party updates such as picked up, in transit or delivered. It explicitly says manual fulfillment events do not start this trigger and recommends Order fulfilled for manual fulfillment workflows. Check your provider's actual event mapping before defining conditions. Read Shopify’s primary documentation and related Shopify guidance before changing live settings.

Set up a review-first process

Select the trigger and add a narrowly scoped condition for the event you want to monitor, using the fields available in your Flow editor. Begin with an internal notification or log rather than an automatic customer-facing message. Ask your third-party fulfillment service how to create a safe test update. Inspect the Flow run, shipment record and tracking timeline together.

Example: apply the rule carefully

An order ships in two packages. One package receives a delivered event while the other remains in transit. A message stating that the whole order has arrived would be misleading. Identify the specific fulfillment and package context available in the event and confirm your notification copy matches it. Test delayed, duplicate and out-of-order provider updates before adding any external action.

Build a shipment-aware support process

Capture the fulfillment identifier and the type of update available from the event, then give support a way to inspect the associated tracking timeline. For a multi-package order, staff should verify each fulfillment separately before making a whole-order promise. Document how the team handles conflicting scans or a package marked delivered but reported missing. Avoid sending personal addresses into shared channels when an order reference is sufficient.

Test before going live

Ask the fulfillment provider to simulate an update in a controlled store. Confirm that a third-party event reaches the intended branch and that a manual fulfillment follows a separately tested workflow. If the provider can repeat or reorder events, check that notifications remain understandable and downstream integrations can reconcile duplicates. Compare the tracking record with the Flow run before treating the test as successful.

Operational limitations

A carrier scan does not by itself resolve claims, returns or missing parcels. Give support staff a process for discrepancies and avoid exposing customer addresses in broad alerts. If your team manually marks orders fulfilled, use and test the separate Order fulfilled trigger as Shopify recommends. Recheck the workflow after changing carriers or fulfillment apps because available events and timing may differ.

Design messages for partial shipments

Customer communications should say which package or fulfillment the update concerns whenever that information is available. If the event does not provide sufficient context, route it to an internal review instead of making a broad delivery claim. Keep the carrier tracking link and provider record available to support staff. A later delivery correction may arrive after the first event, so avoid treating the first notification as a permanent final state without checking the latest tracking information.

Do manual fulfillment updates start this trigger?
Shopify says manual fulfillment events do not start it and points manual workflows to Order fulfilled instead.
Does one delivered event mean the entire order arrived?
Not necessarily. Split orders can have several fulfillments, so review the specific shipment and remaining packages.
How should I test a third-party update?
Coordinate a controlled test with the fulfillment provider and compare the Flow run with the actual tracking timeline.
Related guides

Ready to build a faster, higher-converting store?

Every Shoptimity theme ships with conversion widgets built in — so you get speed and features without stacking apps.

7-day free trial · all themes included · cancel anytime