Ecommerce · Part 2 of 7 · 2 min read

Cannabis Product Naming FAQ

On this page
  1. Why is product naming a technical control?
  2. What should the canonical menu title include?
  3. Which fields should be stored separately from the title?
  4. How should units be normalized?
  5. How does naming affect search?
  6. How does naming affect filters?
  7. How does naming affect reconciliation?
  8. What QA process should be used?

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 shows up on your product pages, in site search, in the filters, in Google results, in automatic customer emails, and in the exports you match against the POS. When the name is inconsistent, every one of those gets worse. So set naming rules for the whole store and follow them, rather than leaving names to each person's style.

What should the canonical menu title include?

Put the brand first, then the product line, the cannabinoid mix, the form, the size, and the dose in milligrams, like this:

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?

Build the visible title from separate fields wherever you can. Keep these for every product: the product ID, brand, product name, menu title, category, subcategory, form, weight, THC and CBD amounts, photo, COA link, and active or inactive status.

How should units be normalized?

Keep the number and the unit in separate boxes: the number typed as a number, the unit picked from a list instead of typed. Then a cartridge listed as 0.5g and one listed as 500mg both count as 500 mg, so they land in the same filter and add up together in the reconciliation exports.

Site search should match on the brand name, product line, strain, form, category, the nicknames customers use, and the cannabinoid amounts. Keep abbreviated distributor names in internal fields only, since customers rarely type your wholesale shorthand.

How does naming affect filters?

Filters should read their own entries in the product record, not words pulled out of the title. Category, brand, form, potency range, weight, strain type, terpenes, dietary tags, and stock status each should have its own entry, starting with the ones your filters use. 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 be matched by their ID numbers first, not by name. Clean naming still matters, though, because someone has to chase down the mismatches by hand, and ambiguous names slow down physical counts and catalog repairs.

What QA process should be used?

  1. Make drop-down lists for brand, category, form, unit, strain type, and status, so nobody types their own spelling.
  2. Clean up the best-selling products first, then the rest.
  3. Check each product's label, COA, POS entry, and online listing against each other.
  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 each product has the same ID in both.
  7. Keep new products off the online menu until their fields are complete.

Let’s work together

Menu, catalog, or checkout drifting?

I help teams keep online availability honest and the data behind it clean.