Key takeaways
- Create stable IDs for services or menu items and maintain location-level price, availability, duration, and eligibility.
- Define which system is authoritative for each field and how profile, site, POS, booking, and printed materials receive changes.
- Review machine-transcribed or customer-uploaded menu information and publish a current preferred source.
- Measure mismatches that affect a real purchase, not only catalog completeness.
01
The customer finds the mismatch at the counter
Search shows a service and a price. The location page describes a different package. Booking uses an old duration, and the branch says the service was retired. Every surface copied a once-correct record, but none owns the current truth.
Model each item with a stable ID, public name, description, category, locations, channel eligibility, price and currency, tax treatment where relevant, duration, staff or equipment requirement, availability state, effective dates, source system, approver, and last verified time. Keep the display wording separate from the identifier so a copy edit does not create a new product.
Swipe to compare every column
| Field | Authority candidate | Critical mismatch |
|---|---|---|
| Price | POS or commerce system | Profile or menu shows an unhonored amount |
| Availability | Inventory or scheduling | Customer can order what the branch lacks |
| Duration | Service operations | Calendar capacity becomes false |
| Description | Reviewed content catalogue | Claim exceeds the actual service |
02
Use the platform field for the job it actually does
Eligible profiles can show services, menu sections, items, descriptions, and prices. Restaurants may have owner-uploaded, customer-uploaded, API-provided, or website-transcribed menu sources. Choose and maintain the preferred source rather than assuming the newest visible menu came from the business.
Custom service names must follow policy and should remain names—not a place for phone numbers, personal information, price stuffing, or promotional copy. Descriptions can carry useful scope and constraints while the location page provides fuller context.
03
Release changes across channels with effective time
A price or availability change should produce updates for POS, ordering, booking, site, structured data, profile, call scripts, printed materials, and staff guidance. When a channel cannot update at the same time, define the safe sequence and temporary customer message.
Sample locations after propagation. Check mobile display, category grouping, currency, modifiers, taxes or fees, unavailable state, and the final transaction. A profile editor showing the new value does not prove the customer-facing menu or ordering provider has changed.
04
Reconcile the promise to the transaction
Log customer-reported mismatches with item, location, source, observed value, actual value, time, and outcome. Use those reports to improve monitoring rather than correcting one screen and closing the case.
Track stale items, price conflicts, unavailable purchases, wrong-duration bookings, source overrides, update latency, and disputes. Catalog operations are successful when a customer can choose and buy what the local business actually offers.
Primary sources and further reading
Use the source material to validate details against your own context and current platform configuration.
This field note follows the XenGrowth editorial policy: primary sources where available, visible limitations, material review dates, and no invented first-hand experience.
Stay with the problem
