TMS Customs Fields Setup After the De Minimis End

Why Your TMS Customs Setup Is Already Out of Date

If your TMS still routes low-value cross-border parcels through a Type 86 / Section 321 workflow, that workflow is dead. Paper entry forms are no longer accepted for low-value imports, and affected products can't be entered using Entry Type 86, with Entry Type 11 (informal) and Entry Type 01 (formal) now the only acceptable paths. This isn't a future-planning exercise anymore. It's a configuration gap you're operating with right now.

Here's the timeline that matters for your de minimis TMS setup. CBP issued two interim final rules on June 24, 2026, indefinitely suspending the administrative de minimis exemption under 19 U.S.C. § 1321, with one rule covering the international postal network and the other covering air cargo, express couriers, ocean, and truck. The non-postal suspension took effect June 24, 2026; the postal version followed a month later. On top of that, the One Big Beautiful Bill Act, signed into law on July 4, 2025, eliminates the de minimis exemption entirely, effective July 1, 2027, making the current entry process a bridge to a permanent structural change rather than a temporary emergency measure. Translation: there is no scenario where this reverts to the old $800 duty-free model. Build for formal/informal entry as your default, not as an edge case.

If your TMS was configured any time before mid-2025, it was almost certainly built around manifest-style clearance under Type 86, which has been eliminated as of August 29, 2025. That means your entry-type decision tree, your field mappings, and probably your broker integration are all pointing at a process that CBP no longer accepts. Multi-carrier platforms serving direct-to-consumer merchants, including Easyship, Shippo, and ShipStation/ShipEngine, pushed emergency merchant guidance through 2025 as this unfolded. This post is the TMS-admin-side version of that scramble: the actual config work, not the advisory memo. Teams running MercuryGate, Descartes, Oracle TM, or Cargoson for multi-carrier connectivity are all facing the identical reconfiguration problem, regardless of which platform sits in the stack.

What You Need Before You Touch the Config

Gather these four things before you open a single config screen, because half of the rework requests we see start with someone discovering mid-migration that they're missing one of these.

• An active customs bond. Type 11 informal entries generally don't require one for non-regulated goods, but Type 01 formal entries do, and you won't know which bucket most of your volume falls into until you've run step 2 below.
• A designated customs broker with ABI (Automated Broker Interface) access, or a carrier brokerage service such as FedEx Trade Networks, UPS Brokerage, or DHL Global Forwarding. Confirm they're already filing under the new entry types, not still quoting Type 86 pricing.
• A clean product master with 10-digit HTS codes and country of origin per SKU. This is the single biggest point of failure in every reconfiguration we've seen. A 6-digit HS code is not a 10-digit HTS code, and your TMS needs to know the difference.
• An Importer of Record (IOR) number — an EIN, SSN, or CBP-assigned number — mapped to the correct legal entity for each shipping lane.

Step-by-Step: Reconfiguring Customs Fields in Your TMS

This is the sequence we'd run on a live system, in order, with checkpoints built in so you're not discovering a gap at go-live.

