Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For Tanzania
From Dar to Dodoma, one governed operation
Multi-branch stock, van routes that reconcile nightly, procurement with real approvals, and donor funds tracked to the shilingi — with offline mobile built for the distances.
- The subject
- The days a load spends being nowhere in particular. A system that confirms a transfer on despatch is not slightly wrong for those days — it is confidently wrong, and it produces a promise, a replenishment decision and a shortfall nobody can pin on the journey.
- Fiscalisation
- No TRA fiscal device integration. Our transmission layer is Kenya's eTIMS and it is Kenya-only. We run alongside your existing EFD or VFD process and the records reconcile. No roadmap date on this page.
- The fleet limit
- No distance is held anywhere in the product, so fuel-per-kilometre cannot be computed and no asset carries a service interval. Custody, movement and condition are real. This page overstated it once and the correction is on it in three places.
- Payroll
- Kenya-only. PAYE, NSSF and SDL are not calculated here. Employee records, attendance, leave and payroll cost allocation are.
The corridor, as a timeline
One consignment, six days, and two systems that only agree at the ends
A worked example rather than a measurement: one load leaving Dar for a depot upcountry, on a timeline that happens to run six days. Read the last two columns against each other. They match on day one, they match on day seven, and in between one of them is describing stock that does not exist where it says it does. Nothing in that week looks like an error, which is precisely why it survives.
The load is released from the Dar warehouse and the paperwork is raised.
The system believesDar down by the full load. Depot up by the full load.
What is trueDar down by the full load. Depot has nothing.
The truck is on the road. Nobody in either location touches the system.
The system believesDepot holds the stock and can sell it.
What is trueThe stock is on a road and can be sold by nobody.
A customer near the depot asks whether the goods are available.
The system believesYes — the position says they are on the shelf.
What is trueNo. The promise made on day four is a promise about a truck.
Head office runs the replenishment report for the region.
The system believesThe depot is well stocked; no order needed.
What is trueThe depot has been empty all week and the report cannot see it.
The truck arrives and the goods are counted in — two cartons short.
The system believesNothing changes. The stock was already there.
What is trueThe shortfall becomes visible for the first time, six days after it could have been raised with the driver.
The fix is one word in the process rather than a module: a transfer is confirmed on ARRIVAL, not on despatch. In between it is in transit — a real position with an owner, visible to head office, not sellable by the depot and countable against the driver when it lands. That is the whole difference between the two columns, and it is why the in-transit state is the first thing to look at in any demo you take on this market.
Operations in Tanzania
Stock that spends a week being nowhere in particular is the Tanzanian operating problem.
The EFD answer is above and it is short. The thing that actually costs a Tanzanian distributor money is the corridor: goods leave Dar, arrive in Mwanza six days later, and for those six days they exist in a state most systems have no word for. Add a van that sells off its own load all day and a depot manager whose stock card and shelf disagree by Friday, and you have described the job.
Inventory
Goods in transit as a state, not a gap
A transfer is confirmed on receipt rather than on despatch, so the six days between Dar and the depot are visible instead of being a discrepancy somebody reconciles at month end. Each depot holds its own position and head office sees all of them.
Stock transfers
Van load-outs that reconcile the same night
The load leaves as a movement with an owner, sales come off it during the round, and the variance is per route and per driver at close. A shortfall becomes a conversation on Tuesday rather than a suspicion in the quarter.
Landed cost
The inland leg costed onto the goods it moved
Duty, clearing, port charges and the road freight upcountry attach to the consignment as their invoices arrive — weeks after the stock does — and the unit cost moves each time. A margin set from the supplier invoice alone is wrong by the whole cost of the corridor.
Procurement
Four documents that stop living in four places
The tender minute, the quotes, the delivery note and the invoice against one transaction, with the approval threshold refusing rather than warning. The audit file exists because the work created it.
Assets
Fleet and equipment with a custodian per item
Named custodian, movement between zones, condition at every hand-off. No fuel log, no distance held anywhere and no service interval — so fuel-per-kilometre is not something this register can answer and we will not imply otherwise.
Offline operations
Capture that does not need the corridor to have coverage
Receipts, counts, custody and job time recorded with no signal and synced on return — the design centre rather than an adaptation, because it was built for exactly these distances.
The honest limit on the fleet card is worth repeating because it is the one people assume past: no distance is held anywhere in the system, so fuel-to-distance cannot be computed and a service calendar does not exist. Custody, movement and condition are real. Maintenance planning is a different product and you should keep the one you have.
Recognisable, we hope
Four failures that all resolve themselves before anyone files a ticket
Distribution across real distances
Vans and depots from Dar to Mwanza, visible only when the paperwork arrives — days later.
Branch stock on trust
Transfers depart full and arrive approximate; stock cards and shelves tell different stories.
Donor programs at scale
Tanzania's NGO and program sector runs multi-region operations on spreadsheets built for one office.
Procurement files in pieces
The tender minute, the quotes, the delivery note, and the invoice live in four different places.
Running in the product today
- Depot and branch stock with in-transit visibility, transfers confirmed on arrival, blind counts and valued variance.
- Van stock as a movement with an owner, on-route sales against it, and nightly variance by route and by driver.
- Landed cost that stays open after receipt, so duty, clearing and the inland freight reach the unit cost weeks after the goods did.
- Procurement thresholds that refuse, RFQ comparison, purchase orders, three-way matching and the authorisation trail on the transaction.
- Asset registers with named custody, movement between zones and condition on every hand-off.
- Offline capture for four field operations — stock transfers, inventory check-out and check-in, and asset movements — syncing when the network returns. Counting, receiving a purchase order and job time are not among them.
- TZS as your base currency, with foreign-currency purchases and grants held at the rate actually applied.
More we can add — on the roadmap, and commissionable now
- A TRA fiscal device integration. Our e-invoicing transmission is Kenya's eTIMS and it is Kenya-only. In Tanzania we run alongside your existing EFD or VFD process and the records reconcile. Transmission with retries, a failure queue and a reconciliation report is an ordinary integration project.
- Tanzanian statutory payroll. The maintained statutory engine covers Kenya only. PAYE, NSSF and SDL are not calculated here; employee records, attendance, leave and payroll cost allocation are.
- A fleet maintenance layer. Service interval, next-service date and fuel log and no distance. This was a claim on this page that overstated the product until it was corrected in August 2026, and the correction is left visible rather than tidied away.
- Bank statement reconciliation — for any market, in whatever form the bank exports.
What we would decline, and would rather say now
- We will not file with TRA. We hold the records and make them reconstructable; the filing is yours. A vendor who takes on a filing duty has accepted something they cannot discharge, and you carry the assessment either way.
- We will not become a fleet maintenance system. Service scheduling, parts and workshop management is a real product with real users, and a weak version of it hidden inside an operations platform would serve nobody. We hold custody and condition, and we integrate with whatever runs the workshop.
The middle column is work rather than positions, and each is commissionable now on a written specification, a timeline and a price agreed before any money moves. Kenya is the evidence that this is a real offer: its eTIMS transmission and its statutory payroll engine were both built exactly this way, by clients who needed them. A date belongs in a quote rather than on this page.
If TRA integration is the requirement that decides your purchase rather than one of several, weigh the middle column heavily — a vendor already shipping it starts where we would be finishing. If the decision is really about the corridor, the depots and the vans, that is the left-hand column and it is where this product is strongest.
How this starts
Three moves, starting at the end of the corridor rather than the beginning
Map the operation
Depots, branches, routes, or programs — we scope the first module around the biggest leak.
Go live at one site
One depot or one program runs a full month governed — training on your data.
Scale across regions
Sites onboard one at a time; head office sees everything, live.
Read before you shortlist
Guides for this market
NGO Operations in Tanzania: Designing for Distance
Zonal offices as real nodes, offline field capture, dual-jurisdiction records, and the fleet as a program cost — operations for programs from Dar to Kigoma.
Distribution & Inventory in Tanzania: Port to Depot to Route
The long chain — landed costs at the port, regional depots, in-transit as a location, van routes, and agent consignment — with the leak at every link named.
Multi-Country NGO Operations: One System, Five Tax Regimes
Four registrations, four currencies, one donor report — country dimensions, cross-border cost allocation, inter-office balances, and consolidation without the quarterly ritual.
Three Quotes and No Way to Score Them
We have requests for quotation with real line items and recorded responses. We have no request for proposal, no scoring model, no panel and no sealed bids. Those are not degrees of the same thing, and one of the four cannot be substituted procedurally.
What Reaches the Job and What Does Not
A purchase can name the job it is for, and so can a stock issue — costed at the price stamped when it left the store, so a finished job cannot change price later. Two things never reach the job at all, and one of them will surprise you.
The Session That Only Counts the Cash
A till session opens with a float, records every drop, and closes with a counted figure and a variance against the person who counted it. All of it is about cash — so on a counter where most customers pay by phone, the strongest control in the shop is watching the smallest pile of money.
Questions we are asked in Dar es Salaam
Straight answers, and where a build would start
Does AWRA integrate with TRA's fiscal devices (EFD/VFD)?
Not as a built-in integration today — and we would rather tell you that than discover it together later. AWRA governs operations (stock, procurement, assets, donor funds) alongside your existing fiscalization process. If TRA integration is central to your needs, describe your requirements to us and we will scope it honestly.
Does it support TZS and Tanzanian VAT?
Yes — Tanzanian Shilling and the standard 18% VAT rate are supported for transactions and reporting, plus multi-currency grant tracking for program operations.
Can it handle a distribution business with vans and depots upcountry?
That is the home use case: depots as locations, vans as traveling stock with nightly reconciliation, transfers with in-transit visibility, and offline mobile capture built for exactly the connectivity reality between regions.
What about Tanzanian payroll statutory (PAYE, NSSF, SDL)?
Statutory payroll engines are currently Kenya-only. For Tanzania, keep your payroll process and use AWRA for operations — and tell us your payroll requirements so localization gets scoped on real demand rather than promised on hope.
Our vans sell off the vehicle. Can the stock on a van be a real position?
Yes, and it is one of the better-fitting parts of this product for a Tanzanian distributor. A van is a location: stock is transferred to it, the transfer is confirmed rather than assumed, what is on board is a position you can query, and what came back at the end of the round is reconciled against what went out. Sales off the vehicle reduce that position, so the difference between loaded, sold and returned is arithmetic rather than an evening conversation. Two honest caveats. The van's round is not a route plan — we hold what moved and where it went, not an optimised sequence of stops. And the mobile capture that makes this work covers stock issues, returns, transfers and asset movements offline; counting and receiving a purchase order still need a connection, so a full stock count on the vehicle is a connected activity.
Does it handle fleet maintenance — servicing, parts, workshop?
No. And this page has to be blunt about it because an earlier version of our material implied otherwise: there is no service interval, no next-service date, no fuel log and no distance anywhere in the product. What exists is a register of vehicles with a named custodian, condition recorded at each hand-off, movement history and documents attached — custody, not maintenance. This is a boundary rather than a backlog. Fleet maintenance is a genuine product category with vendors who do nothing else, and a thin version inside an operations system is actively harmful: somebody retires the spreadsheet that was working, and three months later a service is missed by a system nobody realised was not scheduling anything. Buy it from a fleet vendor. Use us for custody, for the cost of the fleet attributed to depots and routes, and for the movement record underneath.
Our depots upcountry have poor connectivity. What actually works offline?
Four operations, named rather than described as "mobile support": issuing and returning stock, transfers between locations, inventory check-out and check-in, and asset movements. Those work with no signal at a depot or on a round and sync once on return without creating a duplicate. Three things do not: receiving a purchase order, counting, and dispatch each need a connection. That is worth testing against your actual week rather than accepting, because if your binding constraint is counting at a depot with no coverage then we are the wrong purchase and it is far cheaper to establish that now than in month three. Broadening the offline set is ordinary work on the roadmap and commissionable with a written specification, a timeline and a price — but the four are what runs today, and the list is deliberately specific so you can check it.
Bring your Tanzanian operation to a demo
One depot, one route, one program — governed end to end, with straight answers on localization.