How to track CBP CSMS duty-rate changes for your import catalog

Q: Does Tandom offer a public real-time CSMS alert or webhook API?

No. Tandom's public API and MCP connector do not currently expose CSMS monitoring, alerts, subscriptions, tariff events, or webhooks. Subscribe through CBP and use Tandom's public point-in-time tools for verification.

Q: How do I receive new CBP CSMS messages?

Subscribe through CBP's GovDelivery page, select relevant topics, and route messages to a shared inbox with a named reviewer and backup.

Q: What HTS granularity belongs in the watchlist?

Keep each filed 10-digit HTS code and its 8-, 6-, and 4-digit parents because CSMS messages cite codes at different levels.

Q: Should an importer track AD/CVD case numbers separately?

Yes. Track relevant AD/CVD case numbers separately because messages may cite a case without listing every HTS code. Written scope language controls.

Q: What should I do when a CSMS corrects or replaces an earlier message?

Link both message IDs, mark the earlier interpretation as superseded, and repeat the impact check from the replacement while preserving the audit trail.

Q: Can the Tandom API tell me which future CSMS messages affect my catalog?

No. Tandom's public tools are point-in-time lookups and calculations; they do not store a watchlist or notify you about future events.

Q: Who should approve a rate-change response?

The importer owns the decision and evidence; a customs broker, trade counsel, or other qualified reviewer should confirm material filing treatment.

TL;DR

Subscribe directly to CBP CSMS through the free GovDelivery page. Tandom does not currently provide a public CSMS monitoring or alert API.
Maintain an importer-owned watchlist that maps each industrial SKU to its filed 10-digit HTS code, parent codes, origin, manufacturer or exporter, relevant AD/CVD cases, and an internal owner.
When a relevant message arrives, record the message ID, source link, issue and effective dates, exact cited provisions, products potentially affected, and the reviewer. Treat this as a triage record, not as an automatic legal conclusion.
Use Tandom's public, point-in-time tools to inspect a known HTS hierarchy, check Chapter 99 and AD/CVD signals, recalculate a duty scenario, and verify source freshness. A broker or qualified reviewer should confirm material filing changes.

For a US industrial importer, the practical risk is broader than a customs entry. A change can alter a supplier comparison between RFQ and award, invalidate a purchase-order cost assumption, or require new facts from a mill or manufacturer before the first shipment.

Start with the public source

CBP uses the Cargo Systems Messaging Service to publish operational notices to the trade community. Subscribe through GovDelivery and use CBP's CSMS archive when you need to retrieve or corroborate a message. Tandom also provides a browsable CSMS catalog, but the underlying government notice remains the source to retain with the review.

A CSMS message may explain how CBP expects a change to be reported, while a proclamation, Federal Register notice, tariff schedule note, or Commerce instruction supplies the controlling authority. Preserve both. Do not reduce a message to a subject line or assume that every code mentioned applies to every product beneath it.

These archived examples show why the record needs the exact message ID and source text: CSMS 64384423 contains updated steel guidance, CSMS 67834313 addresses the end of IEEPA duty collection, and CSMS 68253075 addresses updated Section 232 reporting. Read each notice rather than relying on a label or summary.

Build an importer watchlist

Start from products the company buys or is actively qualifying—not every code in a broad tariff chapter. Export a list from the item master, prior entry records, and open sourcing projects. One row per SKU is easier to audit than one row per tariff heading.

sku,product,filed_hts_10,parent_8,parent_6,parent_4,origin,manufacturer,adcvd_cases,open_shipments,owner,last_reviewed
FST-448,steel cap screw,7318.15.80.66,7318.15.80,7318.15,7318,CN,Vendor A,,PO-1842,Jordan,2026-08-28
AL-210,aluminum machine bracket,7616.99.51.90,7616.99.51,7616.99,7616,CN,Vendor B,,PO-1911,Jordan,2026-08-28

