On this page
The practical answer
AI can extract shipment drafts and explain document discrepancies. Check totals and units with explicit rules, preserve evidence, and require qualified human approval. Document preparation does not establish customs eligibility or authorise a filing.
Orders record agreements, commercial invoices record goods and amounts, and packing lists record package contents. Copying between them can conceal a partial shipment or outdated revision. Compare the records before preparing the final package.
The AI output should be a document draft with unresolved questions, without declaring shipment compliance. Start with one shipment type whose source records and reviewer are understood.
An example workflow
From source records to a reviewable package
Freeze the source revision
Extract with evidence
Compare with explicit rules
Resolve discrepancies
Approve the exact package
Record the handoff
Decision at a glance
Choose the right mechanism for each task
| Task | Appropriate mechanism | Release condition |
|---|---|---|
| Extract fields from inconsistent documents | AI draft with a source reference for each field | A reviewer can inspect the original |
| Reconcile quantities, prices and weights | Explicit rules and arithmetic | Differences are resolved or held |
| Prepare shipment document templates | Approved data mapped to agreed fields | The exact revision is approved |
| Decide classification, tariff, origin or filing | Qualified responsible people and current official guidance | Outside this preparation workflow |
Scroll horizontally to see the full comparison.
1. Agree what the package contains and who owns it
Collect the order revision, approved descriptions and commercial terms, invoice draft and warehouse packing record. Give the shipment a stable identifier and record each input’s source. Name the owners of order changes, pricing and packed quantities. A missing warehouse record should create a hold, even if the order appears complete.
Agree the output before connecting systems: a field comparison, draft invoice and packing list, source references, and an exception list. Trade.gov explains that document requirements vary with the shipment and destination. A qualified person should confirm the relevant requirements against current official sources and the parties handling that shipment.
2. Keep extraction separate from calculation
Require a supporting file, page or row for each proposed value. Preserve original text alongside normalised values: “8 USD per piece” needs its unit and currency. Define date formats and authoritative sources for each field. Mark unreadable fields unavailable and request a better copy.
Use ordinary rules to sum packed quantities and calculate line totals. Check invoice currency against the approved terms, and keep net weight, gross weight and package count separate. Do not invent conversion factors or overwrite a conflict with whichever document looks newest. Record the reason for every accepted correction.
3. Work through a partial-shipment discrepancy
Hypothetical example, not a client project: an order lists 12 blue cotton pouches at USD 8 each. The invoice draft still lists 12 units and USD 96. The warehouse record shows two cartons containing five pouches each. The system should display 12 ordered, 12 invoiced and 10 packed, with links to those three records.
AI can draft the question “Is this an approved partial shipment?” It cannot answer it from the numbers alone. Operations confirms the 10-unit shipment; the commercial owner confirms how the remaining two units and any charges will be handled. Only then can the package use the approved quantity and corresponding USD 80 goods subtotal. The original order remains visible rather than being silently rewritten.
4. Draw a firm boundary around customs data preparation
The packing list is evidence about package contents; it does not replace the commercial invoice. Trade.gov describes their different purposes and the importance of consistency. Use those distinctions to build checks, while treating any route-specific document checklist as a separately maintained input with an owner and review date.
This workflow does not determine HS classification, tariff treatment, origin, valuation conclusions or regulatory eligibility, and it does not automatically file declarations. Where an approved specialist record supplies a relevant value, preserve its reference and approval context; do not present a model guess as an authorised determination. Qualified responsible people must resolve those questions using current official requirements and shipment-specific evidence.
5. Approve the exact revision, then record the handoff
Show the source comparison next to the proposed documents. Require the reviewer to resolve each material discrepancy, record any correction and approve a specific package revision. Changing a source quantity, address or commercial term after approval should reopen review. A generic “checked” box does not show which documents or values a person accepted.
Keep “draft”, “awaiting information”, “approved for handoff” and “handed to the responsible party” distinct. Record the recipient, revision and time when handing the package to the authorised logistics or customs professional. A successful file upload proves a technical transfer only; it does not prove filing, acceptance or clearance.
6. Test disagreements and recover without losing evidence
Build a small test set containing a complete shipment, a partial shipment, mixed currencies, a missing weight unit, an illegible scan and a changed order revision. Write the expected exception and responsible owner before running it. Verify that calculations match an independently checked result and that every approved field can be traced to its evidence.
Keep failed extraction sources and allow justified manual entry. Hold packages affected by template changes until mappings are checked. After a transfer timeout, check its record before resending. Run preparation alongside the existing process and record corrections and review effort before expanding.
Before you commit
Before a package leaves review
- Source versions and shipment identifier are fixed.
- Units, currency and totals have explicit checks.
- Every material discrepancy has an owner and resolution.
- The exact document revision has qualified approval.
- Handoff evidence does not imply customs acceptance.
Questions before you start
Can AI complete missing invoice information from a product name?
It can flag gaps and request information. A product name cannot establish commercial terms or specialist customs decisions. Leave the field unresolved until an approved source supplies it.
Do we need AI if all order and warehouse data is structured?
Possibly not. Field mapping, arithmetic and comparison rules may solve the problem more reliably. Add AI where document variation or explanation creates a demonstrated need, and keep the checks outside the model.
Does an approved package mean the shipment can clear customs?
No. It means a named reviewer approved a particular preparation output. Filing, applicable requirements and acceptance remain separate responsibilities and require the qualified parties handling that shipment.
Sources and further reading
The next step
AI integration
If this is the right direction for your business, start with a clear scope, testing plan, and handover.