Compare access and connectivity
Identify which users work at a counter, in a warehouse, in another branch or away from the business. Describe what must remain available when connectivity is unreliable and how remote users will be supported.
Do not assume that an online label includes offline synchronisation, or that a local installation automatically supports secure remote access. Demonstrate the behaviour you need and record the limitations.
- User locations and connectivity needs
- Hosting, device and network responsibilities
- Backup and restore ownership
- Update, support and remote-access arrangements
Plan for the daily operation
Assign responsibility for hosting or local hardware, access changes, updates, backups and restoration. Include the people who will administer the system after the implementation team leaves.
Use a representative demonstration to check permissions and reporting across the required business locations. Multi-branch operation and standalone installations should be evaluated against the specific product scope.
Price the system over its expected use
Compare setup, software, hardware where applicable, hosting, backups, support and future changes. Use published rates to explore the starting configuration, then confirm the full arrangement in the proposal.
A migration between deployment models is a separate requirement. Describe your existing data, history and access needs so that a trial and acceptance plan can be prepared.
Common questions
Is online ERP always the better choice?
The suitable option depends on connectivity, remote access, operational responsibilities and the features you need. Compare both models against your actual business workflow.
Does a local ERP installation include cloud backup?
Do not assume that it does. Backup storage, frequency, retention, restoration and responsibility should be specified in the deployment and support scope.
Can we change deployment models later?
Ask the team to review product compatibility, data, history, hosting and integration dependencies. A migration should have its own scope, trial and acceptance checks.