Bulk India Post booking preparation
Bulk booking fails for boring reasons: a missing PIN digit, a weight in the wrong unit, a phone number with a country prefix. PostVery catches those before the file leaves your desk.
Import mapping
february-orders.xlsx · 248 rows
- Shipping NameRecipient name
- Shipping ZipPIN code
- Total Weight (g)Weight · converted to kg
- Payment MethodCOD flag
241
Validated
5
Warnings
2
Errors
- Row 118 · PIN code has 5 digits
- Row 204 · phone number includes country prefix
Prepare hundreds of shipments without repetitive entry.
Import a spreadsheet, map the columns once, and let PostVery validate every row before a booking file is produced. Errors are reported per row so nothing fails silently at the counter.
- CSV and XLSX importsUpload exports from your store, marketplace panel or accounting tool. Large files are processed in batches.
- Reusable column mappingsSave a mapping per source so the next import is a single click, even when column order changes.
- Address and shipment validationPIN code format, missing phone numbers, weight limits, value fields and prohibited-content flags are checked before export.
- Compatible booking-file generationProduce a structured booking file laid out for bulk-booking workflows, ready to submit through your own India Post channel.
- Booking-result importBring the returned file back in to attach article numbers and booking dates to the right shipment records.
- Row-level error reportsDownload a report that lists each rejected row with the reason, fix it in place and re-run only the failures.
Excel booking versus API booking
Excel booking means PostVery prepares a structured file that you submit through your own India Post channel; the department processes it and returns article numbers you import back. API booking means consignments are created programmatically against an eligible contractual account, which requires approval and credentials issued to your business.
- Excel booking: available to any seller with a booking arrangement
- API booking: requires an eligible contractual account and department approval
- Both methods produce the same shipment records inside PostVery
Validation rules you can edit
Each workspace carries a validation profile — required fields, weight ceilings, insured-value thresholds, COD limits. Rows that fail are held back rather than silently exported.
Audit trail
Every import keeps the original file, the mapping used, the generated output and the result file, so a dispute three weeks later can be traced to a specific batch.
Excel-based booking and direct API booking are different methods. Spreadsheet preparation works for any seller; direct API booking requires an eligible India Post contractual account and approval from the department.
Works together with
- Shipping Labels and BarcodesGenerate single or bulk India Post shipping labels, allocate barcode references safely, reprint without waste and prepare dispatch manifests.
- Shipping DashboardA single India Post dispatch workspace: order queues, batch preparation, label runs, handover status and exception queues with full activity history.
- Tracking and Delivery OperationsTrack India Post shipments in operational queues: delayed consignments, failed delivery attempts, follow-ups and exception reports in one workspace.
Bulk India Post Booking questions
Still unsure? Ask us directly.
CSV, XLS and XLSX. The first row is treated as the header row.
In the spreadsheet workflow, no — you submit the prepared file through your own channel. Direct submission is only possible where an authorised API integration is available to your account.
They stay in the batch with an error flag and are excluded from the generated file. You can correct them inline and re-generate.
Put your India Post dispatch on autopilot.
Start with spreadsheet imports today and move your store connection across when your beta slot opens. No card is collected during early access.