ARMADA application
Contract-based previewInventory
Inventory governs movement across branches and locations through defined documents and states while keeping product identity separate from operational stock.
Contract-defined scope
Contract-based preview — not connected to live data
Inventory
Outcomes
What changes in your operation?
Keep physical counts separate from transfers
Trace a document from receipt to delivery
Operating journey
From start to outcome
- 1
Receive
Record quantity, location, and source.
- 2
Move
Control movement between locations in the correct branch context.
- 3
Review
Raise differences and exceptions for review.
Application scope
Core capabilities
A practical scope that explains what this application covers and where its current boundary sits.
Documented receipt
Keep source, quantity, and location in a movement with a clear reference and state.
- Defined receiving location
- Reviewable reference
Movement across locations
Organise transfers in the correct company and branch context.
- Known source and destination
- Traceable movement state
Visible differences
Keep physical counting separate from transfers and raise differences for review.
- No silent stock creation
- Explicit exception decision
Control and governance
How does the work stay controlled?
Operating controls that preserve context, permission, and a reviewable trail.
Branch and company consistency
Movement validates the company, branch, and location context before transition.
A count is not a transfer
A physical count remains a fact for review and cannot silently create an unauthorised movement.
Movement history retained
Each transition remains linked to its document and state instead of replacing history.
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.
InventoryContract-defined scope
Purchasing
Links a receipt to its order and source when purchasing is included in scope.
Sales
Coordinates fulfilment and delivery without allowing sales to write inventory directly.
Reports
Supplies movement documents as sources for receipt, transfer, and delivery views.
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
Map locations and movements
Fix branches, warehouses, receipt and delivery points, and movement responsibility.
An operating map without ambiguous locations - 2
Prepare items and opening data
Review item identity, units, and the approved opening-balance approach.
A reconcilable starting point - 3
Test a complete cycle
Run receipt, transfer, count, delivery, and at least one exception scenario.
Practical proof of movements and controls
Designed for
Fits different teams and operating models
WarehousingDistributionRetailRestaurants
Before you decide
Common questions about this application
Does a count automatically transfer or distribute stock?
No. Physical counting is separate from transfer and distribution; every difference needs an explicit review and action.
Can movement across branches be traced?
The design retains source, destination, company, and branch context. Live movement follows the approved scope.
How are current balances migrated?
Item and location data is reviewed first, then a separate migration and reconciliation plan is accepted.