Ship ecommerce stores in days, not weeks.

Stop rebuilding checkout on every client project. The Merchant Engine gives you checkout, inventory, payments, an admin dashboard, and a ready-to-brand storefront out of the box. Launch with the included storefront, or build your own on top of the API.

Get early access See how it works

Built by a dev who shipped this 10+ times by hand. Now you don't have to.

~/new-client-store
# the old way: rebuild the backend from scratch, again
$ build checkout # ~3 days
$ wire up payments # again
$ set up inventory # again
$ build admin dashboard # every. single. time.

# the Merchant Engine way
$ plug in The Merchant Engine
✓ checkout + payments flow ready
✓ inventory management built in
✓ admin dashboard live
✓ storefront live · English + Arabic
→ now go make it yours.

This is the admin your client gets on day one.

Orders, catalog, customers, analytics, and activity in one dashboard. Not a mockup. Real screenshots of the admin that ships with the engine.

the-merchant-engine · admin · dashboard
The Merchant Engine admin dashboard: orders and revenue KPI cards with sparklines, a recent activity feed, and quick actions, in a dark interface.

Everything at a glance. Orders and revenue with trend sparklines, a live activity feed from the audit log, and quick actions like new product, gift cards, and the review queue.

admin · orders
The Merchant Engine admin orders screen: order list with totals, status badges, payment states, CSV export, and status filters.

Orders under control. Statuses, payment states, filters, and CSV export. Every order flows through checkout, stock, and payment logic underneath.

admin · analytics
The Merchant Engine admin analytics screen: revenue, orders, sessions and conversion tiles plus reports for funnel, product performance, customers, search, and tracking pixels.

Analytics built in. Revenue, conversion, funnel drop-off, product performance, and tracking pixels. No third-party dashboard needed on day one.

Included

It comes with a storefront, too.

You don't start from a blank page. The engine ships with a full server-rendered storefront: home, catalog, search, cart, checkout, and customer accounts. Bilingual English and Arabic with full RTL, SEO-ready out of the box. The screenshots below aren't a staged demo: they're Al Khaleej Store, a happy client running this exact storefront in production, taking real orders today.

al-khaleej.store · live · home
Al Khaleej Store home page, built on The Merchant Engine: honey hero banner, product search bar, Arabic language switcher, and category grid.

A real store, not a demo. Captured live from al-khaleej.store. Hero sections, banners, and featured rails are all content the store owner manages from the admin, no deploy needed.

al-khaleej.store · popular + trust bar
Al Khaleej Store popular-products rail with real product photos and prices, plus a trust bar: 24-48h delivery, easy returns, Arabic and English support.

Merchandising from the admin. Popular rails, trust badges, and promo banners, with delivery promises and support in both languages.

al-khaleej.store · product page
Al Khaleej Store product page for a honey product: image gallery, price, live stock status, delivery estimate, add-to-cart button, and rich description.

Product pages that convert. Gallery, live stock status, delivery estimates, wishlist, and add to cart. Wired to real inventory underneath.

Same backend. Different client. Every time.

If you build ecommerce stores for clients, you already know this loop. It's not the interesting work. It's the plumbing you rebuild before you can build anything that matters.

01
Build the checkout
02
Set up inventory
03
Integrate payments
04
Wire up the admin

After the 10th store, one question gets loud: why am I rebuilding the same backend from scratch on every project?

Build the checkout3 days
Wire up payments + webhooks1 day
Set up inventory1 day
Build the admin dashboard2 days
Refunds, taxes, edge cases∞ days
= a week gonebefore you build anything

Every store. Every client. The Merchant Engine gives you that week back.

Plug in. Get the infrastructure. Build on top.

The Merchant Engine isn't a template you build around. It's a backend you build on.

STEP 1

Plug it in

Drop The Merchant Engine into your project. Checkout, payments, inventory, and admin come wired together, not as four separate integrations you stitch by hand.

STEP 2

Make the storefront yours

Brand the included storefront and launch, or build a custom frontend on the same API. Either way, your hours go to the part clients actually see and pay for.

STEP 3

Hand off & manage

Your client gets an admin dashboard to run orders, products, and inventory from day one. You get your weekend back.

We built the backend so you don't have to.

READY

Checkout & orders

Cart, checkout, order lifecycle, refunds, and returns. Idempotent order creation, so a double-click never charges twice or oversells stock.

BUILT IN

Inventory management

Stock, products, and variants with atomic, race-safe decrements. No overselling when two buyers hit the last unit at once.

LIVE

Admin dashboard

Orders, catalog, customers, promotions, gift cards, reviews, returns, and analytics in one place. Ready to hand to the client on day one.

LIVE

Bilingual by design

Every product, category, and email exists in English and Arabic. The storefront flips to full RTL. One store, two languages, zero plugins.

