Logistics

Extract certificates of origin to structured JSON

Certificates of origin verify where goods were produced, enabling preferential tariff treatment under trade agreements. Formats vary by issuing body and agreement. Use Sensible to get structured certificate data for customs compliance, duty optimization, and trade documentation.

customs clearance | trade compliance | tariff classification

Validated JSON

Schema-enforced output; every field matches your contract

Source coordinates

Every value links back to page + bounding box for audit

Per-document pricing

Predictable cost. No token-volatility surprises

Trusted by teams turning documents into production data

What makes certificates of origin hard to extract

Issuing bodies, trade agreements, and country formats all differ, and HS codes and product detail have to land exactly right. Hybrid extraction reads each format; validation holds the codes to your schema.

01

Trade Agreement Variation

USMCA demands different fields than CPTPP or EU preferential certificates. Each trade agreement gets its own extraction configuration, capturing the specific preference criteria, blanket period, and certifier declarations it requires.

02

Multi-Format Issuing Bodies

Chambers of commerce, customs authorities, and exporters each issue certificates in their own format. The hybrid approach (LLM parsing for layout variation, SenseML rules for field validation) handles them all.

03

HS Code and Product Detail

HS codes, product descriptions, quantities, values, origin criteria: each line item is extracted with its full trade classification detail, enabling automated duty calculation and compliance checks.

Managed services

Don't want to build it? We'll write your configs from your samples.

Solutions engineers handle plan, build, deploy, and adjust on your behalf. You see clean JSON in your API response. Same engine as self-serve, just with the configuration work outsourced.

What's included

01Plan.Engineers review your samples and pick the right method

02Build.SenseML configs written from your samples

03Deploy.Same engine as self-serve, ready for production

04Adjust.We update configs when formats shift or new edge cases appear

05Integrate.Help with custom integration into your downstream systems

Fields we extract

We configure every certificate of origin extraction to your exact schema, not a fixed field list. The fields below are the ones trade teams pull most often — tell us what your customs-compliance workflow needs and we map the rest.

01

Parties

Exporter name/address, importer name/address, producer name/address, consignee, certifying authority, chamber of commerce

02

Product detail

HS tariff code, product description, quantity, weight, value, origin criterion, country of origin, invoice number/date

03

Certification

Trade agreement, preference criterion, blanket period dates, certifier signature, date of issue, certificate number

config.json

SenseML

{ /* SenseML: certificate of origin extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "exporter", "description": "exporter name, exporter, certifier, producer" },
{ "id": "hs_code", "description": "HS code, tariff classification, harmonized code" },
{ "id": "country_of_origin", "description": "country of origin, origin country, goods originating in" },
{ "id": "trade_agreement", "description": "trade agreement, USMCA, CPTPP, preferential treatment" }
// + more fields, mapped to your schema
]
}
}
]
}

Supported certificate types

Sensible processes certificates for USMCA, CPTPP, EU, ASEAN, and other trade agreements. New certificate formats from any issuing body can be configured to your customs compliance schema in hours.

By trade agreement

USMCA, CPTPP, EU-origin (EUR.1), ASEAN (Form D), GSP (Form A), generic certificates

By issuing body

Chamber of commerce certificates, customs authority certificates, self-certified (USMCA/CPTPP), notarized affidavits

Common Questions

Answers about trade agreement support, HS code extraction, and issuing body formats.

Can Sensible extract HS codes from certificates of origin?

Yes. By default Sensible captures Harmonized System (HS) tariff codes, product descriptions, quantities, weights, and values for each line item. What gets pulled per line is configuration, so you can extend it to country-specific codes or additional commercial detail your customs process tracks.

What trade agreement fields does Sensible capture?

The default config reads the applicable trade agreement (USMCA, CPTPP, EU-origin), preference criterion, producer information, blanket period dates, and certifier declarations. These are starting fields defined in configuration. Agreements and forms not yet covered get added when you bring them.

Can Sensible detect signatures on certificates of origin?

Sensible detects signature presence and extracts the signatory name, title, date, and company when printed. Signature image extraction is not supported, but presence/absence detection is available.

Does Sensible handle certificates of origin from different countries?

Yes. Certificates come from many issuing bodies and countries, and Sensible reads exporter, importer, country of origin, country of destination, and certifying authority across those layouts. The named ones are examples, not a fixed list. A format that hasn't been seen before gets configured to fit.

Do you support webhooks?

Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.

Does Sensible support human review?

Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.

What security certifications does Sensible have?

Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.

How long is document data retained?

Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.

Is there a free trial?

Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.

How is pricing structured?

Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.

How do I integrate with Sensible?

Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.

What file formats does Sensible support?

Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.

How accurate is the extraction?

Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.

How fast is document processing?

Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.

Start free

Turn your next certificate of origin into JSON.

Free 14-day trial. No credit card required. Start extracting in minutes.