The Operations section shows a chronological log of everything that happened to an order behind the scenes.
Each entry represents a system action or event, helping you understand what happened, when it happened, and what triggered it. This is especially useful for troubleshooting, support requests, or auditing order flows.
What do the logs show?
Each log entry contains:
Timestamp – When the action occurred
Action type – What happened (e.g. order status change, payment update, POS sync)
Additional details – Technical context such as the source, device, or external system involved
Entries are listed from newest to oldest, so the most recent activity is always at the top.
Common log events you may see
Order status updates
These logs show when the order moved between different states (for example from New to Preparing or Done).
They often include:
The new status value
The source that triggered the change (e.g. a device, live screen, or POS)
POS & integration events
When an order is sent to an external system (such as a POS), this is logged here.
These entries help confirm:
That the order was successfully sent
The external reference or order ID returned by the POS
Webhooks & system callbacks
Incoming webhooks from payment providers or POS systems are logged to show status updates coming from external services.
This is useful to verify that integrations are communicating correctly.
Payment events
Payment-related logs show when an order was marked as paid and may include:
The payment ID
The payment method or provider used
Notifications
Actions such as confirmation emails or receipts being sent are also recorded, making it easy to verify customer communication.
Why this section is useful
The Operations log gives you full transparency into the lifecycle of an order by showing:
The exact order flow
Which system or device triggered each action
Where something may have gone wrong if an issue occurs
It’s primarily intended for support, debugging, and advanced operational insight.