Packing lists in fresh produce shipping: a complete guide

The packing list is the only document that tells you what you actually bought. The bill of lading says a container moved. The commercial invoice says what it cost. Neither can tell you whether the pallet your customer expects on Thursday is size 18 or size 24.

That makes it the document your week runs on. It is also the one document in the stack with no standard behind it: sixty growers will send you sixty layouts, in four languages, and change them mid-season. This page covers what is on a packing list, why they vary so much, and what you need pulled out of one. It also names the specific ways a packing list misleads a reader in a hurry.

What the document is for, after it arrives #

A packing list is the exporter’s statement of what is physically inside the container: how many pallets, what is on each one, which variety, which calibre, how many boxes, and what it all weighs. Four different people then use it, and each of them needs a different part.

Your customs broker needs it alongside the invoice to file the entry. Without it the entry does not go in cleanly, and the container waits in the terminal, where free time is running.

Your sales team works from it before the vessel arrives. A pallet of size 18 avocados and a pallet of size 24 are different products, with different buyers and different prices. The packing list is where that distinction is written down first.

Your warehouse receives against it, pallet by pallet, so the pallet identifiers on the sheet have to be the ones printed on the labels.

Your claim, if you have to make one, starts from it. If the container arrives warm, the packing list is the baseline for how much fruit of what grade was loaded — reefer cargo claims covers what else a claim needs.

So a packing list is not read once. It is read four times, by people who each need a different column, which is why “we got it, it’s in the folder” is not the same as having it.

What is on a packing list #

The fields below are the ones that do work downstream. Not every exporter sends all of them, and the ones they leave out are rarely the ones you would choose.

GGN is the GLOBALG.A.P. number that identifies a certified grower. Where your buyer requires certified fruit, it is the field that proves it.

If you ship into the US, the grower and lot fields are about to carry more weight. The FDA’s food traceability rule — section 204 of FSMA — covers most fresh fruit and vegetables. Food on that list has to travel with a traceability lot code and a set of key data elements attached to it. For an importer, the packing list is usually where those codes arrive: the grower reference, the lot number, the pack date. The compliance date has moved. It now sits at 20 July 2028, after Congress directed the FDA not to enforce the rule before then. What that changes this season is the habit rather than the deadline. A packing list that names the grower and the lot pallet by pallet is a record you will need, and one that names neither is a gap worth finding now.

Calibre is the field worth insisting on. North American buyers and their packhouses call the same field size or count. A Spanish sheet heads it Calibre or Cal. All three mean the number of fruit that fill one box. A size 18 avocado and a size 24 avocado came off the same tree in the same week, and in your warehouse they are two products at two prices. It is also the field most likely to be abbreviated, moved into a heading, or dropped entirely.

Here is one sheet with those fields on it, and with the seven places a reader goes wrong marked. It is a composite rather than one exporter’s document, but nothing on it is invented — every trap below is one we have met on a real consignment. The sections after it take each one in turn.

Why every exporter’s packing list looks different #

Ask why there is no standard, and the answer is structural rather than careless.

Nobody issues it but the exporter. A bill of lading is the carrier’s document, on the carrier’s form. A phytosanitary certificate follows an international model certificate laid down by the plant health convention. A packing list has no issuing authority and no model. It is printed by the packhouse, out of the packhouse’s own software, in whatever shape that software prints.

The columns follow the packhouse, not the buyer. A packhouse that grades by tie count prints a tie count. One that sells by carton format prints “C.18KG” in an Envase column — envase is Spanish for packaging — and expects you to read the box weight out of that string. Neither is being awkward. Both are printing what their packing line records.

They move during the season. A retailer asks a grower for a label reference, and from the next consignment there is a new column in the middle of the table. The format you learned in April is not the format arriving in July.

The words are not English, and often not one language. Cajas, colli, bultos and C/S are all box counts. English is not one word either: a box on a European sheet is a carton or a case on a North American one. Parihuela is Peruvian Spanish for a pallet. Calidad — literally “quality” — is the category header on plenty of Peruvian sheets, where you would expect Categoría. And one document frequently runs two languages at once: an asparagus list heading one column “Espárrago” and the next one “Asparagus”.

What reaches you is usually a picture of the real document. The exporter has a spreadsheet. They print it to PDF, or scan the printout, or photograph the scan at the packhouse before dawn. Every step throws away the structure that made it a table.

