AWRA OpsHub Search

Markets

AWRA OpsHub, one page per market

The operations layer — stock that moves, approvals that refuse, evidence attached to the transaction — is the same in every country we sell into. Five things change at every border: fiscalisation, statutory payroll, how the currency behaves, working language, and who is near enough to support you. Each page below is honest about which of those we handle there and which stay with local specialists.

Written market guides
17
Regions covered
6
Countries supported
88

Where we have written it down

Grouped by region, and ordered the way the guides are. If your country is not here, the operations layer still works — what is missing is a page stating the local specifics, and we would rather talk it through than let you infer it.

A written guide and a supported country are not the same thing. AWRA OpsHub ships tax and currency profiles for 88 countries and runs in your own base currency wherever you are. The 17 guides below are the markets we have done the research for and can speak to specifically — the tax authority by name, how the currency behaves against your cost base, which payment rails matter, and who is near enough to support you. The other 71 are supported but unwritten. That is a gap in our documentation, not in the product, and a call is the faster route until the page exists.

Africa

What is the same everywhere, and what is not

Most of the value in an operations system does not change at a border. The parts that do are the parts vendors are vaguest about — so they are the first thing each country page settles.

The same in every market

  • Inventory across locations, with governed transfers and a real in-transit position.
  • Procurement with approval thresholds that refuse, RFQ comparison and three-way matching.
  • Landed cost from freight, duty and clearing, written onto the goods.
  • Asset registers with named custody, verification history and disposal.
  • Projects, funders and cost attribution captured as work happens.
  • Offline mobile capture with duplicate-safe sync, and documents attached to the transaction.

What changes at the border

  • Fiscalisation. Kenya's eTIMS is our only revenue-authority integration anywhere, and it is not portable.
  • Statutory payroll. Maintained for Kenya only; elsewhere the computation belongs with a local bureau.
  • Currency behaviour. A peg, a float and a redenomination are three different operational problems.
  • Working language. The interface is English only, which is decisive in some markets and we raise it early.
  • Support geography. We are remote-first from Nairobi, with no office anywhere else.

Not sure your market is a fit?

Tell us where you operate, what you hold, and who keeps your books. On a good number of these calls the honest answer is a local vendor, and we would rather reach it in week one than month three.