aimeos for TYPO3: E-Commerce & Online Shop

Running a shop inside TYPO3 is hard to beat when aimeos is part of the stack

Organizations that already operate a TYPO3 website and want to add e-commerce face a fundamental question: a separate shop system (Shopware, Magento, WooCommerce) with a CMS interface, or a native e-commerce framework within TYPO3? aimeos is the second option and has been the most established TYPO3 shop framework for over 10 years. More than 200,000 installations worldwide (as of Packagist, 2026), active development and support for TYPO3 v12 and v13 speak for stability.

The decisive advantage: content and commerce run in the same system. Product pages use TYPO3 content elements, landing pages can embed shop components, editors work in a single interface. With separate systems, synchronization problems arise - duplicate maintenance and inconsistent design.

Typical use cases

B2B shops with complex pricing logic. Industrial companies with customer-specific prices, volume discounts, minimum order quantities and approval workflows. aimeos natively supports customer group pricing, price plugins and rule engines. A chemical distributor with 8,000 items and 400 customer groups can be mapped without hardcoding every pricing rule.

Marketplaces and multi-vendor scenarios. aimeos can serve as a marketplace backend where multiple suppliers list their products. Each vendor manages their catalog, the platform handles checkout, payment and shipping routing. The framework supports multi-shop setups where different storefronts access the same catalog but display different assortments and prices.

Internationalization from day one. Companies with websites in 5+ languages and multiple currencies benefit from aimeos natively supporting multi-language and multi-currency. Product names, descriptions and SEO metadata can be maintained per language. Prices can be defined per currency or converted automatically.

Technical architecture

aimeos is built on its own MVC architecture (Manager, Controller, Client) that integrates into TYPO3 as an extension. The core is framework-agnostic and also runs under Laravel and Slim. The TYPO3 adapter layer ensures that aimeos plugins are embedded as TYPO3 content elements.

The product catalog uses a tree structure with arbitrarily deep nesting. Attributes (color, size, material) are managed as separate entities and delivered through faceted filters. The search function defaults to SQL full-text search but can be switched to Elasticsearch or Solr.

Payment integrations run through service providers: Stripe, PayPal, Mollie, Amazon Pay, Klarna and others are available as plugins. Every payment provider is addressed through a unified API. The checkout process is implemented as a step pipeline and can be extended with custom steps (e.g. age verification, B2B approval).

Caching operates on multiple levels: TYPO3 page cache for static pages, aimeos internal caching for catalog queries, and optionally Varnish or Cloudflare as a reverse proxy. For catalogs with over 100,000 items, index management is critical: aimeos creates search and price indexes that are updated incrementally on product changes.

Common problems and solutions

Performance drops with large catalogs. Shops with 50,000+ items become slow when indexes are not current or the catalog cache is deactivated. Solution: run php typo3/sysext/core/bin/typo3 aimeos:jobs as a cronjob (every 5 minutes for index updates, hourly for cleanup jobs). Clear the aimeos admin cache manually after bulk imports.

Checkout abandonments due to payment errors. Common cause: outdated API keys or incorrect webhook URLs after a domain migration. Every payment provider needs a correct notify URL for asynchronous payment confirmations. Solution: verify webhook URLs in the payment provider dashboard after every migration, run test orders in sandbox mode.

Conflicts with TYPO3 caching. aimeos pages with shopping cart or login must not land in the TYPO3 page cache. Solution: mark the relevant pages as USER_INT or run aimeos in SPA mode (AJAX-based). Since aimeos 2024.x, SPA mode is the recommended default.

Migration and version compatibility

aimeos fully supports TYPO3 v12 LTS and TYPO3 v13 since aimeos 2024.x. For TYPO3 v11, maintenance releases are available but no new features.

Migration from other shop systems is a realistic scenario. From Shopware, WooCommerce or tt_products, products, categories, customer accounts and order history can be transferred to aimeos. Gosign uses CSV/XML import pipelines where product data is transformed and mapped into the aimeos structure. Depending on data quality, migrating a shop with 5,000 products takes between 3 and 10 days.

Those coming from tt_products should plan the switch with the next TYPO3 major version: tt_products has been minimally maintained for years and has no official TYPO3 v13 compatibility.

Another migration path concerns organizations that have been running a separate Shopware or Magento shop alongside their TYPO3 website. Merging into a single system eliminates interface complexity: no REST API synchronization for product data, no duplicate template management, no separate deployments. The downside: aimeos does not cover every feature a dedicated shop system offers (e.g. Shopware Flow Builder, Magento Page Builder). But the tradeoff pays off for organizations where content and commerce carry equal weight - not just the shop, but also magazine, knowledge base and service pages.

Gosign advises on a project-specific basis whether aimeos is the right choice or whether a separate shop system with headless connection to TYPO3 represents the better architecture. The decision depends on three factors: catalog complexity (variants, configurators, bundles), transaction volume (under or over 1,000 orders per day) and existing TYPO3 infrastructure (extensions, templates, editorial workflows).

An aimeos setup with product catalog, shopping cart, Stripe and PayPal payment, shipping calculation and base templates is estimated by Gosign at 15 to 25 development days. Custom themes, complex pricing logic or marketplace features increase the effort accordingly. Ongoing operations require regular updates (aimeos and payment provider plugins) as well as monitoring of checkout performance and conversion rate. Security patches for aimeos and payment plugins should be applied within 48 hours, because shop systems handling payment data are a preferred attack target.