Limitations & Known Issues
This page lists current product limitations and known issues so users understand expected behavior.
Current Functional Limitations
🔸 Offline mode cannot sync KDS
KDS requires real-time connection.
Orders created offline only appear when connection is restored.
🔸 Delivery zones require manual setup
Waiterr cannot auto-detect zones.
You must define radius / polygons manually.
🔸 Multi-KDS split timing not granular
If a single order has products going to:
- Bar
- Kitchen
- Dessert station
Only one unified status timeline is shown (per order, not per KDS).
🔸 Ingredient inventory not available yet
Ingredients affect allergens and descriptions
—but do not impact stock (future module).
🔸 Reservation slots cannot auto-detect staffing levels
Slots are based on hours only, not on:
- server availability
- seating capacity (future)
- overlapping bookings
🔸 Menu availability applies globally
Menus cannot use:
- multiple day intervals
- variable seasonal schedules
(yet)
🔸 QR codes must be reprinted when regenerated
For security reasons, old QR becomes invalid.
Performance Considerations
⚡ Very large menus (200+ items)
May load slower on old devices.
Solution: Use categories to reduce scroll.
⚡ Very large table plans
Large maps (>80 tables) require good device performance.
Known Bugs (Being worked on)
These depend on your actual dev backlog — adjust as needed.
- Rare mismatch in table status after rapid offline/online switching
- Delivery ETA occasionally not recalculated on slow networks
- QR scan popup animation flicker on iOS Safari
Upcoming Fixes
- Per-KDS timeline
- Seasonal menu intervals
- Dynamic QR codes
- Inventory sync
- Reservation capacity engine