AWRA OpsHub Search

Implementation

From spreadsheets to AWRA.

“How do we actually move from Excel to this?” Six steps, one workflow at a time — and you do not have to digitise everything on day one.

The rollout

Six steps, each with a finish line.

Each step says what your team does, what AWRA does at that point, and the checkpoint that tells you it is finished — so you know when to move on rather than guessing.

Step 1

Map your workflows

What your team does

Pick the one workbook that hurts most — usually the stock sheet or the purchase tracker — and write down who raises, who approves, who issues and who pays.

What AWRA does

Departments, locations and reason codes become the skeleton those roles hang on, so the map turns straight into configuration.

Done when: Every step in that first workflow has a named role, not a name in a cell.

Departments, locations & reason codes

Step 2

Import your data

What your team does

Agree one naming standard, de-duplicate the item list, then download each template and fill it from your sheets.

What AWRA does

Items, suppliers, customers, assets, warehouses, locations and the chart of accounts upload from CSV or Excel. A file goes in whole or not at all, so a bad row is a message, not half a catalogue.

Done when: The item list in AWRA matches the shelf, not the sheet — confirmed by a count at each location.

Bulk import

Step 3

Configure users and approvals

What your team does

Decide who may raise a request, who approves it, who issues stock and who records payment — and keep those four people apart.

What AWRA does

Roles carry the permissions and the Approvals Hub collects what is waiting on each person. Downstream, the system refuses on its own: a purchase order can only be made from an approved quotation, an over-receipt is blocked, and a stock adjustment above the value you set cannot be approved by whoever raised it.

Done when: Raising, approving, issuing and paying sit with different roles — and you have checked it by trying to cross one.

Workflow automation

Step 4

Train your team

What your team does

Train by role, not by module. A storekeeper needs check-in, check-out and counts; an approver needs the Approvals Hub; finance needs the Payments Register.

What AWRA does

The mobile app works without a signal and syncs later, so stores and field staff learn on the device they will use. Help-center articles and Academy courses cover each role.

Done when: Each role has done its own task once, on real data, without help.

Academy

Step 5

Go live

What your team does

Pick a date, run opening counts, and freeze the old workbook as a read-only reference. Do not delete it — keep it until the numbers have matched for a month.

What AWRA does

The Control Tower ranks what is stuck in the first weeks — stock at risk, delayed orders, suspicious adjustments — so problems surface while the old sheet is still there to compare against.

Done when: Nobody has edited the old workbook since go-live day.

Operations hub

Step 6

Improve and automate

What your team does

Look at what people still do by hand — the weekly report, the reorder check, the reminder email — and choose the next workbook to retire.

What AWRA does

Saved filters, scheduled reports, low-stock alerts and workflows take over the repeat work, and webhooks tell the systems you kept.

Done when: The next workflow is chosen, and step one starts again on it.

Saved filters & scheduled reports

Pace

You do not have to digitise everything on day one.

The rollouts that stick start small. One workflow your team trusts beats six that nobody is sure about — and every one you add after it goes faster, because the items, people and approvals are already there.

Day one

One workflow

The workbook carrying the most risk — stores issue-out, stock across branches, or the purchase tracker. Everything else stays where it is.

The first term or quarter

The chain around it

Requests, approvals and purchasing once the stock figures are trusted, because an approval is only as good as the balance it is approving against.

When you are ready

The rest of the suite

Sales and POS, accounting, HR and payroll, assets, the helpdesk. They are switched on in the trial; your team uses them when the earlier ones have stuck.

Where to start

Schools, NGOs and SMEs start in different places.

The six steps are the same. The first workflow is not.

Schools

Usually starts with

Stores and department requests

Departments request supplies, the bursar or budget owner approves, and the store issues against a balance that is real. Procurement follows once a term of issue-outs shows what is actually consumed.

Inventory and procurement for schools

NGOs

Usually starts with

Programme stock and field requests

Field offices request against a programme, approvals are recorded, and every transfer is signed for at both ends. RFQ evidence and payroll allocated to the grant come next, when the donor report is due.

Procurement and stock for NGOs

SMEs

Usually starts with

Items, stock by location and sales

One item list, stock by branch, and sales or POS that deduct as they happen. Purchasing joins when reorder decisions need evidence, and QuickBooks can stay as the books.

Inventory management software

Migration

Already using Excel, QuickBooks or another system?

You do not need to throw everything away. Most teams keep something they already run and connect it, rather than replacing it on day one.

Excel → AWRA

Import items, suppliers, customers, assets and your chart of accounts.

  • Upload a CSV or Excel file for items, vendors, customers, assets, custodians, warehouses, locations or the chart of accounts — each from a template you download first.
  • A file is imported whole or not at all. One bad row rolls the file back, so you never find half a catalogue in the system and half still in the sheet.
  • Opening stock comes in on the item sheet into your default location; a count at each branch then puts every unit where it actually sits.
  • Employees import from CSV with a preview you check before anything is written.

