The Activity log and Back-office activity log reports are audit tools that record every action performed in the app and in your business's back-office. They let you monitor how the system is used, identify operational issues and keep a detailed history of every operation.
App
Review what happens on the devices
See the actions recorded in the app and filter by date, device, employee or type.
1Activity log (app)
Go to the back-office → Reports → Activity log.
Important
Order movement logs are only visible for the last 30 days.
Once inside, select the date range you want. You can use the following optional filters to speed up the search:
| Filter | Description |
|---|---|
| Date | Filters by an exact time range |
| Device | Select one or more devices |
| Employee | Filters by a specific employee |
| Type | Log type: information, warning, error, etc. |
| Model | Enter a data model: user, tenant_user, etc. |
| ID | ID of an order, shift, invoice, etc. |
| Action | Search by keyword: offline, network, invoice, etc. |
Each log shows: date and time, device, employee, type and action description.
Back-office
Audit the changes made in the back-office
Check who changed the settings, products or employees, and when.
2Back-office activity log
Go to the back-office → Reports → Back-office activity log.
This log is separate from the app log. It captures every action performed directly in the back-office: settings changes, product creation or editing, rate changes, employee management, etc.
The following filters are available:
| Filter | Description |
|---|---|
| Date | Date range of the action |
| User | Back-office user who performed the action |
| Model | Affected entity: MenuItem, Category, TenantUser, TillReport, etc. |
| ID | ID of the modified item |
| Action | Operation type: created, updated, deleted |
Each entry shows:
- Date and time of the action
- User who performed it
- Model and ID of the affected item
- Change description: modified fields, previous and new values
This log does not include actions performed in the iOS app. For those, see the Activity log (app).
Common use cases
- Audit who changed a price or a productFilter by model
MenuItemand the item ID. - Check whether an employee was created or deletedFilter by model
TenantUser. - Review changes to the business settingsFilter by model
BusinessorOrderConfig. - Detect accidental deletionsFilter by action
deletedin the suspicious date range.
Logs
Interpret each app log
Find the meaning of each message, grouped by action type.
3App log details
Below you will find the meaning of each log that can appear in the Activity log (app). The symbol %@ represents a dynamic value that changes with the context (product name, ID, amount, etc.).
Order management
| Log | Meaning |
|---|---|
Added (%@) | Product added to the order |
Add default item: (%@) %@ | Default product added automatically |
Quantity updated for %@ from %@ to %@ | Product quantity changed |
Removed item: %@ (%@) with quantity: %@ | Product removed from the order |
Order emptied | The order has no products left |
Cancel order | The order has been cancelled |
Set free | Order discarded because it has no products |
Toggle splited items | Products split in the order |
Merge with %@ | Order merged with another |
Move content %@ to new table %@ | Content moved to an empty table |
Move content %@ to table %@ | Content moved to an open table |
Move to virtual %@ | Table moved to virtual |
Discounts
| Log | Meaning |
|---|---|
Added discount (%@) | Discount added to the order |
Applied general discount to each content | General discount applied to the whole order |
Discount removed | Discount removed from the order |
Saving and syncing
| Log | Meaning |
|---|---|
Save | Order saved locally |
Saved state - context, analytics, offline orders, userDefaults | Internal activity log saved by Revo XEF when the app goes to the background. |
Retry to save | Retrying to save the order |
Save failed! %@ | Error saving the order |
No need to save to server, order has't been changed | The order has not been changed and does not need syncing |
Trying to save when still saving... | Save attempt while another save was in progress |
Close without saving yet | Order closed without saving |
Updated status | Server data update |
Locking and access
| Log | Meaning |
|---|---|
Lock | Order locked |
Unlock | Order unlocked |
Force unlock | Forced unlock of a table with an existing order |
Check if locked | Lock status check |
Can't lock because is locked by: %@ | Cannot save: order locked by another user |
Try to print when locked by another | Print attempt while the order is locked by another user |
Invoicing and payment
| Log | Meaning |
|---|---|
Invoice created | Invoice created |
Failed to get new invoice id | Error getting a new invoice ID |
Delete invoice with id:%@ | Invoice deleted |
Delete payment with id:%@ | Payment deleted |
Reopen and delete invoices | Order reopened and invoices deleted |
Reopened | Order reopened |
Charged with (payment method) | Payment made with the indicated method |
Changed payment method | Payment method changed |
Fast Cash | Fast payment completed |
Charge with mPOS | Payment started with mPOS |
Send invoice by mail | Invoice sent by email successfully |
Printing
| Log | Meaning |
|---|---|
Print | Order sent to print |
Print check from preview | Receipt printed from the preview screen |
Print copy | Copy printed |
Fast print check | Fast receipt print |
Reprinted invoice from tables layout | Invoice reprinted from the tables view |
Print kitchen note: %@ | Note sent to the kitchen |
Kitchen note printed: %@ to %@ | Error printing a kitchen note |
Print to kitchen failed | Kitchen printing error |
Print to kitchen dish orders: [X] | Kitchen printing of products by course |
Print to kitchen dish orders: [] | All courses printed |
Print to kitchen dish orders: [0] | First course printed |
Print to kitchen dish orders: [1] | Second course printed |
Print to kitchen dish orders: [2] | Third course printed |
Printed to kitchen from ip X.X.X.X | Kitchen printing from the indicated IP |
Table and session
| Log | Meaning |
|---|---|
Loaded table: %@ with %@ items | Table loaded with the indicated number of products |
Changed table name to %@ | Table name changed |
Preview | Preview screen opened |
Close | Order closed |
Open cash drawer | Cash drawer opened |
Login (S) - Date - IP - Version | Login with date, IP and app version |
Logout (S) | Session closed |
Exit kiosk mode | Kiosk mode session closed |
No Network, went offline | No connection: offline mode activated |
Went online | Connection restored |
Order recovery
| Log | Meaning |
|---|---|
Order recovered | Order recovered successfully |
Order NOT recovered | The order could not be recovered |
Cash machine
| Log | Meaning |
|---|---|
Cash machine charge completed: %.2f | Cash charge completed for the indicated amount |
Cash machine charge failed: %@ | Cash charge failed |
Cash machine canceled | Process cancelled on the cash machine |
Example
Follow a table from start to finish
Match each step of a real sale with what appears in the log.
4Practical example
The following example shows the full sequence of a table from opening to payment:
- Table 1 is opened.
- Products are added: Coca Cola Zero, Coca Cola, Tsukune, Edamame.
- The app checks whether the order is locked.
- The order is saved and synced with the server.
- All courses are printed to the kitchen (IP 10.0.1.200).
- The preview is opened. More products are added: Unagi, Okonomiyaki, Cheesecake Japonesa, Dango.
- They are printed to the kitchen again and the order is saved.
- A note is sent to the kitchen: Marchar postres a la impresora Star blanca.
- The bill is printed from the preview (€47.25, 8 products).
- The order is locked and unlocked to show that the bill has been printed.
- Payment by card is started and completed (€47.25, change €0.00, tip €0.00).
- The order is closed, saved and the invoice is created.
