AMIGA runs in the cloud—no on-site AMIGA server to install. Plan your data, ERP connection and team training around the way your distribution business works.
Data flows and integration agreed for your system.
Conceptual connection overview · Final scope agreed together
The implementation starts with your existing systems, required workflows and priorities.
Review what needs to move between the office and the field, and how your current system can support it.
Plan the configuration and transition for the business functions included in your rollout.
This is the proposed rollout approach. Timing and deliverables are agreed for your business.
Map the journey from customer visit to order, invoice and collection, including warehouses and the systems used today.
Confirm product scope, data flows, migration needs and responsibilities.
Prepare agreed data, configure access and build required connections.
Test a customer order, return, collection and stock movement in the agreed scope. Check totals and balances with your team.
Train office and field users, agree the transition and confirm readiness.
Support the agreed rollout, review early use and address outstanding actions.
Name a project owner and involve the people who understand the daily work.
| Area | PCS / AMIGA team | Your team |
|---|---|---|
| Business scope | Guide discovery and document the proposed solution. | Explain priorities, workflows and acceptance needs. |
| Data preparation | Agree formats, mapping and validation requirements. | Provide authorized data and resolve source-data issues. |
| Integration | Implement and validate the agreed connection scope. | Coordinate ERP access, technical contacts and vendor involvement. |
| Workflow review | Support testing and address issues within scope. | Review business scenarios and confirm acceptance. |
| Training & rollout | Deliver agreed training and rollout assistance. | Arrange user participation and internal coordination. |
| Ongoing support | Provide the support agreed in your commercial terms. | Nominate contacts and report issues with useful context. |
A short overview is enough to begin. Detailed data and technical access can follow through an agreed process.
No. AMIGA runs in the cloud, so you do not need to buy, install or maintain an on-site AMIGA server. Office access requires an internet connection. Supported mobile workflows can use downloaded data offline and synchronize when connected. If you keep an existing ERP, its hosting and integration requirements remain separate.
Timing depends on scope, integration, data readiness and team availability. We agree a plan after reviewing those requirements rather than promising a fixed duration upfront.
No. We assess your system and its available interfaces, agree data flows, and identify any custom integration work needed.
A focused pilot can be discussed as part of the rollout. Its users, workflows, duration, success criteria and commercial terms are agreed for your business.
Migration scope is agreed during discovery. Source data, mapping, opening balances and reconciliation requirements must be reviewed before the transition.
Support channels, coverage, responsibilities and commercial terms are confirmed in your agreement. The rollout plan should identify who to contact and how to raise an issue.
We'll discuss the scope, integration and rollout that fit your operation.