Skip to content
Robnu
Glossary · Order processing

All-or-nothing

Ajio's batch upload rule — every line in the upload succeeds, or the whole batch fails.

app.robnu.com/ai/conversationsRobnuAI · seller-scopedai_conversations · ai_messages · ai_tool_callsWhy did Ajio short-pay batch 7782?tool_calllookup_payouts(batch=7782)7 of 218 lines were short-paid by ₹47 each — SLA-missdeduction. All 7 are recoverable. I drafted claims foryou with the manifest + AWB pre-attached.→ /claims · 7 drafts readywithSellerScope · seller_id locked

Ajio's confirmation upload accepts a batch of order lines as one transaction. If any line fails validation — bad SKU, mismatched quantity, expired confirmation window — the whole batch is rejected.

This is brutal at first, friendly at scale. It means you can't accidentally half-confirm a batch and end up with split state. Either the upload succeeds and your batch is locked in, or it fails and you fix the offending line and retry.

Robnu validates locally before upload (stage 5 of the 11-stage flow). The vast majority of all-or-nothing rejections are catchable client-side — quantity mismatches, expired windows, malformed lines. Robnu catches them before they hit Ajio.

build 3724c76bafbf7cbcc3bd010d27df0223a625fc38 · 2026-07-10T08:10:07+05:30