Shopify HS code sync: staying customs-ready as your catalog changes
Getting your catalog customs-ready once is a project. Keeping it that way is the part nobody plans for. Every new product, new variant, seasonal drop, and supplier change can land in Shopify without an HS code, country of origin, or weight — and Shopify won't tell you. Three months after your big cleanup, you're quietly back to a catalog with gaps, and the first you hear of it is a carrier rejection or a customer's held parcel.
Why customs data drifts out of sync
New products are the obvious source, but not the only one. Duplicated products copy some fields and not others. Apps and imports (PIM syncs, marketplace connectors, CSV uploads) routinely write products with the customs subsection empty, because the standard product CSV has no HS code column. Staff adding variants fill in price and inventory and skip the collapsed "Customs information" section entirely — it's the least visible field group in the Shopify admin.
What "sync" should actually mean
You don't need real-time enforcement — you need a loop that catches drift before parcels do. Three workable versions, in ascending order of effort saved:
| Approach | How it works | Where it breaks |
|---|---|---|
| Checklist discipline | "Every new product gets customs data before publish" as team policy | Humans, apps, and imports don't follow policies |
| Scheduled manual audit | Monthly pass through the admin looking for gaps | No native report shows what's missing; hours of clicking at scale |
| Automatic scan on change | A tool watches the catalog and re-flags any product that appears or changes without complete customs data | This is the one that holds — it's what Origova's auto-sync does |
Origova stays connected to your catalog after the first scan: when products are added or edited in Shopify, they're re-checked automatically — no manual rescan — and anything incomplete shows up in the Scan & fix tab with the rest of your open issues. Your "catalog readiness" number stays honest as the catalog changes, which is the entire point.
The launch-day pattern worth stealing
Stores that stay customs-ready treat the scan like a pre-flight check: run it before every collection launch and every bulk import, fix the flagged items in one batch, then ship. It turns customs data from a recurring cleanup project into a two-minute step in a workflow you already have.
Frequently asked questions
Does Shopify keep HS codes in sync automatically?
Shopify stores whatever HS code you enter, but it has no mechanism to flag new or changed products that are missing one. Products created by imports, apps, or duplication regularly arrive with empty customs fields, and nothing in the admin surfaces them.
How does Origova's auto-sync work?
After the first scan, Origova stays in sync with your Shopify catalog: products you add or edit are re-checked automatically against the six-point compliance check (HS code, country of origin, weight, materials, titles, descriptions), and anything incomplete appears as an open issue — no manual rescan needed.
How often should I audit my catalog's customs data?
If you rely on manual checks: before every collection launch, after every bulk import, and monthly at minimum. With an automatic scan-on-change tool, the audit is continuous and the answer becomes 'glance at your readiness number when you ship something new.'
Related: Bulk HS codes in Shopify · HS code automation for large catalogs · How Origova works
Your catalog changed since you last checked.
Scan it free — and let auto-sync catch the next gap before a carrier does.
Install on Shopify