Frequently asked questions
Answers about Simor ERP, custom software development, implementation, demos, integrations, deployment, and working with Simor Soft.
What is Simor ERP?
Simor ERP is Simor Soft's customizable business-management platform. It connects inventory, purchasing, sales, accounting, manufacturing, MRP, costing, payroll, reporting, users, roles, and licensing in practical workflows.
Can Simor ERP be customized?
Yes. Pages, fields, rules, reports, documents, permissions, integrations, and modules can be changed. New modules can also be designed when the standard platform does not cover a required process.
Is Simor Soft only an ERP vendor?
No. Simor Soft is a software development company. We build custom business applications and also offer Simor ERP, Booking App, and Upload Document as working foundations that can be adapted and extended.
Who is Simor ERP designed for?
It is intended for small and mid-sized businesses and can support larger or more complex organizations through configuration and custom development. Common use cases include manufacturers, warehouses, distributors, and product or service companies.
Can we review a live version before a guided demo?
Yes. The public Simor ERP, Booking App, and Upload Document environments can be explored from their product pages. A guided demo is used to discuss your specific workflows, users, data, and implementation needs.
Does Simor Soft provide data migration and integration?
Yes. An engagement can include data mapping, migration rehearsals, reconciliation, API development, imports, exports, webhooks, and connections with existing business systems.
Can the software be deployed for a specific customer?
Deployment can be planned around customer requirements, including cloud, on-premise, hybrid, or controlled environments where appropriate. Licensing and enabled modules can be managed per customer deployment.
How does an implementation begin?
It begins with discovery: current problems, users, data, decisions, exceptions, integrations, and success criteria. The work is then divided into controlled releases that can be configured, built, tested, migrated, and accepted.