USTR posts a new Section 301 list at 3:14 p.m. on a Tuesday. Six hundred and twelve new HTS codes, an additional 15% ad valorem, effective in 30 days. By 3:20 p.m., somebody in your finance org has emailed asking what this means for next quarter.
For most trade compliance teams, what follows is a week. For the operators on Mamora, it's an afternoon. The gap isn't software-magic. It's a series of small architectural choices that compound. This is the playbook.
The legacy process, with timings
Here is what we used to do, and what almost every FTZ team without modern software still does:
- Read the list. A senior compliance person reads the Federal Register notice, the USTR annex, and any accompanying CBP CSMS message. (45 minutes.)
- Cross-reference to internal HTS codes. Compliance pulls the master HTS list out of the WMS or ERP, dumps it into Excel, and manually flags which of the 6,000 to 80,000 internal codes match the 600 in the new annex. (4 to 8 hours, depending on overlap.)
- Reprice. For each flagged code, look up the on-hand inventory in the FTZ, calculate the additional duty exposure, and propagate to the duty-rate engine inside the trade software. (1 to 2 days, because the software was usually written when faxes were a verb.)
- Communicate. Email finance, email procurement, email the 3PL, update the quarterly forecast. (Half a day.)
Total: 3 to 5 working days, assuming nothing else is on fire. Two of those days are spent waiting on a tariff engine to recompute.
The painful part of the legacy process isn't the work. It's the four days the finance team doesn't have an answer. CFOs make decisions on what they know now, not what they'll know in a week. By the time you have the answer, three commitments have already gone out the door.
The Mamora process, with timings
Here's the same exercise running on Mamora. We'll use a real anonymized customer (apparel importer, 14,200 active SKUs, FTZ #161 Charleston) for the timings.
- Tariff feed lights up. Mamora subscribes to the USTR and CBP CSMS feeds directly. The new list lands as structured data in the tariff engine within the hour of publication. (0 minutes of your time.)
- Auto-classification flags inventory. Every SKU in our system has a confirmed HTS at the 10-digit level, signed and dated by a licensed broker. We cross-walk the new annex against the SKU master automatically. For this customer, 2,140 SKUs were affected. (~5 minutes for compliance to review.)
- Reprice runs as a query. Because the tariff engine is event-sourced (more on this in our reconciliation post), we don't recompute the world. We just run the new rate against on-hand FTZ inventory plus the next 90 days of inbound POs. (Sub-minute.)
- Communicate. The Mamora dashboard generates a one-page exposure summary that's already in the format finance wants: duty exposure by SKU group, by week, against forecasted sell-through. The compliance lead reviews, sends. (10 to 15 minutes.)
Total: about 20 minutes of compliance team time.
The architectural choice that makes this possible
The reason this is fast is not that we have more engineers than the legacy vendors. It's three specific design decisions:
One: tariffs are data, not configuration. When USTR publishes a list, we don't ask customers to "configure" anything. The tariff is a row in a versioned table with an effective date. Reads against it are O(1). The legacy systems make tariffs feel like a software update because, internally, they are one.
Two: classification is a property of the SKU, not the entry. Every SKU carries a current HTS classification, signed by a broker, with audit history. When a tariff changes, we don't have to re-classify. We just have to recompute.
Three: reprice is a query, not a job. Our duty engine is read-after-write consistent. There's no overnight batch. The CFO can ask "what would happen if this list went into effect today" and get an answer before they finish asking.
What this means in practice
If you operate an FTZ and you're still doing the four-day version of this work, the cost isn't the time. It's that the CFO learns to stop asking. By the time you have the answer, the question has moved on. Software should be measured against the second-order effect: does it make the rest of the business smarter about tariffs, or does it make the tariff team a bottleneck?
If you want to see the 20-minute version on your actual data, we'll run a free model. Bring a recent USTR annex (your choice) and your SKU master. We'll show you the exposure before lunch.