| Note |
|---|
This feature is available only when the delivery promise is activated. |
...
To make sure the promise is met, several milestonesare calculated by OneStock for each order item ( order line). By default, 3 milestones are calculated:
Order confirmation date (purchase cutoff): date until when the order must be placed and confirmed to be able to deliver on time.
Orchestration date (without always at start operations): date until when the order must start being orchestrated. If preliminary operations (like payment confirmation, fraud check…) prevent starting the orchestration at this date, the order won’t be delivered on time.
Carrier pickup date: cutoff of carrier pickup depending on the configured pickup times on the stock location.
More milestones can be calculated by Onestock based on the operations configured on the delivery promise. WHERE DO WE CONFIGURE THE MILESTONES WE WANT TO GET CALCULATED?Depending on the delivery promise configuration, other milestones will be calculated an available for triggering alerts. The list of “other” milestones corresponds to all the operations configured at in different delivery method (in store preparation, reception at destination, etc.).
Every time an order is imported in OneStock with a promised delivery date on it, the its milestones will be calculated. This is a backward calculation starting from this promised date, based on the complete configurations of the delivery promise.
In case , the promised date can’t be met because the order is already late, WHAT HAPPENS?, an alert can be triggered, and the new delivery promised can be calculated and communicated to the client.
During order execution
When the order has been imported and milestones calculated for each order itemline, an alert can be automatically raised when a milestone is missed. This is configured in the order item line state diagram.
The alert can trigger many type types of actions: send a notification to an external system, send an email, push a notification to a store, flag the order with an alert, etc.
You can even have an escalation process by defining multiple alerts for a single milestone. Each alert can be raised exactly when the milestone is missed, or a delay before or after the milestone can be applied. This delay is based on a 24/7 calendar, not based on opening hours or other calendar. You can raise a first alert 1 hour before the milestone and raise an escalation alert 15 minutes after the milestone has been missed.
...
It is also possible to sort the orders so that the most urgent ones appear first.