Product Controls
The Evidence Packet for a New Dispensary Product Launch
DispensaryVA Editorial TeamPublished
product launchCOA reviewmenu copydispensary inventory
Powered by StealthAgents
Powered by StealthAgents
Product Controls
A new product launch is usually treated as a marketing moment. The buyer orders a case, the team builds a menu tile, and the floor gets a quick briefing before the weekend. When a customer asks who tested the batch or why the label says one thing and the menu says another, the answers are scattered across email, a vendor PDF, and someone's phone.
An evidence packet turns the launch into a controlled sequence. It does not make the product safe, compliant, or profitable by itself. It gives the operator one place to see what was approved, what was published, what staff were told, and what happened in the first week.
Every launch has at least six links: vendor and product identity, regulatory or internal approval, certificate-of-analysis review, label and menu copy, staff briefing, and post-launch review. A weak link does not always stop the launch, but it should be visible.
Start by naming the accountable owner for each link. The buyer may own vendor identity, the compliance lead may own document review, the marketing coordinator may own menu copy, and the store manager may own the staff briefing. A remote assistant can maintain the packet and chase missing items; the licensed owner or designated reviewer keeps the decisions.
The first section should answer what the product is and who supplied it. Include the product name, brand, category, package size, SKU, batch or lot, vendor legal name, vendor contact, delivery reference, and the date the product was accepted.
Attach the current vendor license or registration evidence if your state requires it, the invoice or manifest, and the receiving record. Do not rely on a vendor's logo or a sales representative's email signature as proof of authorization.
If the product is new to the store but not new to the market, record the prior sales history only if it is verifiable. A vendor's claimed "top seller" is not evidence. A documented sell-through report from a trusted source is. The packet should distinguish claims from records.
The certificate of analysis is the bridge between the product file and the customer-facing copy. Use your existing COA review routine to confirm that the batch identifier, product name, test date, lab, and required panels match the package and the vendor documents.
Record the COA version and the review date. If the COA is missing a required panel or the batch identifier does not match, the launch should pause at the review step. The COA management support workflow can keep the documents organized, but the authorized reviewer decides whether the product may proceed.
Do not copy lab results into marketing copy unless the claims are accurate, not misleading, and consistent with the applicable advertising rules. A potency number on a menu is not the same as a health claim. The FDA's cannabis and cannabis-derived products page is a useful reference for the federal regulatory boundary, but state cannabis advertising rules still govern the launch.
Create one approved copy block for the product. It should include the product name, brand, category, size, price, potency or profile fields that your menu supports, and any required warnings or disclaimers. Store the approved version with the date and approver.
Then compare the package label, the POS record, the menu feed, and the website listing. A launch packet is not complete until those four surfaces agree on the facts the customer will see. Common mismatches include:
Assign one person to make the correction and another to verify it in the customer-facing view. A screenshot with a timestamp is useful evidence that the customer saw the corrected version.
Staff do not need a marketing essay. They need five answers:
Record who attended the briefing and when. If the launch includes a vendor-led training, keep the attendance record and the training materials. Do not let a sales representative's verbal claim become the store's official product description.
The launch packet should include a short review after the first seven days. Look at units sold, returns, customer questions, menu corrections, and staff feedback. If the product is not moving, the answer may be price, placement, staff confidence, or customer fit. Do not change the product claims to fix a sales problem.
Record the review date and the owner. If the product is discontinued, note the reason and the inventory disposition. If it is reordered, note the evidence that supported the decision. That turns the next launch into a comparison rather than a fresh guess.
A launch should stop or pause when the product identity cannot be matched, the COA is missing or inconsistent, the label conflicts with the approved copy, the vendor cannot produce required authorization, or the price and promotion cannot be verified in the POS.
The stop condition should be written into the packet. "Hold until the compliance owner reviews the COA" is actionable. "Use good judgment" is not. When a stop condition occurs, preserve the documents, notify the owner, and record the decision. Do not launch on a verbal approval that is not in the file.
A workable packet has eight tabs or sections:
| Section | Minimum evidence |
|---|---|
| Product identity | Name, SKU, size, batch, category |
| Vendor | Legal name, contact, authorization document |
| Receiving | Invoice, manifest, acceptance date |
| COA | Current report, batch match, reviewer, date |
| Label | Approved label image or text, version |
| Menu copy | Approved copy, price, promotion, approver |
| Training | Briefing date, attendees, materials |
| First week | Sales, returns, questions, corrections, decision |
Keep the packet in a controlled location and link to source documents rather than duplicating sensitive files. A remote coordinator can maintain the index, request missing items, and prepare the review. The licensed operator and designated reviewers keep the launch decision.
Choose the next new SKU and run the packet from vendor contact to first-week review. Time each step. If the COA review takes three days because the document is missing, the packet has done its job by making the delay visible. If the menu copy changes after approval, the packet shows where the version control failed.
The goal is not a perfect launch. The goal is a launch the dispensary can explain.