Manifest automation
Generate manifest from confirmed orders, not Excel exports
- Generate manifest from confirmed orders, not Excel exports
- Closure policy decides immediate / delayed / manual per batch
- Document pipeline keeps packing slip, vendor invoice, customer invoice tied together
The use case: you're closing manifests by hand at end-of-day, copying data between three tabs, and finishing at midnight more often than you'd like.
What gets automated
The manifest itself, generated from the confirmed shipment set:
- Manifest line per shipment, populated from the canonical order record
- Courier partner pulled from the shipment listing (stage 6 of the 11-stage flow)
- AWB pulled from the shipment listing
- Closure timing per the closure policy (immediate / delayed / manual)
You don't copy from one place to another. The manifest is built from one source of truth.
What still requires you
The decisions:
- Closure mode per batch — immediate is best for steady-state, delayed for fixed end-of-day, manual for high-variance days
- Closure timing if delayed — pick a fixed close time, usually 17:30
- Override on edge cases — pulling a shipment that's not ready, holding for one more order, etc.
You make the calls. Robnu does the work between them.
Why this is the highest-leverage automation
A manifest closure has 12+ shipments per day for a typical 15-orders/day seller. Doing it by hand takes 22 minutes. Across a month that's 11 hours. Across a year, a full work week.
Automating manifest generation isn't about saving the 11 hours per month — it's about removing the cognitive overhead of "where am I in the workflow." That overhead is what causes the missed SLA, the missing slip, the wrong AWB on the slip.
How to start
Start free. Manifest automation is part of Process, which is live today.
For the closure policy details, see Closure policy explained.