OXID eShop 7.0.0

Release date: 30-05-2023

The most important changes at a glance

  • OXID eShop 7.0 natively supports the template engine Twig.


    To make the changeover easier for you, we are still providing the previously used Smarty template engine for OXID eShop 7.0 as an alternative package.

    However, OXID eShop 7.1 will no longer support the Smarty engine.

    Therefore, we recommend switching to the new Twig standard as soon as possible.

  • MySQL 8, Composer 2.7 and the image format WebP are supported.

  • Module handling has been optimized and adapted.


Improvement of the module system


According to the philosophy of Composer, module files are read exclusively from the vendor/ directory.

When installing modules, the files are no longer copied to the source/modules/ directory.

For more information, see our developer documentation at Module skeleton: metadata, composer and structure.

YAML files

We have adjusted the structure of the configuration files.

For more information, see

When updating to version 7, it is therefore necessary that you transfer your custom modules to the new structure.

For more information, see Check changes in the module handler.


The commands for handling modules have changed.

For more information, see

New functions

Tracking URL per shipping method

Store one tracking URL per shipping method.

As soon as the parcel ID (depending on the shipping provider tracking code, parcel label number, parcel reference, shipment number, etc.) has been entered with the order, the tracking link consisting of the tracking URL and the parcel ID of the order will be available.

For more information, see Tracking-URL.

Setup via command line

To simplify the implementation of your project, as an alternative to the web-based setup, you can create and configure your OXID eShop via the command line.

You have the following options on the OXID eShop console:

  • Use oe:setup:shop to create the database and configure your OXID eShop.
    You pass the necessary information for this with parameters.

  • Install demo data with oe:setup:demodata.

  • Create the store administrator with oe:admin:create-user.

  • If you have OXID eShop Professional or Enterprise edition, add license keys with oe:license:add.

    It is technically not possible to replace existing license keys with new ones. Therefore, if you replace an existing license key with another one, delete all license keys first with oe:license:clear and then add the license keys again.

For more information, see Setup via command line.

Clean Up

We have removed the following deprecated functions.

Test library

Use the native PHPUnit and Codeception functionality instead of the test library.

For more information, see the developer documentation under Testing.

RSS functionality

The RSS functionality has been dropped.

Login via LDAP

If you have an LDAP environment, you need to implement your own login solution.

Credit card as payment method

We no longer support the credit card payment method implemented in OXID eShop for security reasons.

Use the module of a payment provider to offer credit card payment to your customers.

Newsletter dispatch

We have removed the rudimentary basic newsletter feature for sending a newsletter from OXID eShop.

Customers can still subscribe to newsletters.

To use the data in a professional marketing tool, export the list of your newsletter subscribers in the administration area.

For more information, see Newsletters.


With the introduction of the Flow theme (OXID eShop 6.0.0), you could already access news under Admin ‣ Customer information ‣ News only via a link in the footer.

To present news or offers, we recommend to implement landing pages with Visual CMS (for Professional and Enterprise Edition) in the future.

Encrypted values in the database

We have removed the native encryption of the store configuration in the oxconfig table, because MySQL 8.0 does not support this feature anymore.


Components of the compilation

The compilation contains the following components:

System requirements

For the system requirements, see Server and system requirements.



To install, follow the instructions under Installation.


Many thanks to your merge requests published with this release!