Platform, Customization & Integration
Change screens, rules, approvals and integrations without a developer and without a fork.
Every ERP evaluation ends at the same question: what happens when the system does not do what we need. The usual answers are all bad — pay for a custom build, take a forked version you can never upgrade, or change how your business works to suit the software. Nama's answer is that the change is configuration, held as data in your own database. Screens, validations, automations, approval routes and notifications are things an administrator defines and a Nama upgrade leaves alone. That is not a feature list; it is what lets a company that reshaped the system years ago still take the current release.
What Platform, Customization & Integration covers
10 modules, licensed together or separately.
- Entity Flows — Automation Without Programming Automate rules, validations and actions across the system without writing code.
- Screen Modifier — Customize Screens Without Code Rearrange, hide and extend any screen without touching source code.
- Approval Cycles Multi-step approvals routed by amount, department or any condition you set.
- Mobile Apps Approvals, attendance, sales and field work from a phone.
- Notifications — Email, SMS and WhatsApp Alerts Alerts by email, SMS and WhatsApp, triggered by events you define.
- Document Management — A Register for the Paper You Keep The paper register: which shelf a contract is on, and who has it now.
- Security and Permissions Roles, field-level permissions and a full audit trail of who did what.
- Integration and REST API A REST API and integration tooling for the systems around the ERP.
- Data Import and Export Bulk import and export of any entity, for migration and for routine loads.
- Replication Branches that keep working without a link and reconcile with head office.
How it works together
This family is the answer to “we are not a standard business”, and it is organised as a ladder: use the smallest rung that solves the problem.
- Change what people see. The screen modifier rearranges, hides and extends screens, including new fields, without touching source code.
- Change what the system allows. Validations stop a document that breaches a rule, at the moment it is entered rather than in a report next month.
- Change what happens automatically. Entity flows create documents, fill fields, and trigger actions when a condition is met.
- Change who has to agree. Approval cycles route by amount, department or any condition, with as many steps as the decision actually needs.
- Change who is told. Notifications go by email, SMS or WhatsApp when the event you care about happens.
- Connect what is outside. The REST API, import and export tooling and the mobile apps put the same data where the rest of your estate can reach it.
Underneath all six sit security and permissions, which is what makes the rest safe to hand to somebody who is not a developer: every one of those changes is made by a user with defined rights, and every change is on the audit trail.
Why this is the page to read before choosing
A SaaS ERP will tell you customisation is a liability. It is right — when customisation means code. Here it means rows in your own database describing screens, rules and routes, which an upgrade reads rather than overwrites. That distinction is the whole commercial argument: you can run on-premise or in a cloud you chose, keep your data in a jurisdiction you picked, change the system to fit a business no vendor has ever seen, and still take the next release. A subscription-only product cannot offer the first two at all, and that is a constraint no feature comparison will show you.
Every screen, field and setting is documented in full.
Read the documentation →Good question — already answered
Can we change screens without a developer?
Yes. The screen modifier rearranges, hides, renames and extends screens — including adding fields — from inside the system. The change is configuration on your database rather than a build, so it survives upgrades.
What can entity flows automate?
Rules, validations and actions across the system: block a document that fails a condition, populate a field from another record, create a follow-on document, fire a notification. There are hundreds of available actions and none of them require code.
How do approvals work?
Approval cycles route a document through as many steps as you define, by amount, department, or any condition you can express — so the same purchase order can need one signature at one value and four at another.
Is there an API?
Yes, a REST API, with import and export tooling alongside it for bulk movement of any entity. The e-commerce and marketplace connectors are built on the same layer, which is why a new storefront is an integration rather than a release.
How granular are permissions?
Down to the field. Roles control what a user can see and do, permissions extend to individual fields, and an audit trail records who changed what — which is what an auditor asks for and what most mid-market systems cannot produce.
Can branches keep working without a connection to head office?
Yes. Replication lets a branch run on its own and reconcile with the centre, which matters where the connection is not something you can assume.
Industries that lean on this
Companies already running Nama ERP
A note of thanks and appreciation to the team at Namasoft for their effort, and every appreciation for the company's products. Thank you.
Get started with Nama today
Tell us how your business runs and we will show you how Nama ERP fits it — in your language, on your infrastructure.