How Customs Brokers Monitor Tariff Changes for All Clients at Once
What changed: Rewritten: GingerLite's Compliance Radar checks the codes in your own account; per-client lists and white-label alerts are a custom build, like the system GingerControl built for Jet Import Brokers (contact GingerControl). The broker tier, white-label and client-tenant claims, the unsourced daily-check figures and the old company line are gone.
Keep each client's product list with HTS codes and origins in one place, check every new U.S. notice against every list, and tell only the clients a notice touches, with what to do by its effective date. The hard part is the matching, which grows with clients times codes times notices. GingerControl's Compliance Radar, in the GingerLite app, checks notices against the codes saved in your own account. A radar that keeps a separate list per client, or sends alerts under your brokerage's name, is a custom build, like the system GingerControl built for Jet Import Brokers; for that, contact GingerControl.
Next step:Get the policy briefings
In this post
- Why is monitoring for many clients harder than for one importer?
- What do brokers owe clients when rules change?
- What does a workable multi-client workflow look like?
- What tools can do the matching?
- What does a custom radar for a brokerage look like?
- What are the three ways brokerages run tariff monitoring?
- Frequently Asked Questions
- Moving from reactive to proactive
- References
Why is monitoring for many clients harder than for one importer?
Because every notice has to be checked against every client's codes. An illustration: a brokerage with 75 active clients averaging 200 HTS codes each holds 15,000 client-code pairs. Every proclamation, executive order or Federal Register notice that changes a duty has to be read against all of them. Done by hand, that gets done for the big headlines and skipped for the long tail, such as an exclusion that expires or a new subheading added to a Section 232 list, which is exactly where a client gets caught.
Two failure modes follow. Clients hit by a long-tail change find out after entries were filed at the old rate. Or the brokerage sends everyone a digest, clients learn to ignore it, and the one alert that mattered is lost in the noise.
What do brokers owe clients when rules change?
Brokers act under a license (19 U.S.C. 1641) and the duties in 19 CFR Part 111 [1] [2], which include supervising the brokerage's work, keeping records and advising a client who has not complied with CBP requirements on the corrective action to take (19 CFR 111.39(c)). The importer of record carries the duty of reasonable care in classifying and valuing goods (19 U.S.C. 1484) [3]. Filing an entry at a rate that changed last week serves neither. A documented record of which notices were checked, which clients were told and when is the practical answer to both.
What does a workable multi-client workflow look like?
- One list per client: products, HTS codes, countries of origin, and the date each code was last confirmed.
- One feed of primary sources: presidential proclamations, executive orders, Federal Register notices, HTS revisions and CBP messages, not newsletters.
- A match for every notice: which subheadings and countries it names, which client products fall under them.
- A notice to each affected client: what changed, which of their products, the effective date, and what to prepare (a new code, a recalculated duty, documents such as the metal content behind a Section 232 claim).
- A record: the notice, the match, who was told and when, kept with the client file.
What tools can do the matching?
| Tool | What it matches | Per-client lists and branded alerts |
|---|---|---|
| Compliance Radar in GingerLite | New U.S. notices against the HTS codes saved in your own account (products you classified or put in the Parts Library); alerts by email with the effective date | No; one account's own codes |
| A system built for your brokerage | Every notice against every product on every client's list | Yes, built to your workflow; contact GingerControl |
| Descartes CustomsInfo | Tariff data updates and content alerts; CustomsInfo Manager flags which of a user's stored classifications an HS amendment affects | Depends on your setup with Descartes |
| Spreadsheets and newsletters | Whatever someone reads and remembers | Manual |
Compliance Radar reads presidential proclamations, executive orders, Federal Register notices and HTS updates, checks each against your saved codes and origins, and emails which products are affected, with two next steps (reclassify the product or recalculate its tariffs) and the effective date. It covers U.S. imports. GingerLite, the GingerControl app for customs brokers and small businesses, is $150 a month for 300 credits.
What does a custom radar for a brokerage look like?
The one on record is the system GingerControl built for Jet Import Brokers, a U.S. customs broker. A compliance radar added to Jet's system checks each policy update against every product on every client's list. Each affected product says why it is hit, how, and what to do; the new HTS code and duty are calculated ahead; and where a new code needs a fact, for example the steel, aluminum or copper share at a Section 232 update, the report says which. Each client gets an impact report per product list: the update in brief, its broad impact, how their products are affected and what to prepare.
That is a custom build, fitted to one brokerage's clients and screens. If your brokerage needs the same, contact GingerControl.
What are the three ways brokerages run tariff monitoring?
- Reactive. Clients hear when something makes the news, and the long tail is handled when a client asks. Cheapest, and the most exposed.
- Proactive, broker-led. The brokerage matches notices internally and sends each affected client its own notice with the broker's analysis. More work per change, far fewer surprises.
- Direct to client. Clients receive alerts for their own products automatically, with the broker copied, and the broker steps in for the decisions (reclassification, sourcing, refunds). This needs per-client lists and alerts under the brokerage's name, which is a custom system.
Frequently Asked Questions
Can a customs broker keep separate client catalogs in Compliance Radar?
Not in GingerLite. Compliance Radar there checks new U.S. notices against the HTS codes saved in your own account. Separate lists per client, alerts per client and alerts under your brokerage's name are a custom build, like the system GingerControl built for Jet Import Brokers; contact GingerControl about it.
Can I white-label tariff alerts for my clients?
Not with GingerLite's Compliance Radar. White-label alerts are part of a custom system built for a brokerage. That is a custom requirement: contact GingerControl.
How does tariff monitoring fit with my ABI filing software?
It sits upstream. Monitoring tells you before filing which client products a new rule touches and from which date, so entries after the effective date go out with the right code and rate. Filing stays in your ABI software.
How many notices does a brokerage need to check?
Every notice that changes a U.S. duty, classification or entry requirement, against every client product it could touch. The volume varies with policy; what scales badly is the matching, which grows with clients times codes, not the reading.
Does monitoring help a broker's compliance obligations?
It helps show diligence. Part 111 sets out broker duties, including advising a client who has not complied with CBP requirements on the corrective action, and the importer carries reasonable care under 19 U.S.C. 1484. A dated record of which notices were checked and which clients were told supports both.
What does a small brokerage need to start?
A clean list of each client's products with codes and origins, a primary-source feed, and one person who owns the match. For a brokerage's own research and checks, GingerLite gives you the Classification Researcher, the Tariff Calculator and Compliance Radar for $150 a month for 300 credits.
Moving from reactive to proactive
Start by putting each client's codes and origins in one list and matching every new notice against it. For your own classification research and rule alerts, open GingerLite. For a radar across all your clients' lists, with reports per client, contact GingerControl: that is a custom build. More on how matching works is in tariff alerts by HTS code and Section 301 policy alerts.
Compare trade policy alert services by sources, product matching, effective-date information and follow-up actions.
References
- 19 U.S.C. 1641, Customs brokers
Data cited: licensed broker requirement for customs business
Source: 19 U.S.C. 1641, Legal Information Institute - 19 CFR Part 111, Customs Brokers
Data cited: broker responsibilities, including 111.39(c) on advising a client of noncompliance and keeping a record of it
Source: eCFR 19 CFR Part 111 - 19 U.S.C. 1484, Entry of merchandise
Data cited: the importer of record classifies and values goods using reasonable care
Source: 19 U.S.C. 1484, Legal Information Institute
Reading every CSMS and Federal Register notice yourself?
Hand this to GingerOS.
Pick a 30-minute slot on the next page with Chen Cui, our CEO. Bring one notice or one SKU list (an ERP export, a spreadsheet or an email will do) and see what GingerOS does with it.
Reviewed by Michael Weick, LCB / CCS




