Bork Booking
Checking your session and loading restaurant data.
If this screen remains visible, reload the page.
Reload pageOperations
Recent middleware events
Up to 100 recent events loaded.
New requests will appear here automatically.
Operations
Time window
Statistics follow the log retention period.
Counts represent stored requests, counted once by current status. Success rate excludes pending and ignored requests. Durations cover successful requests delivered on their first attempt, from webhook receipt to provider completion. Older or unmeasured requests are excluded from duration statistics.
| Integration | Requests | Successful | Failed | Pending | Ignored | Success rate | Measured | Average | Fastest | Slowest |
|---|
Both directions of a route are measured separately. Provider request duration excludes queue wait and any deliberate delay (e.g. a configured bill-complete delay). Queue wait is not applicable for actions executed directly within the webhook response.
| Route | Measured | Average | P50 | P95 | P99 | Fastest | Slowest | Queue wait | Delay |
|---|
| Restaurant | Requests | Successful | Failed | Pending | Ignored | Success rate | Measured | Average | Fastest | Slowest |
|---|
Capabilities
Reservation sources send guest, table, and booking changes through the middleware to the point of sale.
Reservation source → Middleware → Point of SaleProduct updates
September 2026
New integrations and operator-facing behavior are recorded here when they are released.
A new "Name in memo" switch in the Domino settings puts the guest name at the top of the booking memo. It works independently of "Send guest name", so the name can be left out of the Domino name field and only appear in the memo.
Guest tags coming from SevenRooms are included in the POS memo by default. A new "Send booking tags" switch in the Domino settings lets a restaurant turn them off.
A configured bill-complete delay (e.g. Domino waiting before delivering to SevenRooms/Zenchef/Odin) was being counted as processing time in the overall "Average"/"Slowest" cards and the P50/P95/P99 duration cards, making a restaurant with a 60-120s configured delay look like it had multi-minute latency. Those cards now exclude the deliberate delay, matching how queue wait already did; "Avg deliberate delay" continues to show the delay itself separately.
Duration percentiles used to be computed from every matching delivery in the selected window, so a busy restaurant or a wide timeline range could make this the slowest read in the admin and trigger "Could not load statistics: Loading took too long". The underlying query now takes a random sample of up to 3,000 deliveries per restaurant/route — statistically just as accurate for percentiles — and the request also gets more time (45s instead of 15s) to finish.
Live measurements showed Cloudflare Queues itself adding several seconds of latency, even with the fastest possible batch settings. A freed reservation is now delivered to Domino directly within the webhook response instead of waiting for queue delivery; the queue is still used as the retry path if that first attempt fails.
Reservation-to-Domino delivery now runs on a dedicated, latency-critical queue, separated from Domino-to-reservation-system replies. The queue processes one message at a time instead of waiting to batch, and duplicate database reads before the Domino request were removed.
Domino-to-reservation-system deliveries (SevenRooms, Zenchef, Odin) now record the same timings as the reverse direction, including actions executed directly in the webhook response. Statistics show queue wait separately from any deliberate delay (such as a configured bill-complete delay), add P50/P95/P99 alongside average and slowest, and break results down by integration route.
Analyze the last 30 minutes, hour, four hours, or choose an exact period within retained logs using the timeline and date-time fields.
The restaurant audit trail now sits below the configuration form and stays collapsed until you open it.
Inspect timings per delivery attempt and compare successful requests, errors and processing durations across restaurants and incoming integrations. Statistics cover the configured log retention period.
Restored missing sign-in and configuration controls. Startup now shows a loading screen and reports stalled requests instead of leaving an empty page.
Queue batch waiting is reduced from 5 seconds to 0.5 seconds for all booking providers. New delivery attempts record webhook, queue and Domino request timings to support further performance analysis.
Restaurant errors now combine repeated missing-table messages into one compact table-number list.
Formitable, SevenRooms, Frank, Zenchef, and Odin can now each restrict Domino TicketExport traffic to configured CenterKey values.
Live traffic and Issues can now be narrowed to an exact period within the available event history.
Odin follows the familiar booking-provider pattern: one unique webhook URL token per restaurant and one bearer token for API calls.
Connect Zenchef’s development environment to Domino with a unique, copyable webhook URL per restaurant.
custom_field = bork loop protection, and skipped-table rules are supported.Skip-table settings now accept inclusive ranges alongside individual table numbers.
0, 666, 200-250
Management
Configuration
Connect a booking system to a point-of-sale system.
Access
Team
Manage who has access to this operations console.
Account
Create an additional account for a colleague.