OXID Agency: support, updates and migration

OXID ESHOP MAINTAIN, EXTEND OR MIGRATE

OXID eShop is a PHP shop system by OXID eSales AG of Freiburg, Germany, widely used in German B2B commerce. We keep your OXID shop running, build modules, connect ERP and PIM – and plan the move to Shopware 6 when it pays off for you.

Discuss your project

OXID or Shopware 6? Technical audit as a first step

238: Stars on GitHubShows interest and reach, not quality.Green from 100K stars, orange below 10K, red below 1K.
9: Releases in the last 12 months, a median of 27 days apartMany small releases usually mean bugs get fixed quickly.Green from 50 releases a year, orange below 7, red below 3.
7.6.0: Latest version, released 07/10/2026Useful to compare with the version you run.Green when at most 14 days old; orange over 120 days, red over 365 days.
25K: Downloads per month via PackagistIncludes automated builds: a usage trend, not a user count.Green from 50M downloads a month, orange below 100K, red below 1K.

What does an OXID agency do?

An OXID agency maintains, extends and modernises shops built on OXID eShop. nextlevels handles modules, updates to OXID 7 with Twig, ERP and PIM integrations and technical audits. As a Shopware agency, we also tell you honestly whether to keep developing OXID or whether migrating to Shopware 6 is the better path.

Price rules, live – B2C or B2B

Switch the customer group, change quantities and apply a coupon: group price, tier price, free-shipping threshold and VAT recalculate instantly. The list shows which rule changed the price. Example products and prices, calculated in your browser.

Consumers always see gross prices

Apply coupon NL10

Work gloves
€23.74 / unitwas €24.99
€284.88
Cordless drill
€99.96 / unit
€99.96
Screw set
€5.00 / unit
€0.00

Goods value: €384.84
Shipping: free
Total: €384.84
incl. 19 % VAT: €61.45

Rules applied

Tier price from 10 units −5 %: Work gloves−€15.00
Free shipping from €150.00 goods value−€5.95

Example products and prices. Tiers: from 10 units −5 %, from 25 units −10 %. Calculated in your browser.

What we do with OXID

Bookable individually or as a project. And if switching systems doesn't pay off for you, we tell you.

Technical audit as a first step
We review code, modules, performance and security of your OXID shop. You get a prioritised list and a clear recommendation: develop further, update or migrate.
Takeover from other providers
We take over access, code and servers in an orderly way, document modules and interfaces that have grown over the years and bring the shop back to a state where work can continue.
Maintenance and update to OXID 7
Security updates, an eye on the PHP version and moving Smarty themes and modules to Twig so your shop can run the current 7.x release.
Modules and B2B logic
Custom modules for customer prices, tiered pricing, approvals and special processes, built cleanly on OXID's Symfony components and covered by tests.
ERP, PIM and payment integrations
Interfaces to ERP, PIM, payment providers and shipping, encapsulated so you can reuse them if you switch systems later.
Migration to Shopware 6
Data mapping, transfer of products, customers and orders, rebuilding the B2B logic and redirects for every relevant URL – in separate phases.

How a OXID eShop project runs

Cost and duration depend on scope. Our project calculator gives you a first range; the binding figure comes with the offer after the workshop.

First call
You describe the goal, the users and the systems you already have. We tell you straight away whether OXID eShop fits or whether another route is better.
Architecture workshop
We define the data model, interfaces and hosting and cut the scope into packages. The offer is based on that.
Delivery in iterations
We ship in short steps to a test environment, so you see every stage. Tests and code review are part of each step.
Go-live and operations
We deploy to your infrastructure or run the application for you. After that we handle updates and monitoring if you want.

Discuss your project Open the project calculator

Brands that work with us

Pros and cons of OXID eShop

Pros

OXID ships with B2B features such as customer-specific prices, tiered pricing and approval workflows.
The vendor is based in Freiburg, and documentation and ecosystem are strongly geared to the German market.
With OXID 7 the system uses Twig and current Symfony components instead of Smarty.
Editions range from the open-source Community Edition to the Enterprise Edition, with purchase or subscription licences.

