Country of origin is one of those fields that is irrelevant right up until it is blocking. Then a carrier rejects a label, a customs broker emails asking for data you thought you had, a marketplace feed fails validation, or a customer in another market is charged duty they should not have paid.
It is also a field that is nearly identical across most of your catalog — which makes filling it in product by product especially galling.
Where origin data gets used
- Customs declarations. Commercial invoices need an origin per line item. Missing origin means held shipments.
- Duty and tax calculation. Origin combined with destination determines the duty rate and whether a trade agreement applies.
- Trade agreement claims. Preferential rates depend on provable origin. No data, no claim, higher duty.
- Marketplace and comparison feeds. Several require origin and reject listings without it.
- Storefront claims. "Made in" is a selling point for a lot of brands — and a legal statement, so it should come from one source of truth rather than being retyped into a description.
Where it lives in Shopify
Shopify has a country of origin field in the customs information section of each variant, and many stores also keep an origin metafield — usually because the storefront needs to display it, a feed needs it in a specific format, or a fulfilment partner reads it from there.
SheetSync exports both standard fields and metafields in the same sheet, so you can keep the customs field and the display metafield in step instead of discovering six months later that they disagree.
The bulk workflow
Export your catalog with the origin fields included and you get one row per product or variant alongside vendor, type and SKU. Then:
Fill by supplier. Sort by vendor, select the block, type the country once, fill down. Most catalogs are 90% done after three or four of these.
Fill by SKU pattern. If your SKUs encode the factory or region, a formula reads it straight out: =IF(LEFT(C2,3)="PTL", "PT", "CN").
Find the gaps. Filter to blanks. That list is exactly what you need to email your suppliers about, and it is far easier to chase as one list than as a drip of customs rejections.
Catch the inconsistencies. A pivot on the origin column shows every distinct value in your store. If you see Portugal, PT and portugal sitting side by side, you have found the real problem.
Update after a supplier change. Moved a product line to a new factory? Filter and replace in one action rather than opening eighty products.
Step by step
- Open Product Info Sync and include country of origin — the standard customs field, the origin metafield, or both.
- Export the catalog.
- Fill the column by supplier, by rule, or by pasting data from your purchasing system.
- Normalise to one format before syncing.
- Sync back and review the log.
- Check a product's customs section in admin to confirm.
Getting the format right
- Use ISO 3166-1 alpha-2 codes —
PT,CN,DE. Shopify's customs field expects a country code, and codes are what carriers and customs systems consume. Keep a full country name in a separate display column if the storefront needs one. - Watch autocorrect. Spreadsheets will happily reformat short codes. Format the column as plain text before you paste.
- Origin is where it was manufactured, not where it shipped from and not where your supplier is incorporated. Getting this wrong on a customs declaration is a compliance problem, not a data problem.
- Origin can vary by variant. If the same product is made in two factories, it needs two values — do not flatten it to one at the product level.
- Do not guess. A blank is honest and chaseable; a wrong value is a declaration you made. Leave unknowns empty and work the list.
Country of origin pairs naturally with HS codes — both are customs fields, both come from the same supplier conversation, and both can be filled in the same sheet and the same sync.
Set origin across the catalog
Fill country of origin in a spreadsheet and sync it to every product at once.
Try SheetSync today