Data model
This page is a conceptual map of the things that live inside a workspace and how they connect. It is not a database reference; it is here so you understand why entering a fact in one place makes it answerable everywhere.
The entities
| Entity | What it is | Belongs to |
|---|---|---|
| Workspace | Your isolated environment (a tenant) | — |
| User | A person who signs in | One or more workspaces (via membership) |
| Membership | A user's role in a workspace (owner / admin / member) | Workspace + user |
| Business | A legal entity that places goods on the market | Workspace |
| Contact | A named person for a business (incl. the regulatory contact) | Business |
| Brand | A trading brand; can span several businesses | Workspace (linked to businesses) |
| Product | Something you sell | Business (and optionally a brand) |
| Pack | A named outer pack (case, mailer, transit wrap) | Product |
| Pack component | One material line (material + weight) | Product (primary) or a pack |
| Volume | Quantity placed on a market in a period | Product + business + market |
| Market | A nation/region with its own rules | The regulatory brain (referenced by code) |
| Registration | A business's enrolment with a market's scheme | Business + market |
| Obligation | A market's requirement (register / report / pay) | The regulatory brain |
| Label check | A point-in-time check of on-pack artwork vs. cited rules | Product |
| Estimate / redesign | Product Builder outputs (new-product estimate, redesign concept) | Business / product |
Two of these - market and obligation - live in the read-only regulatory brain, not in your workspace. Your data references markets by their code; the brain supplies the rules.
How they relate
Reading it in words:
- A workspace holds many businesses; each business has contacts and can be linked to many brands (and a brand can span many businesses).
- A product belongs to a business and optionally names a brand. Its packaging is a set of pack components - primary packaging attaches straight to the product; secondary and transit packaging is grouped into named packs.
- Volume ties a product to a market and a period - the quantity that drives fees.
- A registration records a business's enrolment in a market's scheme; the obligations for that market come from the brain.
- Label checks and Product Builder outputs (estimates and redesign concepts) hang off the product or business they concern.
Why the shape matters
Because everything funnels through this shared model, you enter a fact once:
- Change a pack component's weight and every fee, recyclability rating and report that uses it updates together.
- Add a market to a product's volume and its obligations, labelling rules and deadlines appear - no re-entry.
- Split work across businesses and access can be granted per business, enforced at the database (see Tenant isolation).
Every computed number carries a confidence label and a citation back to the brain rule behind it.
Where to go next
- Products & packaging - creating the products, packs and components above.
- Markets & streams - the market/obligation side.
- Glossary - each entity defined in one line.
- Tenant isolation - how this data is kept separate.