HomePortfolioBusiness ERP & Workflow Automation
02ERP & Business AutomationUnited Arab Emirates

Business ERP & Workflow Automation

A custom ERP for a UAE trading and distribution business: sales, purchasing, stock, invoicing and customer records in one system, with the repetitive work between them automated.

What we built, and why it is built that way

A trading and distribution business in the UAE was running sales, purchasing, stock, customer records and invoicing as separate activities, with no single place management could look at to see the state of the business. The brief was to centralise them and automate the repetitive work in between.

We built a custom ERP rather than configuring an off-the-shelf one. Distribution businesses tend to have pricing, approval and credit rules specific to them, and the usual result of forcing those into a package is a team keeping spreadsheets alongside the ERP to handle the exceptions -- which is the problem they started with.

The system covers the full cycle: purchase orders raised, stock received and tracked, sales orders out, invoices raised against them, and customer records carrying the whole history rather than the last transaction. Approval chains and role-based access decide who can see and change what, which in a distribution business usually comes down to who may alter a price or release stock. Management reporting is assembled by the system from its own data, so the unified view the brief asked for is a consequence of everything living in one place rather than a dashboard stitched over several.

It runs on React and Next.js at the front, Node.js behind it and PostgreSQL underneath, with REST APIs between the parts so a later integration does not mean reaching into the database. Automated workflows handle the steps that used to depend on somebody remembering: reorder triggers, invoice generation, status changes and the notifications that follow them.

Code, database and infrastructure accounts are the client's, handed over documented.

Built with

What this project actually used. We pick a stack to suit the problem and the people who will maintain it, so this is not the same list on every project.

Next.jsNode.jsPostgreSQLREST APIsReact

Services this project used

Each page below covers the process, the stack and the questions buyers usually ask about that kind of work.

Is this close to what you need?

Tell us where your situation differs and we will tell you which parts of this would carry over and which would not — including where we think you need less than this.

Talk to us