ARMADA application
PilotPoint of Sale
ARMADA Point of Sale covers daily cashier work with explicit sessions, collection methods, synchronisation handling, and clearly defined branch and device constraints.
Branch operating scope
Contract-based preview — not connected to live data
Branch operating scope
- Defined cashier session
- Focused daily checkout
- Synchronisation review
Outcomes
What changes in your operation?
A defined branch and location context for every transaction
A review path when synchronisation cannot complete
Operating journey
From start to outcome
- 1
Open a session
Start cashier work for the selected branch and device.
- 2
Record the sale
Add products and capture the payment method.
- 3
Close and review
Reconcile the session and raise exceptions for review.
Application scope
Core capabilities
A practical scope that explains what this application covers and where its current boundary sits.
Defined cashier session
Open and close work for a known branch, device, and employee within the approved operating scope.
- Explicit branch context
- Reviewable operating responsibility
Focused daily checkout
Add products and record the collection method in a concise cashier flow.
- Few, clear steps
- Understandable transaction state
Synchronisation review
Distinguish a completed transaction from one that needs review after connectivity problems.
- No silent success
- Explicit exception path
Control and governance
How does the work stay controlled?
Operating controls that preserve context, permission, and a reviewable trail.
Branch and device scope
The session is tied to a defined operating context to prevent location mixing.
Authorised actions
Session opening, sale capture, and closing follow the agreed role permissions.
Visible exceptions
Interrupted or unresolved synchronisation remains available for review instead of becoming a default success.
One shared core
How does it connect to other applications?
Intended connections to the shared ARMADA core. Only the integrations covered by the approved scope are enabled.
Point of SaleBranch operating scope
Sales
Keeps the point-of-sale transaction within the agreed branch sales journey.
Inventory
Applies quantity movement for the selling location under the approved synchronisation policy.
Kitchen Display
Can coordinate restaurant preparation when the operating scope includes kitchen stations and devices.
Implementation approach
From operating study to acceptance
A practical sequence that starts with the real operation and ends with clear acceptance of the agreed scope.
- 1
Fix the branch scenario
Define devices, sessions, collection methods, and included interruption cases.
Known operating boundaries - 2
Run a controlled branch launch
Train a focused team and run sale, close, and review scenarios.
Evidence from real cashier work - 3
Review and accept scope
Assess launch results and decide what can expand and what needs further work.
An evidence-based expansion decision
Designed for
Fits different teams and operating models
RestaurantsRetailMulti-point branches
Before you decide
Common questions about this application
How does Point of Sale begin across branches?
The branch, devices, collection methods, and synchronisation scenarios are defined in a clear scope, then expansion follows operating results.
What happens when connectivity is lost?
Interruption and synchronisation behaviour is fixed for each branch scope. Any unresolved state remains visible for review.
Does it connect to Kitchen Display automatically?
The connection operates in a scope that includes the kitchen stations, devices, and accepted end-to-end order journey.