Skip to main content

Aimeos Roadmap

New versions of the Aimeos e-commerce library and its application/framework integrations are released on a quarterly base.

In the beginning of each year, new major versions will be available with a three month beta and a six month stabilization phase. They will contain code cleanups and reorganizations and aren't backward compatible with previous releases. During the stabilization phase, only features will be added that aren't likely to break backward compatibility to working code.

Latest stable (LTS) version:

  • will get bugfixes and security patches
  • will be supported for one year free of charge
  • is supported another four years with extended support (ELTS)

We recommend to use the stable releases for production and upgrade to the corresponding LTS version after it has been released.


Support periods

Support type
Beta release
Stable releases
Long term support (LTS)
Commercial extended LTS support

Planned for 2020+

  • Implement more Vue.js components for admin interface
  • Add iterate() method to all managers for large result sets
  • Merge mshop_order and mshop_order_base tables
  • Use product ID in stock items instead of product code
  • Remove "standard" from configuration settings
  • Use filesystem abstraction everywhere
  • Add mshop_price_taxrate table for changing taxrates easier
  • Reduce madmin_job table to the minimum (id, siteid, label, filepath, status)
  • Allow passing additional configuration to CLI commands
  • Streamline createListsItem() to createListItem()
  • Provide Blade/Fluid/Twig templates for the HTML clients
  • Use AI-based services for image optimization
  • Simplify product CSV import format
  • Create simple to adapt Progressive Web Application based on Vue.js and Nuxt.js
  • Add scalar type to order product/service attributes to allow internationalization
  • Replace admin interface REST API by GraphQL API
  • Implement GraphQL API as alternative to JSON REST API for PWA frontend
  • Better reusable address partial for HTML and e-mail templates
  • Use document oriented way to store unit test data
  • Clean up and simplify unit test data