The things people ask before they trust us.

A subscription in birr, with four plans, paid monthly or once a year — a year costs eight months' price. What separates them is how many locations and staff seats you get, not a feature list. Every price is published on the pricing page, and you choose your plan once your account is created, 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. Two capabilities vary by plan: Payroll & HR and API access. Neither is on the entry plan, and everything else is on all four.

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 industry 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.