Frequently asked questions

Clear answers before you begin

Questions that matter to the decision: scope, price, implementation, data, and support.

Transparency before the sale

Each application scope, implementation responsibility, data requirement, and integration boundary is made clear before a proposal is approved.

Frequently asked questions

Clear answers before you decide

What is ARMADA?

ARMADA is an Iraqi business platform connecting sales, inventory, purchasing, accounting, and reporting through one operational core and expandable application packages.

Which applications does ARMADA cover?

The site covers Sales, Point of Sale, Inventory, Purchasing, Accounting, Reports, Kitchen Display, Access Control, and sector packages. The actual scope for each organisation is confirmed in the proposal and implementation.

Is ARMADA only for restaurants?

No. Restaurants are one package. The platform is also designed for retail, distribution and warehousing, clinics and pharmacies, manufacturing, and services.

Why is there no fixed price on the website?

Price depends on applications, branches, implementation, training, and integrations. ARMADA does not publish a number that is not supplied by its approved pricing source; a versioned proposal follows the needs review.

How does system selection begin?

Selection starts by understanding the sector, branches, roles, and daily problem, then defining applications, implementation, data, and training before any subscription or operating environment.

Can you migrate data from our old system?

The source, quality, fields, and required history are assessed first. ARMADA can then define cleaning, trial, migration, and reconciliation work; automated migration is never promised before inspection.

Are training and support included?

The proposed implementation journey covers discovery, configuration, training, launch, and follow-up. The actual scope and service level are confirmed in the commercial proposal.

How are access and data handled?

The design uses isolation, default denial, scoped permissions, and an event trail. Actual environment, backup, and retention details are presented in a technical review before contracting, without unverified certification claims.