Guide
Why bearing country of origin belongs to unit or lot evidence
Country of origin describes where a physical unit was made, not a universal property of a manufacturer part number. How to model it by scope and source basis.
Country of origin (COO) is often requested as if it were a product attribute, sitting alongside bore diameter and closure type. For bearings it usually is not. A manufacturer can produce the same designation in more than one plant, and the origin of the units a distributor holds depends on which lot they received. Modelling COO as a single product-level value produces records that are confidently wrong.
This guide explains the scopes involved and how to store origin evidence so it remains true.
Three different scopes
Separate three things that are frequently merged into one catalog row:
| Scope | What it describes | Example question it answers |
|---|---|---|
| Manufacturer product | The design identified by manufacturer and full designation | What are the dimensions and configuration of this product? |
| Supplier listing | A seller’s offer of that product, with its own SKU, pack and description | What does this seller say they offer? |
| Inventory unit or lot | Physical units in stock, with lot, condition and documents | Where were the units we actually hold made? |
Dimensions and configuration belong to the manufacturer product. They do not change between lots of the same full designation. Origin belongs to the unit or lot, because it is a fact about where those particular units were produced.
Why product-level COO goes wrong
Consider a typical enrichment attempt. A researcher looks up a designation, finds a marketplace listing showing “Made in Country X”, and writes Country X into the product record. Several things are wrong with that result:
- The listing describes the seller’s units, not the units in your warehouse.
- The same designation may also be produced in Country Y; the listing does not exclude that.
- Once written to the product record, the value propagates to every listing and lot linked to it, including ones with different origin.
- Downstream users, such as customs, compliance or customer service, cannot tell the value came from a third-party listing.
The record now asserts a universal fact supported only by one seller’s unit.
Source basis matters
Origin evidence varies widely in strength and scope. Record which kind you have:
| Source basis | Scope it supports | Notes |
|---|---|---|
| Marking on the physical unit or its packaging | That unit or lot | Strong for the lot inspected; says nothing about other lots |
| Supplier documentation for a delivery | That delivery or lot | Tie it to the delivery or lot identifier |
| Manufacturer statement for a specific shipment | That shipment | Keep the document reference |
| Manufacturer general publication listing production sites | Product, as a set of possible origins | Supports “possible origins”, not which one applies to your stock |
| Third-party marketplace listing | The seller’s units only | Weak evidence for your inventory |
A useful rule: an origin value is only as broad as the evidence behind it. Evidence about one lot creates a lot-level assertion. It never overwrites a product-level field.
A model that keeps origin honest
Illustrative, synthetic values:
| Entity | Identifier | Field | Value | Scope | Source basis |
|---|---|---|---|---|---|
| Manufacturer product | DEMO-101-SEAL (Example Maker A) | possible_origins | Country X, Country Y | manufacturer_product | Manufacturer general publication |
| Supplier listing | SUP-88812 | stated_origin | Country X | supplier_listing | Seller listing text |
| Inventory lot | LOT-2026-0412 | country_of_origin | Country Y | inventory_lot | Packaging marking, inspected |
| Inventory lot | LOT-2026-0519 | country_of_origin | (unknown) | inventory_lot | Not yet inspected |
The table shows three separate facts that would have collapsed into one wrong value in a flat product row. The seller states Country X. The lot actually received says Country Y. A second lot has not been checked, and the record says so.
In the MyBearings draft record envelope, every attribute carries a scope of manufacturer_product, supplier_listing or inventory_lot. The synthetic fixture marks its origin example as inventory_lot with status not_researched, precisely to show that origin is not a product default.
What to publish in a catalog
If your storefront or PIM needs a single origin field, decide what it means and say so:
- Per-lot or per-stock-location origin where your systems track lots. This is the most accurate option.
- “Possible origins” at product level, labelled as such, when only general manufacturer information is available.
- “Not specified” when no suitable evidence exists. A truthful blank is better than a borrowed value.
Avoid presenting a marketplace-sourced value as the origin of your stock. If you must show it, label it with its source.
Questions to settle before enriching COO
- Which scope does the requesting team need: product, listing or lot?
- Which source bases are acceptable for that scope?
- Does your system have somewhere to store lot-level facts, or does it need one?
- What should be shown when evidence is missing?
Answering these first saves research effort that would otherwise produce values nobody can rely on.
Apply it
- See how scope is modelled in the draft bearing record schema.
- Read how MyBearings separates supplier listings from manufacturer products in supplier data.
- If origin is a compliance or customer requirement in your catalog, discuss your catalog.
Methodology article using synthetic examples only; it states no manufacturer specifications. Independent technical review: not yet assigned. Found an error? Tell us.
