Field reference · 4 minute read

The packing list fields
worth getting right.

Supplier layouts vary. This checklist gives your team a consistent starting point for reviewing a packing list and preparing receiving data.

Shipment references

  • Packing list number: the supplier’s identifier for the document.
  • Purchase order: the reference that connects the shipment with your order.
  • Shipper and consignee: who sends and receives the goods.
  • Document date: preserve the source value and confirm ambiguous formats such as 03/04/2026.

Product and packing details

  • Product code or SKU: retain punctuation, leading zeroes, and variant suffixes.
  • Description: keep enough detail to distinguish variants.
  • Quantity and unit: record the number alongside pieces, sets, cases, or another source unit.
  • Carton count and carton marks: check whether counts refer to a product line or shared cartons.

Weight and dimensions

Capture net weight and gross weight in separate fields. Net weight generally describes the goods themselves, while gross weight includes packaging. Check the document’s definitions and units rather than assuming every supplier uses the same convention.

Record dimensions with their units and ordering. If you calculate volume, distinguish your calculated value from a volume printed by the supplier.

A small example

Source label CSV field Review check
Item No. product_sku Keep leading zeroes
QTY / PCS quantity Confirm pieces
CTNS carton_count Check shared cartons
G.W. / KGS gross_weight_kg Check row vs shipment total

Missing is different from zero

A document can omit a field, leave it unreadable, or use a value that conflicts with another page. Keep those states visible in your review process. Do not guess a missing SKU, weight, or customs classification.

This checklist supports data preparation; it does not determine customs requirements or replace your broker’s instructions. Confirm the required documents and fields for your shipment with the responsible operations team.

Next: turn these fields into a consistent CSV, or explore the CartonField sample.