2. Available Events and What Triggers Each One
Postflows supports 8 shipping events. This article describes each event, when it fires, and what carrier situations it covers.
How events are triggered
Most events fire when Postflows receives a tracking update from your carrier. The exception is Order Created, which fires directly from Shopify when a new order is placed - no carrier tracking needed.
For all carrier-based events, Postflows maps the carrier's status update to the appropriate event. Multiple carrier situations can map to the same event - for example, a package delivered via signature, left with a neighbor, or collected as a COD all trigger Shipment Delivered.
The 8 events
1. Order Created
When it fires: When a new order is placed in your Shopify store.
Use case: Send an order confirmation or "your order is being prepared" message. This is the first touchpoint in the post-purchase sequence.
Note: This event fires from Shopify directly, before any shipping label is created or carrier is involved.
2. Shipment In Transit
When it fires: When the carrier confirms the package is moving through their network toward its destination.
What it covers: All standard in-transit statuses - package accepted by carrier, moving between sorting facilities, crossing borders, progressing toward delivery.
Use case: Reassure customers their order is on its way. Reduces "where is my order?" support inquiries.
3. Out for Delivery
When it fires: When the carrier loads the package onto the final delivery vehicle, indicating delivery is expected today.
What it covers: Package on delivery vehicle, delivery expected same day.
Use case: Set expectations for the delivery window. Customers know to be available or arrange a safe drop spot.
4. Shipment Delivered
When it fires: When the carrier marks the package as delivered.
What it covers: All successful delivery outcomes, including:
Standard delivery
Delivery requiring a signature
Package left with a neighbor
Cash on delivery (COD) completion
Use case: Confirm receipt and follow up - review requests, loyalty incentives, repurchase prompts.
5. Label Created
When it fires: When a shipping label is generated for the order.
What it covers: The moment the order is packaged and ready for carrier pickup. The carrier has the label information but may not yet have physically collected the package.
Use case: Let customers know their order has been packed and is waiting for carrier pickup. Useful for stores with longer fulfillment times.
6. Shipment Exception
When it fires: When a problem occurs during shipping that prevents normal delivery.
What it covers:
Package lost or missing
Customs hold
Address issue (undeliverable, insufficient address)
Payment required (customs duties, COD issue)
Returned to sender
Delivery refused by recipient
Other carrier-reported exceptions
Use case: Proactively notify customers of delivery problems before they contact support. Provide next steps or a way to get help.
7. Delivery Attempt Failed
When it fires: When the courier attempted delivery but was unable to complete it.
What it covers:
No one available to receive the package
Access to delivery location not possible
Delivery refused
Use case: Alert customers immediately so they can arrange a redelivery, update their address, or collect from a depot before the package is returned.
8. Ready for Pickup
When it fires: When a package arrives at a pickup point, parcel locker, or post office for customer collection.
What it covers: Package available at a designated pickup location.
Use case: Notify customers their package is ready and prompt them to collect it - especially important since uncollected packages may be returned after a holding period.
Events not covered
Postflows covers the shipping milestones listed above. Events not in this list - such as carrier pre-alerts before a label is scanned, or in-store pickup from your own location - are not currently supported.