For AI-enabled catalog operators
Already AI-Forward? Use Tariff Code Compliance to Get Your Shopify Catalog Ready for International Shipping
If you already use Claude, ChatGPT, or another agent to run store operations, Tariff Code Compliance can join that same workflow. Connect the agent to Shopify, add current tariff evidence, review what truly belongs together, and write back only what you approve.

Your agent can work with the catalog you actually have
Savvy operators already use agents to research products, inspect store data, and take repetitive work off their teams. Shopify now documents official store connections for ChatGPT, Claude, and Perplexity. With the access you approve, the agent can read and manage store data such as products without a catalog export or another spreadsheet.
Connect Shopify to your agent
Use Shopify's official app for your AI tool, or its CLI connector, to give the agent permission-scoped access to the catalog. Read access supports analysis; write access lets the agent make changes you explicitly authorize.
Add Tariff Code Compliance evidence
Connect Tariff Code Compliance Explorer with MCP so the same agent can research current tariff systems, exact versions, hierarchy, notes, and alternatives. The tariff tools stay read-only; Shopify remains the system that holds catalog data.
Start with our guides to connect Tariff Code Compliance to ChatGPT or Claude. Then connect Shopify using its official, permission-scoped agent integration. Shopify's Storefront MCP is designed for customer-facing product search, carts, and store policies; it is not the merchant-admin write surface used in this workflow. Shopify documents both connecting AI tools to a store and its Storefront MCP server documentation.
Every Shopify Catalog is Unique
Catalogs reflect how a business sells, not how a tariff schedule is organized. One merchant may sell kits or bundles containing several articles. Another may use variants for material, construction, intended audience, quantity, or a measure such as weight that changes the tariff branch for that product family. Two records can share a title, image, tag, or Shopify product type and still need different codes.
The agent's first job is therefore not to copy a code. It is to inspect the relevant Shopify records, form a candidate group, and identify missing facts. Tariff Code Compliance can then research the current schedule and explain which facts support one code—or why a bundle or variant must be handled separately.
How Shopify stores HS codes
A quick refresher matters before we touch the catalog. Shopify stores customs information on each product variant's inventory item. The six-digit HS code is the required international foundation, but it is only the minimum. The Admin GraphQL API's InventoryItemInput separates two fields:
- General HS code: Shopify's
harmonizedSystemCodefield holds the shared six-digit value. For the men's shirts below, that value is620520. - Country- or region-specific codes: Shopify's
countryHarmonizedSystemCodesfield can hold a separate classification for every destination market. For the United States, this example stores6205202047. Add the local extension for each country or region you ship to when that market publishes one.
Why bother with the extra digits? When a country-specific code exists, Shopify uses it to calculate duties for that market; otherwise it falls back to the six-digit code. The destination code is therefore what connects the product to the local tariff line used for duty treatment. We cover the distinction in more detail in our guide to HS codes versus HTS codes. You can also read Shopify's HS code guidance for its product-page and country-specific workflows.
Let's run through the following example
Two men's shirts differ only by color. A women's shirt uses the same cotton plaid fabric, but its cut and intended audience can send it to a different tariff heading. The useful question is not which products look alike. It is which products share the facts that determine their code.
| Product | SKU | Classification facts | Decision |
|---|---|---|---|
| Men’s navy plaid shirt | TCC441-M-NAVY-M | 100% cotton; yarn-dyed plaid woven fabric; shirt-weight; men’s cut | Classify first |
| Men’s red plaid shirt | TCC441-M-RED-M | Same material, construction, use, audience, and decisive features; color differs | Compare with first |
| Women’s navy plaid shirt | TCC441-W-NAVY-M | Same material and construction; women’s cut and marketing | Classify separately |
The two men's shirts can be researched together because color does not change the relevant tariff branch. The women's shirt shares Chapter 62 with them, but it follows heading 6206 and a different six-digit HS and ten-digit U.S. HTS path. Treat it as a second classification group instead of copying the men's result across all three products.
Train your agent to classify the catalog only you know
You know why a bundle exists, what each variant means, and which product details actually distinguish one item from another. Teach your agent that catalog logic, then use Tariff Code Compliance to supply exact-version tariff evidence. The agent can turn your model into repeatable classification groups, surface missing facts, and preview every proposed change before asking permission to update Shopify.
Read the following Shopify products and their current customs fields:
- TCC441-M-NAVY-M: 100% cotton, yarn-dyed plaid woven fabric, shirt-weight, men's cut
- TCC441-M-RED-M: same material, construction, use, audience, and decisive features; color differs
- TCC441-W-NAVY-M: same material and construction; women's cut and marketing
Use Tariff Code Compliance to research the current U.S. tariff schedule. Classify the men's navy shirt, decide whether the men's red shirt can share that result, and handle any product that needs a separate classification as a separate work group.
For each work group, return the exact tariff-system version, general six-digit HS code, U.S. HTS code, linked evidence, alternatives considered, assumptions, and uncertainty. Then preview the current and proposed Shopify values for every SKU. Do not write anything until I explicitly approve the exact items and values.In the historical run captured on August 26, 2026, we used ChatGPT with 5.6 Sol Extra High. Tariff Code Compliance returned US_HTS version 2026-rev-16, kept every link on that exact version, and returned the following result for the two men's shirts. Revision 16 identifies the release returned for that dated run; it is not a claim about today’s current or default release.
Classification output, annotated
General HS: 620520
U.S. HTS: 6205.20.20.47 — men's woven cotton shirts, other, with two or more colors in the warp or filling, napped.
Confidence: Moderate until the raised or napped fabric surface is confirmed.
The reasoning followed woven Chapter 62, including note 1; the shirt definition in note 4; heading 6205 for men's shirts with the audience check in note 9; subheading 6205.20 for cotton; subheading 6205.20.20; and finally the yarn-color and napped statistical line 6205.20.20.47. Read the full flannel-shirt classification walkthrough for the completed fact pattern and linked notes.
Separate result for the women's shirt
A separate exact-version research pass moved the women's shirt to heading 6206 for women's woven shirts, then to general HS 620630 and U.S. HTS 6206.30.30.11. That recommendation assumes the same 100% cotton woven, two-color yarn-dyed construction and no specialized blouse or hospital-garment features. It should become a second Shopify proposal with its own preview and approval—not inherit the men's code and not disappear from the workflow.
What the agent ruled out
A useful classification does more than name a code. It shows the nearby choices and the product fact that makes each one a worse fit. That gives you a short list of assumptions to verify before approving a write.
Use this men’s statistical suffix instead if the fabric is not napped.
Rejected because the test garment is a casual flannel shirt, not a dress shirt.
Rejected because the yarn-dyed plaid uses multiple colors in the warp or filling.
Rejected because heading 6105 covers knitted or crocheted shirts, while this fabric is woven.
This is classification research only. It does not calculate taxes, fees, landed cost, or make a binding legal determination. If the napped-surface assumption is wrong, the U.S. suffix must be reconsidered before any customs use.
Preview the changes before anything is written
The complete cleanup now has two proposals: one for the two men's shirts and another for the women's shirt. The table below keeps both visible while making clear that only the men's group was approved for this write. At that point Shopify was still unchanged. We used ChatGPT for the original live proof, but the review boundary belongs to the workflow, not to one agent.
| SKU | Existing HS | Proposed HS | Existing U.S. | Proposed U.S. | Status |
|---|---|---|---|---|---|
| TCC441-M-NAVY-M | None | 620520 | None | 6205202047 | Approved men’s group |
| TCC441-M-RED-M | None | 620520 | None | 6205202047 | Approved men’s group |
| TCC441-W-NAVY-M | None | 620630 | None | 6206303011 | Separate proposal; not in this write |

