Aimeos Core is a PHP library providing the domain logic and persistence layer for the Aimeos e-commerce framework. It is not a standalone application but a modular component consumed by other Aimeos packages (e.g., Laravel adapter, admin UI). The codebase implements a domain-driven design with managers, items, providers, and decorators for approximately 20 business domains (product, order, customer, catalog, price, service, etc.). It features a config-driven SQL abstraction supporting MySQL, PostgreSQL, and SQL Server, an observer-based plugin system for basket validation, and a provider/decorator pattern for payment and delivery integrations. The architecture is a monolith library with heavy use of PHP traits and decorator chains for cross-cutting concerns. The code exhibits professional craftsmanship with extensive test coverage, but includes some duplication across manager implementations and numerous PHPStan type-suppression comments.
This is a Laravel service provider package that integrates the full-featured Aimeos e-commerce system into Laravel applications. It provides route definitions (admin backend via JQAdm, GraphQL API, JSON REST API, MCP bridge, frontend catalog/checkout/account pages), controllers that delegate to Aimeos HTML/JSONAPI clients, CLI commands for setup, account management, job execution, and cache clearing, and a set of service container bindings (aimeos.shop, aimeos.context, aimeos.config, etc.) that wire Laravel's session, mail, filesystem, and database managers into Aimeos' context. The architecture is that of a thin integration layer: the actual e-commerce logic (products, orders, customers, pricing, basket, checkout, shipping, payments, subscriptions, SEO, multi-vendor, multi-warehouse) lives in the separate aimeos-core and ai-* packages. This package handles Laravel-specific concerns like routing, authentication, configuration merging, and view rendering. It also includes a MCP (Model Context Protocol) bridge that exposes Aimeos admin tools through Laravel's optional MCP SDK, a resolver controller for URL-based content routing (catalog categories, products, CMS pages), and a set of facades for frontend controllers. The code is well-structured, follows PSR-4, uses scoped service bindings, and has comprehensive test coverage.