Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This feature is available only when the delivery promise is activated.

OneStock provides a delivery promise before the customer places its order. Once it has been confirmed, OneStock will monitor the order execution to make sure that the order is delivered as promised. If 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 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?

Every time an order is imported in OneStock with a promised delivery date on it, the 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?

During order execution

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

The alert can trigger many type 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. 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, Bag and Reserve, the remaining time to prepare the order before the carrier pick-up or collection promise is displayed for each order.

It is also possible to sort the orders so that the most urgent ones appear first.

  • No labels