Your actual sidebar is the best starting point. A module name in configuration does not guarantee it is installed, enabled for your subscription, or included in the native app.
2 procedures · Field reference · Practical example · Common questions
This manual covers the customer workflows available in the inspected Compact installation and explains the platform boundary. It is not a claim that every upstream Ultimate POS extension is installed or included in every subscription. A feature name in code/configuration is not enough to train users on it: activation, permission, screen and workflow need confirmation.
Field reference
Use this while completing the form. A required field is marked with *; conditional fields appear only when enabled.
Field / control
What to enter or understand
Installed module
Module code present on the portal; it can still be disabled for a tenant.
Subscription entitlement
Features/limits purchased for the business.
Role / location
Which actions and outlets this individual can access.
Web / native / offline
Three different availability boundaries; a web module is not automatically a native or offline module.
Before you start Ask the business administrator if an expected module is missing.
Steps
This guide covers the core retail web modules and the live demo’s Accounting, CRM, Essentials/HRM, Project, Repair, WooCommerce and Connector menus.
Manufacturing source exists in the workspace but its workflow was not available in the inspected live demo menu. Ask for activation and training before using production recipes or production stock.
Asset Management, CMS, Ecommerce, Field Force, Product Catalogue, Spreadsheet, AI Assistance, Hotel/Gym, Custom Dashboard, Cheque and ZATCA names appear in configuration but are not verified as installed customer workflows in this portal review.
Superadmin is installation-wide tenant/package administration, not a customer cashier feature. Ordinary business users manage their own roles/settings and package subscription.
When a new module or app feature is released, its own verified steps and screenshots should be added to this guide before training users on it.
Check the result The guide avoids sending customers to features unavailable in their installation.
Where to go Administrator → your business feature review
Before you start Ask for the actual module and intended user role.
Steps
Confirm the module is installed and enabled for the business package.
Review the user’s permitted actions and locations, then open the actual customer screen.
Practise an approved demo lifecycle including create/view/correct/report rather than only a dashboard visit.
Add verified field explanations and screenshots to the module documentation before staff use it in real operations.
Record whether the workflow is web-only, native online or offline-supported.
Check the result Staff learn a real available workflow with the correct platform scope.
IN PRACTICE
A practical example
Repair may be available in the web sidebar while the native app provides retail sales. That does not mean the native app can intake a job sheet offline; use the documented web Repair workflow.
Common questions
Does this guide guarantee all extensions?
No. It describes verified workflows and identifies unavailable/unverified optional modules.
Why does the administrator see more than the cashier?
Installation/package management and broader permissions are separate from ordinary customer counter access.
