AI customs entry automation breaks on a product master that stores conclusions

Altana announced on 21 July that it had acquired Cervo AI, whose agentic entry writer drafts submission-ready customs entries out of unstructured shipment documents. The pitch for AI customs entry automation is a throughput number: brokers can process five times as many entries. Evan Smith, Altana’s co-founder and CEO, described the combined system as running “from the moment goods are classified to the moment the entry clears.”

Start with the first clause in that sentence. Classification is where the money is decided, and it is the weakest record in most importers’ systems.

TL;DR: AI customs entry automation multiplies entries, not correctness. The duty owed on a shipment is decided upstream of any model by three fields most item masters hold badly — the HTS subheading, the country-of-origin determination, and whether the good already sits under Section 232. Two US tariff actions this month made the same USMCA flag mean opposite things four days apart. If your master stores “duty-free” as a conclusion instead of the facts a rule runs over, a rule change makes your records wrong overnight while nothing about the product changes.

The rate is the easy part

Tariff volatility gets discussed as though the difficulty were keeping up with rates. It isn’t. A rate is a lookup — a number attached to a tariff line, published, dated, machine-readable. Any competent trade system absorbs a new one in an afternoon, and this is precisely the part vendors demo.

What actually decides the duty sits upstream:

• the HTS subheading the good falls on
• the country of origin, which is a legal determination about where substantial transformation occurred, not where the container was loaded
• whether the good is already covered by a Section 232 action, which changes its treatment under other programs

Those three fields decide everything downstream. In most companies they are inherited — set once at item creation by whoever onboarded the SKU, copied from a supplier’s paperwork, and never revisited. There is no owner. There is frequently no recorded reasoning. And they are exactly the fields an agentic entry writer reads before it drafts anything.

Four days apart, opposite answers on the same field

July gave us the cleanest illustration of this I have seen.

On 23 July, USTR announced a Section 301 action on forced-labour grounds, in force at 12:01 a.m. Eastern on 24 July: an additional 10% or 12.5% duty across 60 economies — 10% for the seventeen that have imposed a forced-labour import prohibition or committed to, 12.5% for most of the rest, with a net-of-MFN structure for the EU, Taiwan, Japan, South Korea and Switzerland. Goods of Canada and Mexico entered free of duty under USMCA are exempt.

Three days before that, on 20 July, three proclamations under Section 338 of the Tariff Act of 1930 imposed an additional 50% on a set of Canadian goods, effective 19 August. The White House fact sheet is explicit that these apply regardless of whether a good originates under USMCA.

Same flag. Two programs. Opposite consequences.

	Section 301 forced-labour action	Section 338 Canada proclamations
Announced / in force	23 July 2026 / 24 July 2026, 12:01 a.m. ET	20 July 2026 / 19 August 2026
Additional duty	10% or 12.5% ad valorem	50% ad valorem
Scope	60 economies	~554 eight-digit tariff lines, Canada only
Does a USMCA-qualifying flag exempt the good?	Yes — USMCA duty-free entries are exempt	No — applies regardless of USMCA origin
Section 232 interaction	certain steel, aluminium, vehicle, wood and semiconductor products excluded	goods already subject to Section 232 excluded
What your master must hold to answer	origin + program eligibility, evaluated per program	8-digit HTS line + Section 232 status

A field named usmca_qualifying has no stable meaning across that table. It is an input to a rule, and the rule differs by program and by date. Any system that treats it as an attribute of the product — a thing the product simply is — will be confidently wrong for one of these two programs.

The category labels don’t rescue you either. Global Trade Alert’s read of the Section 338 annexes found the motor-vehicle tranche contains no vehicle tariff lines at all; it falls on agricultural and industrial goods, sugars and syrups, wood, paper, sporting goods. The White House’s own examples run from wine to hockey sticks to cement. The tranche is named for the grievance, not for the goods. You cannot filter this by product category and you cannot filter it by intuition. You have to evaluate the tariff line.

Your master stores conclusions

Here is the schema argument, and it generalises well past customs.

Most item masters store duty treatment — a flag, a preference program, sometimes a landed-cost estimate. That is a conclusion. It is the output of a rule that ran at some point, against facts, under a regime that was in force on that day. Store the output and you have stored something with an expiry date you didn’t record, derived from inputs you didn’t keep, by reasoning nobody wrote down.

Facts about a good are durable. What it is made of, where it was substantially transformed, what it is used for, which subheading that composition and use put it on, and the ruling or reasoning that supports the call — those change when the product changes. Duty treatment changes when a proclamation is signed on a Monday.

The mechanical version of this failure is unglamorous and extremely common. The Harmonized System is internationally identical only to six digits; US duty rates run at the eight-digit line, and the statistical suffix goes to ten. Plenty of item masters carry a six-digit code, because that is what the supplier’s documentation supplied and six digits was enough for the paperwork nobody was auditing. A rule written on 554 eight-digit lines cannot be evaluated against a six-digit master. Not slowly, not approximately — the distinguishing facts were never captured. The agent will still produce an entry. It has to guess the last two digits, and it will guess plausibly.

There is a related conflation worth checking today: in a great many systems the “country” on an item is the supplier’s country, populated from the vendor record, and it is being read as country of origin. Those are different legal objects. One is where you buy from. The other is a determination about substantial transformation that decides whether you owe 0% or 50%. When two systems use one word for two different things, the agent inherits the ambiguity and resolves it silently.

Five times the entries is five times the exposure

The liability regime has already answered the question agentic tooling raises, which is convenient, because it means this isn’t speculative.

Under 19 U.S.C. 1484, the importer of record must use reasonable care in making entry and in declaring value, classification and applicable duty rate. That duty is the importer’s. Engaging a broker does not move it, and neither does buying software. Separately, 19 C.F.R. 111.28 requires a licensed customs broker to exercise responsible supervision and control over the customs business transacted. A licensed person has to be exercising judgment over what gets filed.

Put the throughput claim next to that. Five times the entries, drafted from the same item master, filed under the same licence, against a classification table with no owner. The volume of filings a licensed broker must responsibly supervise went up fivefold. The importer’s reasonable-care obligation did not get divided across them. If the underlying determinations are sound, automation is a genuine gain — the drafting really is mechanical work and it really does deserve to be automated. If they aren’t, you have industrialised a defect and shortened the interval before it compounds.

This is the same shape as agentic payments executing against an unowned vendor master: the automation is competent, the record it reads is not, and speed converts a quiet data problem into a fast financial one.

What the working version looks like

Name an owner for classification. Not a queue and not a shared inbox — a person accountable for what an HTS assignment asserts, who can be asked why, and who answers. Trade compliance functions often have this and product-data functions almost never do, which is why the field goes stale in the master while the compliance team maintains a spreadsheet beside it.

Then change what the master stores. Keep the facts: composition, intended use, origin determination with the basis for it, the subheading and the ruling or rationale behind the call. Derive program eligibility at entry time, per program, per effective date, from a rule that lives in one place and can be re-run. When the next proclamation lands, you update a rule and re-derive, rather than hunting for every row that silently became false.

Then make it effective-dated, so there is one answer to what you declared last quarter and why. That is the record that survives an audit, and it is also the only version an agent can be trusted to act on — a determination with its reasoning attached is a data contract, and a bare flag is a rumour.

Do that and the entry writer becomes what it should be: a fast, tireless drafter working from determinations a person stands behind, with the exceptions routed to someone who can actually resolve them.

Nothing about the product changed on 20 July. The records were wrong the next morning regardless. That’s not a tariff problem — it’s a schema that stored the answer where it should have stored the question.