LOADING
PRODUCTS, SERVICES AND THEIR DOCUMENTATION
The master registry for everything a merchant sells. Ordinary products and services sit alongside heavily documented categories, and the difference is which fields are required rather than which system holds them.
A SKU exists here first. Creating one in a storefront does not make it sellable; the registry state does.
Certificates and safety data sheets are required by product category and program, not universally. A retailer registers products without either.
Where a category calls for it, the product page is generated from structured fields rather than typed by the merchant, so there is no free-text surface for claims to appear on.
Quantity ceilings, geographic restrictions, age restrictions and permitted rails travel with the SKU into every eligibility decision.
Internal ID, merchant SKU, name, category, supplier and manufacturer.
Where required: certificate of analysis, safety data sheet, license or certification, with lot and batch association.
Laboratory identity is checked against a known-lab registry, analysis date for currency, and declared identity against the SKU record.
Chemical identity is checked against the patented and branded compound registry. A match makes the SKU permanently unpublishable.
Quantity ceiling, permitted geographies, permitted rails, age restriction where applicable.
DRAFT to REVIEW to APPROVED to ACTIVE. An unknown SKU fails closed at checkout.
A lapsed certificate moves the SKU to SUSPENDED and removes payment eligibility. Support cannot lift it.
The registry is the source of truth for what may be sold. A product in a storefront that does not exist here, or exists here in any state other than active, is blocked at eligibility rather than quietly permitted.
BRD-9002 sits suspended on an expired certificate. The document drives the product state, and no role can lift it.
