The product stayed the same.
Everything around it changed.

Early catalog concepts combined product content, store prices, quantities, and lab evidence. Potency appeared editable even though it came from a lab result. Reviewing the workflow and wireframes exposed facts with different sources and lifecycles.

The historical Georgia consumable-hemp launch scope supplied product-form, testing-evidence, and labeling constraints for these publication checks.

I considered keeping certificate fields on the product. Instead, I gave lab evidence its own Lab Result record and validity period. When evidence expires, the publication check blocks the affected store listing and names what needs attention. The product’s description and packages remain intact.

That split adds records and links to maintain. It also gives recovery a clear target: review replacement evidence, link it to the applicable product or variant, and check the listing again. The operator fixes the changed fact without rebuilding the product.

I separated five records. Product holds shared identity and content. Variant describes a sellable package. Listing is a store’s offer; Inventory tracks stock at that store. Lab Result supplies testing evidence for the applicable product or variant.

The certificate-capture flow follows the same boundary: capture its source, review extracted results, link its coverage, derive lab-sourced values, and explain publication blockers. Potency stays traceable to the result that supplied it.

We compared browsing by record type, a guided launchpad, and a queue of work spanning the catalog. I chose guided setup for first publication, with direct catalog and inventory workspaces for returning operators.

A record-first structure makes the model visible, but asks a new operator to know where to start. Guided setup provides that sequence; direct workspaces avoid making a returning operator repeat it. Both paths use the same records.

Research into standards and vendor formats did not yield a complete product-data contract for this catalog. We developed and published the versioned Cannabis Product Schema, with a neutral core and a separate Georgia hemp profile.

The application’s Variant and the schema’s Package serve related but different jobs. Listing and Inventory organize store operations, while the schema also defines Label and Party documents. I kept the exchange contract separate from the operator’s work rather than forcing the interface to mirror an import file.