A corporate order: 'send our gift box to 40 employees' addresses'. One order, forty shipments — the multi-address problem is really forty bookings wearing a trenchcoat. How to run it without losing your mind.
The order-split reality
Each destination is its own shipment — its own quote, AWB, label, tracking. The 'order' is a container for N shipments; the logistics treat them as separate parcels that happen to share a payment.
The spreadsheet flow
Collect addresses in a template (name, phone, address, pincode, email optional) → CSV → bulk upload → validates all rows → books all shipments → labels print in batch. The 40-address order becomes a 10-minute upload instead of 40 manual bookings.
The validation that matters
Forty addresses from an HR spreadsheet will have errors — pincode typos, missing phone digits, truncated lines. The upload validation pass catches them all before booking — fix the bad rows in one pass rather than discovering NDRs one by one.
The festive-gifting use case
Diwali corporate gifting is where this lives — bulk hampers to scattered addresses, the order booked once, the shipments tracked individually. Price it as bulk (the freight quote is the sum, but the admin cost is where you win).
Pakka Parcel runs the whole stack described here — one place for every carrier.
See how →The playbook
Collect addresses in the template
The CSV columns are the booking fields.
Validate before booking
40 rows, 3 bad — fix in one pass.
Batch-book and batch-print
N shipments, one upload, one label run.
Track per-recipient
Each AWB tracks independently to its destination.
