How Ethiopian businesses sell without losing track.
Stock, sales, credit, cash and staff in one system — one that keeps working when the internet doesn't. Built in Addis Ababa for how business is actually run here.
Works offline · Six languages · Ethiopian numbers
Product screenshot — placeholder
The real dashboard goes here once the first module ships.
One system, not seven.
Everything a business already tracks — in notebooks, phones, spreadsheets and somebody's memory — kept in one place that agrees with itself.
The problem
Your business is running in six places at once.
The sales are in a notebook. The stock is in someone's head. What customers owe you is on a phone. Payroll is on paper. Ask what today's profit was and nobody can answer without an hour of adding up — and by then it is yesterday's answer.
Scattered across six places
- Sales in a notebook
- Stock in someone's head
- Credit on a phone
- Payroll on paper
- Cash in a drawer
- Expenses nowhere
Wired into one system
One system. One version of the truth.
Every sale, purchase, payment and adjustment lands in the same place, once. Ask what you made today and the answer is already there — the same answer on every device, at every location, whether the connection held or not.
How it holds together
Five things that stop being your problem.
Not features on a list. These are the specific ways a business loses money it already earned.
Sell fast, and count it correctly.
Cash, Telebirr, bank, credit, or any split of them. VAT applies itself. Whether a sale is Paid, Credit or Partially Paid is worked out from what was actually collected — never chosen by the person at the counter.
Stock that reconciles instead of drifting.
Every sale, purchase, transfer and adjustment is its own record, and the quantity on hand is the sum of them. Nobody overwrites a number, so nobody has to work out afterwards who was right.
Know exactly who owes you what.
Credit is a payment method, not an afterthought. Every credit sale carries a real customer and a due date, and what is still owed to you stays separate from what is actually in the drawer.
Pay your people without a spreadsheet.
Staff, attendance, leave and payroll sit in the same system as the money they are paid from — with permissions deciding who can see a cost price and who cannot.
Close the day with something you can defend.
Every action is logged as it happens, and the log cannot be edited by anyone — not staff, not the owner, not someone reaching the database directly. A correction is a new line that supersedes the old one, never a rewrite of it.
Business types
Four categories. One backbone.
Amod is not four products. It is one system with a configuration layer on top — so a pharmacy gets expiry dates and a parts shop gets part numbers, without either one becoming a different piece of software.
- Building now
Trade
Buy it, sell it, keep the margin.
Auto spare parts · Pharmacy · General trading · Stationery · Cosmetics · Clothing · Mobile shops · Building materials
Services
Booked by appointment, not sold off a shelf.
Salons · Garages · Clinics
Manufacturing
Make it, then account for what it cost to make.
Bakeries · Small clothing production
Enterprise
Larger businesses, handled individually rather than through a standard module.
Custom requirements · Negotiated with our team
For developers
Your data does not stop at our screens.
Amod offers API access, so the systems around your business can read and write the same records your staff work with — a website showing live stock, a booking page creating real appointments, a reporting tool pulling its own numbers. No exports, no overnight file, no second version of the truth.
One record, everywhere
Anything written through the API goes through the same rules the app does — the same validation, the same isolation, the same audit line. There is no back door that skips them.
Scoped to one business by construction
Access is bound to a single business, and that boundary is enforced by the database itself rather than by a check somewhere in application code.
Built for the same conditions
Written against a system designed to reconcile cleanly after a device has been offline for a day — a harder problem than most APIs are built to survive.
API access is available on the Growth and Elite plans. It is not part of Core.
Endpoint documentation is issued to customers on those plans rather than printed here — an interface published on a marketing page is a version that goes out of date the day it changes.
Ask about API accessWhere we actually are
What we can tell you honestly.
Amod is pre-launch. These are real, checkable numbers — not projections, and not a customer count we have not earned yet.
6
Languages, complete
English, Amharic, Afaan Oromo, Tigrinya, Somali and Arabic — each written for business software, not run through a translator.
4
Business categories
Trade, Services, Manufacturing and Enterprise, each built on one shared backbone rather than four codebases.
13
Business types mapped
From auto spare parts and pharmacies to salons, garages, clinics and bakeries.
100%
Of actions work offline
Every action, on every page, on every plan. There is no allowlist and no page-by-page exception list.
Ethiopia first
Built for where the connection drops.
Amod was designed around Ethiopian conditions rather than adapted to them afterwards: unstable connections, staff who are not developers, and a working day that cannot stop because a line went down.
- Addis Ababa
- Adama
- Bahir Dar
- Hawassa
- Mekelle
- Dire Dawa
- Jimma
- Gondar
- Jigjiga
Ethiopian mobile numbers, Ethiopian birr, VAT at 15%. Savana operates from Addis Ababa and Dubai.
Why Amod
Running a business is hard enough.
No training week. No consultant. No server in the back room. It opens on the phone your cashier already has, in the language they actually speak, and it keeps working when the line goes down.
Questions
The things people ask before they trust us.
A monthly subscription in birr, with four plans. What separates them is how many locations and staff seats you get — not a feature list. You see the exact price for your plan when you choose your business type at sign-up, before entering any payment detail.
Locations and staff. A location is anywhere stock sits or a sale happens — a shop, a store room, or both at once — and every plan counts them the same way, with transfers between them never restricted. The one capability that varies by plan is Payroll & HR, which is not on the entry plan.
Four categories. Trade, for anyone who buys and sells — auto spare parts, pharmacies, general trading, stationery, cosmetics, clothing, mobile shops, building materials. Services, for appointment-led work like salons, garages and clinics. Manufacturing, for small production from bakeries to small clothing lines. Enterprise, for larger businesses handled individually.
Auto Spare Parts is the first module being built, with General Trading and Pharmacy directly behind it. The rest are mapped onto the same shared backbone, so the order they arrive in is a scheduling question rather than a rebuild. If your business type is not live yet, ask us and you will get a straight answer about where it sits.
Nothing. Every action on every page works with no connection — recording a sale, receiving stock, taking a payment, deleting a record. It saves on the device immediately and syncs by itself the moment the line returns. There is no offline mode to switch on and no button anybody has to press.
Usually there is nothing to resolve — separate events simply both apply. Two situations genuinely conflict: two devices selling the last of the same item, and two devices taking payment against the same debt. Both are flagged on your dashboard, you choose which one stands, and the other is reversed automatically through its proper correction path — a return, or a reversing payment. Never a silent overwrite.
You, and whoever you give access to. The separation between one business and another is enforced by the database itself rather than by a check in application code — which matters, because an application check is the thing a bug gets around. Inside your business, staff permissions decide what each person sees, including whether they see cost prices at all.
The activity and audit logs cannot be updated or deleted by anyone — not staff, not the owner, not someone reaching the database directly — and that is enforced by database permissions rather than by our code. A correction is a new entry that supersedes the old one. Sales and purchases work the same way: never deleted, only reversed by a return.
An Ethiopian mobile number and a phone. You confirm the number with a one-time code sent by SMS or Telegram, choose a 4-digit PIN, and that PIN is how you sign in from then on. No email address, and no password to forget.
The account takes minutes. Getting your real stock in takes as long as counting it: you enter what you have and what it cost, and Amod calculates your opening value rather than asking you to type a figure. That is a one-time entry — once you are live, corrections happen through normal transactions, never by editing history.
No. It runs in a browser and installs onto a phone's home screen like an app, with no server to buy and nothing to maintain. Each person picks their own language independently, so a cashier can work in Afaan Oromo while the owner reads reports in Amharic — same business, same data.
Contact us
Talk to a person who works on it.
Whether Amod fits your business, which plan you would need, when your business type goes live — ask, and you will get a straight answer rather than a sales sequence.
The chat window opens in the corner of this page.
Stop running your business from six places.
Choose your business type, confirm your number, and see your own numbers in one system.
Choose your business typeEthiopian mobile numbers · Works offline from the first day