Product & Party Master Data
One product record and one party record per tenant — with per-jurisdiction customs classifications hanging off the product, country of manufacture and country of origin kept as different facts, party identity / roles / registrations as separate axes, and change detection that flags when a supplier or spec moves in a way that should trigger re-review.
The problem
"We import the same part into the US, the EU, and Mexico. Our 'HS code' field is one value — those are different classifications with different review status."
One code, many jurisdictions
"Origin gets set to whatever the manufacturer's country is. That's not how origin works, and it's a Reasonable Care problem."
Origin ≠ manufacture
"A supplier changed. Nobody re-checked the parts we source from them. Is this party a 'verified supplier'? Depends who you ask."
Stale, ambiguous parties
How Qubere addresses it
One product, many classifications
The most important design point for a multi-region import program. A classification is a reviewable case with the GRI analysis, the rulings referenced, and the reviewer's identity — not a code in a field.
| Jurisdiction | Classification | Status | Reviewer | Effective |
|---|---|---|---|---|
| 🇺🇸 US HTS | 8537.10.9170 | APPROVED | D. Osei (broker) | 2026-04-01 → |
| 🇪🇺 EU CN | 8537 10 91 | IN_REVIEW | pending | — |
| 🇲🇽 MX | — | not started | — | — |
Product master-data review
Product.reviewStatus is a separate lifecycle from any classification, origin, or trade-remedy decision attached to the product — it's the sign-off on the record itself: its name, description, identifiers. A product can carry an APPROVED US classification while its own master data has never been looked at, and the reverse is also true. Neither one is allowed to stand in for the other.
| Action | Transition | Reviewer | When |
|---|---|---|---|
| APPROVE | IN_REVIEW → APPROVED | D. Osei | 2026-10-02 |
| START_REVIEW | NEEDS_REVIEW → IN_REVIEW | D. Osei | 2026-10-01 |
| REQUEST_CHANGES | IN_REVIEW → NEEDS_REVIEW | D. Osei | 2026-09-30 |
Origin as a fact
Country of manufacture and country of origin are stored as different facts. If there's no approved origin determination, the system says so — and the AI assistant refuses to substitute a manufacturer or supplier country, even when its own fields mention one.
Party master · identity / roles / registrations
Those aren't the same question and Qubere doesn't pretend they are. PartyRole records what a party does; PartyRegistration tracks per-country claims through their own CLAIMED → UNDER_REVIEW → VERIFIED lifecycle — independent of the party's UNREVIEWED → IN_REVIEW → APPROVED status.
One party, every role
A supplier that later becomes your client's importer of record doesn't start a second life as a new record. It's the same party gaining a role — its screening history, its known aliases, every document already linked to it, all carried forward. Search for the company once and see everything it does for you, not whichever module happened to create it first.
Change detection & CSV import
Signals that a product's spec, sourcing, or supplier moved in a way that should re-open review — surfaced, not silent. CSV import matches against existing records rather than blindly duplicating, and flags ambiguous matches for a human.
| CSV row | Best match | Score | Decision |
|---|---|---|---|
| "BMS Ctrl Bd RevC" | PRD-2291 BMS Control Board Rev C | 0.96 | auto-match |
| "Enclosure ALU 240" | PRD-2288 / PRD-2312 | 0.71 / 0.69 | review |
| "Cell 21700 5Ah" | — | — | create new |
Product Intelligence
Matching a line item to a product isn't the end of the story. Once a filing is accepted or released, Qubere compares what was actually filed against the product's current approved classification and verified origin — and flags a mismatch for review, even if the filing already went out the door. An unusually priced line gets the same treatment against that product's own historical pricing.
The master, extended
Assistant reads all of it — get_product, get_party, get_party_history, get_product_origin_position — RBAC-gated, through the same services the screens use.
Objection handling
| "We already have an ERP item master / MDM." | Qubere isn't replacing the commercial item master — it's the customs master: per-jurisdiction classification, origin determination, sourcing evidence, screening summary. Import from the ERP; be the system of record for the trade attributes the ERP models badly. |
| "Auto-classification?" | AI assists (GRI analysis, ruling references) and can auto-approve above a confidence threshold you set. Assisted, auditable, reversible — never a black box that silently sets the field. |
| "PEP / beneficial ownership on parties?" | PEP (politically exposed person) screening is not built. Ownership and relationships are: each party has a Relationships tab, network findings show the ownership graph behind a screening hit, and a 20-character LEI can be looked up against public GLEIF data and attached as evidence without changing party facts. |
| "If a supplier becomes an importer, do we lose their history?" | No — it's the same party gaining a role. Screening history, aliases, and every document link carry forward; nothing restarts from zero. |
The close
Next step: send us a slice of your product catalog. We run the CSV import live — you see the match-don't-duplicate behavior and the per-jurisdiction model on your own data.
Full detail: docs/apps/customs/sales/product-and-party-master.md · docs/apps/customs/data/product-master.md · docs/apps/customs/data/party-master.md