What Customs Entry Intelligence Does
Powered entirely by public government data — USITC HTS 2026, CBP CROSS rulings, OpenSanctions UFLPA, Census Bureau trade stats — with zero proprietary data requirements.
The Mixpeek Difference
Competitors return a single HTS code with no sourcing. Mixpeek returns a ranked classification with GRI basis, alternative headings, confidence score, and direct links to the CBP rulings that support each decision.
Classification Workflow
HTS Classification with CBP Ruling Citations
Classify any product to the 10-digit HTS suffix in seconds, with three relevant CBP CROSS rulings cited automatically — the same citations a licensed broker would find after 20 minutes of manual research.
Key Benefits
- 20–30 minutes of manual research compressed to under 5 seconds
- GRI basis cited (GRI 1, GRI 3(b), etc.) for every classification
- Alternative HTS headings surfaced automatically to flag ambiguous entries
The Mixpeek Difference
Manual document review is error-prone and time-consuming. Mixpeek ingests all three documents simultaneously and runs structured field comparison — catching the BOL/invoice quantity delta that a broker would miss under time pressure.
Document Validation Flow
Cross-Document Validation
Automatically compare commercial invoice, bill of lading, and packing list against each other. Flag quantity discrepancies, value mismatches, and country-of-origin inconsistencies before they become CBP examinations.
Key Benefits
- Catch quantity and value discrepancies before CBP examination
- Country-of-origin validation against USMCA and GSP eligibility rules
- Structured JSON output ready to pre-populate Form 7501
The Mixpeek Difference
S301 rates live in Chapter 99 cross-references, not goods-level HTS rows. Most tools miss them. Mixpeek materializes the full duty stack at ingestion time and joins UFLPA/WRO entity lists at query time for real-time screening.
Duty & Compliance Flow
Section 301 / 232 Duty Exposure & Entity Screening
Calculate total landed duty exposure — MFN rate plus Section 301 or Section 232 adders — and screen every party on the entry against the UFLPA and CBP WRO entity lists in the same pipeline.
Key Benefits
- Full duty stack: MFN + S301 + S232 calculated per line item
- UFLPA and CBP WRO entity screening against OpenSanctions data
- Drawback eligibility and S301 exclusion flags surfaced automatically
How Customs Professionals Use Mixpeek
From licensed brokers to customs technology platforms — Mixpeek's API powers the classification and compliance layer.
Mid-size Licensed Customs Broker
Reduced average entry classification time from 28 minutes to under 90 seconds. Broker team of 12 now handles 3x more entries per day without adding headcount.
Schedule a DemoCustoms Technology Platform
Embedded Mixpeek's classification API into their GTM portal. Launched HTS auto-classification as a premium feature within 6 weeks — zero ETL infrastructure built in-house.
Schedule a DemoImporter of Record (Electronics)
Caught a $340K Section 301 exposure across 14 shipments that a manual broker review had missed. S301 Chapter 99 cross-references were not in their existing HTS lookup tool.
Schedule a DemoWhy Mixpeek Powers Customs Automation Platforms
Public data, private infrastructure
All seven government datasets — USITC HTS, CBP CROSS, OpenSanctions, Census Bureau, Federal Register — are ingested and indexed once. Your platform inherits 35,000+ HTS codes and 199,000+ CBP rulings without building the ETL yourself.
Hierarchical taxonomy at query speed
The 4-level HTS hierarchy (Chapter → Heading → Subheading → Suffix) is materialized at ingestion with learned fusion weights. Queries return Chapter 84 alternatives alongside the best match — not just a single code — enabling GRI analysis at scale.
Multi-tenant namespace isolation
Each brokerage or importer gets a dedicated namespace. Classification signals, ruling preferences, and duty profiles adapt per tenant through Thompson Sampling without cross-contaminating data between clients.
Frequently Asked Questions
What data sources power the classification engine?
Seven public government datasets: USITC HTS 2026 CSV (35,733 HTS codes), CBP CROSS rulings API (~199,000 rulings), Census Bureau international trade API, OpenSanctions UFLPA/WRO entity lists, Federal Register API, USTR Section 301 Chapter 99 cross-references, and CBP ACE entry data. No proprietary data required — all sources are freely available and updated on official government schedules.
How does it handle Section 301 duty rates, which are in Chapter 99 not the goods-level HTS?
S301 rates are stored as Chapter 99 cross-references, not on goods-level HTS rows — most lookup tools miss them entirely. Mixpeek materializes the full duty stack at ingestion time: MFN base rate + Chapter 99 S301 adder + any Section 232 adder for steel and aluminum. The query returns a single landed duty figure per line item rather than requiring the broker to manually sum multiple sources.
Can this integrate with existing brokerage software (ACE, GTM platforms)?
Yes. The output is structured JSON that maps directly to CBP Form 7501 fields: HTS number, country of origin, duty rate, entered value, and party information. This JSON can pre-populate any GTM platform, ABI filing system, or ACE Direct workflow. Mixpeek exposes a REST API — integration is a single POST request per entry.
How does cross-document validation work for invoice vs. BOL discrepancies?
Upload the commercial invoice, bill of lading, and packing list simultaneously. Mixpeek extracts structured fields from each document — quantities, weights, descriptions, values, country of origin, shipper/consignee — and runs a comparison pass. Discrepancies (e.g., BOL shows 500 units, invoice shows 480) are flagged with field-level citations. The broker sees exactly which field on which document doesn't match, not just a generic error.
What confidence threshold triggers a manual review flag?
Configurable per tenant, defaulting to 85%. Below that threshold the entry is flagged for broker review with the top three alternative HTS headings displayed. Above 85%, the classification proceeds automatically with the GRI basis logged for audit. Brokers can tune this threshold based on their risk tolerance and the commodity mix they handle.
Is the UFLPA entity screening real-time?
Yes. OpenSanctions publishes daily entity list updates. Mixpeek ingests these on a 24-hour schedule. Party names on the entry (shipper, manufacturer, supplier) are screened against the current list at query time using fuzzy name matching to catch transliteration variants. Hits are returned with confidence scores and the specific list (UFLPA, WRO, or OFAC cross-reference).