On time RTS
- ASHITA GUPTA (Unlicensed)
- Mituj Rana
Intro:
Whenever an order is created in Eshopbox, the expected RTS date is assigned to the order. Expected RTS date defines by when the order should be marked as ready to ship. For marketplace orders like Myntra, Flipkart, Amazon etc., the expected RTS date is provided by the marketplace only. For website orders (Shopify, Magento, Custom etc.), the expected RTS is assigned by Eshopbox.
Eshopbox calculates the on-time RTS rate on the basis of the first RTS attempt done for the order.
On-time ready-to-ship means that ready-to-ship action is attempted within the expected RTS time.
Why on time ready to ship rate is relevant ?
This rate is relevant for several reasons:
Customer satisfaction
Repeat business
Reputation
Cost savings
Why its is important to have on time ready to ship dashboard?
A ready to ship dashboard is a tool that provides real-time visibility into order fulfillment process. It displays key performance indicators, such as the number of orders received, the number of orders shipped on time, and the status of late and overdue orders and how many orders are subject to RTS SLA breach.
Let us understand some important terminologies:
On-time ready to ship (RTS) rate - percentage of orders where ready to ship is attempted within expected ready to ship date.
Late - when the order is ready to ship but the expected RTS is crossed it will be considered as late. Refers to an order that is not shipped by the expected RTS date, but the Expected delivery date has not yet passed.
For example, if a customer places an order with a promised expected delivery date of February 20th, but the product is not shipped until February 21st, then the order is considered late. But the order is delivered in expected delivery date.
Overdue-order that is not shipped by the expected RTS date, and the expected delivery date has already passed.
Example as above, if the product is not shipped until February 21st, and the promised delivery date was February 20th, then the order is considered overdue.
Exceptions - These consist of those orders which are unfulfillable and the expected RTS date is crossed.
Note: Any order for which an RTS attempt is not done AND Expected RTS date < Current time, such orders won't be considered while calculating On-time ready-to-ship (RTS) rate
Scenario | Expected RTS date | First RTS attempt | Expectation |
|---|---|---|---|
Expected RTS date > First RTS attempt | 10th Jan 2023 15:00:00 | 10th Jan 2023 14:00:00 | On time |
Expected RTS date < First RTS attempt( First RTS attempt was made after the expected RTS date) | 10th Jan 2023 15:00:00 | 10th Jan 2023 16:00:00 | Late |
Expected RTS date <Current time(Expected RTS date is crossed) AND first RTS attempt is not done | 10th Jan 2023 15:00:00 | - | Overdue |
Order status is unfulfillable AND Expected RTS date < Current time (Expected RTS date is crossed) (For this we need to treat Unfulfillable_reason as historical status to identify whether this item was Unfulfillable anytime. We will consider unfulfillable reason as product is out of stock, item not found at location ) | 10th Jan 2023 15:00:00 | - | Exception |
Shipment created < Expected RTS date -previously it was unfulfillable →
How it is calculated?
On time RTS rate = on time / ( on time + late + overdue)
On Time Ready to Ship Rate = (Number of Orders Shipped on Time / Total Number of Orders -On time orders+ late orders + overdue orders)
Example- 1,000 orders were expected to be ready for shipping in the last 30 days. Of these, 900 (94% = 900/900+25+25) were on time, while 25 were late. An additional 25 orders are still due past the expected date, and 50 orders faced exceptions that may require your attention.
Please note : On time ready to ship rate will have following color bifurcation -
Green: On-time ready-to-ship rate for a sales channel >= Total on-time ready-to-ship rate.
Red: On-time ready-to-ship rate for a sales channel < Total on-time ready-to-ship rate.
Date period | On time ready to ship rate | Sales channel | Sales channel wise On time ready to ship rate | Color to highlight |
|---|---|---|---|---|
1st Jan - 10th Jan | 90% | Myntra | 95% | Green |
|
| Flipkart | 89% | Red |
|
| Amazon | 90% | Green |
11th Jan - 15th Jan | 94% | Myntra | 95% | Green |
|
| Flipkart | 89% | Red |
|
| Amazon | 90% | Red |
Fields required:
First RTS attempt +time stamp
Expected RTS date
Current_status - to track the unfulfillable order
OPEN - How can we fetch the unfulfillable reason for the order items older than 6 months if Big query sync is required in any case?
Proposed Solution - All these unfulfillable reasons - product is out of stock ,item not found at location , Other product is out of stock, other item not found at the location
can be created as separate columns in order_unfulfillabletable where corresponding order item ID will be saved.
Overdue - When
Case 1: When First attempt is less thn or equal to Expected RTS: On time
Case 2: When First attempt is more thn Expected RTS: Late
Case 3: When expected RTS date is not assigned and status is cancelled: Exlcude from dashboard (Shopify and Amazon prime)
Case 4: Cancelled before Expected RTS AND no attempt: Exlcude from dashboard
Case 5: Cancelled after Expected RTS: (Reason: Cancelled due to delay in RTS)
Attempt within expected RTS: On time (Covered in Case 1)
Attempt after expected RTS: Late (Covered in Case 2)
Attempt not done:
Unfulfillable:
Not found: Late
Out of stock: Exception
No unfulfillable history: Late
Case 6: Shipment created within 30 mins OR after expected RTS:
Attempt available after expected RTS
Shipment delayed due to out of stock: Exception
Shipment delayed due to not found: Late
No unfulfillable history: Late
Attempt available within expected RTS:
Shipment delayed due to out of stock: On time
Shipment delayed due to not found: On time
No unfulfillable history: On time
Attempt not done and within expected RTS:
Shipment delayed due to out of stock: On time
Shipment delayed due to not found: On time
No unfulfillable history: On time
Attempt not done and after expected RTS:
Shipment delayed due to out of stock: Exception
Shipment delayed due to not found: Overdue
No unfulfillable history: Overdue
Case 7: Unfulfillable and expected RTS is not breached:
Out of stock: Exception
Not found: On time
Case 8: Unfulfillable and expected RTS is breached:
Out of stock: Exception
Not found: Overdue
Case 9: Attempt not done AND expected RTS is breached: Overdue
Exception reasons: (Logic ?)
P1: Unfulfillable
P2: Failed to RTS
P3: Higher than daily pick capacity
Grouping of Failed to RTS reasons