Cons

There are fewer agencies, developers and ready-made extensions than for Shopware.
Older shops on Smarty themes need a theme and module rework before updating to OXID 7.1 or later.
Modules that grew over years are often poorly documented, which makes every further change more expensive.
Headless frontends are possible but less common than on API-first platforms.

Is OXID eShop right for you?

A good fit if …

You run a B2B shop on OXID that covers your processes and should keep evolving.
You need a new provider to take over and document an existing OXID shop.
You are planning the update to OXID 7 and need to move themes and modules to Twig.
You want a neutral review of whether an update or a migration to Shopware 6 makes more sense.

Probably not if …

You are launching a new shop with no legacy system – then we would rather compare Shopware and headless options directly.
You are looking for a certified OXID partner for a large new build on OXID.
You only need a single off-the-shelf module without integrating it into your shop.
Your shop should stay as it is and only needs hosting.

We work withOXID eShop

Many OXID shops have carried core B2B processes for years. We take over these systems, untangle legacy customisations and develop them further in a controlled way.

Takeover of existing OXID shops from other providers
Module development and Twig theme customisation
Updates within OXID 6 and 7
Integration with ERP, PIM, payment and shipping

OXID or Shopware 6?

Switching doesn't pay off automatically. Five questions about your shop, and you see which way it leans and why. The weighting follows the trade-off table below.

Question 1 of 5

How well does the shop cover your processes?

All trade-offs as a table

When OXID – and when Shopware 6?

We're a Shopware partner and still look after OXID shops. A switch costs time and money and doesn't automatically pay off. This is how we weigh it:

Decision	Lean towards OXID	Lean towards the alternative
Processes	OXID, if the shop covers your B2B processes today and only individual features are missing.	Shopware 6, if you keep rebuilding special solutions that come as standard there or work via the Rule Builder.
State of the code	OXID, if the modules are documented and can be moved to Twig with manageable effort.	Shopware 6, if the update to OXID 7 amounts to a rebuild – then the budget is better spent on the switch right away.
Team and provider	OXID, if your team or a provider knows the system and supports it reliably.	Shopware 6, if you can hardly find OXID developers any more and want access to a larger market of agencies and extensions.
Frontend and channels	OXID, if the classic themed shop remains your main channel.	Shopware 6, if headless frontends, apps or further sales channels via a Store API are planned.
Budget and timing	OXID, if the budget currently covers stabilisation and the update and the shop should carry you for a few more years.	Shopware 6, if a relaunch is due anyway and you can plan data transfer and redirects in one project.

As of October 2026. The table doesn't replace an architecture decision – we make that with you on the actual project.

OXID eShop compared

OXID eShop next to technologies of the same category, measured with the same public sources.

OXID eShop compared
Figure	OXID eShop	Medusa	Shopware	Spryker
Stars on GitHub	238	37K	3.5K	39
Releases in 12 months	9	37	51	12
Median between releases	27 days	8 days	6 days	15 days
Latest version	7.6.0 (07/10/2026)	2.22.1 (23/10/2026)	6.7.15.1 (02/10/2026)	3.87.1 (14/09/2026)
Downloads per month	25K (Packagist)	748K (npm)	266K (Packagist)	30K (Packagist)
Active contributors (12 months)	8	169	207	0
Security advisories (12 months)	0	1	14	0

Sources: GitHub, OSV.dev, Packagist, npm · as of 29/10/2026. Figures are indicators, not a verdict on quality. Go to the pages: Medusa · Shopware · Spryker

Built for B2B processes

OXID ships with customer-specific prices, tiered pricing, discount rules and approval workflows. We configure them to match your sales process and customer groups.

Editions for different sizes

OXID eShop comes as Community, Professional and Enterprise Edition. We work out with you which edition and licence model fits your catalogue, sales channels and operating model.

OXID 7 with Twig

