Tariff classification with evidence
HS codes proposed from product data and documents, with the ruling, the note and the rejected alternatives kept beside the choice.
TRADE24
Customs, origin and landed cost as a controlled system.
A trade-compliance platform for classification, origin, duty and the broker pack — so an FTA claim, a tariff code and a landed-cost figure are evidenced, not guessed, and a customs question is answered from the file.
DomainCustoms, origin, landed cost
AnchorHS, FTA and duty rules
ScopeShipment to filing to audit
AI roleClassification, document read
Duty schedulescoverage to be confirmed
Shipment→Classify→Origin→Duty→File→Audit
The problem
Duty is a surprise. Origin is a PDF. The code was someone's best guess.
Brokers file what they are sent. Classification lives in a spreadsheet that drifted from the product. FTA certificates are collected after the shipment, or not at all. When customs asks why a rate was used, the answer is reconstructed from email.
TRADE24 makes the shipment the unit of record: classification, origin evidence, duty calculation and the broker pack sit on the same file, so landed cost is known before the goods move.
Who it is for
Trade and customs teams
Owning classification, origin and duty across lanes without a broker-by-broker memory.
Supply-chain and procurement
Needing landed cost and preference eligibility before they place the order.
Group tax
Duty, import VAT and intercompany goods that must agree with CIT24 and TP24.
Advisory firms
Running a portfolio of importers on one classification and origin methodology.
Core capabilities
01
02
Origin and FTA preference
Origin criteria tested against the bill of materials and supplier declarations, so a preference claim has a file, not a hope.
03
Landed cost and duty accrual
Duty, fees and recoverable tax computed per shipment and posted toward the close — visible to CFO24 when both platforms are in use.
04
Broker pack and filing trail
The pack the broker files is generated from the same record; the return and the assessment stay attached.
05
Licence and restricted-goods checks
Controlled goods and licence conditions tested before dispatch, with the permit held against the shipment.
06
Intercompany goods handshake
Related-party shipments share classification and value with TP24 rather than being priced twice.
07
Post-entry and audit defence
Amendments, queries and voluntary disclosures managed against the original file, with every change dated.
08
Lane and supplier intelligence
Repeat lanes remember the last approved classification and origin path, so the next shipment starts from a decision, not a blank form.
AI reads the documents and proposes a code. A deterministic tariff engine computes the duty. A person signs the classification.
A language model never files a declaration. Every rate is rule-versioned and traceable to the schedule and the shipment documents.
How the platform works
Five layers, one line from the shipment to the assessment
01
Data engine
Ingest invoices, BoM, bills of lading and supplier declarations.
02
Rules engine
Effective-dated HS, FTA and duty schedules, versioned.
03
Calculation engine
Duty, fees and landed cost; reproducible arithmetic.
04
Filing engine
Broker pack, declarations, licences and deadline control.
05
AI intelligence layer
Document read, classification assist and gap detection.
Example workflow
A first FTA-preferential shipment on a new lane
Illustrative sequence, not a client engagement.
01
Commercial invoice, packing list and bill of lading are loaded; AI extracts parties, goods and values for review.
02
A classification is proposed against the product description; the specialist accepts or corrects it, with the rejected codes kept.
03
Origin criteria are tested against the bill of materials and supplier declarations; the FTA preference is granted or refused with the evidence recorded.
04
Duty and landed cost are calculated under the chosen schedule; the accrual is available to the close.
05
The broker pack is generated from the same record and filed; the return is attached when it comes back.
06
A later customs query opens the shipment: code, origin test, rule version and the person who signed each step.
Outcomes
Duty known before the vessel sails
Landed cost is a calculation from the file, not a surprise on the assessment.
Preference you can prove
An FTA claim opens to the origin test and the supplier declaration.
Classification that survives turnover
The reasoning lives on the product, not with the person who last guessed the code.
A query is a lookup
Customs questions are answered from the shipment record rather than from email.
Duty and cycle-time comparisons to be added once measured with client data
Data security and auditability
Lane- and entity-level access for groups that separate operating companies.
Immutable shipment file: later analysis never overwrites what was filed.
Every classification change logged with author, date and the codes discarded.
Retention aligned to customs assessment windows.
Certifications and independent assurance to be confirmed
Integration
ERP and procurement for product, BoM and purchase orders.
Broker and customs-filing channels for the pack and the return.
Intercompany value shared with TP24; duty accrual visible to CFO24 and CIT24.
Import licences and permits held with LAW24 when that platform is in use.
Named system connectors to be confirmed
Put the tariff code in a system that can defend it.
We will run one lane and one FTA claim through TRADE24 and show the classification, the origin test and the duty calculation that come out.
Request a Demonstration