The four shapes you will actually meet #

Underneath the variation, produce packing lists come in a small number of structural shapes. Recognising which one you are holding is most of the work.

The flat table. One row per line item, one column per field. Everything below is a complication of this.

The grouped table. Variety, category or colour sits in a banner row above a block of rows, rather than in a column repeated on every row. Read the sheet row by row and the grouping is lost, so every row in the block looks like the same undifferentiated fruit.

The pivot by calibre. Many packhouses give calibre no column at all. They put the calibres across the top — 16, 18, 20, 22 — and put box counts in the grid underneath. This is the layout that catches careless reading, because the number 18 in the heading is a size and the number 18 in the cell below it is a quantity. A grape sheet can carry colour banners above the calibre row as well, so one cell belongs to a colour and a size.

The multi-row pallet. A pallet built over two days, or from two lots, gets one row per lot with the same pallet number on both. A mandarin list out of Peru gives pallet MN-0149 two rows, of 69 and 41 cartons. Your stock system wants one pallet of 110. Counting rows instead of pallets is how a forty-pallet container becomes fifty-three.

There is a fifth shape worth knowing, because it looks like an error and is not one. On asparagus and other produce sold in ties — small bunches, atados in Spanish — the box weight is in no column at all. It is the tie count multiplied by the weight per tie. A column headed “No Tied” holding 20, next to a “Weight (kg)” column holding 0.25, means 5 kg boxes rather than 250-gram ones.

The trap that costs the most: hidden columns #

Hidden spreadsheet columns from another buyer’s order are the single most dangerous defect in a produce packing list, because every number that results is plausible. It gets its own section here because it is invisible by design and the damage it does is silent.

Exporters reuse workbooks. Last month’s order for another customer is still in the spreadsheet, and rather than delete those columns, somebody hides them. The sheet looks correct on screen, prints correctly, and is sent in good faith.

The columns are still in the file. Anything that reads the file rather than the screen — a script, an extraction model, a colleague who widens a column by accident — reads them too. So you get a box count from your order and a calibre from somebody else’s, in the same row, with nothing on the page to say so. Every number is plausible. Nothing looks wrong.

We hit this on real customer documents, and the lesson was that a better reader is not the fix. A better reader reads the hidden columns more accurately. The fix is to remove what the sender hid before anything tries to interpret the sheet, and to let the visible column win wherever the same header appears twice.

If you are doing this by hand, the habit is a small one. Open the workbook, select all the columns, unhide, and look at what appears. If the answer is another buyer’s order, work from the visible columns only — and tell the exporter, because they almost certainly do not know they are sending it to you.

Five more ways a packing list misleads you #

Two columns that both say “cajas”. One is the count for that row. The other is a running total down the page. Add up the wrong one and you have doubled the shipment. This is the most expensive misread we have seen, and it does not come from a difficult document. It comes from a header collision.

A summary sheet that outranks the detail sheet. Many workbooks carry both. The summary is padded, prints nicely, and is useless for allocation: it tells you 2,400 boxes and not which pallet holds which calibre. Work from the detail sheet.

An index column read as a quantity. A bare “Nº” column numbering the rows 1, 2, 3 sits next to the real counts and looks exactly like one of them.

Alphanumeric calibres. Sizes like 1X and 2X, or LG, XL and JBC, are text. Spreadsheets and careless readers turn them into numbers or drop them, and calibre is the field you can least afford to lose.

Category values that carry their own prefix. “Categoría: Cat 1”, “CAT I”, “Cat.1” — three spellings of one grade. They group together in no report until somebody strips the prefix off all three.

The two-minute check that catches all of it #

Every problem above produces the same symptom, and the packing list itself will tell you about it.

A packing list declares its own totals: number of pallets, total boxes, total net weight. The exporter wrote those before anyone tried to read the sheet, which makes them an independent check on every row above them. Sum the box counts you pulled out and compare them with the declared box count. Multiply box counts by box weights and compare that with the declared net weight.

If both reconcile, the reading is almost certainly right. If they do not, something is wrong and you know it in the same second — usually the running-total column, the multi-row pallet, or a hidden column that should never have arrived.

The value of the check is what it does to the type of error. A misread packing list is dangerous because it is confident: right format, right field, plausible number, nothing to notice. The arithmetic turns that into a visible failure. It is also why we would rather fail a box count loudly than quietly correct it — why document automation was impossible until now goes further into what an automated read still gets wrong.

