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 6 Next »

Scheduled events allow impacting the setup of an entity's calendar at a specific date and time.

If on January 1st only some of your stores are opened, you can create a scheduled event that considers them as closed for Delivery Promise and Orchestration purposes.

There are 3 scheduled events configurations

🏪 Stock location scheduled events

Stock location scheduled events allow impacting the calendar of a selection of points of stock during a specific interval of time (start and end included).

Where ? 🧭

Stock locations > Scheduled Events (top right)

Impact ?

Depending on actions and site configuration :

  • Delivery Promise (including during orchestration) : stock locations will be considered as unable to prepare orders for pickup nor to receive orders being delivered. Operations will be postponed till the next available slot.

  • Orchestration : stock location will not be considered as candidates.

  • Stock : stock location’s stock will not be accounted in exports.

  • Order in Store : stock location’s stock will not be accounted when displaying stock of other stores.

  • E-Reservation funnel : stock location’s stock will not be accounted.

Visualizing existing events

Existing scheduled events can be viewed in the stock location scheduled event list. By default, those with an impact interval during the next following 30 days are displayed. Top right date picker allows changing the date interval.

Managing events

To create a new event, click on the create button.

A scheduled event consists of a

  • name

  • impact intervals : from when to when the event will take place (start and end dates included).

  • timezone : time zone of the impact interval

  • list of stock locations : stock locations impacted by the event.

  • actions : actions that will take place during the interval. More details following.

Actions

Actions can be disabled, enabled or left untouched (current value at the moment of the event will persist).

Available actions are :

  • Open : Overloads the stock point's opening hours. While closed (opened disabled), the stock location will not be able to carry out delivery promise operations (including pickups), it will be displayed as closed in order in store and e-reservation tunnels, and no on-demand pickups will be requested to carriers.

  • Claim : When disabled, the point of stock will not be able to claim placed orders. It will not be considered as a candidate during orchestration, either.

  • Stock Export : When disabled, points of stock's stock is not exported. Depending on stock export's configuration, orchestration, delivery promise and accounted stock may be impacted.

🚚 Carrier scheduled events

Carrier scheduled events allow impacting the calendar of a selection of carriers and zones during a specific interval of time (start and end included). This translates into disabling pickups, delivery, or transit operations of a set of delivery routes during an interval of time.

Where ? 🧭

Delivery > Carriers > Scheduled Events (top right)

Impact ?

Carrier scheduled events solely impact the delivery promise. If levering the delivery promise during orchestration, it will be impacted as well.

Visualizing existing events

Existing scheduled events can be viewed in the carrier scheduled event list. By default, those with an impact interval during the next following 30 days are displayed. Top right date picker allows changing the date interval.

Managing events

To create a new event, click on the create button.

A scheduled event consists of a

  • name

  • impact intervals : from when to when the event will take place (start and end dates included).

  • timezone : time zone of the impact interval

  • list of carriers : carriers impacted by the event.

  • list of zones : zones impacted by the event.

  • actions : actions that will take place during the interval on the stock locations calendars. More details following.

Actions

Actions can be disabled, enabled or left untouched (current value at the moment of the event will persist).

Available actions are :

  • Pickup : When disabled, the list of carriers will be unable to do pickups at the list of zones. Pickups will be postponed till the next opening slot.

  • Transit : When disabled, the list of carriers will be unable to operate. Pickups, transits, and deliveries will be postponed till the next opening slot.

  • Delivery : When disabled, the list of carriers will be unable to do deliveries at the list of zones. Deliveries will be postponed till the next opening slot.

⚙️ Orchestration scheduled events COMING SOON

Orchestration scheduled events allow impacting orchestration calendars. This translates into orchestration rules, which use impacted calendars, being paused. Orchestration will be postponed till the next available slot.

Where ? 🧭

Orchestration > Scheduled Events (top right)

Impact ?

Orchestration scheduled events solely impact orchestration. As a result, impacted orchestration will be paused till the next available slot.

Visualizing existing events

Existing scheduled events can be viewed in the event list. By default, those with an impact interval during the next following 30 days are displayed. Top right date picker allows changing the date interval.

Managing events

To create a new event, click on the create button.

A scheduled event consists of a

  • name

  • impact intervals : from when to when the event will take place (start and end dates included).

  • timezone : time zone of the impact interval

  • list of calendars : orchestration calendars impacted by the event.

  • actions : actions that will take place during the interval. More details following.

Actions

Actions can be disabled, enabled or left untouched (current value at the moment of the event will persist).

Available actions are :

  • Orchestration : When disabled, all orchestrations that make use of one of the calendars in the list of calendars will be paused. Orchestration will be resumed at the next available slot.

  • No labels