1. Audit the product master for missing or short HTS codes and country-of-origin gaps. Pull a report of every active SKU and flag anything still sitting on a 6-digit HS code only. The first 6 digits are the international HS level, and a 6-digit code is insufficient for US entry purposes — you need the full 10-digit HTS line from the USITC schedule. Expect this audit to take longer than you think if your product master was built by a merchandising team with no customs context.
2. Rebuild your entry-type decision logic. Retire the default "Section 321 manifest / Type 86" routing rule entirely. Set formal entry (Type 01) or informal entry (Type 11) as the fallback for all shipments under $800, since Type 11 covers shipments at $2,500 or less for non-regulated goods, while Type 01 applies above that threshold or for regulated goods. Your TMS routing rule should check shipment value, HTS classification, and whether the goods are subject to Partner Government Agency (PGA) requirements, then assign the entry type automatically rather than defaulting to a now-defunct path.
3. Map CBP ACE data elements to TMS fields one-to-one. At minimum you need shipper and consignee address, the full 10-digit HTS code, declared value, country of origin, mode of transport, and the bill of lading or AWB number. These are close to the same elements a Type 86 filing required — the 10-digit HTS code, seller and buyer information, country of origin, and shipment data — except now they're mandatory on nearly every filing type, not just low-value ones. If your TMS has a free-text "customs description" field standing in for structured HTS data, this is the step where that gets replaced with a real lookup field tied to hts.usitc.gov classifications.
4. Connect or re-test your broker/EDI link. Whether you're using ABI, EDI 350/355, or a carrier brokerage API, confirm entry data transmits before the shipment arrives at the port, not after. A lag here is what causes holds, and holds on formal entries cost more in demurrage than holds ever did under the old manifest process.
5. Add a landed-cost calculation step to rate shopping. Duty, Merchandise Processing Fee (MPF), and Harbor Maintenance Fee (HMF) all now apply to shipments that used to clear duty-free. Surface these at label purchase, not as a surprise invoice from your broker three weeks later. This is also the point where finance teams usually start paying attention to your TMS project, so get the number right.
6. Run parallel/shadow entries for one week before full cutover. Keep your old config visible but inactive, and file test entries under the new logic against real shipment data. Compare the output against what your broker actually files with CBP.
7. Brief exception handlers on PGA flags. Partner Government Agency requirements (FDA, USDA, CPSC, and others) don't disappear just because the entry type changed. Confirm applicable PGA flags by looking up the HTS code for each SKU category before go-live, and make sure whoever handles exceptions knows which holds are PGA-related versus which are plain HTS or valuation errors.

How You Know It Worked

Pull an ACE entry summary query for your test shipments and confirm zero "missing data" holds across the batch. Then check that declared value and the calculated duty amount match your landed-cost estimate within a tolerance you've defined in advance — 2% is a reasonable starting point for most catalogs. If your test batch clears with no manual broker intervention and the duty figures reconcile, you're ready to flip the switch on live volume. If you're still seeing manual broker calls to "clarify" HTS codes, you're not ready, no matter what the calendar says.

Failure Mode: The Manifest Hold

Here's the one that actually happens. A shipment gets stuck at the port because the HTS field was left at 6 digits instead of 10, or the declared value in your TMS doesn't match the commercial invoice the broker filed. Under the old Type 86 process this might have gone unnoticed since full HTS detail wasn't always enforced at the manifest level. Under formal and informal entry, it stops the shipment cold.

The fix is a pre-manifest validation rule inside the TMS, not a manual spot-check. Block tender if the HTS field length is under 10 digits, or if country of origin is blank. Don't let the shipment leave your warehouse system with incomplete customs data in the first place — it's far cheaper to catch this at pick-and-pack than at the port. For holds that do slip through, set a hard SLA for escalation to your broker, something like 2 hours from the hold flag, rather than letting it age in a queue nobody's watching. Ports don't call you to tell you a shipment is stuck. You find out when the consignee does.

Where This Fits in Your Multi-Carrier Stack

Customs and brokerage capability is now a selection criterion on par with rating and label generation when you're evaluating TMS or multi-carrier tooling, not an afterthought bolted on for a handful of cross-border lanes. Platforms like Cargoson, Descartes, MercuryGate, Shiptify, Sendcloud, and ClickPost all get evaluated on this axis now, specifically on how cleanly they pass HTS, COO, and entry-type data to a broker's ABI connection without a human retyping it. If you're mid-procurement or renewing a contract this year, ask vendors to show you their ACE data mapping, not just their carrier label coverage. The label was never the hard part. The customs data was.

Quick Checklist for Your SOP Pack

• Audit product master: flag every SKU still on a 6-digit HS code instead of 10-digit HTS
• Kill the Type 86 / manifest routing default; set Type 01/Type 11 logic based on value and PGA status
• Map ACE data elements (HTS, COO, declared value, shipper/consignee, BOL/AWB) one-to-one in your TMS
• Re-test your broker EDI/ABI connection for pre-arrival transmission
• Add duty, MPF, and HMF to landed-cost display at rate shopping
• Run a one-week shadow/parallel entry test before cutover
• Train exception handlers on PGA flag lookups and hold escalation SLAs
• Build a pre-manifest validation block for incomplete HTS or missing COO

Print it, hand it to whoever owns customs exceptions on your team, and run the audit this week. The entry types changed months ago. Your config shouldn't still be arguing with CBP about it.