Use the filed code. If the code is only a supplier hint or search candidate, label it as unconfirmed and do not use it as the sole basis for a cost or filing decision.
Keep parents explicitly. A CSMS may cite 7616, 7616.99, or a Chapter 99 provision rather than the full 7616.99.51.90 statistical breakout.
Keep supplier identity and origin.Those facts can change AD/CVD exposure, country-specific measures, and the evidence the buyer must request.
Keep open commercial decisions.Include active RFQs, purchase orders, in-transit shipments, and unshipped first orders so the response reaches procurement as well as customs operations.

Triage every relevant message

1. Preserve the notice

Record the CSMS ID, title, source URL, publication time, stated effective date, and any linked authority. If the message says it updates, corrects, or supersedes another message, link the records.

2. Extract only what the notice actually says

Copy the cited HTS and Chapter 99 codes, countries, AD/CVD case numbers, manufacturer or exporter names, entry dates, and filing instructions. Put uncertain interpretations in a notes column. Do not manufacture a before-and-after rate when the message does not state one.

3. Match against the watchlist

Compare exact 10-digit codes first, then the 8-, 6-, and 4-digit parent columns. Separately compare Chapter 99 provisions, origins, and AD/CVD case numbers. A broad parent-code match is a reason to review scope; it is not proof that every child code is covered.

4. Identify business exposure

Mark affected sourcing comparisons, open quotes, purchase orders, in-transit shipments, customs templates, and already-filed entries. Use the legally relevant date for each scenario, not the date the team happened to read the email.

5. Assign and close

Give each potential match an owner, reviewer, due date, disposition, and evidence link. A useful disposition is specific: “not in scope after heading-note review” or “broker confirmed new Chapter 99 reporting for entries on or after the effective date,” not simply “reviewed.”

Worked industrial example

Assume an importer has a 14-SKU catalog of fasteners, machined brackets, pump components, and electrical assemblies sourced from China, Mexico, and Vietnam. Two previously filed lines are 7318.15.80.66 for a steel fastener and 7616.99.51.90 for an aluminum article. The links provide tariff context; this example does not reclassify either product.

The team receives CSMS 68253075. The reviewer copies the codes and dates stated in the message, matches any cited 7318 or 7616 parents to the watchlist, and opens two review rows. The parent match does not automatically change the duty on either SKU.

csms_id,sku,match_basis,entry_or_po,possible_change,owner,status,evidence
68253075,FST-448,parent 7318,PO-1842,Section 232 reporting,Jordan,broker review,CSMS source + HTS notes
68253075,AL-210,parent 7616/7616.99,PO-1911,Section 232 reporting,Jordan,needs material facts,CSMS source + mill records

For each row, the team checks the HTS hierarchy and notes, confirms material and origin facts with the supplier, runs a dated duty scenario, and sends the source packet to the broker. Procurement updates the purchase-order cost model only after that review. The change log keeps the old and new assumptions so the buyer can explain why the sourcing comparison moved.

Open a dated calculator scenario →Read CSMS 68253075

Verify with public tools

Tandom's 13-tool public MCP allowlist is read-only, and the public API operations useful here are point-in-time decision-support calls. They cover source freshness, HTS search and context, Chapter 99 applicability, AD/CVD screening, PGA flags, and duty calculation. There is no public monitor, subscription, alert, event stream, or webhook operation.

Check freshness: GET /v1/regulatory-data/status before relying on a time-sensitive result.
Understand a known code: GET /v1/hts/hierarchy and GET /v1/hts/notes. Keyword search can find candidates, but it does not classify a product.
Screen layers: GET /v1/chapter99/applicable, GET /v1/adcvd/check, and GET /v1/pga/check. AD/CVD scope text and agency rules still require review.
Reprice a scenario: GET /v1/duty/calculate with the known HTS code, origin, customs value, relevant date, transport mode, and conditional facts requested by the result.

curl https://api.tandom.ai/v1/regulatory-data/status

curl https://api.tandom.ai/v1/hts/hierarchy \
  -H "Authorization: Bearer tk_live_..." \
  -G -d "code=7616.99.51.90"

