Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For Egypt
We do not integrate with the Egyptian Tax Authority, our interface is in English, and Egyptian statutory payroll is not ours. What we do run is everything underneath: stock that is true continuously, procurement that refuses, route and cash custody, and imported cost measured at the rate that actually applied.
Where the stock actually is
Warehouse software is built around a building, and an Egyptian distributor's inventory largely is not in one. It is on a route, in a rep's hands, sitting at a customer who has not paid for it yet, or on a truck between two of your own places. Read the middle column. Where a system has no word for a position, that stock does not stop existing — it becomes an adjustment at month end, which is the same thing as saying nobody knows.
TypicallyA real position. This is the one every system models properly.
HereA location with its own position, blind counts and valued variance.
TypicallyUsually real, sometimes a sub-total of the national figure rather than a position that can disagree with it.
HereEach branch holds its own position and is allowed to disagree with head office, which is the only way a disagreement gets found.
TypicallyRarely modelled. The load is deducted at load-out and reappears as sales, and in between it is nobody's.
HereThe load is a movement to a location that happens to move, with one owner. Sales come off it during the round and the close is a variance by route and by person.
TypicallyUsually not a state at all. Confirmed on despatch, so it is counted at the destination days before it arrives.
HereIn transit is a real position. Transfers confirm on arrival, so the days on the road are visible instead of being a discrepancy somebody explains later.
TypicallyAlmost never. It has usually left your inventory entirely, which makes it invisible until it is written off.
HereStock held at a location you do not own is still a position with a custodian, so it is countable, agable and recoverable rather than gone.
Three of five, and the three are exactly the ones an Egyptian distribution business lives in. The test to take into any demo on this market is not "can you show me stock" — it is "show me the stock that is on a van right now, and tell me whose it is." If the answer involves an adjustment, a spreadsheet or the words "at the end of the day", you have your answer about the other four rows too.
Operations in Egypt
The three refusals are in the hero and they are real. What is left is the layer an Egyptian distributor actually spends the day in, and its defining feature is that a large share of the inventory is not in a building. It is on a route, in a rep's hands, being sold and collected against all day, and the systems most organizations run only acquire an opinion about it at the evening reconciliation — by which point a variance is an argument rather than a record.
Stock transfers
A van load as a position with an owner
The load-out is a movement to a location that happens to move, sales come off it during the round, and the close is a variance by route and by person rather than a discussion. One owner per stock position, including the positions with wheels.
POS reconciliation
Cash custody closed at the shift, not at the month
Shift reconciliation with takings, variance and stock movement on one record, against the same inventory the back office is counting. Where cash and goods change hands together, the shift close is where the shrinkage argument is either settled or postponed.
Inventory
Stock that is true continuously rather than at month end
Each warehouse, branch and van holds its own position, transfers confirm on arrival, counts are blind and adjustments carry a reason and a person. A figure that is only correct on the last day of the month is a figure you cannot buy against.
Procurement
Approvals that refuse
Requisition, threshold, RFQ comparison, purchase order, three-way match — with the threshold blocking the transaction instead of logging a caution. The audit file is a by-product rather than a project.
Landed cost
Imported cost at the rate that actually applied
Duty, clearing, port charges and inland transport attach to the consignment as their invoices arrive, and the foreign-currency purchase keeps both amounts and the genuine rate rather than a stale assumption.
Assets
Named custody on everything that leaves a building
Custodian, location, condition at each hand-off, movement history and documents attached — the record that answers who had it, which an ownership register does not.
One genuinely useful thing that is built and easy to miss: the working week is configurable per organization. Ticking Friday and Saturday makes leave arithmetic, the attendance present-rate average, workflow due dates and escalation all follow the Egyptian week, and public holidays are configured separately. Ageing buckets stay on calendar days, as is conventional.
Recognisable, we hope
Goods priced at the rate assumed when the order was placed, paid weeks later at a different one, with duty and clearing arriving later still. The margin looks fine and was gone before the first sale.
Loaded in the morning, cashed up at night, and forty drops in between that nobody recorded — so a shortfall has forty explanations and no evidence.
A compliance product and an operations product with no written boundary between them is the most reliable way to end up trusting neither.
The quote, the approval, the delivery note and the invoice all exist — in four places, held by three people, retrievable only by whoever remembers.
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 Arabic we would show you a customer-facing document before you signed anything. Kenya is the evidence that this is real: its eTIMS transmission and its statutory payroll engine were both built exactly this way. The honest caveat is that a vendor already shipping the language starts where we would be finishing.
The order of this page is deliberate. The three things we cannot do are in the first sentence rather than in the last answer, because in Egypt any one of them can be decisive and a reader who has to hunt for them has been treated badly.
How this starts
Establish your ETA obligation with the authority or your adviser and choose whatever satisfies it. Every other decision here is downstream of that answer.
Customers, items, prices, stock, invoice numbering — one owner each, agreed before go-live and visible to both vendors. This is the step that decides whether two systems is stable or painful.
Your sites, your routes, your imports and your approval chains, on your data, with training for the people who key transactions rather than the people who read reports.
Read before you shortlist
In Egypt "is it localized?" has five different answers depending on which layer you mean — language, currency, tax rate, e-invoicing, working week. A layer-by-layer buyer's guide, including the one where we tell you to look elsewhere.
Egypt's electronic invoicing regime is not an optional integration you can defer — and we do not provide it. What that actually means, how the split works in practice, and what to demand from whoever does provide it.
A city of twenty-odd million where a delivery van covers a fraction of the ground it would anywhere else, and the working week ends on a different day. Density, custody and the routing of stock through a megacity.
Questions we are asked in Cairo
No, and we would rather lead with that than have you find it in month three. There is no connection to the Egyptian Tax Authority of any kind — nothing is structured, submitted, registered or retrieved, and no e-receipt is produced. Our only fiscal e-invoicing integration is Kenya's eTIMS and it is Kenya-only. Where an Egyptian obligation applies to you, a separate compliant solution handles it and AWRA runs the operations layer alongside it. Confirm the scope and timing of your own obligation with the ETA or your tax adviser. That is on the roadmap rather than a boundary, and it is commissionable now. The ETA interface is published and clearance-based, which makes it a defined engineering job rather than an open question. 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. If this is the thing standing between you and a decision, say so and we will come back with a written specification, a timeline and a price before you commit to anything. What we will not do is print a date nobody has paid for.
No. The interface is English only, there is no right-to-left layout, and documents such as invoices and purchase orders are produced in English. This is a genuine limitation rather than a setting, and for organizations whose warehouse, route or branch staff work in Arabic it is likely to be disqualifying — in which case an Egyptian vendor is the better purchase and we will say so. For organizations whose back office works in English it is usually a non-issue. Test it with the person who will actually key transactions. That is on the roadmap rather than a boundary, and it is commissionable now. Arabic is not a translation job — it is mirrored layout, numeral formatting and column order — so we would scope and price it as engineering and show you a customer-facing document before you signed anything. 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.
The pound and an Egypt VAT rate ship as built-in presets, and every sales and purchase line separates net, tax and gross at the point of capture. Foreign-currency purchases record the rate actually applied to that transaction rather than a standing rate, and landed cost folds duty, freight, clearing and inland transport into true unit cost. We ship one maintained VAT preset rather than a maintained rate history; additional tax lines are configurable but yours to keep current. Confirm all rates and treatment with the ETA or your adviser.
Our maintained statutory payroll engine covers Kenya only. Egyptian income tax withholding and social insurance are not calculated, no statutory output is produced, and nothing is submitted or remitted on your behalf. We recommend an Egyptian payroll specialist for that layer, with AWRA holding employee records, attendance, leave and payroll cost allocation to projects and cost centres.
Once you set it. Non-working days are configured per organization, so ticking Friday and Saturday makes leave-day arithmetic and the attendance present-rate average follow the Egyptian week. Public holidays are configured separately, and workflow due dates and escalation read the same week and the same holidays, so an approval deadline will not land on your weekend. Support SLA targets can be set to count working hours per ticket category, so a commitment worded in working hours is measured that way. Ageing buckets stay on calendar days, as is conventional.
When your fiscal obligation is already handled by a compliance product or a local specialist, your back office works comfortably in English, and your real problem is operational — stock across sites, route and cash custody, procurement governance, imported cost, assets, or project and donor attribution. That is a real and reasonably common shape, particularly for importers, distributors, international organizations and group subsidiaries. Outside it, buy locally.
Nairobi, with remote onboarding and live training in English. Cairo is one hour behind us, so your working day overlaps ours almost entirely.
Tell us your fiscal arrangement and your working language. In one call we can usually say whether the operations layer is worth discussing or whether you should buy from an Egyptian vendor.