Tell the agent exactly what to write
Approval should name the exact products and values, and it should say what must remain unchanged. Because the proposed men's suffix assumes a napped surface, this prompt blocks the write until that decisive fact is confirmed. It also preserves existing country entries and asks the agent to read everything back so a successful item cannot hide a failed sibling.
Before writing, confirm that the two men's shirts have the raised or napped fabric surface assumed by the proposed code. If that fact is not confirmed, stop and reclassify the men's group; do not write 6205202047.
If the napped surface is confirmed, apply only these approved men's-shirt changes from the preview:
- TCC441-M-NAVY-M: general HS 620520; U.S. HTS 6205202047
- TCC441-M-RED-M: general HS 620520; U.S. HTS 6205202047
Do not change TCC441-W-NAVY-M; it belongs to a separate classification and approval step.
For each approved item, preserve every existing country-specific HS entry and add or replace only the U.S. entry.
After the write, read all three inventory items back from Shopify. Report the final general and U.S. values for each SKU, any item-level errors or failures, and confirm that the women's item remained unchanged.Shopify's Admin API is GraphQL. With the Shopify permissions you granted, your agent can call the inventoryItemUpdate mutation to write the approved general and country-specific codes to each variant's inventory item. A safe agent reads the existing country entries first, preserves them, changes only the approved destination, reports item-level GraphQL errors, and then reads the updated records back. You approve the catalog change; the agent handles the API call.
Check the result in Shopify Admin
Do not stop at the agent's success message. Open Shopify and inspect the same customs fields a teammate will see when they manage the product:
- In Shopify Admin, go to Products and open the product you updated.
- If the product has variants, open each updated variant. HS codes belong to the variant's inventory item, so check the variants your agent changed.
- In the shipping and customs information, confirm the general HS code is
620520. - Choose Add HS codes by country/region and confirm the United States code is
6205202047. Make sure codes for every other destination are still there. - Confirm the country or region of origin and product weight while you are there. Those fields also matter for international shipping and duty estimates.
Shopify documents the same clicks in its guide to adding HS codes on the product page. After a write that passes the fact check above, both men's shirts should show general HS 620520 and U.S. code 6205202047. If Shopify shows anything else, stop and reconcile the agent's readback with the Admin fields before continuing.
Let's recap the workflow
- Ask the agent to read a manageable set of Shopify products and their current customs fields.
- Give it the product facts and destination, then let Tariff Code Compliance research the current tariff system.
- Review which products can share a result and which need their own classification.
- Check the proposed HS and country-specific codes beside the values already in Shopify.
- Approve the exact products and values, then have the agent write and read them back.
This first pass gives you a controlled way to work through the catalog you have today. It is not permission for automatic catalog-wide writes. Existing codes should be shown rather than silently replaced, and a failed item should not be hidden by successful siblings.
Sound like a lot of work? Let Catalog Watch handle continuous maintenance
A clean catalog starts changing the next day. New products launch, variants get added, bundles change, and materials, descriptions, or intended uses are updated. Tariff systems move too: a code that existed in one version may no longer exist in the current one.
After the initial cleanup, Tariff Code Compliance for Shopify turns the process into continuous maintenance. Catalog Watch generates HS and U.S. HTS proposals for new products, carries approved codes to genuinely matching variants, and sends classification-relevant changes back through review. Catalog Health gives you a point-in-time check for missing codes and codes absent from the current tariff version.
That is the handoff: use your agent to understand and clean the catalog you have today, then use Catalog Watch so new products, new variants, and meaningful product changes do not become another manual checklist. After a tariff release, rerun Catalog Health and review anything that no longer exists in the current version. Automatic tariff-system monitoring and regulatory reclassification are not included. Every proposal remains reviewable, and you control what is approved.
To run the workflow yourself, follow the setup guide for ChatGPT or Claude, then use the complete flannel example as a model for classification evidence and uncertainty.