Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For Côte d'Ivoire
Abidjan carries the heaviest multi-site operations in the franc zone — plants, depots upcountry, corridors to landlocked neighbours and export customers who audit you. That is the layer we are built for. Statutory accounts and CNPS payroll stay local, and we say so before you ask.
The same claims, two conditions
Every operations system looks competent at head office, where the people are trained, the connection holds and somebody senior is watching. The Ivorian test is what survives at the far end, where the storekeeper was hired to run a store rather than keep books. Below is the same set of claims put through both. Read the last row first; it is the one that fails.
claims that survive the depot.
that does not, and it is ours to own rather than explain away.
Head officeTrivially. Trained staff, good connection, daily oversight.
The depotHolds. Blind counts and issues that carry a reason and a person do not require an accountant to operate — they require a form that is shorter than the alternative.
Head officeRarely tested. Everyone at head office is senior.
The depotHolds, and this is where it matters. Roles restrict a site user to movements without reaching pricing, other sites or approvals — which is what makes a simple interface safe rather than dangerous.
Head officeLooks fine either way, because head office sees the totals.
The depotHolds. Transfers confirm on arrival, so a corridor load to a landlocked neighbour is a position rather than a hole in someone's count.
Head officeHolds — the records are all here.
The depotHolds, provided the depot recorded the despatch. Which is the same as saying it holds if the offline capture works, and that is the next row.
Head officeNever tested. The connection is fine in Abidjan.
The depotHolds, and it is the row the other five depend on. Stock transfers, inventory check-out and check-in, and asset movements captured with no signal on mobile and synced on return.
Head officeHolds. Your Abidjan team works in English comfortably enough.
The depotFails. The interface is English only, with no French, and documents print in English. A storekeeper who reads French and not English cannot operate this well, and no amount of training makes that untrue.
Five and one, and the one is ours to own rather than to explain away. A French interface is scoped, priceable engineering rather than a setting, and an Abidjan vendor already shipping it starts where we would be finishing — so if that row is your first requirement rather than your third, buying locally is the rational move and we would rather write it here than spend your third month proving it. If it is survivable at your sites, then scope the pilot at your worst depot rather than your best one: it holds there or it holds nowhere, and you will find out for the price of one site instead of a rollout.
Operations in Côte d'Ivoire
Every operations system looks competent in Abidjan. The Ivorian question is what it does at the far end of the operation, where the storekeeper is not an accountant, the connectivity is intermittent, the stock is worth real money and nobody senior is watching. A system that requires care and attention to stay accurate will be accurate at head office and fictional at the depot, and the gap between those two is where the loss is.
Inventory
Plant-to-depot stock as separate positions
Every plant, depot and corridor holds its own position, transfers confirm on arrival, and goods on the road to a landlocked neighbour are a state rather than a hole in the count. A national total that averages four incomparable positions is not a management number.
Access control
Depot staff who can only reach what they should
Roles restrict what a user at a site can see and do, so the storekeeper records movements without being able to reach pricing, other sites or the approvals above them. At the far end of an operation this is what makes a simple interface safe rather than dangerous.
Inventory adjustments
Counts and issues that a non-accountant can do correctly
Blind counts, issues carrying a reason and a person, valued variance calculated for whoever reviews it. The discipline has to survive being operated by somebody who was hired to run a store, not to keep books.
Inventory
Traceability forward to the customers who audit you
From an input lot forward to every customer that received it, and back from a complaint to the batch. Ivorian exporters are audited by their buyers, and this is the question those audits open with.
Landed cost
The corridor leg costed onto the goods it moved
Port charges, duty, clearing and the road freight to Ouagadougou or Bamako attach to the consignment as their invoices arrive, weeks after the goods, with the unit cost moving each time.
Offline operations
A depot that keeps working when the network does not
Stock transfers, inventory check-out and check-in, and asset movements captured with no signal on mobile and synced on return. This is the single card that decides whether the rest of this list is real at the far end of your operation.
The invitation in the heading is meant literally. Scope the pilot at your worst depot rather than your best one. If it holds there it holds everywhere, and if it does not you will have found that out for the price of one site instead of a whole rollout — which is also the fastest way to find out whether the English-only interface is survivable for the people who will actually use it.
Recognisable, we hope
You can show which inputs went into a finished batch. You cannot say which customers received a given input lot — and that is the question a customer audit actually asks.
Bouaké and Korhogo have intermittent connectivity, no permanent finance staff and a strong incentive to keep goods moving. Software chosen at head office fails there quietly.
Between dispatch and receipt on a corridor, goods are either overstated at origin or exist nowhere at all — so a loss in transit surfaces as a difference at month end rather than as an event with a carrier attached.
A French-language local suite against an English-language international platform is a decision about who does what, in which language, and who is accountable. Treating it as a feature grid is how buyers end up at the wrong end of the axis.
Running in the product today
Absences — on the roadmap, and commissionable now
What we would decline, and would rather say now
The middle column is absences rather than positions, and each is commissionable now on a written specification, a timeline and a price agreed before any money moves — and for French we would put a customer-facing document in front of you before you signed anything. Kenya is the evidence that this is real: its eTIMS transmission and its maintained statutory payroll engine were both built exactly this way, because clients needed them and commissioned them.
Judge all three columns at the depot. Head office will make the left column look good and will hide whether the middle one matters, and the whole argument of this page is that the far end of the operation is the only honest test of an operations system.
How this starts
Fully local suite, or local statutory and payroll with international operations. Both are coherent. Drifting toward one international platform for everything is where this goes wrong.
The site with the worst connection and the least-trained staff. Ask someone who works there to receive a delivery unaided. Fifteen minutes there beats any amount of head-office discussion.
What your expert-comptable receives and when, and which payroll provider does the statutory computation. One page, before go-live, and the arrangement runs itself.
Read before you shortlist
Abidjan runs more multi-site industry than anywhere else in the CFA franc zone, and the shortlist is usually a French-language incumbent against an English-language platform. What that trade actually costs, priced honestly.
Bamako is three days from Dakar and the truck is not a rounding error. Corridor distribution, border custody, and why the in-transit window is the number your stock report quietly refuses to show you.
A numbered, nine-class chart of accounts is not a preference in OHADA countries — it is the law. Our ledger has no account numbers at all. Here is why that is the right design, and exactly how the handoff should work.
Operations registers the truck once. Your expert-comptable registers it as four things with four different lives, because under the harmonised plan you do not choose your asset classes and a significant machine is not one depreciable object. The two documents agree on the total and disagree on how many things exist — and nothing tells you, ever.
Six markets, one currency, and three purchases that get bundled into one conversation. Two of the three are better bought locally, and one of them should be bought before us.
Goods in transit are on your balance sheet and in nobody's stock count. Most systems model a location you operate, so a consignment sitting in a foreign port for eleven days becomes a purchase order — which is a document, not an asset.
Questions we are asked in Abidjan
No. Our chart of accounts has no account-number field at all, so a numbered SYSCOHADA plan cannot be represented and a statutory presentation cannot be produced. This is a deliberate design decision rather than an unbuilt feature — maintaining a statutory plan across seventeen member states is an ongoing professional commitment, not a feature, and it is already well served locally. Your statutory books belong with a local accounting package or your expert-comptable, working from the operational records we hold. Confirm your obligations with them or the DGI. This one is a boundary rather than a backlog — it does not change with a commissioned build, and deliberately so. A numbered SYSCOHADA presentation is prescribed by law and belongs to your expert-comptable, who signs it. We hold the operational detail underneath it, which is the part that cannot be reconstructed a year later.
No. English only, with no translation files in the product and no setting to enable one. All printed output — invoices, delivery notes, purchase orders, credit notes, receipts — is in English. Your data can be entirely in French, since item names, locations, customers, suppliers, projects and notes are free text we do not alter, but the frame around it is English. Test this at your least-trained site rather than at head office; it is the fastest way to a real answer. That is on the roadmap rather than a boundary, and it is commissionable now. French interface text and document templates is scoped, priceable work. Kenya's eTIMS transmission and its maintained statutory payroll engine both exist because Kenyan clients needed them and commissioned them — neither arrived on a roadmap by itself. The honest caveat: a vendor already shipping the language starts where we would be finishing, so if it is your first requirement rather than your third, buying locally is the rational move and we would rather write that sentence than lose your third month to it.
Yes, provided the discipline is in place: lot identity created at receipt, consumption recorded against the production job at the time rather than reconstructed later, finished output carrying its own batch linked to its inputs, and the batch carried through dispatch. Forward trace is the harder direction and the one customer audits actually test. Bring a real lot to the demo and time us. We are not a quality management system and not a manufacturing execution system.
That is the right question to press every vendor on, including us, and it should be tested at the depot rather than in a demo room. What matters is whether a depot user can be given genuinely restricted access, what happens mid-capture when a connection drops, whether receipts can be entered as counts rather than as confirmations of a dispatch note, and whether a photo can be attached at the tailgate. Judge the system on the worst site you run.
Yes, both as built-in presets. The CFA franc is resolved automatically as the base currency and everything is stored, invoiced and printed in it, with no exchange rate anywhere inside the monetary union. An Ivorian value added tax rate ships as a maintained preset with net, tax and gross separated line by line on purchases as well as sales. Additional lines are configurable with their own rates and effective dates but are yours to maintain. Confirm current rates with the DGI or your adviser.
Not as turnkey statutory payroll. CNPS, the income tax scale and sector collective agreements are not maintained calculations in our product — Kenya is our only market where that is true. Employee records, contracts, leave with balances, attendance and posting payroll cost into projects and cost centres all work. The statutory computation and declarations belong with an Ivorian payroll provider or your expert-comptable, and we would rather lose that line item than have someone calculating contributions from a formula nobody has revisited since implementation.
When your operation is domestic, works entirely in French, and your complexity sits in accounting and payroll rather than in stock, procurement and multi-site operations. A good Ivorian or regional suite then gives you one accountable vendor, French documentation and support in your language, and the split we recommend would add coordination cost for no operational gain. We reach this conclusion on first calls regularly and prefer to reach it quickly.
Not the head office — the depot upcountry with the bad connection and no finance staff, and one real input lot to trace forward. That is the honest test.