Order Journeys
Define order lifecycles with milestones and thresholds
A order journey is a way of defining the life cycle of an order. A journey consists of a set of milestones that are key points in the order's journey, for example, when the order is placed, when the shipment is delayed or when it has gotten delivered.
Each milestone is defined by thresholds that must be met for the milestone to be considered reached. These thresholds can not only be based on events from the transporter but also events from other systems or some time constraint, and more. This approach makes the journey a very powerful and flexible tool for keeping track of what happens to the order.
Each shipment of the order will be described by its own journey, which allows you to keep track of multi-shipment orders well. A single shipment can also have multiple journeys, which allows you to define one journey that is presented for the end-customer, one for triggering notifications, and one for statistical purposes, etc.
To learn more about how to use order journey using out API, please refer to our order journey API documentation.
Milestones
A milestone represents some key point in the order journey. Some examples of milestones are:
- Order received - The warehouse received notification about the order.
- Order delayed - The transporter notified us with a delay event or more than X days passed without it being picked up.
- Delivery after promised delivery time - It has been delivered but it was after the promised delivery time.
- Shipment is going to Norway - Norway is the destination country.
It's worth noting that a milestone can belong to multiple journeys, allowing you to easily reuse the same key point to mean different things in different contexts.
Conditions and thresholds
Milestones are reached based on defined thresholds, such as transporter events, time constraints, or order and shipment properties like the destination country. To learn more about configuring events for transporters or other systems, please refer to our events documentation.
Thresholds are grouped into conditions, which determine milestone completion. A simple milestone might have one condition with one threshold, while a complex one could include multiple conditions and thresholds. For example, an "order delayed" milestone might check for a delay event and whether X days have passed without pickup.
You can specify whether all or any thresholds in a condition must be met, and whether all or any conditions must be satisfied for the milestone to be considered reached.
Triggers
When a milestone in a journey is reached, you can trigger some action. These allow you to react to what happens to your orders and can help you notify your customers or update your internal systems. To learn more about setting up triggers, please refer to our triggers documentation.
Default journey
To get started, Skrym provides a set of predefined milestones that can be used to define the journey of am order:
| Milestone | Description |
|---|---|
| Order Received | Warehouse received notification about the order. |
| Order Sent | Warehouse handed over the package to the carrier. |
| Order Delayed | The transporter notified us with a delay event. |
| Order Delivered | Package delivered to the final location. |
These milestones are assigned to you by default during onboarding and Skrym creates a default journey. This means you can start using them right away without any additional setup. You can simply track and order and assign the predefined journey to it.