Aimeos Laravel is an MIT-licensed e-commerce package for PHP that adds a full-featured shop—catalog, basket, checkout, admin backend and APIs—to an existing Laravel application, and it is aimed at Laravel developers building online shops, multi-vendor marketplaces and complex B2B commerce applications.

What it is

Aimeos Laravel is a Laravel package that ships a complete e-commerce stack rather than a thin set of helpers. It is installed with Composer into an existing Laravel application, where it provides product and catalog management, a flexible basket rule system, order handling, an admin backend and a dashboard, and both a JSON REST API following jsonapi.org and a GraphQL API for administration. The codebase is described as completely modular, and the README states that anything can be adapted, extended, overwritten and customized to fit a project's needs.

The concrete problem it solves is the amount of undifferentiated work that every shop project otherwise repeats: payments, pricing rules, baskets, vouchers, translations, SEO markup, an administration interface and a transactional API. Aimeos Laravel replaces building that foundation by hand on top of Laravel, offering it as a reusable package that plugs into an application which already exists. It lives in the PHP and Laravel ecosystem, is distributed through Packagist as aimeos/aimeos-laravel, and sits alongside two sibling distributions from the same project—the Aimeos shop distribution for full applications and the Aimeos headless distribution for teams building their own single page or progressive web application frontend.

Key capabilities

• Multi-vendor, multi-channel and multi-warehouse operation, including support for multi-tenant e-commerce SaaS solutions with unlimited vendors.
• Catalogue scale from one item up to 1,000,000,000+ items, with response times the README cites as down to 20ms.
• Product types covering bundles, vouchers, virtual, configurable, custom and event products, plus subscriptions with recurring payments.
• 100+ payment gateways, block and tier pricing out of the box, discount and voucher support, and an extension for customer or group based prices.
• A flexible basket rule system for composing pricing, discounting and checkout logic.
• JSON REST API based on jsonapi.org and a GraphQL API for administration, alongside a full-featured admin backend and a configurable product data set.
• Full RTL support in frontend and backend, SEO optimization including rich snippets, translation into 30+ languages and AI-based text translation.

Who uses it and how

• Laravel teams adding commerce to an existing application rather than starting from a separate shop system, using the package directly inside their current codebase.
• Marketplace operators who need multi-vendor, multi-channel and multi-warehouse behaviour without assembling vendor, payout and catalogue logic themselves.
• SaaS builders running multi-tenant e-commerce for many vendors on one installation, which the README lists as an explicit target.
• B2B implementers who need customer or group based prices, block and tier pricing, and subscriptions with recurring payments.
• SPA and PWA teams who keep the Aimeos backend and APIs but write their own frontend, using the separate headless distribution rather than the bundled HTML frontend.

Getting started

Install with Composer as the aimeos/aimeos-laravel package inside an existing Laravel application; the README describes this as taking about five minutes. For a ready-made application or a first test, the Aimeos shop distribution provides a fully working online shop in under five minutes, and the Aimeos headless distribution serves single page or progressive web application builds.

How it compares

No list of paid products this project replaces was provided, so the comparison stays inside the family of tools the facts name. Aimeos Laravel is the package for teams that already have a Laravel application, while the Aimeos shop distribution is the full application recommended for new projects and quick trials, and the Aimeos headless distribution is the choice when the HTML frontend is not wanted and an SPA or PWA frontend will be built separately. All three share the same underlying commerce feature set, so the decision is about how much of the application already exists.

When to use it — and when not to

A self-hoster must operate a supported stack: Linux/Unix, WAMP/XAMP or macOS, PHP 8.1 or later, a web server such as Apache or Nginx, and a database chosen from MySQL 5.7.8+, MariaDB 10.2.2+, PostgreSQL 9.6+ or SQL Server 2019+, with Composer reporting any missing PHP extensions. Only the 2024.10 and later releases are fully supported, with the 2025.10+ LTS line covering Laravel 10.x, 11.x and 12.x, and major version upgrades require following the published upgrade guide. Anyone outside the PHP and Laravel ecosystem should look elsewhere, and teams wanting a no-code hosted store should note that this is a package to integrate and maintain, with setup detail living in the external documentation rather than in the repository README.