Monitoring Order execution to meet the promised date

OneStock provides a delivery promise before the customer places his order. Once it has been confirmed, OneStock will monitor the order execution to make sure that the order is delivered as promised. If the order is getting late, OneStock will raise alerts and recalculate a new delivery promise.

To make sure the promise is met, several milestones are calculated by OneStock for each 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.

Depending on the delivery promise configuration, other milestones will be calculated and available for triggering alerts. The list of “other” milestones corresponds to all the operations configured 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, and it's orchestrated with a ruleset chaining that respects the delivery promise, 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, an alert can be triggered, and a new delivery promise can be calculated and communicated to the client.

During order execution

When the order has been imported and milestones calculated for each order line, an alert can be automatically raised when a milestone is missed. This is configured in the order line state diagram.

The alert can trigger many 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, recalculate the order’s delivery promise, 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.

In the vendor interface

On the vendor interface, on the pages Pack and Bag, the remaining time to prepare the order before the carrier pick-up or collection promise is displayed for each order.