Reviewing a Vendor COA Change Before a Menu Update

Published November 3, 2026

A certificate of analysis can change after a product has already been listed, and a menu update made too quickly can leave the store advertising a result that no longer matches the package. The front office does not need to interpret the science, but it does need a reliable handoff between the lab document, the package record, and the person who publishes the menu. That handoff is the subject of this routine. The front office can protect the store by making that handoff visible rather than relying on a verbal warning at the counter.

Treat a COA change as a menu-control event

A new certificate is not just a file replacement. It may reflect a new batch, a re-test, a corrected result, or a document that was uploaded to the wrong product. The menu team should treat any change as an event with a source, a version, and a reviewer. The event stays open until the package record and the public listing agree on the facts the store is allowed to publish.

Separate the document review from the marketing decision. The reviewer confirms which certificate applies to which package and whether the required fields are present. The menu owner decides how the product is described and when the update goes live. Combining the two roles makes it easy to publish a claim because the file looked official, even when the package link is still unresolved.

Compare the certificate to the package record

Start with the identifiers. The certificate should connect to a batch or lot, a product name, a testing date, and a laboratory. Compare those identifiers with the package record in the traceability system and the label on the physical product. If the names differ by a capitalization or a flavor descriptor, do not assume the match. Record the exact values and let the reviewer confirm the relationship.

Check the version and the date observed. A certificate downloaded last month may not be the current document, and a screenshot may not show the full report. Keep the original file or a controlled link, note the retrieval time, and record who supplied it. When a supplier sends a replacement, preserve the earlier version so the change can be explained later. Version history is part of the evidence, not an optional convenience.

Hold the menu update until the comparison is done

A hold is a deliberate state, not a failure. The menu item can be marked as pending review while the store continues to sell product that is already verified. The hold should name the reason, the owner, and the condition that releases it. If the product is already visible to customers, the team may need an approved interim description that avoids the disputed claim until the review closes.

Do not use the hold to hide a product problem from the compliance owner. The same event should route to the person who can decide whether the product may remain on the floor, whether a batch must be quarantined, or whether the supplier needs to be contacted. The menu team's job is to keep the public listing accurate while that decision is made. It is not to make the decision.

Document the version and the reviewer

The record should show the certificate version, the package identifier, the menu item, the observed fields, the reviewer, and the time of the decision. If the reviewer relied on a supplier email, attach the reference rather than paraphrasing it. If a field was unreadable or missing, write that down instead of filling it from a similar product. A clean record makes the next review faster and reduces the chance of repeating the same question.

Use a short reason code for the outcome. Examples include matched, matched with a corrected description, awaiting a supplier document, package mismatch, and quarantined pending review. The code should describe the evidence state, not the person who raised it. That wording matters when the store reviews patterns across suppliers, categories, or locations.

Handle a mismatch without guessing

When the certificate and the package record disagree, preserve both values and stop the dependent action. The menu update waits, and the compliance owner receives one clear question. Do not average the results, choose the more favorable number, or publish a range that the document does not support. The store can explain that a review is in progress without turning the uncertainty into a marketing claim.

If the mismatch involves a product already sold, the event may need to connect to the recall or customer-notification routine. That does not mean every discrepancy is a recall. It means the reviewer should have a path to escalate when the facts require it. Document the referral and the time it was made so the team can see that the handoff happened.

Keep batch and product names aligned

Menu names often differ from the names on the certificate and the package. A house name, a brand name, and a strain name can all appear in different systems. Maintain a mapping that shows which public name belongs to which package record and certificate. Review the mapping when a supplier changes a label or a product is re-listed under a new name. Without that map, a correct certificate can be attached to the wrong menu card.

The mapping should be owned by one role and stored where the menu team can use it. It should not live only in a spreadsheet on someone's desktop. When a product is discontinued, mark the mapping inactive rather than deleting it, so historical records remain explainable. The goal is a traceable public name, not a perfect taxonomy.

Review COA changes monthly

Report counts with their denominators. How many COA changes were received, how many required a hold, how many were released with a matched record, and how many remain open? A rising number of holds may be a sign of stricter review rather than a worse supplier. A falling number may mean the team stopped documenting. Interpret the trend with the process change that accompanied it.

Close with a public listing that matches the record

Close the event only when the certificate, the package record, and the menu listing agree on the fields the store publishes. Record the final description and the time it went live. If the product was removed, record the reason and the effective time. The close should let a later reviewer answer a simple question: what did the store tell customers, and what evidence supported it?

This routine does not require the front office to become a lab. It requires a disciplined comparison, a visible hold, and a named reviewer. Dispensaries that build that habit can move quickly on routine menu updates while keeping the rare discrepancy from becoming a public claim they cannot defend. The certificate is one input; the package record and the approved listing are the other two.

Sources

• Metrc, resources and traceability documentation
• Virginia Cannabis Control Authority
• U.S. Food and Drug Administration, recalls, market withdrawals, and safety alerts

Confirm current Virginia requirements and your own written operating procedure before changing a workflow. This guide is operational context rather than legal advice. Keep the approved policy version beside the routine so staff can see which rule applies. Review the routine after any change in the underlying requirement.