Broken out below into the working areas inside them — Purchase alone carries seven. Each module is switched on per role, so a team sees the part of the business it works in and nothing else. Start with three modules or all six groups; the system does not care which.
From the first quotation to the signed delivery note, with the customer record underneath it all.
Two document types on one engine. Line discounts, validity dates, customer PO and RFQ references, and tax applied at either document or line level. A quotation moves Draft → Pending Approval → Approved, then converts to a sales order in one click and locks itself.
Every quotation carries a live timeline — approved, converted, procured, delivered — derived entirely from the records that actually exist. Nothing on it is a manually ticked checklist, so it cannot be wrong.
Commercial invoices and sales invoices, each with its own approval queue. Payment receipts are recorded separately as payment or GST receipts, with withholding tax captured on the receipt itself.
Credit limit, credit term, cash or credit terms, and three tax identifiers per customer. Multiple named contacts, one flagged primary, selectable directly on a quotation.
A first-class party alongside customers, with region and assigned area, credit terms, and a default delivery method — company vehicle, third-party logistics, or both.
Own-fleet or client-collected dispatch, multi-stop routes, waybill numbers, and uploaded driver-licence and vehicle-registration scans. Trip cost is captured line by line — fuel, driver allowance, tolls, miscellaneous — so a delivery has a real cost, not an assumed one.
Purchase orders, partial receipts, a two-stage payment approval, and a vendor portal vendors run themselves.
Pending, Approved, Partial, Received, Closed, Cancelled — with received quantity tracked per line, so a part-delivered order says exactly which lines are still outstanding instead of sitting at "open".
Receipts record the delivery note number, vehicle, driver and transporter, and carry backorder quantity per line. Stock moves on the receipt, not on the order.
A two-stage chain: Submitted → Manager Approved → Approved, each stage stamped with who and when. Withholding tax, the vendor bank and IBAN snapshot, and the uploaded transfer receipt all travel with the payment.
Categorised by the fields they supply, with certificates on file and an approval state per application. Approving or rejecting one sends the vendor a templated email you can edit yourself.
A separate application on its own login, deliberately isolated from staff sessions. Vendors register themselves, pick the categories they want to be invited for, and upload their certificates.
Publish a request for quotation with a deadline and target cities or countries; eligible vendors are found by explicit invite, category match or location. Vendors bid in the portal, and every recipient is tracked — emailed, failed, or opened.
Any quotation line flagged as needing procurement surfaces here as a buy request, showing live whether a purchase order has been raised against it yet.
The workshop floor and the service bay, with the measurements and the stock ledger that come out of them.
Equipment in for inspection, testing or repair. Customer complaint, scope of work, assigned engineer, priority, fitness status and final conclusion — linked back to the quotation, sales order or delivery it belongs to.
Reusable specification, inspection and test templates per equipment type. Add an item to a job and its standard checklist instantiates itself, so two engineers test the same equipment the same way.
Entries are typed — assessment, inspection, test, progress, part, conclusion — and a test entry records method and tool, initial and final value, unit, tolerance and result. Before-and-after photos flag individually for inclusion, and the whole job prints as a consolidated service report.
Per machine, per shift, with downtime minutes and reason, and per-line quantity produced, waste quantity and rejection reason. Entries move Draft → Submitted → Locked.
A two-level parent-SKU to sub-SKU hierarchy with auto-generated codes, carrying size, material, pressure rating, length and unit of measure. Each sub-SKU maps to its raw materials through a versioned bill of materials.
Every movement is a row: goods received, production in, production out, sale out, adjustment, return in — each with quantity in, quantity out and the running balance after it. Reorder levels drive an out-of-stock, low-stock and in-stock view on the dashboard.
Machine register with status — active, inactive, under maintenance — and the parent and sub-SKUs each machine is capable of running.
Ledgers, vouchers and expenses, with the approvals that decide what gets into them.
A grouped, parented chart with account type, per-account currency, opening debit and credit, and an Arabic account name alongside the English one.
Per-invoice gross, GST, withholding tax and remaining payable on the receivable side; the same shape against purchase orders and approved payments on the payable side.
Receipt and payment vouchers against customers, distributors, vendors, employees or other parties, with narration, prepared-by and approved-by, moving Draft → Posted → Cancelled.
Mapped to a chart-of-accounts code through the expense category, with expense date and posting date held separately, department tagging and a receipt upload. Vehicle expenses are typed — fuel, maintenance, damage, other — and report on their own.
Staff claim with a mandatory receipt. Approved claims flow into payroll as an earning line, or into the expense ledger, keyed so the same claim cannot post twice.
One queue for reimbursements and purchase-order payments alike. Final approval on a payment checks the remaining order balance first and refuses to overpay it.
Employees, the hours they worked, what they are owed, and what they have been asked to do.
Codes, national ID, nationality, department, job title, employment type, join date and contract expiry, salary split across basic, housing, transport and other allowances, bank and IBAN, and an Arabic name field. Two reporting lines — direct manager and operational manager — and those are what drive approvals.
Bulk import from a biometric device export, matched on the machine user ID held against each employee and tracked by import batch. Working hours, late minutes, early leave, overtime hours and amount are computed from the shift, and can be recalculated across history when a policy changes.
Shift codes with in and out times, a late-in grace period, and an overtime rate per hour set per shift rather than globally.
Configurable earning and deduction heads, generated per employee per month with present, absent and leave days, gross and net. Payment method, company bank, reference and the uploaded transfer receipt are recorded against the run, and each employee gets a printable salary slip.
Advances given and repayments received as typed transactions with their own numbering, method and reference, printable as slips and soft-deleted rather than erased.
Assign work to an employee with a deadline and notes, broken into an ordered sub-step checklist. Completion raises a notification badge for whoever assigned it.
An administrator connects one Google account once; after that the system mints a Meet link for any meeting without ever prompting an ordinary user. Invitations and cancellations go out through your own mail server, and an in-app reminder surfaces the next one.
The parts that make it yours — your documents, your numbering, your roles, your mail server.
Eight document types, each designable two ways: tick which header and line-item fields appear and rename any label, or write the HTML yourself in a built-in code editor with live preview. QR codes embed automatically on quotations, purchase orders, invoices and delivery notes.
Fourteen configuration areas — company information, multiple office addresses, multiple company banks, tax categories, per-module terms and conditions, per-document signature images, letterhead, transportation and more.
Fifteen document series, each with its own prefix, format template, sequence length and next number. Your numbering convention, not one imposed on you.
Fourteen built-in reports, from vendor purchase ledgers and sales tax and withholding tax, to raw material purchased against production consumed, rolled up daily, weekly, monthly or yearly. Paper size, orientation, header, logo, letterhead, watermark and footer are configurable per report, and every one exports to CSV or prints.
Nineteen entities importable from Excel or CSV, each with a downloadable template. Every run is logged with rows total, inserted, skipped and errored, plus the per-row errors — so a failed import tells you which line failed and why.
A full mail client inside the system, speaking IMAP and SMTP to your own server. Folders, attachments, drafts, an address book that builds itself from who you correspond with, and a company signature image applied on send.
When someone without rights to a locked document needs a change, the system captures the change they wanted — the full proposed record and their reason — as a request for review, instead of simply refusing them.
Google Drive folders embedded in the application and scoped per role, so a team opens its own documents without leaving the system or being handed a link to everything.
An internal ticket desk with categories, priorities and attachments, and an asset register covering assignment history, condition out and in, service and repair costs, warranty expiry, and printable QR asset tags.
Direct messaging between users with read receipts, on a floating widget available from every screen.
Discontinuing asks for a reason, and keeps it.
Every checkpoint below is enforced by the system rather than left to training or memory. This is where most of the money is saved, and most of the arguments avoided.
Paying a vendor twice for the same purchase order because two people approved separately.
The quoted price quietly changing after the sales order has already been raised from it.
Handing someone a powerful role just so they can sign off their own team’s claims.
Claims entering payroll with nothing behind them to audit later.
Deals vanishing from the pipeline with no record of why they died.
Committing to a delivery the warehouse was never going to be able to make.
A mistaken deletion taking a document and its history with it permanently.
A hidden menu item being treated as security when the underlying data is still reachable.
These ship with a fresh installation, each already scoped to what that job actually does. From there you create your own — with its own name, tag and colour — and set five independent rights on every module: whether it appears in the menu, and whether that role may view, add, edit or delete. Only the super administrator role is locked.
Tell us what your company does and which of these modules you would actually use. We will walk you through the system handling your work — not a slide deck.