Find anything faster with the finder
Search is most useful when it recognizes ordinary wording while preserving precise identifiers. A misspelled setting name may still find the correct page, but a receipt number or barcode must remain exact. Review result groups and permissions before turning a convenient shortcut into a routine.
Before using this with live customers
Start in a fictional training workspace with a small catalogue, named staff and known opening quantities. Decide what the operator should be able to do, which branch owns the work and which evidence will show that it succeeded. Check the installed edition and build before following a new control. A plan entitlement, a workspace switch and a staff permission are separate checks. Hiding a menu simplifies the view; it never grants permission to the underlying operation. Keep administrator credentials private and give each employee an account that matches their responsibilities.
A short, repeatable acceptance exercise
Write down the starting record and the expected result before making the change. Use one ordinary item and one edge case: a decimal quantity, a modifier, a discount, a missing cost or a long Arabic product name, depending on the task. Perform the action once, inspect its saved record, then reopen the screen in a separate session. Verify that the original identity and totals survived. If a button disappears, examine role, feature switches and branch scope before assuming that data has been lost. A fictional demonstration is evidence of that tested workflow, not of every possible customer configuration.
Online / SaaS
Tablet navigation and the finder
- Use the menu button to collapse the sidebar. Pin the expanded menu when there is enough width; the saved preference belongs to the current user/browser.
- Open Search pages, actions and records, or press Ctrl+K/Cmd+K when you are not entering a barcode. Start with a product name, setting concept or receipt reference.
- Use result groups and filters. Typo-tolerant name matches help with wording; check exact barcode and receipt numbers before choosing a record. More results means the initial list is bounded.
- Open a result to inspect its page. Search never executes a sale, refund or settings change. Use related-record links only within your branch and role scope.
Roles, duties and branch access
- Open Team as owner. Create a separate account for each employee; do not share the manager password.
- Assign actual rights and permitted branches. Give waiters table/service tools, chefs kitchen tools and cashiers checkout tools; an employee with several authorized roles can switch workspaces.
- Test the account in a separate session. The role landing page, menus and finder should show only authorized tools. A hidden link never grants or removes server permissions.
- Use the read-only accountant preset for inspection and exports. Test a write refusal before handing over the account. Revisit rights when duties change.
Classic Desktop / Windows
Tablet navigation and the finder
- Use the native menus or toolbar to open Sales, Products, Inventory and Reports.
- Search the product list by its name or barcode and inspect the chosen record before adding it to a bill.
- Use the available keyboard shortcuts and scanner input on the sales screen. The browser Ctrl+K finder is a different feature.
- Return to the original record before editing or posting an action. Searching and selecting a row does not complete a sale.
The new browser finder and collapsible browser sidebar are SaaS controls. Classic Desktop uses its native menus, product search and keyboard shortcuts. Cloud-connected till screens may show the browser finder; that does not make it a classic Desktop feature.
Roles, duties and branch access
- Open staff management as the local administrator. Create a separate local account for each operator.
- Set cashier rights for the work that person performs. Do not share the administrator password to bypass an absent control.
- Sign out and test the account, including refusal of an unauthorized refund or settings change.
- Local accounts and cloud Team accounts are separate. Pair the cloud till and use cloud credentials when working against the online shop.
On classic Desktop, manage local staff and cashier rights in the program. Local staff records are distinct from online team accounts. Pair and sign into a cloud till to use cloud accounts; do not assume local users automatically become cloud employees.
Review the evidence rather than the animation
A preview is not a posted movement, an accepted request is not provider settlement, and a queued message is not verified delivery. After a financial or inventory action, inspect the original receipt or movement before retrying. Keep the original request identity for an uncertain replay. Do not create a new sale merely because the first response was slow. For exports, compare the selected range and totals with the source report. For staff reports, distinguish an actual event from a missing timestamp. Do not turn missing data into zero seconds or a claim that an employee did no work.
Keep edition and external-service limits explicit
Classic Desktop, a cloud-connected till and the SaaS browser share concepts but do not expose every control in the same place. The sections below give separate procedures and explain real alternatives. Follow the manual for the edition you are actually using. Device compatibility still requires the exact model and protocol to be tested. External payment, accounting and dashboard services require their own account, authorization and configuration. This article does not promise a live delivery-platform integration, a new paid-plan inclusion, a hardware supply service or an approved wallet pass. Confirm those conditions separately before a customer commitment.
Actual interface reference images
