CloudERP.OneCloudERP.One is an enterprise ERP delivered as a managed cloud service. Accounting, sales, purchasing, inventory, manufacturing, projects, payroll and point of sale run on one platform, with a single ledger across every company in the group.
Fully managed. Hosting, backups, updates, security and support are included in the subscription.
| Document | Party | Amount | Status |
|---|---|---|---|
| SI-2026-0881 | Medfield Pharmacy | 1,240,000 | Paid |
| SO-2026-0412 | Okonkwo Stores | 385,000 | To deliver |
| PO-2026-0221 | Ember Pharma | 2,400,000 | Awaiting receipt |
| SI-2026-0876 | Crest Logistics | 760,000 | Overdue |
| Item | Qty | Amount |
|---|---|---|
| Paracetamol 500mg x100 | 240 | 696,000 |
| Vitamin C 1000mg x30 | 180 | 457,200 |
Each module is a complete set of screens, records and reports for that part of the business. Select one to see it as it appears in the system. Start with the modules you need and switch on the rest later; nothing is re-implemented.
Unknown credit, reference 77120, 96,000. No payment entry matches the amount or reference.
General ledger, receivables, payables, bank reconciliation, taxes and financial statements. Every invoice, receipt, payslip and stock movement in the other modules posts here automatically, so the books are always current.
Open Accounting and FinanceLeads, quotations, sales orders, deliveries and invoices in one flow, with price lists, discounts and credit control applied as the order is entered.
Open Sales and CRM| Item | Qty | Rate | Amount |
|---|---|---|---|
| Paracetamol 500mg x100 | 1,200 | 840 | 1,008,000 |
| Amoxicillin 250mg x100 | 600 | 1,350 | 810,000 |
| Vitamin C 1000mg x30 | 400 | 1,055 | 422,000 |
| Net total | 2,240,000 |
Material requests, supplier quotations, purchase orders, receipts and supplier invoices, with approval at each step and landed cost added where it belongs.
Open Purchasing| Item | Main store | Ikeja | Abuja | Total | Reorder |
|---|---|---|---|---|---|
| Paracetamol 500mg x100 | 1,240 | 310 | 180 | 1,730 | 400 |
| Amoxicillin 250mg x100 | 96 | 40 | 12 | 148 | 300 |
| Vitamin C 1000mg x30 | 820 | 210 | 150 | 1,180 | 250 |
| Glucose 50g sachet | 4,100 | 900 | 620 | 5,620 | 1,500 |
| Cough syrup 100ml | 310 | 75 | 0 | 385 | 200 |
Items, warehouses, batches, serial numbers and valuation, with every movement recorded as it happens and stock value posting to the ledger.
Open Inventory and WarehouseBills of materials, work orders, job cards and production planning, with the real cost of each work order built up from materials, labour and overhead as it runs.
Open ManufacturingProjects, tasks, timesheets and costs, with billing from timesheets or milestones and profitability per project.
Open ProjectsEmployee records, attendance, leave, payroll with statutory deductions, expense claims and an employee self-service portal.
Open HR and Payroll| Year | Depreciation | Net book value |
|---|---|---|
| 2024 | 4,750,000 | 23,750,000 |
| 2025 | 5,700,000 | 18,050,000 |
| 2026 | 5,700,000 | 12,350,000 |
| 2027 | 5,700,000 | 6,650,000 |
| 2028 | 5,700,000 | 950,000 |
An asset register with depreciation, movements, maintenance and disposal, posting to the ledger on schedule.
Open Fixed AssetsA counter point of sale that sells from live stock, takes several payment modes, and closes each cashier's shift against the cash actually counted.
Open Point of Sale| Parameter | Specification | Reading | Result |
|---|---|---|---|
| Moisture content | 10 to 12 % | 13.1 % | Fail |
| Protein | at least 11 % | 11.8 % | Pass |
| Colour | creamy white | creamy white | Pass |
| Foreign matter | none | none | Pass |
| Pack weight | 50 kg, within 0.2 | 49.9 kg | Pass |
Inspection templates, incoming and in-process inspections, non-conformance and corrective action, tied to receipts, work orders and deliveries.
Open QualityTickets from email and a customer portal, service levels, assignment rules, warranty claims and maintenance visits.
Open Support| Territory | Customer | Net total | Margin |
|---|---|---|---|
| Lagos Mainland | Medfield Pharmacy | 6,420,000 | 31% |
| Lagos Mainland | Okonkwo Stores | 2,110,000 | 18% |
| Lagos Island | Sunrise Supermarket | 9,860,000 | 22% |
| Abuja | Crest Logistics | 3,240,000 | 27% |
| Abuja | Northline Foods | 4,180,000 | 19% |
| Total | 25,810,000 | 23% |
Standard reports in every module, a report builder that needs no code, dashboards with charts and number cards, and scheduled reports by email.
Open Reports and DashboardsThe modules share one set of customers, items, employees and accounts. A document entered in one place is the same record everywhere else, and the reports read from all of it.
Platform capabilities that apply to every screen in the system, included in the subscription.
Several companies, branches or cost centres in one system, reported separately and together.
Who can see and do what, down to the field, with a record of every change.
Fields, forms, workflows and print formats are set up in screens, not written in code.
Connect banks, websites, payment and messaging services, and anything with an API.
Taxes, currencies and fiscal settings configured for each country you operate in.
How people use the system every day, on any device.
You use CloudERP.One in a browser. We run the servers, the backups, the updates and the security, and we answer the phone when something needs attention.
Implementation is a fixed sequence run by our team, with your data in the system before anyone is trained on it. Larger groups are planned in phases, one company or one module set at a time.
We meet your team, walk through how the business runs today, and agree the scope: which modules, which companies, which branches, and what has to be true at go-live.
We set up your companies, chart of accounts, items, warehouses, price lists, taxes, users and roles. You see your own data in the system before any training.
Customers, suppliers, items, opening stock and opening balances are loaded from your current system or spreadsheets, checked, and signed off by you.
Each team is trained on its own screens with its own data: accounts, sales, stores, HR. Short sessions, repeated as needed, with written guides left behind.
We run the first days alongside your staff, on site where it helps, and close the first month end with your accountant.
After go-live you have a named contact, a ticket system and the emergency line. Changes to configuration and new reports are handled as part of the subscription.
CloudERP.One is a general business system, configured to how your company works rather than sold as a version for one trade. The team behind it has implemented and supported ERP for retailers, distributors, manufacturers and service firms for more than fifteen years.
Trading, distribution, retail chains and manufacturers: inventory, purchasing, sales, point of sale and manufacturing with accounting underneath.
Consultancies, contractors and agencies: projects, timesheets, billing, expenses and payroll.
Several companies or many branches that need one view: consolidation, inter-company, branch reporting and central control of prices and products.
Short answers here; the detail is on the deployment and implementation pages.
Two to six weeks for most companies, depending on the number of modules, the state of the data to be migrated, and how quickly decisions are made on your side. Larger groups take longer and are planned in phases.
No. CloudERP.One is hosted and managed by us. You need a browser and an internet connection. If you have IT staff, they can administer users and configuration; if not, we do it.
Yes. Most companies start with accounting, sales, purchasing and inventory, and add HR, manufacturing or projects later. Modules are switched on in configuration; nothing has to be re-implemented.
An annual subscription scoped to your company, plus a one-time implementation fee quoted after discovery. We give you both figures in writing before you commit to anything.
Customers, suppliers, items, stock and opening balances are migrated as part of implementation. Historical transactions can be loaded where you need them for reporting.
A demo takes about an hour. Send a few items, customers and a trial balance beforehand and we will load them first.
General ledger, receivables, payables, bank reconciliation, taxes and financial statements. Every invoice, receipt, payslip and stock movement in the other modules posts here automatically, so the books are always current.
Unknown credit, reference 77120, 96,000. No payment entry matches the amount or reference.
The ledger is the centre of CloudERP.One, and almost nothing is typed into it directly. A sales invoice posts a receivable and revenue the moment it is submitted. A purchase invoice posts a payable and either an expense or stock. A payroll run posts salaries, PAYE, pension and the net amount due to staff. A stock transfer between warehouses posts nothing to profit but moves inventory value between accounts. The accountant's work is to review, reconcile and close, not to re-enter what the operation has already recorded.
The chart of accounts is built to your structure, one per company, with a shared group chart for consolidation. Every ledger line can carry a cost centre and up to three further dimensions, typically branch, department and project, so the same expense account answers three questions at once: how much, where, and for what. Accounts can be held in any currency, with exchange rates maintained centrally and unrealised gains and losses revalued at period end.
Receivables and payables are managed from the documents that created them. A payment entry allocates against one or many invoices, handles advances and part payments, and deducts withholding tax where the customer has withheld it. Statements and reminders go out on a schedule. Credit limits are enforced in Sales, so the finance team sets the rule once and the order screen applies it. Bank reconciliation works from an imported statement: lines are matched to payment entries automatically where amounts and references agree, and the rest are matched by hand or turned into new entries without leaving the screen.
VAT and withholding tax are computed on each document from the tax templates you configure, and the returns reports summarise them by period. Period closing locks the books up to a date so that nothing can be back-posted after the accounts have been issued. Financial statements run by company and consolidated, by cost centre and by any dimension, with comparison columns for the previous period and the budget. Every entry keeps its full history: who created it, who approved it, what was changed and when.
Reconcile the bank accounts from the imported statements, review documents still in draft, post recurring journals, run the revaluation, produce the statements, lock the period. Each step is a screen, and the close takes days rather than weeks.
Upload the bank statement. Lines that match a payment entry by amount and reference are matched automatically; the rest are matched by hand, or a new payment or charge is created from the line. The reconciliation report shows the book and statement balances agreeing.
Three companies, three charts of accounts mapped to one group chart. Inter-company invoices post to both companies at once. The consolidated profit and loss and balance sheet run with eliminations, by month, with the previous year beside them.
We load a sample of your records before the demo so the screens show your business, not ours.
Leads, quotations, sales orders, deliveries and invoices in one flow, with price lists, discounts and credit control applied as the order is entered.
Selling in CloudERP.One is a chain of documents where each one is created from the last. A lead becomes an opportunity, the opportunity produces a quotation, the accepted quotation becomes a sales order, the order is delivered on one or several delivery notes, and the deliveries are invoiced. Because each document is built from the previous one, the item, the price, the customer and the terms are entered once and travel with the deal.
Pricing is a set of rules rather than a conversation at the counter. Price lists apply by customer group, territory or currency. Pricing rules add quantity breaks, promotional prices with start and end dates, and free items. Discounts above a threshold route to a manager for approval before the order can be submitted. Credit limits are checked when the order is saved, and a customer over the limit or with overdue invoices is placed on hold until finance releases the order.
The CRM side keeps the pipeline honest. Opportunities carry a stage, a value, a probability and a next action, so the sales pipeline report shows what is likely to close this month rather than what somebody hopes will. Emails sent to a lead or a customer are filed against the record. Follow-ups, calls and meetings are logged as activities, and a salesperson's day starts with the list of what is due. Targets are set by salesperson, territory or item group and tracked against actual invoiced sales.
Fulfilment handles what real orders do: partial deliveries, back orders, substitutions and returns. A return creates a credit note against the original invoice, and the stock comes back into the warehouse it is returned to, not the one it left. Sales analytics run by customer, item, item group, territory, salesperson and period, with drill-down from any figure to the invoices behind it. A mobile application for field sales teams, with route plans and order capture on the road, is available separately and posts into the same sales orders.
The salesperson converts the accepted quotation to an order. The warehouse delivers against the order, in two shipments. Finance invoices the deliveries. The customer, items, prices and terms were entered once, on the quotation.
A customer is at their credit limit with two invoices overdue. The order is saved but placed on hold, the credit controller is notified, and the delivery cannot be created until the hold is released or the account settled.
Targets are set by territory and salesperson per quarter. The performance report shows invoiced sales against target, pipeline by stage, and conversion from quotation to order, by person and by region.
We load a sample of your records before the demo so the screens show your business, not ours.
Material requests, supplier quotations, purchase orders, receipts and supplier invoices, with approval at each step and landed cost added where it belongs.
| Item | Qty | Rate | Amount |
|---|---|---|---|
| Paracetamol 500mg x100 | 1,200 | 840 | 1,008,000 |
| Amoxicillin 250mg x100 | 600 | 1,350 | 810,000 |
| Vitamin C 1000mg x30 | 400 | 1,055 | 422,000 |
| Net total | 2,240,000 |
Purchasing begins with a need, not with a supplier. A material request is raised by a department, a project or automatically by a reorder level in Inventory. It is approved, then sent out as a request for quotation to one or several suppliers. Supplier quotations come back and are compared side by side on price, lead time and terms, and the chosen one becomes a purchase order with the supplier's price already on it.
Approval is a workflow that follows your delegation of authority. A purchase order under a set value is approved by the department head; above it, by operations and then finance; above a further value, by the managing director. The workflow is configured by value, department and item group, and the order cannot be submitted until the required approvals are recorded. Budgets are checked at the same point: a request against a cost centre whose budget is exhausted is stopped, or flagged for an exception, depending on how strict you want the control to be.
Suppliers are managed as records with a history. Each one carries price lists, agreed lead times, payment terms, tax status and the documents that support them. A supplier scorecard rates delivery on time, quality on receipt and price against the market, and the purchasing team sees that score when choosing who to buy from. Blanket orders cover an agreed quantity over a period and release call-offs against it.
Receiving closes the loop. The warehouse receives against the purchase order, so quantities over or under the order are visible immediately. Landed cost adds freight, duty, clearing and insurance to the cost of imported goods, allocated across the items by value or quantity, so the stock is valued at what it really cost to bring in. The supplier invoice is matched to the receipt and the order, the three-way match, before it can be paid. Returns to supplier, debit notes and accruals for goods received but not yet invoiced are all handled from the same documents.
The supplier invoice arrives for 1,200 units. The receipt shows 1,150. The invoice is matched to the receipt, the shortfall is flagged, and finance pays for what was received while purchasing raises the query with the supplier.
A container arrives with goods, freight, duty and clearing charges on four different invoices. The landed cost voucher allocates them across the items by value, so each item carries its true cost into stock and into the margin on the sales it goes into.
A request for quotation goes to three suppliers. Their quotations are entered or uploaded and compared on one screen by item: price, lead time, minimum quantity and terms. The chosen quotation becomes the purchase order in one step.
We load a sample of your records before the demo so the screens show your business, not ours.
Items, warehouses, batches, serial numbers and valuation, with every movement recorded as it happens and stock value posting to the ledger.
| Item | Main store | Ikeja | Abuja | Total | Reorder |
|---|---|---|---|---|---|
| Paracetamol 500mg x100 | 1,240 | 310 | 180 | 1,730 | 400 |
| Amoxicillin 250mg x100 | 96 | 40 | 12 | 148 | 300 |
| Vitamin C 1000mg x30 | 820 | 210 | 150 | 1,180 | 250 |
| Glucose 50g sachet | 4,100 | 900 | 620 | 5,620 | 1,500 |
| Cough syrup 100ml | 310 | 75 | 0 | 385 | 200 |
Inventory is the module most of the others depend on, and it is designed to be trusted. Every movement of stock is a document: a purchase receipt, a delivery note, a stock entry for a transfer, issue or manufacture, or a stock reconciliation for a count. Each one updates quantity and value the moment it is submitted, so the figure on the screen is the figure on the shelf, and the stock ledger shows every movement with its running balance.
Items are described once with their units of measure and conversion factors, so a product bought in cartons, stored in pieces and sold in packs is one item, not three. Variants handle size and colour. Batches carry manufacturing and expiry dates, and picking can be first-expiry-first-out. Serial numbers track individual units from receipt to sale and through warranty. Warehouses are arranged in a tree, company to branch to room to bin, and reports roll up at any level.
Valuation is automatic and posts to the ledger with each movement, using FIFO or moving average as you choose per item. The stock value in the balance sheet is the sum of the stock ledger, always, with no month-end adjustment to bring them together. Reorder levels and reorder quantities are set per item and warehouse, and when stock falls below the level the system raises a material request for Purchasing or a work order for Manufacturing, before the shortage is noticed on the floor.
Counts do not stop the business. A stock reconciliation records the physical count for a warehouse or a part of it, compares it with the book figure, and books the difference to a variance account with a reason, subject to approval. Negative stock is prevented by default, so a sale cannot be posted for goods that the system does not hold. Reports cover stock balance, stock ageing, slow and dead stock, projected stock against open orders, and valuation by warehouse, item group or batch.
Stock leaves the main store on a transfer and sits in an in-transit warehouse until the branch confirms receipt. Nothing is counted twice and nothing disappears between the two; what is on the road is visible as a line in the stock balance.
A count is run for one warehouse, aisle by aisle, over two evenings. Each count sheet is entered as a stock reconciliation against the book figure at that moment; variances are listed with reasons and approved by the manager before they post.
Every receipt of a perishable item carries its batch and expiry date. Picking is first-expiry-first-out by default, the expiry report lists what will expire in thirty, sixty and ninety days by warehouse, and expired batches are blocked from sale.
We load a sample of your records before the demo so the screens show your business, not ours.
Bills of materials, work orders, job cards and production planning, with the real cost of each work order built up from materials, labour and overhead as it runs.
A bill of materials describes what goes into a product: the raw materials and sub-assemblies with their quantities, the operations in sequence, the workstations that perform them and the time each takes. Bills can be nested to any depth, so a finished good made of three sub-assemblies, each with its own bill, is costed and planned as a tree. Each bill carries its cost, built up from material prices and operation rates, so the standard cost of a product is known before it is made.
The production plan takes the open sales orders, or a sales forecast, and the stock on hand, and works out what to make and what to buy. It produces work orders for the finished goods and sub-assemblies, and material requests for the raw materials that will be short, with the dates by which each is needed. Purchasing sees the shortage before the machine does.
On the floor, a work order reserves its materials and moves through its operations on job cards. An operator starts and completes a job card at the workstation, records the quantity produced and the quantity scrapped, and the next operation becomes available. Materials are issued to the work order as they are consumed, and finished goods are received into stock as they are completed, so work in progress is visible at any moment as a value and a quantity at each stage.
The real cost of a work order is built up as it runs: the materials actually issued at their actual valuation, the labour and machine time actually booked at the rates you set, and overhead applied by the rule you configure. The variance against the standard cost is reported per work order and per product, so a product that is quietly costing more than it should is seen within the week. Subcontracted operations send materials to a supplier and receive the processed goods back against a purchase order, with the service cost added to the product.
The production plan reads the sales orders due in the next two weeks, nets off stock on hand, and creates the work orders and the material requests for what is short. Purchasing sees the material list on Monday morning with the dates it is needed.
Materials are issued at their actual valuation, operators book time on job cards, scrap is recorded at the operation where it happened. The work order shows its actual cost against the standard from the bill of materials, and the variance is explained line by line.
Fabric is sent to a contractor for dyeing on a subcontracting order. The dyed fabric comes back as a receipt against that order, the contractor's charge is added to the cost of the material, and the stock at the contractor is visible while it is away.
We load a sample of your records before the demo so the screens show your business, not ours.
Projects, tasks, timesheets and costs, with billing from timesheets or milestones and profitability per project.
A project in CloudERP.One is a structure for collecting cost and revenue, not just a task list. It carries its tasks with dependencies and milestones, its budget by cost category, its contract terms and billing schedule, and its team. Everything the business spends on the project, from the first timesheet to the last supplier invoice, is coded to it as it happens, so the project's cost is known on any day, not reconstructed at the end.
Labour comes in through timesheets. Staff log hours against a project, a task and an activity type, and the hours are costed at the employee's rate and, where the project is billable, priced at the billing rate for that activity. Expense claims, purchase orders, supplier invoices and stock issued from the store all take a project reference, and each one updates the project's cost to date the moment it is submitted.
Billing follows the contract. A fit-out or construction project bills by milestone, with retention held back and released on completion. A consultancy bills time and materials from approved timesheets, with the hours and rates printed on the invoice. A support contract bills a fixed amount on a schedule. All three produce ordinary sales invoices that post to the ledger and age like any other receivable.
Profitability is reported while the work is going on. The project shows budget against cost to date, cost to complete, billed against earned, and the margin, with drill-down to the documents behind each figure. Work in progress is valued for the balance sheet at period end. Resource reports show who is booked on what and who has capacity, and the Gantt and board views show where the plan stands against the dates that were promised.
A 40 million fit-out is billed in four milestones with ten percent retention. Each milestone invoice is raised from the project when the milestone is marked complete, retention is held in its own account, and the final invoice releases it.
Consultants log hours against the client's project and tasks each day. At month end the approved hours are pulled into one invoice at the agreed rates, with the timesheet detail attached, and the invoice posts to the ledger like any other.
The project report shows cost to date, committed cost from open purchase orders, estimated cost to complete and billed to date. A project heading for a loss is visible in week three, when the scope can still be renegotiated.
We load a sample of your records before the demo so the screens show your business, not ours.
Employee records, attendance, leave, payroll with statutory deductions, expense claims and an employee self-service portal.
The employee record is the single source for everything HR and payroll need: personal and contact details, the contract and its documents, the reporting line, grade, cost centre and branch, the salary structure, bank details, and the history of every change. Onboarding and exit are checklists with owners, so laptops, access cards, system accounts and final settlements are not forgotten.
Attendance can come from biometric or card devices, from a file, from the employee self-service portal or from a manual register. Shift types define working hours, grace periods and overtime rules. Leave is governed by policies: types, annual allocation, carry-forward, accrual and who approves. An employee applies on the portal, the manager approves, and the balance and the payroll are updated without an email or a spreadsheet.
Payroll is a structure of components rather than a list of numbers. Earnings and deductions are defined once with their formulas, assigned to employees through salary structures, and computed for each pay period. Statutory deductions are configured per country and applied automatically. Loans, salary advances, arrears, overtime and unpaid leave feed in from their own records. The payroll run produces payslips, the bank payment file and the journal entry for the ledger, and nothing is paid that has not been approved.
The employee self-service portal gives staff their payslips, leave balances, attendance, expense claims and personal details, and gives managers their approvals, on a phone or a desktop. Appraisals, training records, grievances and disciplinary records are kept against the employee, with access restricted to the people who should see them. Reports cover headcount, turnover, leave liability, payroll cost by department and statutory returns.
Attendance and approved leave are pulled in, overtime and loan deductions applied, PAYE, pension and other statutory items computed from the salary structures. Payslips are issued, the bank file is generated and the payroll journal posts to the ledger in one run.
Staff apply for leave on the portal; managers approve from their phone. Balances update, the attendance register reflects the leave, and payroll picks up unpaid leave automatically. The leave liability report is available to finance at any time.
An employee checks a payslip, submits an expense claim with the receipt photographed, updates a bank detail subject to HR approval, and sees the leave balance, all without an email to HR.
We load a sample of your records before the demo so the screens show your business, not ours.
An asset register with depreciation, movements, maintenance and disposal, posting to the ledger on schedule.
| Year | Depreciation | Net book value |
|---|---|---|
| 2024 | 4,750,000 | 23,750,000 |
| 2025 | 5,700,000 | 18,050,000 |
| 2026 | 5,700,000 | 12,350,000 |
| 2027 | 5,700,000 | 6,650,000 |
| 2028 | 5,700,000 | 950,000 |
The asset register holds every asset the company owns with its category, location, custodian, cost, purchase date, supplier and the documents that prove it. Categories carry the accounting: the asset account, the depreciation method, the useful life and the depreciation account, so an asset placed in a category is set up correctly without a second thought.
Assets are usually created from the purchase invoice, so a generator bought from a supplier is capitalised from the same document that recorded the payable, at the same value. Assets built over time are accumulated in capital work in progress and capitalised when they go into service. Each asset then follows its depreciation schedule, straight line or written down value, and the monthly journal entries are posted automatically on the date you set.
Assets move. A vehicle changes custodian, a server moves from one branch to another, a machine goes out for repair. Each movement is recorded with a date and an approver, so the register says where everything is now and where it has been. Maintenance schedules put servicing on a calendar, with the cost of each visit recorded against the asset; repairs are expensed or capitalised according to the rule you set.
Disposal, sale or scrapping removes the asset from the register and books the gain or loss against its net book value. Revaluation and impairment are recorded as events with their own entries. Physical verification runs by location, with a list to tick off and a report of what was not found. The fixed asset register report ties out to the balance sheet, by category and in total, at any date.
The purchase invoice for the generator is submitted with the asset flag set. The asset is created in the Plant and Machinery category with its cost, supplier and date, and begins depreciating on its in-service date on the category's schedule.
On the last day of each month the depreciation entries for every asset are posted to the ledger, by category and cost centre. The fixed asset register report reconciles to the balance sheet without a spreadsheet.
The verification list for the Abuja office is printed or opened on a tablet, each asset is ticked off, and the exceptions report shows what was not found and what was found that is not on the register, ready for the auditor.
We load a sample of your records before the demo so the screens show your business, not ours.
A counter point of sale that sells from live stock, takes several payment modes, and closes each cashier's shift against the cash actually counted.
The point of sale is a screen in the same system as inventory and accounting, not a separate till that syncs later. When a cashier completes a sale, stock is deducted from the branch warehouse and the sale posts to the ledger at that moment. Items, prices, promotions and product groups are maintained once in Inventory and Sales and apply at every counter in every branch.
The counter screen is built for speed: barcode scanning, search by name or code, quick-select tiles for the items that sell most, quantity and discount entry within the rules set for that cashier, and customer lookup for purchase history and credit sales. Payment can be split across cash, card and bank transfer on one receipt, and the receipt prints to an ordinary receipt printer or is sent by email or message.
Each cashier works in a session. Opening records the float; closing compares the expected cash, card and transfer totals with what the cashier counted and hands over, and the variance is recorded against that cashier and that session. The manager sees every session for the day across all branches, with the variances, voids, discounts and returns that need a second look.
Returns and exchanges are made against the original receipt, so the refund method, the price paid and the stock movement are correct without the cashier deciding. Back-office reports show sales by hour, by item, by cashier and by branch, gross margin by item group, and the stock position at each branch against its reorder levels. The point of sale needs a working connection to post sales, and is sized for retail chains, pharmacies, supermarkets and any business selling across a counter.
The cashier counts the drawer and enters cash, card and transfer totals. The closing entry compares them with the system's expected figures per payment mode, records the variance against the cashier and the session, and the branch manager signs it off.
A customer returns an item two days later. The cashier finds the original receipt, selects the item, and the refund is made in the method it was paid, the stock returns to the branch warehouse and the sale and the credit both appear in the day's report.
The retail director opens the dashboard to see today's sales per branch by hour against the same day last week, the average basket, the top items and the cashiers with the largest variances, while the shops are still open.
We load a sample of your records before the demo so the screens show your business, not ours.
Inspection templates, incoming and in-process inspections, non-conformance and corrective action, tied to receipts, work orders and deliveries.
| Parameter | Specification | Reading | Result |
|---|---|---|---|
| Moisture content | 10 to 12 % | 13.1 % | Fail |
| Protein | at least 11 % | 11.8 % | Pass |
| Colour | creamy white | creamy white | Pass |
| Foreign matter | none | none | Pass |
| Pack weight | 50 kg, within 0.2 | 49.9 kg | Pass |
Quality in CloudERP.One is a set of checks defined once and required at the points you choose. An inspection template lists the parameters to be checked, numeric ones with their acceptable range and pass or fail ones with their acceptance criteria, and the sampling rule. Templates are attached to items, so receiving a batch of flour or a roll of packaging brings up the right checklist without anyone looking for it.
Inspections are required on the documents where quality matters: a purchase receipt before goods enter stock, a job card during production, a stock entry before finished goods are released, a delivery note before goods leave. The document cannot be submitted until the inspection is recorded, and a failed inspection holds the goods in a quarantine warehouse rather than releasing them, with the reason on file.
A failure becomes a non-conformance with a cause, a responsible person and a deadline. Corrective and preventive actions are recorded against it and tracked to closure. Because the non-conformance is linked to the supplier, the batch, the work order or the machine, the history builds by itself: this supplier has failed moisture content three times this quarter; this line's rejection rate rose after the shift change.
Quality procedures, reviews and goals are kept alongside the inspections, so an audit can follow the chain from the written procedure to the template to the inspections performed and the actions taken. Reports cover inspection results by item, supplier and period, rejection rates, open non-conformances by age and the cost of quality where rework and scrap are recorded in Manufacturing.
The purchase receipt for a batch of raw material requires an incoming inspection. Moisture content reads above the limit; the inspection fails, the receipt is held, the goods go to the quarantine warehouse and a non-conformance is raised against the supplier.
Every job card on the filling operation requires a weight check on a sample. The operator records the readings on a tablet; a reading outside the range stops the job card and alerts the supervisor before the batch continues.
The non-conformance is assigned a root cause and a corrective action with an owner and a date. Open actions appear on the quality dashboard by age; the supplier's non-conformance history is on their record when the next order is placed.
We load a sample of your records before the demo so the screens show your business, not ours.
Tickets from email and a customer portal, service levels, assignment rules, warranty claims and maintenance visits.
Support turns every customer issue into a ticket with an owner, a priority and a clock. Tickets arrive from an email address the system watches, from the customer portal, or are logged by phone. The customer, the contract and the history are attached automatically where the sender is known. Assignment rules route the ticket to the right team by product, customer or region, with round-robin or load-based distribution within the team.
Service levels are agreements the system enforces. Each priority has a response time and a resolution time, measured in working hours against the support calendar, and each ticket shows the time remaining. The clock pauses while a reply is awaited from the customer and resumes when they answer. A ticket approaching its limit is escalated and flagged, so the breach is seen before it happens and not in the monthly report.
The conversation stays with the ticket. Replies go out from the ticket and the customer's answers come back to it, so the full thread is on one screen with the internal notes the customer does not see. Warranty claims check the serial number against the sale and the warranty terms before work is approved. Maintenance schedules put planned visits on a calendar, and each visit records what was done, the parts used and the time taken.
Reports cover ticket volume by product and cause, first response and resolution times against the agreement, breaches by team, and the backlog by age. Because the ticket is linked to the customer, the item, the serial number and the invoice, the product team can see which products generate the issues and the finance team can see what support is costing per contract.
A customer writes to support at your domain. The email becomes a ticket, the customer is recognised from the address, the contract's service level is applied and the ticket is assigned to the right team. The first reply goes out from the ticket.
A premium contract has a one-hour response and a one-day resolution; a standard contract has four hours and three days. Each ticket shows the time left on its own clock, pausing while the customer is being waited on, and escalates before the limit.
A maintenance contract for installed equipment generates quarterly visits on the calendar. Each visit records the engineer, the work done, parts used from stock and time taken, and the customer's equipment history builds up visit by visit.
We load a sample of your records before the demo so the screens show your business, not ours.
Standard reports in every module, a report builder that needs no code, dashboards with charts and number cards, and scheduled reports by email.
| Territory | Customer | Net total | Margin |
|---|---|---|---|
| Lagos Mainland | Medfield Pharmacy | 6,420,000 | 31% |
| Lagos Mainland | Okonkwo Stores | 2,110,000 | 18% |
| Lagos Island | Sunrise Supermarket | 9,860,000 | 22% |
| Abuja | Crest Logistics | 3,240,000 | 27% |
| Abuja | Northline Foods | 4,180,000 | 19% |
| Total | 25,810,000 | 23% |
Every module ships with its standard reports: the trial balance, the stock balance, the sales register, the payroll summary, the ageing, and several dozen more, each with the filters and groupings that the module needs. Every figure in a report can be opened to show the documents behind it, so a manager who questions a number can see the invoices or the stock entries that make it up without asking anyone.
The report builder is for the reports that are yours. A manager picks the record type, chooses the columns, adds filters, sorting, grouping and totals, and saves the result as a report that others can run. No code is involved. A sales manager builds a report of orders by salesperson by item group with a margin column; a warehouse manager builds a list of batches expiring in the next sixty days by warehouse. Both can be shared, scheduled and exported.
Dashboards are built from number cards and charts, each backed by a report or a saved filter, and arranged by role. The finance dashboard shows cash, receivables overdue, payables due this week and the month's profit against budget. The sales dashboard shows orders today, pipeline by stage and the top customers. The warehouse dashboard shows stock below reorder, pending transfers and items expiring. Each person opens the system to the view that matters to them.
Any report can be scheduled and sent by email as a spreadsheet or a PDF, daily, weekly or monthly, to a list of recipients inside or outside the company. Print formats put the company's letterhead and layout on invoices, statements and orders. The same data is available through the API for anyone who needs it in another system, with the same permissions that apply on screen.
The profit and loss, cash position, receivables ageing and sales by branch are scheduled as one email each Monday at seven, as PDF and spreadsheet, to the directors. Nobody compiles it.
The auditor asks for every journal entry above a value, posted after period end, by user. The report is built in the report builder in a few minutes from the journal entry record, with those filters and columns, and saved for next year.
Finance opens the system to cash and receivables; the warehouse manager to stock below reorder and pending transfers; the sales director to orders today and pipeline by stage. Each dashboard is a set of cards and charts assigned to that role.
We load a sample of your records before the demo so the screens show your business, not ours.
The capabilities that sit under every module: companies, permissions, configuration, integration, localisation and the way people work in the system day to day.
Several companies, branches or cost centres in one system, reported separately and together.
Who can see and do what, down to the field, with a record of every change.
Fields, forms, workflows and print formats are set up in screens, not written in code.
Connect banks, websites, payment and messaging services, and anything with an API.
Taxes, currencies and fiscal settings configured for each country you operate in.
How people use the system every day, on any device.
Most of what companies ask for is done in configuration screens and included in the subscription: a field on the sales order, an approval step above a value, a print format on your letterhead, a report with the columns your board wants. Work that needs code is scoped and quoted separately, and it is rarer than people expect.
Custom fields and forms, print formats, workflows, notifications, report builder reports, dashboards, user and role setup, data imports.
Integrations with other systems, custom modules, scripted reports with complex logic, and migrations of full transaction history.
Everything configured in your system survives version updates. We test each release against configured sites before it is applied.
If you have a list of must-haves, send it. We will tell you what is standard, what is configuration and what would need to be built.
CloudERP.One is delivered as a managed service. You use it in a browser; we run the servers, the backups, the updates and the security.
CloudERP.One is hosted and operated by us. Your company gets its own address, such as yourcompany.clouderp.one, on dedicated capacity sized to your users and data. Updates, monitoring and security patches are our job, not yours.
Backups run several times a day and are stored separately from the production servers. If something goes wrong, we restore to the latest copy, typically within an hour. Standby capacity is kept to take over production if a primary server fails.
All traffic is encrypted. Access is by named user with role-based permissions, with two-factor authentication available for every account. Administrative access to servers is restricted to our operations team and logged.
The data is yours. You can export any record to spreadsheet at any time, and a full copy of your database is available on request. If you leave, you take your data with you.
Support by email, phone and WhatsApp during business hours, with an emergency line for production issues. Our team is in Lagos and Abuja and works in your time zone.
New versions are applied by us after testing, outside your working hours, with release notes sent in advance. Your configuration and custom fields are preserved.
Any computer, tablet or phone with a current browser. No software to install. Receipt printers and barcode scanners connect to the point of sale as ordinary devices.
A normal internet connection. The system is light on data; a branch on a mobile hotspot works. Point of sale terminals need a connection to post sales.
One person who owns the system on your side, usually in finance or operations, and department leads who sign off their own data and training.
We answer them in writing, and we are happy to talk to your IT staff or auditors directly.
A fixed sequence of six steps, run by our team. Most companies are live in two to six weeks. Larger groups are planned in phases, one company or one module set at a time.
We meet your team, walk through how the business runs today, and agree the scope: which modules, which companies, which branches, and what has to be true at go-live.
We set up your companies, chart of accounts, items, warehouses, price lists, taxes, users and roles. You see your own data in the system before any training.
Customers, suppliers, items, opening stock and opening balances are loaded from your current system or spreadsheets, checked, and signed off by you.
Each team is trained on its own screens with its own data: accounts, sales, stores, HR. Short sessions, repeated as needed, with written guides left behind.
We run the first days alongside your staff, on site where it helps, and close the first month end with your accountant.
After go-live you have a named contact, a ticket system and the emergency line. Changes to configuration and new reports are handled as part of the subscription.
Clean item, customer and supplier lists and a reconciled trial balance shorten migration more than anything else. We send a template on day one.
Accounting, sales, purchasing and inventory together are a four-week project for a single company. Manufacturing, payroll and projects each add one to two weeks.
Chart of accounts, naming, approval limits and who signs off what. We bring recommendations; you decide. Decisions that wait are the usual cause of slippage.
The ones we are asked before every implementation.
Two to six weeks for most companies, depending on the number of modules, the state of the data to be migrated, and how quickly decisions are made on your side. Larger groups take longer and are planned in phases.
No. CloudERP.One is hosted and managed by us. You need a browser and an internet connection. If you have IT staff, they can administer users and configuration; if not, we do it.
Yes. Most companies start with accounting, sales, purchasing and inventory, and add HR, manufacturing or projects later. Modules are switched on in configuration; nothing has to be re-implemented.
An annual subscription scoped to your company, plus a one-time implementation fee quoted after discovery. We give you both figures in writing before you commit to anything.
Customers, suppliers, items, stock and opening balances are migrated as part of implementation. Historical transactions can be loaded where you need them for reporting.
Custom fields, forms, print formats, workflows and reports are configured without code and are included. Anything beyond that is scoped and quoted separately.
Traffic is encrypted, access is by named user and role, and backups run through the day. You can export any record at any time and request a full copy of your database.
A discovery session is free and takes about two hours. You leave with a scope, a timeline and a written quotation.
Tell us what the business does and which modules you are looking at. We reply within one working day with a time for a demo or a discovery session.
A demo is about an hour, on a call or in person in Lagos or Abuja. If you send a few items, customers and a trial balance beforehand, we load them so the screens show your business.
An annual subscription scoped to your company, and a one-time implementation fee quoted after discovery. Both figures are given in writing before you commit to anything. There are no per-transaction charges.