Aimeos

Last reviewed Aug 26, 2026 · 802 words

Aimeos is the right e-commerce choice for one kind of self-hoster: someone who already builds in Laravel, or runs TYPO3, and wants the shop to be part of that application rather than a second platform bolted onto it. For that person it is the fastest route from composer to a catalogue that stays quick at 100,000 products. For everyone else the honest advice is that you will spend more hours learning Laravel than running the store, and WooCommerce or a hosted cart will get you selling sooner.

It is a package, not a product

Most self-hosted shops are applications you install. Aimeos is a library you compose into one. There are two supported shapes: the Laravel distribution (composer create-project aimeos/aimeos myshop), which gives you a complete Laravel app with the shop wired in, or composer require aimeos/aimeos-laravel inside an application you already have. The TYPO3 extension is the same core packaged as a TYPO3 plugin. Either way you get an admin panel at /admin, a storefront at /shop, and a JSON:API for everything the storefront can do.

That framing explains the LGPL-3.0 licence. The core stays open; the extensions you write to customise it can stay private, which matters if you are building a shop for a client. It also explains the 8,692 GitHub stars spread across a project that has been shipping since 2015: this is a developer tool with a developer audience, and it has never tried to be anything else.

The performance claim is real, and it is mostly caching

The project's headline is that it handles millions of products, and the architecture backs it up. Every read goes through a manager with a criteria object that becomes a single well-indexed SQL query, rendered HTML fragments are cached and invalidated by tag, and the storefront ships with no ORM overhead in the hot path. On a 512 MB VPS with MariaDB and Redis, a catalogue of tens of thousands of items feels instant.

The caveat is that the speed comes from the cache, so an under-provisioned database or a shop that bulk-edits products every hour will feel much slower than the benchmarks suggest. Give MariaDB or PostgreSQL its own memory, point the cache at Redis rather than the database, and the claim holds.

Headless is where it shines

The strongest way to run Aimeos in 2026 is as a backend. The JSON:API under /jsonapi exposes the catalogue, basket, checkout and customer accounts, and there is a GraphQL API for admin operations. That lets you keep the shop inside your Laravel app while the customer-facing site is a Next.js or Nuxt build served from wherever you like. If you only ever used the bundled Bootstrap storefront you would be missing the point.

The documentation ends where your questions start

Aimeos's docs are fine for installation and for configuring the shipped features. They thin out sharply once you want to add a product type, change checkout steps, or write a custom payment provider. The pattern is that you generate an extension skeleton from the aimeos.org site, read the core source for the manager you want to override, and ask in the forum when stuck. This is what "requires PHP expertise" means in practice: you will read framework code, not just config files.

Payments go through service providers built on Omnipay, which covers PayPal, Stripe and a few dozen others, and shipping is rule-based rather than carrier-integrated. Compared with WooCommerce's thousands of plugins the ecosystem is small. Anything niche, you write.

How it compares with the other PHP shops

Sylius is the closest sibling: Symfony instead of Laravel, MIT instead of LGPL, a heavier 2 GB footprint, and a stronger enterprise story. If your team is Symfony people, pick Sylius; if they are Laravel people, pick Aimeos; do not make a Laravel team learn Symfony to run a shop. WooCommerce wins on plugins and on non-developer operators. For the full field, the e-commerce category covers the rest, and if you are coming off a hosted platform the Shopify alternatives page is the honest starting point.

What I'd do

If I already had a Laravel application and needed to sell from it, I would add aimeos/aimeos-laravel, put the admin behind my existing auth, run MariaDB and Redis alongside, and build the storefront headless against the JSON:API. Budget a week to learn the extension system before touching checkout. If I did not have a Laravel app, I would not start one to get a shop; WooCommerce for a small catalogue, Sylius for a serious one, and Aimeos only once a Laravel developer is on the team.