An origin or forced-labor question just landed

Where did this actually come from — past what the supplier declared?

A UFLPA detention, a customer origin ask, a forced-labor allegation — each turns on one thing: the real origin of a component, not the one on the form. Map Collective traces parts to source across tiers and lays declared origin against observed trade signal — so you rebut a presumption with evidence, not assertions.

The trigger
A detention, an allegation, a customer audit.
The ask
Real origin, component-deep, on the record.
The gap
A declared origin the data won't support.
01 · The trigger

The label says one country. The components tell another story.

Origin exposure is a tracing question: follow the component back to where the material is actually grown, mined, or made — and lay it against what was declared. We map both, and label every node for exactly what the evidence supports.

02 · Your exposure

The presumption is the law's. The proof has to be yours.

Compliance & legal
Can I rebut the presumption?
Component-level origin traced to source and corroborated in independent trade data — the evidence a UFLPA detention demands, not a supplier's word.
Trigger: a CBP detention, a forced-labor allegation.
Sourcing
Which origins carry the risk?
Every input mapped to the regions it actually comes from, flagged against forced-labor and sanctioned-origin zones — before the order, not after the hold.
Trigger: a new program, a high-risk commodity.
Audit & ESG
Will the origin claim hold up?
Declared origin laid against observed signal, every node labeled corroborated, divergent, or unobserved — defensible in front of a customer or regulator.
Trigger: a customer origin audit, an investor ask.
03 · How the exposure map reads it

One engine. The same exposure spine every door opens.

01 · Integrate

Start from the data you already own.

Your bill of materials, purchase orders, and trade records — fused with observed external signal. No survey. No waiting on a supplier to self-report. We map what's declared and lay it against what's actually moving.

BOM & POsTrade recordsDeclared vs. observed
02 · Rank

Surface where origin risk actually concentrates.

Not every input carries origin risk. GRID ranks by which components trace to flagged or sanctioned regions — so the part that triggers a detention surfaces ahead of the one you assumed was the problem.

Impact-rankedN-tierReal-time
03 · Decide

Rebut with evidence, not assertion.

An origin exposure map you can take to customs or a customer: which inputs trace clean, which carry risk, and how strong the evidence is for each. Every node labeled — corroborated, divergent, or unobserved. We never inflate a guess into proof.

Exposure mapConfidence-labeledProvenance

Every door into one exposure engine.

Origin & forced labor is the source-tracing door — UFLPA, forced-labor presumptions, sanctioned origins. We map exposure, never a certification. It's the same map underneath — opened by a different trigger. Walk in through whichever one is on your desk today.

Start

Prove origin before the shipment is held.

A scoped pilot on one commodity or product line. We trace your components to source, lay declared origin against observed trade signal, and label every claim — so a presumption meets evidence, in weeks, not quarters.

What you'll have at day 60
  • Component-level origin traced to source across tiers.
  • Declared origin laid against observed trade signal.
  • Exposure ranked by which inputs carry flagged-origin risk.
  • Every node labeled — corroborated, divergent, or unobserved.