Knowledge base · Service-King
Cloud or on-premises WMS: costs and responsibilities
There is no single installation model that is best for every company. Compare access, maintenance, backup and integration requirements. More important than the server location itself is a clear division of responsibilities.

Compare the complete maintenance arrangements
| Area | What to compare |
|---|---|
| Access | Branches, remote work and connectivity requirements. |
| Administration | Who updates the system and handles failures. |
| Copies | Coverage, retention, and recovery attempts. |
| Integrations | Access to devices, networks and interfaces of other programs. |
| Costs | Launch, subscription, infrastructure and administrators' work. |
| Exit | Data export, attachments and maintenance termination. |
Compare equivalent scopes over a consistent basis
Subscription and server purchase cost include other items. Local installation includes maintenance, copies, updates and administrator work. For the cloud service, you need to check the access, support and export conditions. A fair account covers the entire comparable period and the same range of functions.
Set the number of users, devices and branches. Add the costs of implementation, integration and configuration changes. Indicate mandatory and optional elements. Thanks to this, the difference in the result will not result from omitting a task that is performed by the supplier in the second offer.
The division of responsibilities should be written down
Who updates the application, who is responsible for the server system and who restores the data? Own infrastructure does not automatically mean full control if the knowledge is with one person. The cloud does not automatically mean that all tasks will be taken over by the provider. Every area needs an owner and a replacement.
This also applies to devices at the station: readers, printers and network connections. A failure of the local network may stop the operation despite the correct operation of the server. Before making a decision, it is worth describing the entire path from the operator to the system and the support conditions.
The local server also needs maintenance
Own infrastructure means responsibility for hardware, updates, security and recovery. No subscription does not mean no maintenance costs. You also need to consider replacing a person who knows the configuration.
In the cloud, some tasks can be performed by the provider, but the scope should result from the contract. The company is still responsible for, among others: for the proper use of accounts and keeping your data up to date.
Test a failure scenario
What happens when I lose my internet connection, my server crashes or my account is blocked? Can the position still work and if so, how does it reconcile the data? Do not assume offline mode without confirming it for a specific application and operation.
Available variants of Service-King implementation and their conditions should be agreed. This text helps you gather requirements; does not constitute a promise of identical availability of each module in any installation model.
Compare offers over the same period
Set of costs of startup, license or subscription, infrastructure, updates and work of people maintaining the solution. Add assumptions about the number of users and devices. Separate mandatory from optional elements. When installing locally, include disaster recovery, and when installing in the cloud, consider export and termination conditions. Comparing the monthly fee alone with the server price does not show the same range and may lead to a wrong purchasing decision.
Related topic: total change cost.
Total cost and maintenance comparison
| Position | Question about the cloud variant | Question about the local variant |
|---|---|---|
| Startup | What does configuration and import include? | What does installation and infrastructure include? |
| Maintenance | What tasks are in the service? | Who performs updates and monitoring? |
| Copies | What scope and recovery was agreed? | Where are the copies and who is testing them? |
| Access | How do branches and devices work? | How is secure remote access ensured? |
| Exit | How will you export data and files? | How will you move or recover your system after a crash? |
Test loss of connectivity as a specific scenario
Determine whether an application and operation can run offline. If so, you need to know what is saved locally and how to resolve conflicts. Offline mode does not automatically result from having a mobile terminal.
If work must stop, prepare a procedure and subsequent data reconciliation. In the local variant, also check for server or power failure, and in the cloud - access from the company's network. The test should cover real workstations, not just the administrator's computer.
How to collect requirements before talking to a supplier
- Branches, users and devices.
- Data types and required roles.
- Integration and network access required.
- Acceptable pause and playback range.
- Team available for maintenance.
- Export method at the end of cooperation.
The availability of Service-King variants and their conditions must be confirmed in the project. Information about is helpful security and implementation.
Scenario: a different person takes over system maintenance
Administrator leaves or supplier changes team. The organization should still know where copies are, how to report a problem, and who can approve access. Continuity of maintenance cannot be based on the memory of one person. This applies to both cloud and on-premises installation.
Prepare a list of responsibilities, rather than an exposed list of passwords. Define account ownership, recovery methods, configuration documentation and contacts. For a hosted service, clarify which tasks belong to the provider and which remain with your organisation. For an on-premises system, also define responsibility for the hardware, operating system and network.
Then go through a controlled failure scenario. Can the replacement person report and describe the problem, find the necessary data and run the appropriate procedure? You don't need to perform a risky production reproduction to check the organizational part. Full technical testing should have an agreed scope and environment.
When comparing costs, take this work and the availability of skills into account. The seemingly cheaper option may require responsibilities that the company has no one to entrust to. On the other hand, a service without clear responsibilities also does not solve the problem. It is worth choosing a maintenance model that can actually be performed, and not just described in the offer.
| Area | Practical arrangement |
|---|---|
| Responsibilities | List of activities on the company and supplier side. |
| Substitute | People and authorized reporting channels. |
| Documentation | Secure access to the information you need. |
| Copies | Responsibility for inspection and recovery. |
| Trial | Emergency scenario within the agreed scope. |
| Cost | Actual maintenance work and competencies. |
Checklist for a supplier discussion
- Number of stations, branches and devices.
- Access and connectivity requirements.
- List of integrations and sensitive data.
- Agreed backups, turnaround times and support.
- Total cost over the comparable period.
Go to security questions and technical consultation.
Questions worth clarifying before implementation
Does local installation work without internet?
May limit some external dependencies, but does not guarantee all modules will work without connectivity. You need to check the architecture, devices, authorization and integrations.
Do I still need an administrator on my side in the cloud?
You need at least a person responsible for accounts, data and maintenance contact. The scope of technical responsibilities results from the agreed model.
How to compare security?
Assess the specific controls, responsibilities and evidence that they work, rather than server location alone. Roles, backups and incident handling need testing in both deployment models.
Go to solutions related to this topic
- Warehouse management (WMS) - Receipts, storage locations and issues.
- System security - Information about access organization and data protection.
- Service-King App - View system areas and select a scope for your company.
- The implementation process - Process analysis, markings, tests and assembly commissioning.
Free consultation
Let's compare implementation options for your organization.
Describe locations, positions and IT requirements. We will determine the available scope and responsibility for maintenance.
Thank you for your inquiry.
Your message has been sent to the correct department. We will contact you to determine next steps.
Send another inquiry