Audience: Retailers and suppliers

As a retailer, you can configure the rules to specify how much time a supplier has to take a specific action – from acknowledging an order to shipping an order on time. The following metrics are available to all participating retailers:

Order Metrics

• Created > Acknowledged measures the amount of time between when an order is available to a supplier in the Dsco platform and when the supplier receives the order (via stream, API, AS2, etc.). If the supplier does not acknowledge the order within the set time, the Dsco platform will create an exception.
• Created > Shipped measures the amount of time between when an order is available to a supplier in the Dsco platform and when the supplier completes all units on all line items of the order, marking them shipped or cancelled. Orders/Lines that are not completed, shipped, or canceled within the set time are in exception and are called late.

Created > Shipped Rules

Ship by date aka Expected Ship Date (ESD)

This is the date a retailer expects a supplier to mark an order or a line item as “shipped”. Orders shipped on or before the ESD are considered “on-time”. Orders shipped after the ESD are considered “in violation” until they are shipped, and recorded as “late” once they are shipped.

Created > Shipped Hierarchy

The rule hierarchy impacts the ESD on an order.

When an order is created, it is evaluated against SLA rule conditions from “top to bottom”.

Supported conditions:

• Suppliers
• Created on days(Created → Acknowledged and Created → Shipped only)
• Ship methods (Created → Acknowledged and Created → Shipped only)
• SKUs (Created → Shipped only)

The first rule that the order matches is applied to the rule.

A “default rule” is applied to orders that did not satisfy any conditions in the hierarchy.

For the Created → Shipped metric, the ship_by_date (ESD) will reflect the rule that is applied to the order.

Applied example:

Ship by date with a timezone

If a retailer sends a ship by date with an embedded timezone (for example, 2022-09-28T16:09:38+05:00) AND the rule hierarchy determines that the ship by date should be used to set the SLA deadline, we will honor the embedded timezone.

ESD updated by supplier

If a supplier updates the ESD on an order, it impacts the calculation of Shipped on Time. After a supplier updates the ESD on an order, any exception notifications are “snoozed”, until the revised ESD passes. Shipped on Time performance is evaluated against the original ESD on an order.

Retailer does not send an ESD

If an order is not measured by SLAs, and there is no ESD on the order, the ship_by_date (ESD) is set to 2 calendar days after the create date.

If an order is not measured by SLAs, we will not surface any warnings or violations in the UI.

• Shipped → Invoiced measures the amount of time between when a supplier ships the order and when the order is invoiced. Orders that are not invoiced on time are in exception and are called late.
• Return Request → Acknowledged measures the amount of time between when a return is requested by the retailer and when the supplier acknowledges (accepts or rejects) the return. Returns that are not acknowledged on time are in exception and are called late return acknowledgments.
• Cancel Request → Accepted/Rejected measures the amount of time between when a cancellation is requested by the retailer and when the supplier accepts or rejects the cancel request. If the supplier does not accept/reject the cancel request within the set time, the Dsco platform will create an exception.

Inventory Metrics

• Inventory Update Frequency measures the frequency with which a supplier must update their inventory.

For more information about order and inventory metrics, see Getting started with performance monitoring.