Capture country of origin for every SKU

Country of origin data tells customs, marketplaces and customers where a product comes from, and it is now needed on every SKU for tariffs, landed cost, listings, labelling and customer questions. In most catalogues it is missing, inconsistent, or held only in a purchasing system nobody else can see. SKULaunch collects it from suppliers as a required, controlled field and keeps it on the product record for every channel.

The problem

Until tariffs started moving, origin was a purchasing detail. It sat on the purchase order or the customs entry, and the product team never needed it. Now finance wants it for landed cost, marketplaces ask for it in listing templates, and customers ask where things are made. The product record is the obvious place for it, and it is usually blank.

Where it does exist, it is free text from a dozen suppliers. "China", "P.R.C.", "Made in China" and "CN" all mean the same thing. "UK", "Great Britain" and "England" get mixed. Some suppliers enter "EU" or "Various". Others give the country they ship from, or the country the brand is based in, which may have nothing to do with where the product was made.

Before and after

An illustrative example from a kitchenware and small appliance distributor.

Before: the origin column across six suppliers

China, P.R.C., Made in China, CN, UK, Great Britain, EU, Germany (brand head office), Various, and blank on many rows.

After: captured in SKULaunch

• Values stored as ISO 3166-1 alpha-2 codes: CN, GB, DE, PT
• China, P.R.C. and Made in China mapped to CN; UK and Great Britain mapped to GB
• EU and Various rejected as values, with the supplier asked for the actual country
• Germany moved to a separate brand country attribute, with origin requested from the supplier
• Country of origin required in the supplier portal for every new line

How it works in SKULaunch

1. Make it a required controlled field. Add country of origin to supplier templates as a required attribute, with ISO country codes as the allowed values.
2. Map what you already have. Normalise existing free text values to codes, and flag values that are not countries.
3. Request the gaps. Send update requests to suppliers for existing products with no value.
4. Review and publish. Approve values in the grid, then send them to every channel and export.

Where packaging images or supplier documents state a country, AI extraction can propose a value for review. It is still the supplier's declaration that counts.

What country of origin data actually means

Three different facts often end up in one field:

• Country of origin. The country a product is treated as coming from for customs and labelling. Where manufacture spans several countries, rules of origin decide which one counts, and those rules vary by authority and trade agreement.
• Country of manufacture. Where the finished product was made or assembled. Often the same as origin, but not always. Some channel templates ask for this by name.
• Ship-from country. Where the goods leave from. A distributor in the Netherlands can ship products made in Vietnam.

Brand country is a fourth, and the most misleading. A British brand can make everything abroad. If you need more than one of these, hold them as separate attributes and label them clearly in supplier templates, so suppliers answer the question you are asking. Which country counts as origin for a given product is a decision for the supplier, your compliance team or your broker. The data job is to capture that answer consistently and keep it current.

Rules for clean country of origin data

• Store ISO 3166-1 alpha-2 codes. Two letters, such as CN, DE or US. Show full country names on the website if you prefer, but store the code.
• GB, not UK. The ISO code for the United Kingdom is GB. UK is a common mistake that many systems will reject.
• No regions or trading blocs. "EU" or "Asia" is not an answer to where something was made.
• No "Various". If origin varies, record it properly, as described below.
• Hold it at SKU level. Colours or sizes of one product can come from different factories.
• Know when it was confirmed. Keep a note of when the supplier last confirmed origin, so you know what to recheck when sourcing changes.

Multi-origin products and kits

Some SKUs are made in two factories in different countries. Stored as one value, the record is right half the time. Where labelling differs, split them into separate SKUs. Where it does not, hold the current origin on the product and update it through a supplier request when sourcing changes, rather than letting it drift.

Kits and sets combine components from several countries. Hold component origins as well if your team needs them, and let your compliance team or broker decide what is declared for the set. SKULaunch holds the data. It does not give customs or labelling advice.

What changes

Every SKU has a country of origin in one consistent format. New lines cannot arrive without one. The same value reaches landed cost files, marketplace templates and the product page.

Common questions

What is country of origin data?

It is the country a product is treated as coming from, held as a structured field on the product record so every system and channel uses the same value.

What is the difference between country of origin and country of manufacture?

Manufacture is where the finished product was made or assembled. Origin is the country it is treated as coming from under the relevant rules. They are often the same, but not always.

What format should country of origin be stored in?

ISO 3166-1 alpha-2 codes, such as CN, GB or US. They are unambiguous, short and accepted by most systems and channel templates.

How do we get country of origin from suppliers who never fill it in?

Make it a required field in the supplier portal for new lines, and send update requests for existing products. Required fields with a fixed list of answers get far better results than an optional free text column.

Can SKULaunch tell us the correct country of origin?

No. SKULaunch collects, validates and holds the value your supplier declares. Determining origin is for the supplier and your compliance team or broker.

How does country of origin relate to HS codes?

They are separate fields, but they are usually needed together for customs data and landed cost. Hold both on the same product record.

More on assigning HS and commodity codes, collecting product data through a supplier portal, turning free text into controlled value lists, requesting updates from suppliers and the supplier portal.