aimeos-typo3-dist is a distribution, and the difference shows in the Initialisation folder

A distribution is a preset, and that changes what you are installing

The readme describes the package as providing an out of the box web shop based on the Aimeos online shop extension for TYPO3, and the second sentence is the specification. It contains a pre-configured, full featured shop including faceted search, product listings and detail views, as well as baskets, coupon handling, the checkout process and all e-mail handling for notifying customers. Read that list as the answer to a question extension documentation rarely answers. Installing the Aimeos extension gives you the machinery. Installing the distribution gives you a shop with search configured, a basket wired to it, a coupon mechanism, a checkout and the notification e-mails that go with orders. That is a meaningful difference in what you inherit, and it comes with a corresponding difference in what you control, because each of those features is a decision someone else made: which search facets exist, which e-mail templates are sent, how the basket behaves. The repository layout supports the reading. There is an Initialisation directory with a British spelling, which is not a directory the extension would have, and it is where the pre-configuration lives. Classes, Configuration, Resources and Documentation follow the extension convention, ext_emconf.php and ext_localconf.php are the standard bootstrap files, and ext_tables.php declares the database tables in PHP rather than in a SQL file, which is the newer TYPO3 way of doing it. There is also a build.xml for an Ant build and both an icon in GIF and in SVG for the extension manager.

Composer path, and the two TYPO3 versions on offer

The composer path begins with fetching a phar of composer directly, which is a slightly different approach from the installer script some projects use:

wget https://getcomposer.org/download/latest-stable/composer.phar -O composer
php composer create-project "typo3/cms-base-distribution:^14.3" myshop

Two base distribution constraints are given, one for the newer TYPO3 line and one for the previous one, and the readme names the alternative explicitly for TYPO3 13 installations. There is no third option offered and no guidance on what happens if your site is on another version, so the supported set is narrow and worth confirming against your installation before you start. After the project is created, the TYPO3 setup command runs and you complete the browser wizard, then the distribution is added:

composer req -W aimeos/aimeos_dist

Note the package name here is the distribution, not the extension, so if you have been reading about the extension you will be looking for a differently named package. The capital W on that command is required for the same reason it is required elsewhere in this ecosystem, because the extension needs newer TYPO3 packages than composer would otherwise be willing to move. The last two commands activate the extensions and build the database:

./vendor/bin/typo3 extension:setup
./vendor/bin/typo3 aimeos:setup --option=setup/default/demo:1

That is the whole composer path, four commands after the base distribution exists. The Aimeos setup command is the one that does the work of creating a shop, and the readme notes that leaving out the demo option is how you skip the sample data.

The demo data switch, and the local test command that hints at the setup cost

For a local look at an installation, the readme suggests PHP's built-in server with a specific set of limits raised:

php -d memory_limit=256M -d max_execution_time=240 -d max_input_vars=1500 -S 127.0.0.1:8000 -t public

Those three values are the most informative line in the readme. A developer who copies a start command without reading the flags would be copying a requirement in disguise. 256 megabytes of memory, four minutes of maximum execution time and fifteen hundred input variables are not the defaults, and the fact that the project's own test instructions raise all three tells you the Aimeos setup import does real work, whether that is building the catalogue index, creating schema for a shop with many tables, or processing the demo data. Expect the initial setup step to be the slow part of the installation and to be sensitive to your PHP configuration on a small instance. The readme also points out that if you use Apache or another web server you can go straight to your installation's URL without starting the built-in server, and that the TYPO3 setup process should be completed before installing the distribution. Both are sensible, and the second is a sequencing note that matters, because a missing TYPO3 setup surfaces as a confusing later failure rather than as a clear prerequisite error.

The extension repository path, and why a distribution can be installed from a browser

For installations that are not composer-based, the readme says you can install the distribution from the Extension Manager by choosing Aimeos from the list of available distributions, and it also links the package on the TYPO3 extension repository for direct download. This is the one install path where a package described as a composer distribution works outside composer, and it is possible because of the extension metadata in the repository: ext_emconf.php describes the extension to the extension manager, ext_localconf.php is its bootstrap, and an icon is present so it can be listed. That is a genuinely useful property for organisations with an established non-composer TYPO3 estate, because it means the pre-configured shop is available without migrating the rest of their installation to composer. The trade is that the two paths are not guaranteed to produce identical installations. A composer install resolves the extension and its TYPO3 version constraints together and will fail loudly if they conflict, while an extension manager install works with what the repository offers for your platform and may land on different package versions. The readme does not describe pinning versions for the non-composer route, so if reproducibility matters to you, the composer path is the one with a documented version constraint and the extension manager route is the one without.

What the package deliberately does not let you choose

A preset shop is convenient until the first requirement conflicts with the preset. The feature list in the readme names faceted search, product listings, detail views, baskets, coupon handling, the checkout process and customer e-mail, and it does not say which of these can be removed, whether the templates are the Bootstrap-based ones from the Aimeos extension or something specific to the distribution, or what the default search facets are. The Initialisation directory is where that configuration would live, and the readme does not describe its contents. There is a related point about the extension itself: its documentation notes that the Aimeos layout expects a grid layout provider, which is a constraint that travels with the distribution since the distribution uses that extension. If your organisation already has a design system with its own grid, adopting the distribution means either accepting the layout that arrives with it or doing template override work, and the readme does not quantify that work. The honest characterisation is that this package optimises for the first hour and punishes the first customisation, which is a reasonable trade for a quick start and a poor one for a long-lived brand site.

Maintenance, licence, and where to go next

The repository publishes no GitHub releases, so there is no tag and no changelog to read before an upgrade, and the last push to the master branch was on 2026-05-30. The readme is explicit about the licence, GPL, and available for free, which matters more here than in a typical code dependency because a distribution carries a shop configuration, and the terms covering configuration data in a GPL distribution are exactly the sort of question that should go to whoever owns your licensing rather than to a readme. A Scrutinizer code quality badge is present in the extension's readme for the same product line, which indicates static analysis runs on the code, though this repository's own readme carries no coverage or build badge and its layout has no Tests directory at the top level, so test coverage for the distribution's own classes is not something the repository layout demonstrates. The links section points to a project web site, a help page, documentation specific to TYPO3, and an issue tracker on this repository. For anyone evaluating, the order that works is: read the TYPO3 documentation page for the version matrix, install into a throwaway instance with the demo data on so you can see the preset, then decide whether the preset or the extension alone is the better starting point.

Editorial conclusion

Adopt aimeos-typo3-dist when you want a working TYPO3 shop in one command rather than a catalogue you configure from empty, because the package arrives with faceted search, product listings, detail views, baskets, coupon handling, the checkout process and customer e-mail already in place, and it ships for both composer and the extension repository. Do not adopt it if you need a minimal installation, since there is no documented way to take the pre-configured part and discard the rest, and the demo data option is enabled in the documented command. Four things to verify first. That your TYPO3 version is one of the two named, since the readme offers a 14.3 base distribution or a 13.4 one and nothing else. That composer 2.2 or later is available, which the readme calls out as a requirement. That you run the Aimeos setup command without the demo option if you do not want sample products. And that your PHP limits are high enough, because the documented local test command raises memory, execution time and input variables, which is a hint about how heavy the setup import is. The licence is GPL, the last push to the master branch was on 2026-05-30, and the repository publishes no GitHub releases.

Frequently asked questions

Official sources

1. aimeos/aimeos-typo3-dist on GitHub
2. Issues
3. License: GPL-3.0
4. Project website
5. README