Research a physical product supply chain from one SKU

Most supply-chain research goes wrong in the first ten minutes.

Someone sees a brand, a country, a retailer listing, or an import category and turns it into a confident story about where the product came from. That is how a useful workflow becomes a hallucination machine.

The better version is an evidence ladder:

SKU or package -> label facts -> source-backed claims -> category context -> unknowns -> verification asks

1. Freeze the product identity

Start with the smallest concrete unit you can prove:

• product name
• brand
• package size
• UPC or SKU
• flavor or variant
• market where it was bought
• front and back package photos
• package-back company line
• lot, plant, or best-by codes

Do not start with "Oreo is made by X" or "honey comes from Y." Start with the package in your hand.

2. Split roles before researching

Create separate rows for each role:

The big mistake is collapsing these into one company. Walmart can sell Oreo without making the cookies. A brand owner can own a product without proving which facility packed one SKU.

3. Build the materials map

Turn label text into lanes:

• main ingredient or material
• secondary ingredients
• additives
• packaging body
• cap, wrapper, seal, pouch, carton, or case
• compliance-sensitive claims

For food, this means ingredients and allergen statements. For packaged goods, it also means resin codes, recycling marks, carton labels, and packaging supplier specs.

4. Gather sources in order

Use this order because it keeps the research grounded:

1. Physical package and label
2. Official brand or manufacturer page
3. Retailer product page
4. Regulatory guidance or official datasets
5. Import records or shipment data, only when product-specific enough
6. Trade codes for category context

Public trade data is useful, but it is not SKU proof. It can tell you a category flow, not the exact path of one bag of chips.

5. Score every claim

Use four labels:

This is where the workflow becomes safe. The output is allowed to contain uncertainty, but uncertainty must be visible.

6. Turn unknowns into questions

Every unknown should become an ask:

• What plant or lot code does this package map to?
• Who packed this exact SKU?
• Which country statement applies to this package?
• What is the packaging film structure?
• Which importer or distributor handled this batch?
• Are authenticity, organic, kosher, halal, allergen, or safety documents available?
• Which HS or HTS code is appropriate for category context?

That action list is the business value. A seller or operator can send it to a supplier, broker, distributor, or internal compliance owner.

7. Publish the pack

The final pack should include:

• product identity
• source table
• claim table with confidence labels
• materials map
• manufacturing and distribution clues
• trade or regulatory context
• unknowns
• verification question list

Do not publish a finished origin claim unless the evidence supports that exact package.

Steal this starter

# SKU supply-chain evidence pack

## Product identity
- Product:
- Brand:
- Variant:
- Package size:
- UPC or SKU:
- Market:
- Package photos:

## Claims
| Layer | Claim | Confidence | Source | Caveat |
|---|---|---|---|---|
| Identity | | | | |
| Materials | | | | |
| Manufacturing | | | | |
| Trade | | | | |

## Unknowns
- [ ] Exact packer or manufacturer:
- [ ] Plant or lot code:
- [ ] Importer or distributor:
- [ ] Raw material source:
- [ ] Packaging material spec:
- [ ] Compliance documents:

## Verification asks
- 

Run the interactive version here: Research Any Physical Product From One SKU.