Arabic-first ERP — operations from purchasing to delivery
Operations is the heart of the system: from the first purchase request to the last delivered order, every movement lives on one database — no scattered spreadsheets, no "final-version-2-edited".
Purchasing: request to receipt with no gaps
The full procurement cycle lives in the system: material requests from any department, supplier quotations compared side by side, approved purchase orders with clear permissions, then receipt, inspection, and automatically matched supplier invoices. At any moment you know what was ordered, from whom, at what price, and what actually arrived — closing the door on ad-hoc buying that eats your margin.
Inventory: real balances, in real time
Every item movement — receipt, issue, transfer, stocktake — posts instantly to the balance. Multi-warehouse, multi-UOM, barcodes, batch numbers and expiry dates are native, with reorder levels that warn you before a stock-out, not after. Valuation runs automatically (moving average or FIFO), so cost of goods sold lands correctly in your financials with zero month-end spreadsheet gymnastics.
Manufacturing & projects: actual cost, not guesses
If you manufacture, build multi-level BOMs and issue work orders that consume materials and compute the real product cost — materials, labor and overhead. If you run projects, tie tasks, purchases, timesheets and invoices to one project and watch its profitability while it is still alive, not months after closing when regret is free but useless.
Why one database? Because fragile integrations lie
The essential difference between a real ERP and "apps wired together": sales, purchasing, stock and accounting are tables in the same database. No syncs that lag, no conflicting numbers between systems, no customer surprised that the displayed item sold out a week ago. And every screen, report and notification is Arabic-first — vocabulary your accountant, storekeeper and buyer already speak.
Permissions and approvals that protect the business
Each user sees only their own scope: the storekeeper never sees prices, sales reps cannot edit after approval, and purchase orders above a threshold route to the manager automatically. A full audit trail records who changed what and when — which alone ends most monthly "discrepancies".
Not theory — Dunally runs on this same foundation
Dunally, our maritime operating system, manages port calls, containers and customs clearance on this exact operations core — running for real operators today. Click and see it.
Dunally ←We're on Excel today — is migration painful?
That is where most of our clients start. We migrate items, suppliers and opening balances with ready templates, train your team in Arabic on their own screens, and the full cycle runs on the system within 30 days.
Multiple branches or warehouses?
Yes — multi-branch, multi-warehouse, even multi-company on one system, with consolidated or per-branch reporting and permissions that scope who sees what.
What about e-invoicing and taxes?
The integrated accounting module ships tax templates for Egypt (14% with ETA), KSA (ZATCA) and UAE — compliant invoices from the same screen, no external system.
Do we need a permanent developer after go-live?
No — screens, reports and approval flows are configured from settings, no code. When deeper customization is needed we build it in a separate app that never touches the core, so upgrades stay safe.
Our data is sensitive — where is it hosted?
On your own server, fully yours, with scheduled backups and full export anytime. We never see your data and there is no lock-in.
See the full operations cycle on data that looks like your business — a live demo with Saleh.