How to Translate a Packing List

A packing list translation must make the shipment readable without changing the shipment itself. This guide shows how to translate the labels and descriptions while protecting every quantity, weight, code, and package reference.

Know What a Packing List Contains

The U.S. International Trade Administration lists the seller, buyer, shipper, invoice number, shipment date, transport method, carrier, package count, item descriptions, package types, net and gross weights, marks, and dimensions among the common fields in an export packing list.

Before translating, separate those fields into text that needs translation and data that must stay unchanged.

Field	Translate?	Rule
Column headings	Yes	Use clear, standard logistics terms
Product descriptions	Yes	Keep the same level of detail as the source
Handling or packing notes	Yes	Preserve warnings and conditions exactly
Company names	Usually no	Use an official translated legal name only if one exists
Addresses	Usually no	Keep the original; add an official transliteration separately if requested
SKU and item codes	No	Copy character for character
Invoice and order numbers	No	Copy character for character
Package and container numbers	No	Copy character for character
Shipment dates	Usually no	Keep the meaning unchanged; clarify an ambiguous format if needed
Quantities, weights, and dimensions	No	Keep the numeric values and units unchanged
HS codes	No	Translation must not reclassify the goods

1. Check the Packing List Before Translation

1. Confirm the required language. Ask the importer, overseas buyer, customs broker, or freight forwarder which language they need. Trade.gov recommends checking document requirements with the foreign customer or freight forwarder because destination and product requirements vary.

2. Use the final source file. Confirm that the packing list includes the latest quantities, package count, weights, and shipping details. Translating an earlier version creates two documents that look valid but describe different shipments.

3. Compare it with the commercial invoice. Check that product descriptions, quantities, package details, and shipment references agree. A packing list supports cargo inspection, but it does not replace the commercial invoice.

If the invoice also needs translation, use the same terminology and follow this guide to translating invoices and receipts.

2. Mark Fields That Must Not Change

1. Highlight every protected value. Mark SKUs, invoice numbers, purchase order numbers, lot numbers, container numbers, package marks, quantities, weights, dimensions, and dates as do-not-translate content.

2. Keep units attached to their values. Preserve entries such as 25 kg, 80 cm, and 1.5 m³ exactly unless the recipient explicitly requests a conversion. NIST recommends using number and unit symbols when expressing measured values, which also reduces ambiguity across languages.

3. Protect HS codes if they appear. The World Customs Organization defines the international HS base as six-digit commodity codes. Do not translate, shorten, or guess a replacement code; ask a customs specialist to resolve any classification question.

4. Avoid automatic number localization. Do not turn 1,250.50 into 1.250,50 unless the recipient specifically requires the target convention. A punctuation change can make a quantity or weight ambiguous.

5. Clarify ambiguous dates without changing them. If 03/04/2026 could mean March 4 or April 3, confirm the source date and write the month as a word. Keep the original numeric date alongside it when the recipient needs to compare documents.

3. Translate Product Descriptions Consistently

1. Translate the product, material, and package type. A useful description distinguishes items clearly: stainless-steel screws, packed in 20 cartons is safer than shortening the line to hardware.

2. Use one translation per repeated item. If cotton shirts appears on twelve rows, use the same target-language term on all twelve. Create a short glossary before translating large lists.

3. Preserve model names and trademarks. Translate the surrounding description, but keep registered product names and model numbers unchanged unless the company provides an official localized name.

4. Keep handling instructions explicit. Translate notes such as keep dry, fragile, do not stack, or this side up without softening or shortening them.

4. Preserve the Table Layout

Packing lists are commonly prepared as PDF, XLSX, or DOCX files. Rebuilding the table by copying text into a separate document creates unnecessary opportunities for missing rows and shifted columns.

1. Upload the original file. Open the OpenL Packing List Translator, then upload the PDF, Excel, or Word packing list. The page supports packing-list translation while retaining item codes, quantities, and table structure.

2. Select the target language. Match the language requested by the importer, freight forwarder, buyer, or customs authority.

3. Download both reviewable outputs. Use the translated document for delivery and the bilingual version for side-by-side checking where available.

4. Inspect the table before editing. Check that text expansion has not clipped descriptions, pushed values into adjacent columns, or moved a row onto the wrong page.

For workbooks with formulas or multiple sheets, follow the additional safeguards in How to Translate Excel Online.

5. Compare the Translation with the Original

Review the two files row by row. A fluent description cannot compensate for one incorrect digit.

1. Match the row and package counts. Confirm that the translated file has the same number of line items, cartons, pallets, crates, or other packages as the source.

2. Compare all numeric values. Check quantities, net weights, gross weights, dimensions, and totals character by character.

3. Compare every identifier. Verify invoice numbers, purchase order numbers, SKUs, lot numbers, container numbers, marks, and HS codes.

4. Check terminology and warnings. Confirm that repeated products use the same translation and that no handling instruction is missing.

5. Ask the responsible trade professional to review it. For customs or regulated shipments, have the exporter, importer, broker, or freight forwarder confirm the final document. Translation software does not determine whether a destination requires additional paperwork or a particular document format.

Final Packing List Checklist

• The buyer, seller, shipper, and delivery details match the source
• The packing list agrees with the commercial invoice
• Every source row appears once in the translation
• Product descriptions are complete and consistent
• SKUs, order numbers, lot numbers, and package marks are unchanged
• Quantities, package counts, and dimensions match
• Net and gross weights match
• Unit symbols and decimal separators are unambiguous
• HS codes are unchanged and reviewed where necessary
• Handling instructions are complete
• No table text is clipped, wrapped into the wrong row, or placed under the wrong column
• The importer, broker, or freight forwarder has confirmed any destination-specific requirement

For a broader final review, use the 15-point translation QA checklist after completing the shipment-specific checks above.

The safest packing list translation changes only what the reader needs to understand. Protect the shipment data, translate descriptions consistently, and compare the final document against both the source and the commercial invoice.

Ready to translate your file? Upload it to the OpenL Packing List Translator and download a layout-preserving translated packing list.

Sources

• International Trade Administration: Common Export Documents — identifies common packing-list fields, explains its role in cargo checks, and distinguishes it from the commercial invoice.
• World Customs Organization: What Is the Harmonized System? — explains the international six-digit HS product-classification system.
• NIST Guide to the SI, Chapter 9 — provides conventions for expressing measurement values and unit symbols.
• OpenL Packing List Translator — documents supported packing-list formats, languages, table preservation, and bilingual review output.