curl https://api.tandom.ai/v1/duty/calculate \
  -H "Authorization: Bearer tk_live_..." \
  -G -d "hts=7616.99.51.90" -d "origin=CN" \
  -d "value=10000" -d "date=2026-04-15" -d "transport=ocean"

Use the current API reference for request and response schemas. A calculation is an import-cost input, not a supplier quote or a final customs determination.

Create an accountable handoff

The importer should own one change record even when a broker performs the entry work. Give the sourcing or procurement owner the commercial impact, give trade compliance the cited provisions and dates, and give the broker the product facts and source documents needed to confirm treatment.

Source packet: CSMS message, linked authority, relevant tariff notes, and data-freshness timestamp.
Product packet: SKU, description, material, function, dimensions, origin basis, manufacturer, exporter, and supporting mill or technical records.
Exposure packet: affected RFQs, purchase orders, shipment dates, entries, values, and the old and proposed landed-cost assumptions.
Decision record: reviewer, decision, effective date, evidence, system changes made, and next review date.

Common pitfalls

Waiting for a private monitoring product

Tandom does not expose public CSMS monitoring or webhooks today. A manual CBP subscription, shared inbox, catalog watchlist, and named review owner are controls you can operate now.

Matching only the 10-digit code

Notices often cite broader headings or Chapter 99 provisions. Keep parent codes for discovery, then read the controlling scope and notes before concluding that a product is affected.

Using the publication date as the entry date

The notice's effective-date and transition language control the scenario to test. Publication, export, departure, entry, and liquidation dates can have different consequences.

Treating a tool signal as a legal conclusion

HTS matches, Chapter 99 signals, and AD/CVD screens narrow the review. They do not replace classification analysis, written scope language, agency requirements, or broker and counsel judgment.

Overwriting corrected guidance

Preserve the original and replacement message IDs. An audit trail should explain which assumptions changed and which open commercial or filing decisions were revisited.

Updating customs but not procurement

An importer can file correctly and still award a supplier using an obsolete landed-cost model. Feed confirmed changes back into RFQs, purchase orders, supplier negotiations, and first-order readiness.

Glossary

CSMS: Cargo Systems Messaging Service, CBP's operational notice channel for the trade community. Preserve the message ID and government source link in each review.
GovDelivery: The service CBP uses for CSMS email subscriptions. It distributes topics selected by the subscriber; it does not know which products are in an importer's catalog.
Watchlist: An importer-owned mapping from SKU to filed HTS code, parent codes, origin, supplier identities, relevant cases, open commercial decisions, and review ownership.
Parent-code match: A match between a broad HTS heading or subheading cited in a notice and a more specific code in the watchlist. It triggers review but does not prove legal coverage.
Chapter 99: The HTSUS chapter containing temporary and special tariff provisions, including many trade-action measures reported alongside the underlying product classification.
AD/CVD scope: The written product coverage of an antidumping or countervailing duty order. HTS codes are generally reference signals; the written scope language controls.
Effective date: The date on which a stated treatment begins or ends. Read transition and in-transit language before mapping it to a shipment or entry.
Decision-support tool: A lookup, screen, or calculation that helps a human review a known scenario. It does not monitor a catalog, file an entry, or make the importer's final legal determination.

FAQ

Practical questions from US industrial sourcing, procurement, operations, and import teams.

Does Tandom offer a public real-time CSMS alert or webhook API?

No. Tandom's current public API and public MCP connector do not expose a CSMS subscription, monitoring, alert, tariff-event, or webhook tool. Use CBP's GovDelivery subscription or public CSMS archive for discovery, then use Tandom's available point-in-time HTS, duty, Chapter 99, AD/CVD, PGA, and data-freshness tools to investigate a known code or shipment.

How do I receive new CBP CSMS messages?

Subscribe through CBP's GovDelivery page and select the topics relevant to your entries. For a company workflow, use a shared compliance inbox or distribution list, add inbox rules, and assign a named reviewer and backup. The email is a prompt to investigate; it is not a product-specific impact determination.

What HTS granularity belongs in the watchlist?