Since OXID eShop 7.0, Twig is the default template engine, and Smarty is no longer supported from 7.1. We move themes and modules from Smarty to Twig so your shop stays upgradable.

A framework on Symfony components

OXID builds on proven Symfony components. That makes clean module code, dependency injection and testing easier – and keeps customisations manageable during updates.

Stabilise an existing OXID shop

If your previous provider is gone or updates have piled up, we take over the shop, document its current state and bring it back to a maintainable baseline.

Prepare the move to Shopware 6

When extending OXID gets too costly, we plan the migration: data mapping, redirect strategy, rebuilding your B2B logic and a cutover without a long shop outage.

OXID eShop Data & Insights

All posts

Commerce & Shopware15/10/2026

Shopware 6 versions: update roadmap

Commerce & Shopware28/10/2026

E-invoicing in wholesale from 2027: what to check in your ERP and Shopware now

Commerce & Shopware19/05/2026

Cross-border e-commerce with Shopware 6: setting up a multi-country shop correctly

Commerce & Shopware24/05/2026

BFSG checklist for Shopware 6: How to make your online shop accessible

Frequently asked questions about OXID eShop

Your question isn't here?

Ask directly

Do you support existing OXID shops even if we don't want to migrate?

Yes. We take on OXID shops for maintenance and further development, even when no platform change is planned. We start by reviewing code, modules and interfaces, document the current state and prioritise updates and open issues. From there we develop your shop in plannable steps.

What changes with OXID eShop 7?

With OXID eShop 7.0, Twig became the default template engine; Smarty was only offered as an alternative and is no longer supported from version 7.1. The Symfony components were updated as well. For you this means that themes and modules still based on Smarty need to be reworked before the update.

Is it worth moving from OXID to Shopware 6?

It depends on your shop. If OXID covers your processes and your team works well with it, an update is often the cheaper option. Moving to Shopware 6 makes more sense if you maintain many custom workarounds, need features like the Rule Builder or headless frontends, or struggle to find developers for your stack. We make that call transparent in an audit.

How does a migration from OXID to Shopware 6 work?

We migrate in clearly separated phases: analysis and data mapping, transfer of products, customers and orders with validation, rebuilding B2B logic and interfaces, and a cutover with redirects for every relevant URL. That way rankings, customer accounts and order history are preserved.

Can you connect OXID to our ERP or PIM?

Yes. We connect OXID to ERP, PIM, payment and shipping via modules and interfaces. We encapsulate each integration so it stays traceable and testable – and can be reused as far as possible in a later migration.

Are you an official OXID partner?

No, we are not a certified OXID partner; we are a Shopware Silver Partner and headless agency. We work with OXID wherever our clients use it: maintenance, extensions, integrations, audits and migrations. We say this openly so you can make the right choice for your project.

Sources

As of: October 2026

Your edge with OXID eShop

We are a Shopware and headless agency that supports OXID shops pragmatically. So you get an honest assessment instead of a knee-jerk replatforming pitch.

Neutral assessment: extend, update or migrate
Experience with PHP and Symfony-based shop systems
Clear documentation of legacy modules and interfaces
Migrations to Shopware 6 in clearly separated phases

Keep developing OXID or switch to Shopware?

We assess your OXID shop honestly and then deliver: continued operation with modules and updates, or a planned migration to Shopware 6.

To the Shopware agency

Ready for your OXID eShop project?

Let's talk about your requirements – we'll get back to you within one business day with concrete next steps.

What's it about?

Discuss your project +49 (0) 2161 539 71 60

Paul Kalisch

Executive Partner

30 minutes by video or phone
You talk directly to a partner, not to sales
You get the order of steps, risks and rough costs

+49 (0) 2161 539 71 60 info@next-levels.de

Related services and technologies for OXID eShop

All technologies

* Sources: GitHub (29/10/2026), Packagist (29/10/2026) · Green: strong, orange: weaker, red: notably weak, each against usual values. A pointer, not a verdict.