BevQ · How-To
BevQ database, mappings, duplicates, and archive
Search canonical beverage records before creating, then map location/POS items without duplicating the shared catalog.
What this does
Search canonical beverage records before creating, then map location/POS items without duplicating the shared catalog.
Steps
- Search by brand, item, style, or known identifier.
- Open the canonical record and review its details.
- Create only when no correct record exists.
- Map the location or POS item to the canonical record.
- Merge or archive only when authorized and after reviewing usage.
- Verify the mapped result in the menu and sync history.
Canonical records
Canonical identity separates shared beverage facts from location-specific price and availability.
Mappings
A mapping connects an incoming POS/location item to its canonical beverage. Ignored items remain intentionally excluded until changed.
Missing, duplicate, archived
Missing requires mapping; duplicate requires reconciliation; archived is unavailable for normal selection but can remain in history.
Permissions and scope
- No Access hides or blocks the module. Read Only permits viewing but disables changes. Editor permits the documented create, edit, publish, or administrative actions within the user's assigned scope.
Mobile
- On narrow screens, open the sidebar or overflow menu to reach the same actions; labels and save behavior are unchanged unless this article says otherwise.
Search and canonical records
This control is covered by the BevQ database, mappings, duplicates, and archive workflow.
Applies to /admin/bevq/database
Create, map, merge, and archive
This control is covered by the BevQ database, mappings, duplicates, and archive workflow.
Applies to /admin/bevq/database
Duplicate and missing-mapping states
This control is covered by the BevQ database, mappings, duplicates, and archive workflow.
Applies to /admin/bevq/database
What happens next
Your change is available within the scope you selected.
Warnings
- Merging or archiving shared records can affect multiple menus and mappings.
Troubleshooting
- Missing mapping means the POS item has no confirmed canonical match; search aliases before creating.
- A duplicate should be reconciled through the available merge/mapping workflow rather than creating another record.
- For duplicate and missing-mapping states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.