Keep the 10-digit HTS code actually used for each imported SKU, plus its 8-, 6-, and 4-digit parents. CSMS messages may cite a heading, subheading, tariff item, statistical breakout, or Chapter 99 provision. Parent columns make a manual match possible without treating every product in a broad heading as affected.

Should an importer track AD/CVD case numbers separately?

Yes. A message can identify an AD or CVD case, manufacturer, exporter, or review period without listing every potentially affected HTS code. Record case numbers associated with prior entries and supplier screens, but remember that written scope language—not an HTS match alone—controls AD/CVD coverage.

What should I do when a CSMS corrects or replaces an earlier message?

Keep both message IDs in the change log, mark the earlier interpretation as superseded, and redo the impact check from the replacement message. Do not silently overwrite the old record; the audit trail should show what changed, when the team learned it, and which purchase orders, shipments, estimates, or broker instructions were revisited.

Can the Tandom API tell me which future CSMS messages affect my catalog?

No. The available public surface performs one-time lookups and calculations. It does not store a catalog, watch future events, send notifications, or update entry templates. Your team must maintain the watchlist and initiate each check after receiving a source notice.

Who should approve a rate-change response?

The importer should own the business-impact decision and keep the evidence. Have the customs broker or another qualified reviewer confirm material classification, Chapter 99 reporting, valuation, origin, AD/CVD scope, and filing treatment before changing live entry instructions.

Share:X

TL;DR

Subscribe directly to CBP CSMS through the free GovDelivery page. Tandom does not currently provide a public CSMS monitoring or alert API.
Maintain an importer-owned watchlist that maps each industrial SKU to its filed 10-digit HTS code, parent codes, origin, manufacturer or exporter, relevant AD/CVD cases, and an internal owner.
When a relevant message arrives, record the message ID, source link, issue and effective dates, exact cited provisions, products potentially affected, and the reviewer. Treat this as a triage record, not as an automatic legal conclusion.
Use Tandom's public, point-in-time tools to inspect a known HTS hierarchy, check Chapter 99 and AD/CVD signals, recalculate a duty scenario, and verify source freshness. A broker or qualified reviewer should confirm material filing changes.

Start with the public source

Build an importer watchlist

sku,product,filed_hts_10,parent_8,parent_6,parent_4,origin,manufacturer,adcvd_cases,open_shipments,owner,last_reviewed
FST-448,steel cap screw,7318.15.80.66,7318.15.80,7318.15,7318,CN,Vendor A,,PO-1842,Jordan,2026-08-28
AL-210,aluminum machine bracket,7616.99.51.90,7616.99.51,7616.99,7616,CN,Vendor B,,PO-1911,Jordan,2026-08-28

Use the filed code. If the code is only a supplier hint or search candidate, label it as unconfirmed and do not use it as the sole basis for a cost or filing decision.
Keep parents explicitly. A CSMS may cite 7616, 7616.99, or a Chapter 99 provision rather than the full 7616.99.51.90 statistical breakout.
Keep supplier identity and origin.Those facts can change AD/CVD exposure, country-specific measures, and the evidence the buyer must request.
Keep open commercial decisions.Include active RFQs, purchase orders, in-transit shipments, and unshipped first orders so the response reaches procurement as well as customs operations.

Triage every relevant message

1. Preserve the notice

Record the CSMS ID, title, source URL, publication time, stated effective date, and any linked authority. If the message says it updates, corrects, or supersedes another message, link the records.

2. Extract only what the notice actually says

3. Match against the watchlist

4. Identify business exposure

5. Assign and close

Worked industrial example

csms_id,sku,match_basis,entry_or_po,possible_change,owner,status,evidence
68253075,FST-448,parent 7318,PO-1842,Section 232 reporting,Jordan,broker review,CSMS source + HTS notes
68253075,AL-210,parent 7616/7616.99,PO-1911,Section 232 reporting,Jordan,needs material facts,CSMS source + mill records

Open a dated calculator scenario →Read CSMS 68253075

Verify with public tools

