Building the connected commerce stack MENA retail has been waiting for.

When I started looking seriously at commerce infrastructure in MENA, the picture was familiar to anyone who has tried to run a store here. A retailer builds on one platform, adds a second for inventory, a third for POS, a fourth for payments, and by year two is paying five different vendors to do work that should belong to one system.

That's not a tooling problem. It's an economics problem. Every disconnected tool adds a tax — a fee, an integration, a support ticket, an hour of reconciliation. For a retailer running on tight margins in Beirut, Dubai, Riyadh, or Cairo, that tax is the difference between growth and grinding.

What the region actually needs

Axisel is built on a simple premise: the software that powers a retailer's online store, point of sale, inventory, orders, payments, and customers should live in one platform, speak one language, and charge one price.

Not because integration is hard (though it is). Because fragmented systems force retailers to make worse decisions. You can't run a real customer program when half your orders live in a plugin your accountant doesn't trust. You can't price intelligently when your cost data is in a spreadsheet your warehouse manager updates on Fridays.

Why now

MENA retail is at an inflection point. Consumer expectations have caught up with global standards. Logistics networks are maturing. Payment rails are finally workable. What's still missing is the unified operating layer — the thing that ties the storefront to the stockroom, the POS to the customer record, the shipping label to the refund.

We're building that layer. Not as a collection of features — as one platform, from the ground up, for this market.

How we're building

In public. Honest about what ships, what's still in progress, and what's on the roadmap. We'd rather earn trust slowly than overpromise and disappear. If you're running a store and want to follow along — or help shape what we build — we'd love to hear from you.