Uber menu, price, and availability sync

Overview

• MiniTill's shared catalogue is the source for POS, Online Ordering, and supported marketplace publishing.
• Marketplace-specific Product/Modifier prices can differ from the normal Store price; normal price is used as fallback where no marketplace override exists.
• Uber catalogue mapping/publishing uses MiniTill Category/Product/Modifier data rather than a separate duplicate operational menu.
• Product/Modifier availability changes can be pushed to the connected Uber Store.
• External availability sync has visible syncing/synced/failed/not-mapped state and retry rather than silently assuming the provider changed.

When to use this

• Use menu/availability sync when changing Uber prices/menu mappings or when the kitchen sells out of a Product/Modifier.

Step-by-step

1. Maintain the Product/Modifier in the normal MiniTill catalogue.
2. Set marketplace price overrides only where required.
3. Review Uber catalogue mapping/preview.
4. Publish/update the menu through the supported Uber workflow.
5. For sell-outs, change MiniTill Availability and monitor Uber sync status.
6. Retry failed provider sync only after checking the mapping/connection error.

Common mistakes

• Do not maintain a completely separate manually duplicated Uber menu unless provider requirements explicitly require data MiniTill cannot represent.
• Do not assume a MiniTill availability change reached Uber when sync shows Failed or Not mapped.
• Do not change normal Store price just to alter Uber marketplace pricing.

Troubleshooting

• If one item does not update, inspect its provider mapping before republishing everything.
• If every availability update fails, check the Store connection/mapping/provider status.