Check freshness: GET /v1/regulatory-data/status before relying on a time-sensitive result.
Understand a known code: GET /v1/hts/hierarchy and GET /v1/hts/notes. Keyword search can find candidates, but it does not classify a product.
Screen layers: GET /v1/chapter99/applicable, GET /v1/adcvd/check, and GET /v1/pga/check. AD/CVD scope text and agency rules still require review.
Reprice a scenario: GET /v1/duty/calculate with the known HTS code, origin, customs value, relevant date, transport mode, and conditional facts requested by the result.

curl https://api.tandom.ai/v1/regulatory-data/status

curl https://api.tandom.ai/v1/hts/hierarchy \
  -H "Authorization: Bearer tk_live_..." \
  -G -d "code=7616.99.51.90"

curl https://api.tandom.ai/v1/duty/calculate \
  -H "Authorization: Bearer tk_live_..." \
  -G -d "hts=7616.99.51.90" -d "origin=CN" \
  -d "value=10000" -d "date=2026-04-15" -d "transport=ocean"

Use the current API reference for request and response schemas. A calculation is an import-cost input, not a supplier quote or a final customs determination.

Create an accountable handoff

Source packet: CSMS message, linked authority, relevant tariff notes, and data-freshness timestamp.
Product packet: SKU, description, material, function, dimensions, origin basis, manufacturer, exporter, and supporting mill or technical records.
Exposure packet: affected RFQs, purchase orders, shipment dates, entries, values, and the old and proposed landed-cost assumptions.
Decision record: reviewer, decision, effective date, evidence, system changes made, and next review date.

Common pitfalls

Waiting for a private monitoring product

Tandom does not expose public CSMS monitoring or webhooks today. A manual CBP subscription, shared inbox, catalog watchlist, and named review owner are controls you can operate now.

Matching only the 10-digit code

Notices often cite broader headings or Chapter 99 provisions. Keep parent codes for discovery, then read the controlling scope and notes before concluding that a product is affected.

Using the publication date as the entry date

The notice's effective-date and transition language control the scenario to test. Publication, export, departure, entry, and liquidation dates can have different consequences.

Treating a tool signal as a legal conclusion

HTS matches, Chapter 99 signals, and AD/CVD screens narrow the review. They do not replace classification analysis, written scope language, agency requirements, or broker and counsel judgment.

Overwriting corrected guidance

Preserve the original and replacement message IDs. An audit trail should explain which assumptions changed and which open commercial or filing decisions were revisited.

Updating customs but not procurement

Glossary

CSMS: Cargo Systems Messaging Service, CBP's operational notice channel for the trade community. Preserve the message ID and government source link in each review.
GovDelivery: The service CBP uses for CSMS email subscriptions. It distributes topics selected by the subscriber; it does not know which products are in an importer's catalog.
Watchlist: An importer-owned mapping from SKU to filed HTS code, parent codes, origin, supplier identities, relevant cases, open commercial decisions, and review ownership.
Parent-code match: A match between a broad HTS heading or subheading cited in a notice and a more specific code in the watchlist. It triggers review but does not prove legal coverage.
Chapter 99: The HTSUS chapter containing temporary and special tariff provisions, including many trade-action measures reported alongside the underlying product classification.
AD/CVD scope: The written product coverage of an antidumping or countervailing duty order. HTS codes are generally reference signals; the written scope language controls.
Effective date: The date on which a stated treatment begins or ends. Read transition and in-transit language before mapping it to a shipment or entry.
Decision-support tool: A lookup, screen, or calculation that helps a human review a known scenario. It does not monitor a catalog, file an entry, or make the importer's final legal determination.

FAQ

Practical questions from US industrial sourcing, procurement, operations, and import teams.

Does Tandom offer a public real-time CSMS alert or webhook API?

How do I receive new CBP CSMS messages?

What HTS granularity belongs in the watchlist?

Should an importer track AD/CVD case numbers separately?

What should I do when a CSMS corrects or replaces an earlier message?

Can the Tandom API tell me which future CSMS messages affect my catalog?

Who should approve a rate-change response?

Share:X