SLA recovery on Ajio
How Robnu catches a missed-manifest event before the marketplace flags it
- How Robnu catches a missed-manifest event before the marketplace flags it
- What the SLA watchdog timer does and why it matters
- The closure-policy choice that prevents most SLA misses
The use case: you're running 5–25 orders a day on Ajio. Every batch has an SLA window. Miss it, the deduction lands two weeks later.
What goes wrong without Robnu
The default Ajio operating environment doesn't tell you during the day that a batch is at risk. You find out either right at the closure deadline (when you're already scrambling) or two weeks later (when the deduction posts). Neither moment is recoverable.
What Robnu does
Robnu's SLA watchdog computes SLA-headroom as a percentage of the closure window remaining. It escalates at 30% (heads-up), 10% (act now), and 0% (breach).
The dashboard surfaces every batch's headroom in real time. You see the clock running. You decide when to close.
The pattern this prevents
The most common pattern is what we call the "16:30 deferred to 23:42" — you have a clean batch ready at 16:30, you decide to wait for one more shipment, you forget about it, and at 22:30 you realise the manifest hasn't closed. Now you're scrambling.
The watchdog re-frames the question at 16:30: "headroom is 18%; do you want to close now, or wait?" If you choose to wait, the watchdog escalates again at 10%. By 23:00 you've either closed or made a deliberate decision to close late.
Result on actual sellers
One Ajio seller we work with moved their median manifest closure time from 23:42 to 17:38 in week one. Same orders, same SKU mix. The watchdog moved the decision earlier in the day; the rest followed.
Where to start
Start free on Ajio. The watchdog is on by default; thresholds are tunable in /admin/settings.
For the deeper version of this story, see What "manifest at midnight" actually costs.