Bulk Order Upload on ShipSeth: The CSV and Excel Format, Column by Column
Two hundred orders in a sheet, one upload, and forty rows come back red. Nearly always it is one of four things: a header spelt differently, a COD amount typed as "1,240", grams in the kilogram column, or a CSV saved the wrong way. This page lists every column the upload reads and checks your sheet the same way before you send it.
Quick Answer
ShipSeth's bulk upload takes a CSV or Excel file of up to 500 orders and 10 MB, with 18 columns, 15 of them required. Headers must match the template names, money and size cells must be plain numbers, and weight is in kilograms. Failing rows stay out; the rest are priced, checked against your wallet in file order, then booked.
Which columns does the bulk upload file need?
Eighteen, in any order. Fifteen must be filled on every row; email, COD amount, declared value and quantity can be left empty.
The upload finds a column by its header. It accepts the name printed in the template, such as Pincode, or the short key, such as delivery_pincode, in upper or lower case. Any other header is skipped without a word, which is why a renamed column fails every row instead of raising one clear error.
| Template header | Short key | Must fill? | What to put, and the usual mistake |
|---|---|---|---|
| Order Reference | order_reference | Yes | Your own order number. Nothing stops you uploading the same one twice, so two rows with one number become two shipments. |
| Shipment Type (b2c/b2b) | shipment_type | Yes | b2c for parcels to buyers, b2b for freight to a business. Fill it on every row: in a CSV a blank cell fails the row, but in an .xlsx it is read as b2c. |
| Customer Name | delivery_name | Yes | The person who will receive it. |
| Phone | delivery_phone | Yes | Spaces and dashes are removed; at least 10 digits must remain. Enter the 10-digit mobile without +91. |
| delivery_email | No | Optional. | |
| Delivery Address | delivery_address | Yes | House, street, area and landmark in one cell. |
| Pincode | delivery_pincode | Yes | Exactly 6 digits after spaces are removed. Not "Pin Code". |
| City | delivery_city | Yes | Town or city name. |
| State | delivery_state | Yes | Full state name. |
| Payment Type (prepaid/cod) | payment_type | Yes | prepaid or cod, nothing else. "COD" in capitals is fine; "Cash on delivery" is not. Never leave it blank: in an .xlsx a blank cell is read as prepaid, so a COD parcel ships with nothing to collect. In a CSV the blank row fails. |
| COD Amount (₹) | cod_amount | On COD rows | The cash the courier collects, as a plain number. On a cod row it must be above 0. |
| Declared Value (₹) | declared_value | No | The goods value. Left blank or typed with a ₹ sign, it is saved as 0. |
| Weight (KG) | weight_kg | Yes | Kilograms. 450 means 450 kg, not 450 g. Write 0.45. |
| Length (cm) | length_cm | Yes | Packed box, in centimetres. |
| Width (cm) | width_cm | Yes | Packed box, in centimetres. |
| Height (cm) | height_cm | Yes | Packed box, in centimetres. |
| Item Name | item_name | Yes | What is inside, in plain words. |
| Quantity | item_quantity | No | Units of the item. Blank counts as 1. |
Weight and the three sizes decide the bill, so measure the packed box, not the product. Courier pricing uses whichever is higher of the scale weight and the box's volumetric weight; the volumetric weight calculator shows which one your carton bills at. If a value matters for a claim later, fill Declared Value properly; the declared value guide explains what to enter.
Will my file pass? Check it before you upload
Paste the sheet below and you will see the result the upload would give, row by row, with the same error messages.
From Excel or Google Sheets, select every cell on the sheet including the header row, copy, and paste. That copies cells exactly as they display, which is also how the upload reads an .xlsx file, so a "₹760" formatted cell shows up as the problem it is. You can also open a .csv file. Nothing leaves your browser.
Rows read
4
Within the 500-row limit
Will pass
0
No warnings
Will fail
4
Shown as invalid after upload; they get no rate
Columns found
17 / 18
Read as tab (copied from Excel) separated
| Header in your sheet | What the upload does with it |
|---|---|
| Pin Code | Skips the whole column. Rename it to "Pincode". |
| Row | Order ref | What the upload will say |
|---|---|---|
| 1 | JPR-1041 | Pincode must be exactly 6 digitsCOD Amount must be greater than 0 for COD shipments ("1,240" is not a plain number) |
| 2 | JPR-1042 | Pincode must be exactly 6 digitsCheck: Phone has 12 digits; drop the +91 or leading 0 so the courier gets a 10-digit mobileCheck: Weight 450 is read as 450 kg; if you meant grams, enter 0.45 |
| 3 | JPR-1043 | Pincode must be exactly 6 digitsCOD Amount must be greater than 0 for COD shipments ("₹760" is not a plain number) |
| 4 | JPR-1041 | Pincode must be exactly 6 digitsCheck: Same Order Reference as row 1; both rows would be booked |
Plain lines are the upload's own validation messages, word for word. Lines marked "Check" are this page's advice, not upload rules: a blank Payment Type or Shipment Type (pasted cells are read as an .xlsx would read them), a 12-digit phone, a B2C weight of 30 kg or more, a side over 150 cm, COD on a prepaid row, a declared value that isn't a number, a repeated order reference. Rows are numbered without the header, as the Bulk Upload screen numbers them. The example rows are made up.
Why does every row fail with the same error?
Because a column header didn't match, so that field is empty on every row.
The upload ignores case and spaces at either end of a header, and nothing else. "Pincode" works. "Pin Code", "PIN", "Pincode " with a trailing space inside a merged cell, or "Pincode*" with an asterisk your team added for required fields do not. Each of those gives "Pincode must be exactly 6 digits" on all 200 rows, even though the digits are sitting right there in the sheet. The same happens to "Mobile" in place of Phone and "Name" in place of Customer Name.
Then there is the CSV problem, and it catches people who did nothing wrong. Excel offers two CSV formats. CSV UTF-8 starts the file with an invisible byte-order mark, and ShipSeth's CSV reader keeps that mark glued to the first header, so "Order Reference" stops matching and every row fails on it. CSV (Comma delimited) has no mark, but it can't hold the ₹ in "COD Amount (₹)" or Hindi text, which turn into question marks. Then the COD column is lost, and so are Devanagari addresses.
Our advice is simple: fill the template in Excel and upload the .xlsx. Use CSV only when the file comes out of another system, a store export or a script, as plain UTF-8 without the mark. If you write the CSV yourself, use the short keys as headers (the button above gives you a blank one); they are plain English letters and survive any save.
Why is my COD amount rejected when it's filled in?
Because the cell isn't a plain number, and a non-number is read as 0.
The upload accepts 1240, 1240.50 and even 1.24e3. It does not accept 1,240, ₹760, Rs 760 or 760/-. Those become 0, and a COD row with a 0 amount fails with "COD Amount must be greater than 0 for COD shipments". The same rule hits weight: "0.5 kg" or "500g" is not a number, so the row fails on weight. Declared Value is quieter and worse. It is optional, so a "₹1,240" there doesn't fail anything; it is simply saved as 0.
In an .xlsx this usually comes from cell formatting, not typing. A column formatted as Currency or with a thousands separator is read the way it displays. Select the COD Amount, Declared Value, weight and size columns, set them to General or Number with no separator, and save. Paste the sheet into the checker again to confirm.
What happens after the file is uploaded?
Four steps on the Bulk Upload screen, which sits under Orders in the sidebar: Upload File, Pickup Point, Review Rates, Confirm.
- Upload File. The step has its own Download Sample Template button if you don't have the file yet. After you upload, the screen counts valid and invalid rows. If no row is valid, you can't move on.
- Pickup Point. Pick the godown the rider comes to. One file ships from one pickup point, so two warehouses means two files. Rates are then fetched in the background, and you see a running "rates ready" count.
- Review Rates. Every valid row gets the cheapest courier option for its weight, size and pincode. Open a row to switch courier, edit a wrong field and re-price it, or delete it. Rows no courier can price show as no rate. The summary panel shows the wallet balance against the total.
- Confirm. The button reads Book followed by the number of rows your wallet covers. Rows are booked one by one in file order. When it finishes you get the booked, rejected and total-cost figures, and a button to download all the labels in one go.
Every upload stays in the history list below the wizard. Its download button gives back your original columns plus five more: Status, Courier, Shipment Number, Rate (Rs) and Remarks, with failed or rejected rows shaded. That file is the quickest way to re-upload only the rows that didn't go. After booking, pickups are requested the same way as for single orders; the pickup and manifest guide covers which day the rider comes and prints a hand-over sheet for 200 AWBs as easily as for 2.
What if my wallet doesn't cover the whole file?
The rows that fit get booked and the rest are rejected with the reason "wallet". The order of your file decides which is which.
ShipSeth walks down the rows from the top, adding each row's rate to a running total. If a row would take the total past your balance it is rejected, and the walk carries on. That last part surprises people: a cheap row near the bottom can still get in after a costlier one above it was turned away.
An example, with made-up rates. Wallet balance ₹500, four rows:
| Row | Rate | Running total if accepted | Result |
|---|---|---|---|
| 1 | ₹180 | ₹180 | Booked |
| 2 | ₹150 | ₹330 | Booked |
| 3 | ₹190 | ₹520, over ₹500 | Rejected: wallet |
| 4 | ₹60 | ₹390 | Booked |
Three shipments go for ₹390, and row 3, maybe the order the buyer chased you about twice, waits. Two habits fix this. Recharge before you confirm, using the total on the Review Rates panel; it's a prepaid wallet with no monthly fee on top. And sort the sheet so the orders that must leave today are at the top. COD money from delivered orders comes back twice a week, on Tuesday and Friday, which is a natural point to plan the next big upload.
Can I put B2B freight in the same file?
Yes, set Shipment Type to b2b on those rows. But each row carries one box size, so it suits single-carton consignments best.
A dealer order of six cartons on one LR is a multi-piece shipment, with a master AWB and a child AWB per carton. A single row with one length, width and height can't describe six different boxes. Book that one from the shipment form instead, and read the multi-piece shipment guide for how the cartons are weighed together. Whether a load should go as a parcel or as cargo at all is covered in B2B vs B2C shipping.
A worked example: one Jaipur sheet, three mistakes
Example only. The sample already in the checker is a block-print seller's Monday sheet copied from Excel, four rows going to Jaipur, Jodhpur and Udaipur. Run it and this is what comes back:
- Every row fails on Pincode, because the header says "Pin Code". The checker names the fix: rename it to "Pincode". One edit clears four errors.
- Row 1 still fails: its COD amount is "1,240". Row 3 fails on "₹760". Both are Currency-formatted cells; switch the column to General.
- Row 2 passes, with two warnings. The phone was typed with +91, giving 12 digits, and the weight of 450 is read as 450 kg for two dupattas. Neither stops the upload. The second would get a 450 kg rate, which is precisely why you check before confirming.
- Row 4 repeats JPR-1041. Someone re-entered the order as prepaid after the buyer paid online. Delete one of the two rows, or the buyer gets two parcels and you pay twice.
Five minutes in the sheet, and the three real orders reach Review Rates clean.
500 orders, one upload
Book Your Whole Day's Orders From One Sheet
Free to register, no monthly fee. Each row is priced across couriers before you book, you pay per shipment from a prepaid wallet, and the labels come out in one download.