Skip to content
Robnu
Field NotesField Notes4 min read

Closure policy explained — immediate, delayed, or manual

Closure policy is the call you make per batch: when do you actually press the close-manifest button? Robnu offers three modes, each with a different operating shape — this post maps when each one wins, when it loses, and the defaults to start from.

Hiren Bhuva
Co-founder, Onviqa Inc. · Robnu
TL;DR
  • Immediate: closes when the last shipment is ready. Best for steady-state, low-error-rate batches.
  • Delayed: closes at a fixed time. Best for sellers who batch slips at end-of-day.
  • Manual: waits for you to click. Best when courier mix needs a human eye.

Closure policy is the call you make per batch: when do you actually press the “close manifest” button? Robnu offers three modes. Each has a different operating shape. Picking the right one for your batch is the difference between a clean closure and a midnight scramble.

Comparison of three manifest closure modes. Immediate closes the moment the last shipment is ready, best for steady-state low-error batches. Delayed closes at a fixed time such as 5:30 pm, best for end-of-day batching. Manual waits for a human click, best when the courier mix needs a human eye.
Figure 1 — The three closure modes side by side, with where each one wins and loses (illustrative).

Immediate

The manifest closes the moment the last shipment in the batch reaches the “ready” state. No human in the loop.

When it wins:

  • Steady-state ops. Same SKU mix, same courier mix, same window every day.
  • Low error rate at stages 4–8. If your slips and invoices reconcile cleanly, immediate is the most efficient closure mode.
  • Small-to-medium batches (< 30 shipments). The risk window is short.

When it loses:

  • High-variance days. If a slip reprint or a quantity correction is in flight, you don’t want the manifest closing automatically with the wrong line.
  • Mixed couriers. If half your batch ships via courier A and half via courier B with different pickup windows, immediate closure can cut the second half out.

Delayed

The manifest closes at a fixed time — say, 17:30 — regardless of whether the last shipment is ready.

When it wins:

  • End-of-day batching. You print all slips at 17:00, run the document pipeline at 17:15, manifest closes at 17:30. Predictable, repeatable.
  • Multi-batch days. Morning batch closes at 13:00, evening batch closes at 17:30. The SLA watchdog plans around fixed close times.
  • Team handoffs. The packer leaves at 18:00; the manifest must close before then.

When it loses:

  • Batches that aren’t ready by the fixed time. Delayed mode will close anyway and you eat the SLA hit on shipments that didn’t make it.

Manual

The manifest waits for you to click “close.” The SLA watchdog still escalates at 30% / 10% headroom, but there’s no auto-close.

When it wins:

  • Categories with high return rates or quality scrutiny. You want a human eye on the final list before submission.
  • Courier negotiations. You’re moving shipments between couriers based on pickup-window slots; you need flexibility right up to the deadline.
  • New ops teams. Until your team trusts the operating model, manual gives you the same flow with a human gate.

When it loses:

  • Volume. At 25+ shipments/batch, manual is too much friction.
  • Off-hours. Manual mode plus a tired team plus a tight deadline equals midnight closure.
Decision flow for picking a closure mode. Start with manual for the first two weeks and watch the watchdog. If the batch is steady with a low error rate, move to immediate. If you batch slips at end of day, move to delayed at a fixed time. If the courier mix needs a human eye, stay on manual.
Figure 2 — A two-week path to your default: start manual, watch the watchdog, then settle (illustrative).

The defaults Robnu ships

For sellers under 25 orders/day:

  • Default: Delayed at 17:30. Predictable, watchable, low cognitive load.
  • Suggested first move: Manual. If you’re new, start manual for two weeks. Watch the watchdog. Pick a close time that consistently works. Switch to delayed.
  • Steady state after 60 days: Immediate. Once your stage 4–8 error rate is < 2%, immediate is faster and more efficient.
Diagram of the SLA watchdog as safety net across closure modes. It escalates at 30 percent and 10 percent SLA headroom. In immediate mode it rarely fires, in delayed mode only on edge cases, and in manual mode it is your most important reminder.
Figure 3 — Whichever mode you pick, the SLA watchdog is the net underneath it (illustrative).

You can change the mode per-batch. Most sellers find a default and stay there, but the option is always present.

Read more

Tags:processmanifestops

Frequently asked questions

  • It is the call you make per batch about when the manifest actually closes. Robnu offers three modes — immediate, delayed, and manual — each with a different operating shape. Picking the right one for your batch is the difference between a clean closure and a midnight scramble. You can change the mode per-batch, but most sellers find a default and stay there.

Start Robnu free

See where you're losing rupees on Ajio

Robnu walks every Ajio order from open through manifest, flags every silent deduction, and watches every SLA. Free during early access. No caps. No card. No trial timer.

  • Ajio order processing — every stage covered
  • Free for ≤ 25 orders/day — forever
  • 11-stage flow, document pipeline, SLA watchdog

Sources & further reading

  1. Meesho supplier panel — dispatch SLA terms
    Meesho Supplier HubAccessed July 2026
Hiren Bhuva
Co-founder, Onviqa Inc. · Robnu

Hiren has spent over a decade shipping commerce software for Indian sellers and runs Onviqa Inc., the parent company behind Robnu. He writes about marketplace ops, deduction defense, and the boring infrastructure that decides whether a small Indian brand keeps its money.

Related reading

All posts
build e7713058ee9ee67dffe938623a3f859dcb157b2a · 2026-07-24T12:14:00+05:30