Digital Operations
Reviewing Menu Feed Price Discrepancies
DispensaryVA Editorial TeamPublished
menu feedsprice accuracydispensary POSdigital operations
Powered by StealthAgents
Powered by StealthAgents
Digital Operations
A customer walks in with a screenshot of a $35 eighth from the dispensary's website. The POS says $40. The budtender checks the menu platform and sees a third price. The customer is annoyed, the line is growing, and nobody knows which system is right.
Menu price discrepancies are common in dispensaries because the customer-facing menu is rarely one system. The POS may feed a menu platform, which feeds a website widget, which feeds a delivery marketplace. Each connection introduces a delay, a mapping rule, or a manual override. A daily review catches the drift before a customer does.
The first decision is which system owns the price. For most dispensaries, the POS or the state inventory system is the operational source, and the menu platforms are downstream. Write that down. If the website is allowed to override the POS for a specific promotion, say so and record the exception.
Do not let every channel be a source of truth. A price that exists only on the website is a marketing claim, not an inventory fact. A price that exists only in the POS but not on the menu is a customer-service risk. The reconciliation needs a clear hierarchy.
Choose a small set of products for the daily check: new items, high-volume items, items with a recent price change, and items with a promotion. Compare the POS record, the feed export, and the customer-facing page. Record the values side by side.
A workable check includes:
The check does not need to cover every SKU every day. A risk-based sample catches more real problems than a rushed full review. Rotate the sample so every category is checked over a week.
A price mismatch is not one problem. Common types include:
Each type has a different fix and a different owner. A sync delay may resolve without intervention, but it still needs a timestamp. A mapping error needs a configuration change. A manual override needs an approval record.
Fix the source before the surface. If the POS is wrong, correct the POS and let the feed update. If the feed mapping is wrong, fix the mapping and re-sync. If the website is stale, clear the cache after the source is correct. Changing the website first can create a third conflicting value.
Record the correction time and the person who made it. Then verify the customer-facing result in a private browser or a test location. A screenshot with a timestamp is useful proof that the customer saw the corrected price.
If the error affected a customer, decide whether to honor the displayed price, offer a correction, or follow the published policy. That decision belongs to the manager, not the coordinator. Record the decision and the reason.
Menu feeds often fail at the edges: a new product category, a size change, a bundle, or a location-specific price. Ask the feed provider how often it syncs, what fields it uses, and how it handles missing values. Test a price change end to end, not just in the POS.
If the dispensary uses multiple locations, confirm that the feed maps the right menu to the right location. A single-location test can pass while another store shows the wrong price. Include at least one product from each location in the weekly sample.
The menu price change approval log should connect the approved change to the feed correction. The POS support team can help troubleshoot the integration, but the operator owns the pricing decision.
Price accuracy is a customer trust issue and, depending on the claim, a consumer-protection issue. The FTC's advertising and marketing guidance explains the general principle that advertising claims should be truthful, not misleading, and substantiated. A menu price is an offer. If the customer cannot buy at that price, the dispensary needs a clear correction process.
Do not use "the menu is just a guide" as a policy. Customers rely on the published price. If the dispensary cannot honor it, the correction should be visible and the customer should be told before checkout.
At the end of the week, count discrepancies by type, product, channel, and owner. Look for repeat sync delays, products that consistently map incorrectly, and promotions that create conflicts. A high number of manual overrides may mean the approval process is too slow or the feed cannot support the promotion.
Share the pattern with the marketing, inventory, and POS owners. The goal is to reduce the number of corrections, not to celebrate a high catch rate. A stable feed with a few documented exceptions is better than a daily scramble.
A virtual assistant can run the daily comparison, capture screenshots, log discrepancies, and follow up with the feed provider. The assistant should not change prices without approval, override a POS record, or decide whether to honor a disputed price.
Escalate when a discrepancy affects a regulated price, a promotion with legal terms, a location-wide outage, or a customer complaint that may become a refund or chargeback. Preserve the evidence and route the decision to the manager.
Week one: document the systems, choose the sample, and build the comparison sheet. Week two: run the check daily and record every discrepancy, including the ones that resolved on their own. At the end of the pilot, calculate the average time to detect and correct a mismatch. If detection takes longer than a day, the check is too broad or the ownership is unclear.
A menu feed is a promise made at a distance. The review makes sure the promise matches the shelf.