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. Sensible extracts certificate data into validated JSON for customs compliance, duty optimization, and trade documentation.
Why certificates of origin need specialized extraction
Country-specific formats, agreement-specific fields, and varied issuing bodies create diverse challenges.
USMCA, CPTPP, and EU preferential certificates each require different fields. Sensible detects the agreement and extracts accordingly.
Certificates come from chambers of commerce, customs authorities, or exporters. Sensible handles all issuing formats and layouts.
Certificates list products with HS codes, descriptions, quantities, and values. Sensible extracts each product line for duty determination.
Fields we extract
Extract any data you need from certificates of origin into your desired output schema
Exporter name/address, importer name/address, producer name/address, consignee, certifying authority, chamber of commerce
HS tariff code, product description, quantity, weight, value, origin criterion, country of origin, invoice number/date
Trade agreement, preference criterion, blanket period dates, certifier signature, date of issue, certificate number
Standard chamber-of-commerce-issued certificate for international trade.
European Union certificate of origin for preferential trade agreements.
North American trade certificate for preferential tariff treatment under USMCA.
Supported certificate types
Common certificate formats can be found in Sensible's logistics template library. Certificates for any trade agreement or issuing body can be custom configured in hours.
USMCA, CPTPP, EU-origin (EUR.1), ASEAN (Form D), GSP (Form A), generic certificates
Chamber of commerce certificates, customs authority certificates, self-certified (USMCA/CPTPP), notarized affidavits
Common Questions
Details on certificate of origin data extraction.
Yes. Sensible extracts Harmonized System (HS) tariff codes, product descriptions, quantities, weights, and values for each line item on the certificate.
Sensible extracts the applicable trade agreement (USMCA, CPTPP, EU-origin), preference criterion, producer information, blanket period dates, and any certifier declarations.
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.
Yes. Sensible processes certificates from various issuing bodies and countries. It extracts exporter, importer, country of origin, country of destination, and certifying authority regardless of format.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Documents are deleted after 30 days by default. You can configure shorter retention periods or request immediate deletion via API.
Yes. Sensible offers a free tier with 50 documents per month. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
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.
Sensible processes PDF, PNG, JPG, and TIFF files. PDFs can be native or scanned.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence scoring.
Most documents process in 2 to 10 seconds depending on complexity and page count.