Extract data from certificates of origin
Unstract reads chamber-stamped and preferential certificates of origin, along with the phytosanitary, fumigation and inspection certificates that travel with them, and returns origin and goods data matched to the invoice in your customs filing or ERP system.
inv. shows 62 ctns on line 2? ask Saffronloom — J.
CERTIFICATE OF ORIGIN · ORIGINAL · 1 OF 1
{ "certificate_number": "NCCI/26/0481173", "exporter": "SAFFRONLOOM TEXTILES PVT. LTD.", "consignee": "FENWICK HOME GOODS INC.", "country_of_origin": "INDIA", "hs_code_line_1": "6302.60", "hs_code_line_2": "6302.91", "invoice_number": "SLT/EXP/2026/0917", "total_packages": 240, "gross_weight_kg": 5460, "certified_on": "17.10.2026"}
Trusted by logistics and supply chain teams around the globe
Origin paperwork turns up stamped, faxed and stapled together
Exporters, chambers, forwarders and inspection agencies each send their own certificate, and no two of them use the same layout.
Stamped originals faxed abroad and rescanned on arrival
A chamber certificate, an EUR.1 and a Form E for the same facts
HS codes struck out and rewritten before the chamber signs
Origin, phytosanitary and fumigation certificates in one scan
Inspection certificates with a result for every lot
Trade compliance teams compare each certificate with the invoice by eye, and an origin or HS code that slips past them becomes a denied preference claim, back duty and a penalty on the importer.
Unstract reads every certificate in the packet, pulls the fields you name, checks origin, goods and packages against the commercial invoice and the entry, and sends the result to your customs filing or ERP system.
Parse, extract and route every origin certificate
Three products that work alone or together: parsing, extraction and automation. Start with the one your compliance desk needs now and add the rest as shipment volume grows.
Parse every certificate of origin into text that keeps its numbered boxes
A certificate of origin splits marks, packages, description and gross weight across narrow columns, and a chamber seal often lands on top of them. LLMWhisperer reads the page with its grid intact, so the HS code stays on the line it belongs to and the carton count never drifts into the marks column.
As a certificate of origin parser it hands layout-kept text to your own LLM, or it opens a wider customs process.
Learn more about LLMWhispererTurn every certificate of origin into one record you can match to the invoice
Write the origin fields you need as a prompt, and each certificate comes back as JSON in one schema: a chamber certificate, an EUR.1, a trade-agreement form, or a phytosanitary or fumigation certificate. This certificate of origin data extractor needs no template per chamber or country. A carton count that disagrees with the invoice, or an HS code that differs from the entry line, comes back flagged with the other document named.
Deploy it as an API, as an ETL pipeline, or as one step inside an orchestrated customs process.
Learn more about Document StudioRun customs clearance with every origin claim checked before filing
Describe in plain English how your team checks a certificate of origin against the rest of the entry packet, and Flow's agents build the workflow: the certificate collected with the invoice, packing list and bill of lading, read, compared line by line, and staged in your customs filing or ERP system. You approve the workflow once, and every shipment then runs through the identical steps.
Choose where it stops: an origin that differs from the invoice, an HS code that does not match the goods, a certificate that is missing from the packet. Those shipments wait for a licensed customs broker with the reason beside the line, and the broker decides whether a preference claim goes on the entry.
Learn more about FlowRead your certificates of origin today. Check the whole entry packet next.
Start for free to parse and extract your own certificates of origin. Automating customs clearance around them starts with a consultation.
Origin, plant health and inspection certificates in one schema
Documents
- Non-preferential certificates of origin
- Preferential certificates of origin
- EUR.1 movement certificates
- Trade-agreement origin forms
- Chamber of commerce certificates
- Phytosanitary Certificates
- Fumigation certificates
- Inspection certificates
- Non-radioactivity Certificates
- Commercial invoices
- Packing lists
- Bills of lading
- Exporter origin declarations
- Any other issuing body's certificate layout
Fields captured
Built for the teams that stand behind an origin claim
Each certificate compared with the client's invoice before the entry is drafted, so the broker sees origin gaps while there is still time to ask the exporter for a corrected copy.
Certificates, phytosanitary and fumigation papers pulled from the shipper's documents at booking, so a missing original is chased before the vessel sails.
Every certificate kept as a searchable record by supplier and HS code, so preference claims and origin audits start from the documents the goods actually shipped with.
Origin and plant-health certificates read for each client's inbound shipments, so held containers are traced to the missing paper the same day.
Origin checked before the entry, not after the audit
Certificates show where you buy and what you claim
A certificate of origin names your exporter, the factory country, the HS code of every line and the invoice it covers. Together they map your supplier relationships. The origin itself is a claim you make to customs: a wrong one exposes the importer to back duty and penalties.
- Encrypted in transit and at rest.
- Certificates and invoices are never used to train models.
- Access by role, branch and client, with every corrected origin, HS code and released flag logged against the certificate number.
- Retention you set, long enough to produce the certificate if customs reviews a preference claim years after entry.
- Brokers and importers that must keep supplier data on their own servers can run Unstract self-hosted.
What trade compliance teams ask about origin certificates
One that reads the certificate as a form, not as loose text. In Unstract, LLMWhisperer keeps the numbered boxes in place, Document Studio uses LLMs to return the fields you named as JSON, and Flow's agents check them against the invoice and entry.
Document Studio returns exporter, consignee, origin, HS codes, packages, weights and the invoice reference from each certificate. Fields are found by what they mean rather than where they sit, so a chamber layout you have never seen works on the first file.
The certificate arrives with the invoice, packing list and bill of lading. Flow reads it with the rest of the packet, compares origin and goods line by line, and stages checked data in your customs filing or ERP system. A licensed broker reviews flagged lines and files.
Yes. EUR.1 movement certificates, trade-agreement origin forms and exporter origin declarations come back in the same schema as a chamber-stamped non-preferential certificate, with the origin criterion captured where the form shows one.
No. Unstract reports what each certificate states and where it disagrees with the invoice or entry. Whether the goods meet the rules of origin for a trade agreement stays a decision for your broker or trade compliance team.
Yes. Inspection, phytosanitary, fumigation and non-radioactivity certificates are read in the same pass as the certificate of origin, so a lot result, a treatment date or a fumigant sits in the shipment record next to the origin.
Yes. LLMWhisperer reads stamp text and handwriting alongside printed values, on faxed and skewed scans too. A value the extraction step cannot read with confidence goes to a person with the page beside it instead of reaching the entry.
The field comes back flagged with both values and the document each came from: a carton count, a gross weight, an HS code or the origin itself. The shipment then waits for a broker to resolve it.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Certificates are encrypted, never used for training, and kept only as long as you choose. Teams that need supplier data on their own servers can self-host. The Trust Center lists each control.
Most teams run live shipments within days of a consultation, where we set the workflow around your suppliers' certificates, your origin checks and your filing system. To test extraction first, start for free and upload one certificate of origin.
Bring certificates from your three largest suppliers to the consultation
Chamber-stamped and preferential certificates of origin, with the phytosanitary, fumigation and inspection certificates that travel beside them. You see each one read on screen, its origin and goods compared with the invoice.