BUILT IN

Marketing engine

Promotions, coupon campaigns, gift cards with race-safe balances, reviews, and wishlists. The levers a store owner actually asks for.

LIVE

SEO & GEO machinery

Server-side rendering, sitemaps, structured data, redirects, IndexNow pings, and a Google Search Console indexing dashboard inside the admin. Plus GEO for the AI era: auto-generated llms.txt and llms-full.txt, rebuilt from the live catalog so ChatGPT, Claude, and Perplexity can read the store.

LIVE

Transactional email

Order confirmations, notifications, and campaigns from bilingual templates the owner edits in the admin, with delivery receipts tracked per email.

BUILT IN

Security floor

Role-based access control, audit log on every admin action, bot protection on public forms, soft deletes, and a full request paper trail.

Wired to the services a real store runs on.

These aren't logos on a wishlist. Everything marked live is running in production on a real store today. Payment providers plug into a locked, server-side allowlist, so adding one is a code change, not a config hole.

Payments ✓ Live
Payments ✓ Live
Transactional email ✓ Live
Bot protection ✓ Live
SEO · Google ✓ Live
SEO · Bing ✓ Live
GEO · AI assistants ✓ Live
Media & assets ✓ Live
Rates & carriers ✓ Live
Card payments Coming soon
Card payments Coming soon

Card gateways are next on the roadmap: the provider framework, idempotent payment flow, and webhook dedup layer they plug into are already built. Need a specific provider? Ask, and it goes on the roadmap.

The story

After 10+ ecommerce stores built from scratch, I finally built the one I keep for myself.

Hey, I'm Badii 👋 I've built ecommerce for three years, for clients, for myself, and now as infrastructure for other devs. 10+ stores shipped from idea to live checkout. Built the #1 livestock marketplace in Saudi Arabia. Shipped Peeps to 85K+ installs. Every project started by rebuilding the same backend from scratch. That shouldn't be the job, so I'm fixing it in public.

10+
Stores shipped
85K+
Peeps installs
#1
Marketplace in KSA
FAQ

Got questions? Good.

Reach out to me on LinkedIn or by email. I answer every message myself.

Or find an answer in the FAQ below 👇

A typed, boring-on-purpose TypeScript stack: a NestJS + PostgreSQL + Redis API, an Angular admin dashboard, and a server-rendered Angular storefront. The API is a clean REST surface, so if you'd rather build the storefront in React, Vue, or anything else, nothing stops you. No lock-in to a proprietary page builder.
No. It's infrastructure you build on top of, not around. You keep full control of the storefront and your code, so you're never fighting a page builder to ship custom behavior for a client.
One is included. A server-rendered storefront with home, catalog, search, cart, checkout, and customer accounts ships with the engine, bilingual English and Arabic with full RTL, and it's already running a real store in production. Brand it and launch in days, or treat it as a reference and build your own frontend on the same API.
Sure, you can get a checkout working with AI in an afternoon. The demo is the easy part. The hard part is what comes after: race conditions on inventory, idempotent orders and payments, refunds and returns, webhook retries, access control, and security holes you won't spot until a store is live and taking real money. The Merchant Engine is that hard part, already built and running in production on real client work, so you're not one prompt away from overselling stock or leaking customer data.
You build on top of it, not around it. The storefront is yours end to end. The Merchant Engine is the infrastructure layer, so you're not fighting a template to get custom behavior for a client.
Yes, that's exactly the point. It's already running on real, paid client work. You ship stores faster and spend your billable hours on the parts clients actually see, instead of rebuilding the same backend every time.
Live today: cash on delivery, manual payment capture, and gift cards, running on an idempotent payment flow with webhook dedup. Next: Stripe and PayPal; the server-side provider framework they plug into is already built. Shipping is zone-based rate calculation with carrier and tracking management, which covers regional stores today; carrier API integrations land per demand. Need a specific provider? Ask, and it goes on the roadmap.
Honest answer: it's v1 and I'm not going to pretend otherwise. But it's in production on my own client projects, and it gets more solid every time a developer puts it under real load and breaks something. Early access means you help shape it.
Pricing is being finalized alongside early access. Get in now and you'll get founder pricing and direct input on the roadmap before it's locked. DM me and I'll walk you through where it stands.
I'm Badii, a full-stack dev with three years of ecommerce behind me: 10+ client stores shipped, the #1 livestock marketplace in Saudi Arabia, and Peeps at 85K+ installs. I built The Merchant Engine because I lived this exact pain, and I'm building it in public so you can watch every decision.
Early access

Save one dev from rebuilding checkout again.

The Merchant Engine is live in v1. If you build ecommerce stores for clients, get early access and stop rebuilding the same backend on every project.

Get early access

v1, and improving fast. Break it, send feedback, help shape it.