Make the arithmetic the system’s job #

The check above is the same one worth demanding of anything that reads packing lists on your behalf, whether you build it, buy it, or hand the job to a colleague. A person can reconcile one sheet carefully. Nobody reconciles sixty of them in the third week of the season, which is exactly when the misread happens.

So the question to ask of an automated reader is not how accurate it is. Accuracy is unobservable on a document you have not checked, and a wrong box count looks precisely like a right one. The question is whether the system checks its own reading and tells you when the check fails. Three reconciliations are enough to build that on, and every one of them uses figures the exporter already put on the sheet:

• Total box count — the per-row counts summed, against the declared total. Catches the running-total column read as a quantity, and the index column read as a count.
• Total net weight — box counts multiplied by box weights, against the declared net weight. Catches a calibre or a weight pulled from the wrong column, including a hidden one, because a wrong weight rarely sums to the right total.
• Pallet count — distinct pallet identifiers, against the declared number of pallets. This is the one that catches the multi-row pallet, and it is the check most often left out, because rows and pallets look like the same number until the day they are not.

Two properties make this worth more than a better reader. It runs on every document rather than the ones somebody had time to look at, and it fails in a way you can see. A document that does not reconcile is not one to correct quietly — it is one to put in front of a person with the failing number named, which is a minute of work on the few that fail instead of a spot-check on all of them.

It also gives you something to ask a supplier for in concrete terms. “Does it read packing lists accurately” has no answer anybody can hold you to. “Does it reconcile box count, net weight and pallet count against the declared totals, and what does it do when one of them disagrees” has exactly one.

What to ask your exporter for #

Five requests, none of which costs the exporter anything, and all of them easier to agree before the season than to argue about during it.

Send the spreadsheet, not a PDF of the spreadsheet. This is the largest single improvement available to you. In the file, every calibre and every weight is a number. In the PDF, it is ink.

Delete unused columns rather than hiding them. Say why. An exporter who understands that hidden columns reach you will usually start from a clean workbook instead.

Send the detail sheet. If the workbook also has a summary tab, that is fine. It just is not the one anybody works from.

Declare the totals. Total pallets, total boxes, total net weight, written at the foot of the sheet. Most packhouse software already prints them and some exporters strip them out to make the page fit. They are the only independent check anyone downstream has on every row above them, and a packing list that declares none cannot be reconciled — by you, by your broker, or by anything you buy to do it for you.

Send it at loading, not on arrival. The exporter has the packing list and the invoice on the day they load the container. Receiving them three weeks later, while demurrage accrues on an entry that cannot be filed, is a process problem rather than a paperwork one. The documents in a fresh produce import covers which ones stop a container and when each is due.

The last piece is what happens once the document is in the building. Somebody has to turn forty pallets and six columns into rows in your system, and that cost is measurable. What manual data entry really costs puts a number on it, errors included.

What is worth changing is not who types it, but whether anybody has to. A packing list that arrives, is read against the container it belongs to, and reconciles against its own declared totals is a document nobody needs to open — which is the job Trackberry does with them. The only ones worth opening are the ones that failed the arithmetic.

FAQ #

What is the difference between a packing list and a commercial invoice? #

The packing list says what is in the container; the invoice says what it costs. They describe the same goods from different angles, which is what makes comparing them worthwhile. A disagreement between the two means one of them was written or read wrong.

Why do exporters hide columns in a packing list? #

Because they reused a workbook. The hidden columns usually belong to another customer’s order, or to a working calculation they did not want on the printout. It is not deception, but the data still travels with the file, and anything reading the file rather than the screen will find it.

Which packing list field is most often wrong? #

The box count, and almost always for the same reason: two columns on the sheet look like box counts, where one is the per-row figure and the other is a running total. Check the sum against the declared total before you trust either of them.

My packing list has no box weights. Can I still use it? #

Yes. Net weight divided by box count gives you the box weight, and on tied produce like asparagus it is the tie count multiplied by the weight per tie. Missing box weights are the most recoverable defect on the document.

Do I need the packing list to track my container? #

No. Tracking needs the bill of lading number or the container number. The packing list is what fills in produce, pallets, calibres and quantities once the container is registered — which is what turns a moving dot on a map into a consignment you can sell from.