More we can add

Opening ledger balances by upload. The template is already in the product, and switching the upload on for your workspace is work we can take on.

QuickBooks → AWRA

Keep QuickBooks for the books. Let AWRA run the operational workflow in front of it.

  • Connect your QuickBooks Online company from settings, with its own sign-in for your organisation.
  • AWRA pushes vendors, items and purchase orders across, so the supplier and item lists stop being typed twice. A vendor saved in AWRA syncs on its own.
  • A sync log shows what went across and what QuickBooks refused, so a failed record is a line you can read rather than a mismatch you find at month-end.
  • Available on Premium and Enterprise.

More we can add

Invoices, bills and payments sent to QuickBooks, and records pulled back from it — both are extensions we can build for your workspace.

Existing ERP → AWRA

Run AWRA beside the system you have, connected through its API and webhooks.

  • A read API, keyed to your organisation, serves items, categories, warehouses, customers, invoices, vendors and purchase orders to the other system.
  • Workflows send signed webhooks when something happens — a stock movement, a low-stock item, a procurement request, an RFQ or a quotation — so the ERP hears about it without polling.
  • Inbound webhooks accept signed events from the other system and start a workflow in AWRA.
  • The same workflows can post to a Zapier or Make catch-hook when the other side already lives there.

More we can add

Write access on the API, so another system can create records in AWRA directly rather than through a webhook-triggered workflow.

Pricing

What it costs to start

Items, multi-warehouse stock, transfers and counts are fully on Basic, which is where most first workflows live. Multi-step approval routing and payroll start on Pro; the QuickBooks connection is on Premium.

Basic plan · Get organised

KES 2,500 / month

or KES 27,500 billed yearly

Source-of-truth inventory and day-to-day operations for a small, hands-on team — now with core people, projects and a support desk.

Before you pay anything

30-day free trial

Thirty days of the full platform, every module switched on and no card required. Choose a paid tier whenever you are ready.

What the rollout runs on, and what we can add to it

What AWRA OpsHub does today

  • Whole-file imports. A spreadsheet upload is committed in one transaction, so a bad row rolls the file back instead of leaving half a list behind.
  • Offline mobile capture. Check-ins, check-outs, transfers, counts, POS sales and approvals queue on the phone and replay when the signal returns.
  • One Approvals Hub collecting requests, RFQs, quotations, purchase orders, transfers, leave and payroll that are waiting on someone.
  • A tamper-evident audit log, hash-chained and exportable, so go-live does not lose the question of who changed what.

More we can add to your workspace

  • A setup checklist inside the workspace that tracks these six steps and shows how far your rollout has got. Today the rollout plan is kept alongside the product rather than inside it.
  • Opening ledger balances by upload. The template exists; the upload for journal opening balances is something we can switch on for your workspace.
  • Opening stock for every location in one file. The item sheet loads into the default location, and a per-branch opening file is an extension we can build.

Where we point you to a specialist

  • We will not load a workbook as the opening position when nobody on your side can say which of its figures are true. A count first is slower and it is the only honest start.

Everything in that middle column is scope, not a ceiling. Tell us which of it you need and we will come back with a written spec, a timeline and a price to add it to your workspace.

Implementation questions

Moving off spreadsheets, answered

Do we have to move everything into AWRA at once?
No, and we advise against it. Start with the one workflow that carries the most risk, prove the numbers match, then add the next. Every module is switched on during the trial, but nothing obliges your team to use one before it is ready.
What can we import from our spreadsheets?
Items with opening stock, suppliers, customers, assets and their custodians, warehouses, locations and the chart of accounts, each from a downloadable CSV or Excel template. Employees import separately from CSV with a preview. A file is imported whole or rolled back whole, so a bad row never leaves a half-loaded list.
Can we keep QuickBooks?
Yes. Connect your QuickBooks Online company and AWRA pushes vendors, items and purchase orders across, so those lists are kept in one place. QuickBooks stays the ledger; AWRA runs the stock, purchasing and approvals in front of it. The QuickBooks connection is on Premium and Enterprise.
What should we do with the old workbook after go-live?
Keep it, read-only, until the figures have matched for a month. Then archive it. Deleting it on go-live day removes the one thing that lets you check the new system against the old one.
Can someone do the setup for us?
Yes. Guided onboarding, data migration, managed implementation and role-based training are offered as services, scoped by proposal, and certified partners can deliver them too.
Does it work where the signal is bad?
The mobile app queues check-ins, check-outs, transfers, counts, POS sales and approvals on the device and sends them when the connection returns, so a store or field office can go live before its internet is reliable.

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center