Section 321 of the Tariff Act — the de minimis provision that allows goods valued at $800 or less to enter the United States duty-free — was designed for travelers and individual purchasers. What's happened to it in the e-commerce era is something the original drafters could not have anticipated. CBP now processes millions of Section 321 shipments per month, many arriving in consolidated aircraft loads where a single carrier handles thousands of individual consignee parcels, each technically requiring its own customs entry.
The Type 86 entry format — introduced in 2019 as an ACE-native mechanism for filing Section 321 shipments — exists specifically to handle this volume. Compared to a formal entry (Type 01) or an informal entry (Type 11), a Type 86 requires less data: no bonds, no merchandise processing fee, no formal liquidation. But "less data" doesn't mean no data. And at the volumes involved in e-commerce logistics, the data gathering and filing process for Type 86 entries is a genuine operational challenge for customs brokers and freight forwarders handling the work.
What a Type 86 Entry Actually Requires
The minimum data requirements for a Type 86 entry under the current ACE specifications include: the importer of record name and address, a description of the merchandise, the 10-digit HTS number, quantity and unit of measure, country of origin, and declared value. For shipments that trigger PGA (Partner Government Agency) oversight — anything touching FDA, USDA, CPSC, or other agencies — additional fields are required even on low-value entries. The de minimis threshold doesn't exempt goods from PGA requirements; it only exempts them from duty.
This matters because a significant fraction of e-commerce import volume is consumer goods: apparel, electronics, cosmetics, food supplements, toys. Many of these categories have PGA requirements that don't disappear because the shipment is under $800. An apparel shipment under $800 still needs a correct HTS, country of origin, and if it's labeled as containing wool or fur — applicable textile and fur labeling disclosures. A cosmetic product still needs FDA product code and establishment data on the entry.
So while Type 86 is administratively lighter than a formal entry, the practical work of assembling the correct fields from source documents remains. And at high volume, that per-entry labor cost is the entire margin problem.
The Volume Economics Problem
Consider a growing e-commerce logistics operation consolidating shipments from multiple overseas suppliers. On a moderately busy week, they might be processing 2,000–4,000 individual Type 86 entries per day across various arrival ports. At even a conservative 3–5 minutes of manual data entry per entry, the labor math doesn't work at competitive pricing. The economics only work if the per-entry cost is fractions of a minute — which means near-complete automation of the data extraction and field mapping step.
The challenge is that the source documents for Type 86 entries are rarely uniform. You might have a commercial invoice in a PDF from the exporter, a carrier manifest in a CSV or EDI format, and a packing list in Excel — and you need to reconcile these three sources to produce a complete, accurate entry record. The reconciliation step — which document wins when there's a discrepancy in piece count, which field to use for goods description when the invoice says "Apparel Accessories" and the manifest says "Knit Beanie Hat" — requires either a human decision or an extraction system that understands which source has authority for which field type.
Where Extraction Automation Changes the Equation
The fields that benefit most from extraction automation in a Type 86 workflow are the ones that appear consistently in carrier manifest data and commercial invoice data: consignee name and address, declared value, quantity, country of origin, and goods description. These are high-confidence extraction targets when the source document is a digital carrier manifest or a well-structured commercial invoice.
The HTS classification step is different. For a genuinely ambiguous goods description — "Fashion Accessories" appearing in a manifest where the underlying product could be anything from jewelry to hair clips to belt buckles — extraction of the description is straightforward but classification is not. That's a decision that either requires a more detailed description from the exporter or human review. We think it's important to be clear about this boundary: extraction automation reliably speeds up the data gathering step; it doesn't eliminate the need for classification judgment on ambiguous entries.
What automation does well is detecting which entries can be filed with high confidence versus which entries need a human touchpoint. A shipment with a detailed goods description, a matching invoice value, a clean country-of-origin field from a country with no active trade programs of concern, and an HTS that maps unambiguously — that entry can be processed without manual review. A shipment with a vague description, a value that seems inconsistent with the declared quantity, or a PGA flag — that entry should be routed for review before filing, not processed automatically.
The Section 321 Scrutiny Problem
It would be incomplete to discuss Type 86 automation without acknowledging that CBP's approach to Section 321 oversight is evolving. There has been sustained Congressional and agency interest in tightening de minimis enforcement, particularly for shipments from certain origin countries, for goods that may be subject to Section 301 tariffs, and for controlled goods that should not be entering through the de minimis channel at all.
Executive actions in 2025 modified the de minimis treatment for certain shipments, requiring formal entry for goods previously eligible for Section 321 treatment from specific origins. The rules in this space have been moving, and any automation approach that hard-codes assumptions about which shipments are eligible for Type 86 without checking current eligibility criteria is a liability.
We don't say this to create alarm — the de minimis framework is still functioning and widely used. We say it because an automation system that helps you process Type 86 entries faster is less valuable than one that also flags entries that may no longer be eligible for de minimis treatment under current rules. That eligibility check — country of origin, HTS, current trade program status — needs to be part of the pipeline, not something you check manually after the fact.
ACE Filing Mechanics for Type 86
Type 86 entries are filed through ACE as advance data under the Air AMS or Ocean AMS program (for carrier data) plus the actual entry filing under the CBP-approved ACE Entry Summary format for informal entries. For most high-volume e-commerce operators, entry filing is handled through a licensed customs broker who has ACE filing credentials, with the broker receiving pre-formatted entry data from the logistics operator's system.
The integration point in this workflow is typically between the logistics operator's warehouse management system or order management system and the broker's filing system. What's being exchanged is a structured data record per shipment — not a PDF. The role of extraction automation in this workflow is earlier in the chain: taking the carrier manifest, commercial invoice, or packing list as input and producing the structured per-shipment record that feeds the broker's ACE filing workflow. That transformation — unstructured or semi-structured document to clean structured data record — is where most of the manual work lives today, and where automation earns its keep.
For operations at 1,000+ Type 86 entries per day, the difference between a manual extraction process and an automated one isn't a productivity improvement — it's the difference between a viable business model and one that can't grow without proportional headcount addition. The document extraction step is the bottleneck, and solving it changes the unit economics of the operation entirely.