Trade fields
Declaration values stay explicit
Customs values, declarations, references, and shipment metadata can be returned as named fields instead of buried inside text.
Customs document OCR API
Trade compliance OCR
Turn customs paperwork into structured trade data instead of manual entry and email chains.
Customs and trade documents combine shipment details, party blocks, declarations, and compliance data across many layouts. LeapOCR helps teams extract those fields into structured output that fits logistics and compliance workflows.
Why teams use this
Extract shipment references, customs values, party blocks, and declaration fields.
Support scanned documents, freight PDFs, and mixed customs paperwork.
Return structured JSON for logistics and compliance systems with markdown available for review.
Trade data request
The useful customs workflow is the one that converts paperwork into named trade and shipment fields.
Customs extraction request
{ "url": "https://example.com/customs-document.pdf", "file_name": "customs-document.pdf", "format": "structured", "instructions": "Extract shipment references, parties, declaration fields, and values."}
Why it works
Why customs documents need dedicated extraction
The difficult part is not only OCR. It is producing data that fits trade and compliance workflows cleanly.
Messy layouts
Support mixed paperwork and scans
Customs documents vary widely by country, carrier, and forwarder, which is why layout resilience matters.
Compliance review
Keep the document readable when needed
Readable output helps compliance and ops teams review the source document during exceptions or audits.
What you control
What logistics and compliance teams usually extract
The useful customs record is the one that downstream trade systems and reviewers can act on immediately.
references
Shipment keys
Shipment, entry, and booking references
These references usually tie the customs document back to the shipment and trade workflow.
parties
Trade actors
Importer, exporter, and related parties
Party blocks need to remain separate because they drive compliance and clearance logic.
values
Trade data
Declared values and related fields
Useful workflows extract customs values, weights, and similar data into explicit fields rather than page prose.
review
Readable mode
Preserve the document for audits
Readable output supports compliance checks and trade exceptions when teams need to revisit the source layout.
Examples
Two common customs-document workflows
Most teams either need a trade-ready structured record or a readable document for compliance review.
Compliance system handoff
Return a structured customs record
Useful when customs paperwork needs to feed a trade, logistics, or compliance workflow directly.
Customs JSON
json
{ "shipment_reference": "BK-440182", "importer_name": "Northwind Distribution", "declared_value": 18420.0, "currency": "USD"}
Audit review
Keep customs paperwork readable for exceptions
Useful when a compliance or ops team needs to inspect the source document during an exception or audit.
Markdown excerpt
md
# Customs declaration- Shipment reference: BK-440182- Importer: Northwind Distribution- Declared value: 18420.00 USD
FAQ
Questions teams ask before wiring this up
Straight answers for teams evaluating how this workflow fits into production.
Can LeapOCR extract shipment references and trade values from customs documents?
Yes. Customs workflows can return shipment keys, party data, declared values, and other trade fields as structured output.
Why is customs document OCR different from generic OCR?
Because customs workflows need named compliance and trade fields that fit downstream systems, not only readable page text.
Can teams still keep a readable customs document view?
Yes. Readable output remains useful for audits, exceptions, and compliance review while JSON powers the main workflow.
Ready to test
Test customs paperwork on a logistics- and compliance-ready OCR API
Run a real customs document and check whether the extracted fields fit your trade workflow without another parsing pass.