Frequently asked questions

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.

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.

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.

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.

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.

Yes. An engagement can include data mapping, migration rehearsals, reconciliation, API development, imports, exports, webhooks, and connections with existing business systems.

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.

Yes. Qualified organizations can request a complimentary, time-limited ERP evaluation environment with full-module access. The evaluation period, users, hosting, sample data, and support arrangements are agreed before access is provided, and there is no software charge during that evaluation period.

The deployable ERP foundation can be prepared once the server or hosting environment, database, access, and initial users are confirmed. Data migration, integrations, training, configuration, and custom changes may require additional implementation time.

The core application stack uses widely adopted open-source platforms and does not require a separate desktop framework licence for every user device. Hosting, domain, certificates, databases, premium third-party services, support, product usage rights, and project-specific costs are identified separately when applicable.

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.