This FAQ covers a naming and catalog-data standard for cannabis ecommerce menus, POS catalogs, product filters, and inventory reconciliation.

Why is product naming a technical control?

The menu title feeds customer pages, search indexes, filters, SEO templates, CRM triggers, and reconciliation exports. When the name is inconsistent, all of those get weaker data. So treat the naming standard as part of your catalog schema.

What should the canonical menu title include?

A practical title pattern is:

Brand + Product Line + Form Factor + Cannabinoid/Dose + Size

Example normalization:

Before: WYLD ELDBRY SLP GUM 100(10)
After:  Wyld Elderberry 1:1 CBN+THC Gummies 10pk 100mg

Which fields should be stored separately from the title?

Generate the visible title from structured fields wherever you can. The minimum set of fields:

product_id
brand_name
product_name_canonical
menu_title
category
subcategory
form_factor
weight_value
weight_unit
thc_total_mg_or_pct
cbd_total_mg_or_pct
image_url
coa_url
status

How should units be normalized?

Store the value and the display label separately. Keep the value numeric and the unit as a controlled enum. Then a cartridge listed as 0.5g and one listed as 500mg normalize to the same base unit for filtering and reconciliation.

display_weight = "0.5g"
weight_value = 0.5
weight_unit = "g"
weight_mg = 500

How does naming affect search?

The search index should include the canonical brand name, product line, strain, form factor, category, common aliases, and normalized cannabinoids. Keep abbreviated distributor names in internal fields only, since a customer is never going to type your wholesale shorthand.

How does naming affect filters?

Filters should read structured fields, not text parsed out of the title. Category, brand, form factor, potency band, weight, strain type, terpene profile, dietary attributes, and inventory status each need to be their own field. The menu title confirms those attributes for the customer, but it can't be the only place they live.

How does naming affect reconciliation?

POS exports, ecommerce exports, and traceability package records should join on stable IDs first, not on names. Clean naming still matters, though, because a person works the exception queue, and ambiguous names slow down physical counts and catalog repairs.

What QA process should be used?

  1. Define controlled values for brand, category, form factor, unit, strain type, and status.
  2. Normalize the top-selling SKUs first, then the long tail.
  3. Compare each product against label, COA, POS catalog, and ecommerce menu record.
  4. Run brand-plus-product searches for the top SKUs.
  5. Test category and unit filters against known inventory.
  6. Export POS and menu records and confirm stable joins.
  7. Block new products that do not meet the catalog schema.