The Merchant Engine compared with WooCommerce
WooCommerce is the largest ecommerce ecosystem on the web and it is not going anywhere. It is also a plugin on a content management system, extended by buying more plugins. The Merchant Engine is a purpose-built commerce stack in TypeScript: one install, an API, an admin and a storefront, and the code is yours to change.
What WooCommerce does better
WooCommerce is GPLv3, free, thirteen years old, and has an extension marketplace nothing here can compare to. If you need an ecosystem, a hosting market and a hiring pool, WooCommerce wins outright.
Row by row
Every claim about WooCommerce was read from its own documentation on 2026-09-09 and carries the page it came from. Every claim about The Merchant Engine links the documentation page that proves it. If a row is wrong, it is a bug: write to bbadii@pm.me and it gets corrected.
| Criterion | WooCommerce | The Merchant Engine |
|---|---|---|
| What it is | A customizable ecommerce platform that runs as a WordPress plugin. “customizable ecommerce platform offers the freedom to sell and grow on your terms” Source: woocommerce.com | A self-hosted ecommerce platform: a REST API, an admin dashboard and a server-rendered storefront, installed together on your own server with one command. Read the page that proves it |
| Language and runtime | PHP, inside a WordPress install. “PHP version 8.3 or greater (tested up to PHP 8.4)” Source: woocommerce.com | TypeScript on Node. NestJS and Prisma for the API, Angular for the admin, Analog.js for the storefront. Read the page that proves it |
| API | A REST API in core, integrated with the WordPress REST API. GraphQL moved out of core into a separate plugin in version 11.2. “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API.” Source: developer.woocommerce.com | REST, one versioned surface under /v1, split by audience into a storefront and an admin OpenAPI document that are generated from the code, never hand-written. Read the page that proves it |
| Admin dashboard | The dashboard is the WordPress admin, with WooCommerce's own screens under a WooCommerce menu inside it. “The Set up payments task opens WooCommerce > Settings > Payments” Source: woocommerce.com | Included and installed with everything else. Angular, role-based permissions on every endpoint, light and dark, and one editing tab per locale on every text field. Read the page that proves it |
| Storefront | A WordPress theme. The official free one is called Storefront. “Storefront is an intuitive, flexible, and free theme offering deep integration with WooCommerce.” Source: woocommerce.com | Included and installed with everything else, server-rendered, and branded from the store configuration rather than forked: colours, fonts, logo, locales and money come from the database. Read the page that proves it |
| Install path | No single command. Install WordPress, add the plugin, activate it, then follow the setup wizard. “When WooCommerce is activated for the first time, the WooCommerce Setup Wizard appears automatically.” Source: woocommerce.com | One command. ./setup.sh asks for the store’s values, verifies each third-party integration live, builds the images, creates the database, issues the certificates and creates the owner account. Read the page that proves it |
| License | GPLv3 or later, free. The marketplace sells paid extensions and themes. “you can redistribute it and/or modify it under the terms of the GNU General Public License” Source: raw.githubusercontent.com | Source available: PolyForm Noncommercial 1.0.0, free for personal, educational, research and nonprofit stores. A store that takes money buys a yearly commercial license in one of four tiers. Read the page that proves it |
| Hosting model | Self-hosted, with recommended hosting partners. The vendor's own hosted offering was discontinued. “Woo Express is no longer available, but check out these other options for hosting your WooCommerce store.” Source: woocommerce.com | Self-hosted only. There is no vendor cloud, no hosted tier and nothing to sign up for; the install runs on your box and the licence check is an offline signed file. Read the page that proves it |
| Extension model | Plugins and themes, through WordPress actions and filters. “open-source ecommerce platform for WordPress” Source: wordpress.org | You own the checkout: it is a modular monolith you change in place, with a documented recipe per kind of change and the gates that keep the change honest. Read the page that proves it |
| Payment providers | Offline methods in core, with card providers such as Stripe and PayPal added as separate official extensions. “review payment providers available for your store country, install a provider, or enable offline payment methods” Source: woocommerce.com | Cash on delivery, manual bank transfer and gift cards ship and work. No card gateway ships in the first release; the payments module has the seams and a recipe for adding one. Read the page that proves it |
| Cash on delivery | Documented as part of the free core plugin, under the offline payment methods. “This documentation is about the free, core WooCommerce plugin” Source: woocommerce.com | Shipped. A payment method row the store owner switches on, published by the public checkout endpoint with its translated name, and snapshotted onto the order. Read the page that proves it |
| Content languages | The interface is translation-ready and translated into several languages. Serving a catalogue in more than one language is not covered there; the recognised route is the third-party WPML plugin. “WooCommerce is translated into several languages and is translation-ready out of the box.” Source: woocommerce.com | French, English and Arabic catalogues ship. A store enables the ones it serves and picks a default; every user-facing field holds one value per locale in one database. Read the page that proves it |
| Right to left | Right to left is not mentioned on WooCommerce's own localization page. WordPress itself has an RTL mechanism that themes inherit, which is where a WooCommerce store gets it from. Searched, not stated: woocommerce.com | The storefront mirrors: the store configuration names the RTL locales and the pages set dir and lang per locale. The admin edits Arabic in a right-to-left tab, but its own interface is English and is not mirrored. Read the page that proves it |
| Infrastructure | PHP, MySQL 8 or MariaDB 10.6, WordPress 6.9 or newer, on Apache or Nginx. “MySQL version 8.0 or greater, or MariaDB version 10.6 or greater” Source: woocommerce.com | PostgreSQL and Redis, in Docker, on one Linux box. The installer sets both up; a second box for the storefront is optional. Read the page that proves it |
| Maturity | On version 11, with more than seven million active installations. The plugin directory states no first-release date. “Active installations 7+ million” Source: wordpress.org | The youngest product on this page, and the page says so: the first public release is not tagged yet. What stands in for a version history is the gate set every push runs, published rather than described. Read the page that proves it |
Which one to pick
Pick WooCommerce when
- The store owner already runs WordPress and their content lives there.
- You need an extension for something unusual and want to buy it rather than write it.
- The budget cannot carry a licence, and GPLv3 with free core is the requirement.
- You want the largest hiring pool and the most tutorials for whoever maintains it next.
Pick The Merchant Engine when
- You are a developer building the same store repeatedly for clients and want one stack you install, not a plugin stack you assemble.
- The store sells in Arabic, French or English and you would rather not buy a translation plugin to do it.
- You want a typed REST API, a generated OpenAPI document and a storefront contract to build a custom frontend against.
- You want the checkout logic in a repository you own, not spread across plugins you did not write.
Questions
Is WooCommerce not good enough for a client store?
It is, for a great many stores. This page exists for the developer whose stores keep needing the same things WooCommerce needs plugins for: several languages with right to left, cash on delivery, an API-first storefront and one codebase per agency rather than per client.
Can I migrate a WooCommerce store to this?
There is no importer today. The catalogue, customers and orders would be moved through the admin API, and that is work. The honest answer is that this engine suits a new store better than a migration.
WooCommerce is free. Why pay a licence?
You pay when the store takes money, and one licence covers a number of live stores rather than one. Weigh that against the extensions a comparable WooCommerce build buys per store.
See it for yourself
The fastest check on any row above is to run the thing: install it locally in one command, or read what an install puts on a box. The other comparisons are on the compare index.
Last updated . Every claim on this page is read from a published source and cited beside it.