Outbound Events
Outbound Events (Email Templates for Outbound Shipments)
Outbound email templates relate to the shipping process from the merchant to the consumer.
They inform the consumer (or internal recipients, depending on template context) about the progress, delays, or exceptions during the outbound shipment. Outbound events are triggered exclusively by carrier updates or by the initial provision of shipment data.
Below is the structured documentation for all outbound events. Please note some E-Mail Tempaltes will be send to the customer (marked as Context = Consumer) and some can be send to internal team(s) (marked as Context = internal).
Sales Order Parcel Prepared for Shipping
Alternative label: Shipment prepared for transport
Trigger
Triggered when the tracking number for a parcel is provided to returns.cloud.
Purpose
Signals that the parcel is registered for shipment and is about to be handed over to the carrier.
Sales Order Parcel Shipped
Alternative label: Shipment in transit
Trigger
Triggered when the carrier confirms pickup or handover of the parcel.
This marks the injection of the parcel into the carrier’s logistics network.
Purpose
Informs the consumer that the shipment is officially on its way.
Sales Order Parcel Delayed
Alternative label: Shipment delayed
Trigger
Triggered when the system receives a carrier event indicating that the parcel is delayed.
Additional Information
Delay reason is only available if the carrier provides it.
Not all carriers supply detailed explanations.
Example Reasons
Parcel is designated for repacking.
Parcel is designated for customs control.
Purpose
Notifies the consumer that the shipment may arrive later than expected.
Sales Order Parcel Ready for Pick Up
Alternative label: Shipment ready for pick up
Trigger
Triggered when the carrier reports that the parcel is ready for pickup at a PUDO location or carrier store.
Important Note
This event is not a proof of delivery.
It only signals availability for pickup.
Sales Order Parcel in Delivery
Alternative label: Shipment in delivery
Trigger
Triggered when the carrier marks the parcel as out for delivery.
Clarifications
Events such as “planned for delivery at 1pm” do not trigger this.
The next event is not guaranteed to be "delivered".
The shipment may later transition to delayed or exception.
Purpose
Provides transparency that the shipment is on the final stretch before delivery.
Sales Order Parcel Delivered
Alternative label: Shipment delivered
Trigger
Triggered when the carrier reports that the parcel has been delivered or picked up from a PUDO point.
Important Notes
This is a proof of delivery.
The timestamp marks the moment when the consumer’s withdrawal period begins.
This differs from certain carrier “delivered” events where parcels are left in places that do not qualify as a true proof of delivery.
Purpose
Confirms final successful delivery to the consumer.
Sales Order Parcel Delivered to Third Party
Alternative label: Shipment delivered to third party
Trigger
Triggered when the carrier reports delivery not to the consignee but to a third party or alternative location.
Examples
Delivered to neighbor
Delivered to a storage shed
Delivered to reception desk
Purpose
Informs the consumer of the exceptional delivery location.
Sales Order Parcel Exception
Trigger
Triggered when the system receives any negative carrier event while the parcel is in the carrier’s responsibility.
Examples
Parcel is lost or damaged
Parcel is blocked by customs
Parcel could not be delivered after multiple attempts
Additional Information
The reason is only available if the carrier provides it.
Purpose
Alerts the consumer (or internal team) that a problem occurred during shipment and further action may be needed.