Shopware vs Shopify: which shop system fits a German merchant?

Shopware vs Shopify: what is the core difference?

Shopify rents you a finished shop; Shopware gives you a shop engine you can own. That single difference explains most of what follows in any honest Shopware vs Shopify comparison.

Shopify is a hosted software service. You pay a monthly plan, Shopify runs the servers, applies security fixes and ships new features to every store at once. You extend it with apps from its App Store and with themes, and you customise checkout only through the extension points Shopify allows. The upside is that a two-person shop team can run a serious store without ever touching a server.

Shopware 6 is software you can install yourself. According to Shopware’s pricing page, the Community Edition is free and published under the MIT licence, and it runs on your own hosting. Shopware also sells paid plans (Rise, Evolve and Beyond), available in its cloud, which add features such as the B2B Components and faster vendor support. Because the code is open, a developer can change almost any behaviour, from pricing logic to checkout steps.

So the real question for a German merchant is not which platform has more features on paper. It is where you want responsibility to sit: with a SaaS vendor that decides the rules, or with you and your developers, who get freedom in return for upkeep.

Which is better for a German shop, Shopware or Shopify?

Neither wins everywhere. Shopify tends to suit consumer brands with a small team; Shopware tends to suit wholesalers, manufacturers and retailers whose ordering rules are unusual. Use the decision rules below rather than feature lists.

We ask four questions before we recommend either side of the Shopware vs Shopify choice. Who will make changes after launch? How many of your orders come from business customers with their own prices? Does your checkout need behaviour that a standard shop lacks, such as delivery-date logic or cut-to-size pricing? And how strongly does your data protection officer feel about where order data is stored?

If the answers are “our marketing team”, “very few”, “no” and “we accept a reputable SaaS with a DPA”, Shopify usually costs less effort. If the answers point to developers, many trade accounts, custom logic and a preference for hosting in Germany, Shopware usually fits better. Mixed answers are common, and then the five-year cost comparison further down decides it.

• Choose Shopify when: consumer sales dominate, the team is non-technical, speed to launch matters most
• Choose Shopify when: you sell internationally and want Markets, currencies and translations handled by the platform
• Choose Shopware when: trade buyers need their own catalogues, price lists and approval flows
• Choose Shopware when: you want the shop hosted in Germany on servers you contract
• Choose Shopware when: your ERP or product configurator must reach deep into checkout
• Stay undecided until you have priced both routes over five years, not just the launch

Shopware vs Shopify fees: licences and transaction charges explained

Shopify charges a monthly plan and, if you do not use Shopify Payments, an extra fee on each order; Shopware charges no transaction fee at all, and its Community Edition has no licence cost. The exact amounts are on each vendor’s German pricing page and change from time to time, so we explain the structure rather than quote figures.

Shopify’s German pricing page lists four plans: Basic, Grow, Advanced and Plus. It also lists a fee for using a third-party payment provider instead of Shopify Payments: 2% on Basic, 1% on Grow, 0.6% on Advanced and 0.2% on Plus. That fee sits on top of whatever your payment provider charges. For a merchant whose customers expect PayPal, invoice payment and direct debit through a provider of their choice, this line deserves a careful calculation.

Shopware’s paid plans work differently. Its pricing page says Rise, Evolve and Beyond are priced on your gross merchandise value plus individual factors, billed monthly, and the Community Edition stays free. Your costs on Shopware are therefore hosting, any paid plan you truly need, commercial extensions from the Shopware Store and developer time.

In the quote we build a small spreadsheet with your real order volume and payment mix so the Shopware vs Shopify fee difference becomes a number, not an argument. For wider budget context, see website development cost in Germany.

Is Shopify cheaper than Shopware over five years?

Often at the start, not always at the end. Shopify usually costs less to launch and run for a small consumer shop; Shopware on Community Edition often costs less for a larger or B2B shop once transaction fees and app subscriptions pile up.

A fair five-year view adds six cost lines on each side. On Shopify: the plan, paid apps (many are monthly subscriptions), any third-party payment fee, theme licence, the initial build and later developer changes. On Shopware: hosting and its administration, any paid plan, Store extensions (some are one-time, some rented), the initial build, updates to core and extensions, and later developer changes.

The pattern we see when we model it: Shopify’s costs grow with revenue and with each app you add, while Shopware’s costs grow with complexity and with how often you change things. A shop that sells more of the same each year tends to favour Shopware over time; a shop that experiments with marketing tools every month tends to favour Shopify, because its app ecosystem makes those experiments cheap.

Remember internal time as well. If every price change on Shopware needs a developer ticket, that time is a real cost even if no invoice shows it.

Shopware vs Shopify for B2B: B2B Components against Shopify B2B and Plus

For simple wholesale, both platforms now cover the basics. For complex trade selling, with many company accounts, individual price lists, budgets and approval chains, Shopware’s B2B Components and custom plugins still give more room.

Shopify’s help centre lists B2B features on its Basic, Grow and Advanced plans: companies with several locations, net payment terms, draft orders, PO numbers, quick order lists and up to three active catalogues across B2B markets. Shopify Plus adds an unlimited number of catalogues, company-specific catalogues for customer-level pricing, and deposits, partial payments and payment requests per fulfilment.

Shopware places its B2B Components in the Evolve plan and above, according to its pricing page, and the Beyond plan adds items such as customer-specific pricing and digital sales rooms. On Community Edition, many wholesalers cover their needs with customer groups, the rule builder, advanced pricing and one or two custom plugins instead of a paid plan.

Where the Shopware vs Shopify gap widens is in the unusual rules: minimum order values per product group, delivery only to approved addresses, sub-accounts with spending limits, or prices pulled live from an ERP. On Shopware those are plugins; on Shopify they are apps, Shopify Functions or a separate portal.

If trade customers are most of your revenue, a separate B2B portal linked to your ERP can beat both shop systems.

German legal requirements: does Shopware or Shopify make compliance easier?

Both platforms can be set up to meet German checkout law; neither does it perfectly out of the box. The difference is in how you get there: configuration and templates on Shopware, settings, theme edits and apps on Shopify.

Three points matter most. First, § 312j (3) BGB requires that the consumer expressly confirms a payment obligation when ordering, which in practice means an order button labelled “zahlungspflichtig bestellen” or equally clear wording. Second, § 356a BGB now requires an electronic withdrawal function on the online interface for distance contracts. Third, German shops need an Impressum, terms, a withdrawal policy, a privacy policy and, where goods are sold by weight or volume, unit prices.

On Shopware, a developer changes the button label in the language snippets, adds unit prices through product fields and builds the withdrawal function as a small extension. On Shopify, button wording depends on the theme and checkout language settings, legal pages are created in the admin, and apps from the App Store handle parts of the rest. Check whether your legal-text provider offers an interface for the platform you choose.

We build and test these pieces; your lawyer approves the wording. We do not give legal advice.

The withdrawal function has its own guide: EU withdrawal button.

Hosting and data location: where does your shop data sit?

On Shopware you decide: a German hosting provider, AWS Frankfurt or Shopware’s own cloud. On Shopify, data is processed on Shopify’s infrastructure, and the terms of that processing are set in Shopify’s data processing addendum.

Shopify’s DPA states that transfers from the EEA to Shopify entities outside it follow Shopify’s Binding Corporate Rules, and that data may be processed in any country where Shopify, its affiliates or service providers are located, naming Singapore and Canada as examples. Canada holds an EU adequacy decision for commercial organisations. Many German merchants accept this; some data protection officers, particularly in regulated sectors, prefer a shop they can host in Germany.

Self-hosting Shopware brings its own obligations. You sign a data processing agreement (AVV) with the host, you are responsible for backups, patching and server security, and you need someone to watch it. That is exactly the work a SaaS platform takes off your plate.

Neither choice is automatically “GDPR-compliant”. What matters is the whole set: consent before tracking, a correct privacy policy, contracts with each processor and data minimisation. Our GDPR-compliant website page covers the storefront side, and your data protection officer or lawyer signs off.

Developer availability and rates: Shopware vs Shopify talent in Germany

Shopware talent is concentrated in Germany and the DACH region, where the platform was born; Shopify talent is spread worldwide. That affects both price and how quickly you can find help when something breaks.

Shopware 6 work needs PHP, Symfony, Twig and Vue.js skills plus knowledge of Shopware’s own layers such as the Data Abstraction Layer. Many experienced Shopware developers work at agencies in North Rhine-Westphalia and elsewhere in Germany, and good ones are often booked months ahead. Shopify work needs Liquid, JavaScript and, for deeper changes, Shopify’s app and Functions APIs; a large global market of freelancers and app vendors exists.

We will not quote other people’s day rates, because quotes vary widely and depend on scope, seniority and who carries the project risk. What we can say is that a remote team usually removes office and account-management overheads from the price, and that for either platform you should compare quotes line by line rather than by rate.

One practical point: after launch, a Shopify shop can survive a few months without a developer. A self-hosted Shopware shop cannot, because core and extension updates keep coming. Budget for that when you weigh Shopware vs Shopify.

Payments German shoppers expect, on each platform

German shoppers like choice at checkout: PayPal, invoice or buy-now-pay-later, cards and direct debit all play a part. Both platforms support these through providers you contract with, but the cost logic differs.

On Shopify, the cheapest route on fees is Shopify Payments, because Shopify’s extra charge for third-party providers then does not apply. If your preferred provider for invoice payments or direct debit is not covered there, you pay that provider’s fee plus Shopify’s percentage. On Shopware, you install the provider’s extension, and the only fees are the provider’s own.

We set up every payment method in sandbox mode first, then run test orders with refunds and partial cancellations. We also check that each payment status reaches your order management correctly, because an order that shows as unpaid when it has been paid causes support work every day. All merchant contracts are in your company’s name; we earn nothing from any provider.

• Write down your current payment mix by share of orders before choosing
• Ask each provider whether they support your chosen platform directly
• Include refunds and chargebacks in the test plan, not only successful payments
• Keep payment credentials in your own accounts, never the developer’s

How far can you customise: Shopware plugins vs Shopify apps?

Shopware lets a developer change almost anything, including checkout; Shopify lets you add almost anything through apps, but changes to core behaviour happen only through the hooks Shopify provides.

On Shopware, custom work takes the form of plugins (running inside the shop with access to its core services) or apps (running outside and talking to Shopware through its API and webhooks). Themes inherit from the default storefront and override Twig blocks. The ceiling is high, and the cost of reaching it is that every custom piece needs updating when Shopware releases new versions.

On Shopify, themes are written in Liquid, apps extend the admin and storefront, and Shopify Functions let developers adjust discounts, delivery and payment options at checkout. Checkout layout and logic can be changed only within Shopify’s checkout extension points. That keeps shops stable during Shopify’s platform updates but blocks some requests entirely.

Before choosing, list the three most unusual things your shop must do. If each maps to an existing app or a Shopify Function, the Shopware vs Shopify decision tilts toward Shopify. If one of them needs to rewrite checkout, it tilts toward Shopware.

Shopware vs Shopify for SEO and AI search visibility

Both can rank well; neither ranks for you. Shopware gives more control over URL patterns; Shopify is faster to get right for a non-technical team but has fixed URL prefixes such as /products/ and /collections/.

On Shopware, SEO URL templates for products and categories are editable, canonical tags handle variants, and a developer can shape structured data freely. On Shopify, structured data usually comes from the theme or apps, the URL structure is fixed, and sitemap and robots handling follow Shopify’s defaults with some room for edits.

For AI answers such as Google’s AI Overviews, the platform matters less than the content: product pages that state materials, sizes, delivery times and return conditions plainly, plus category pages that answer buyer questions in short paragraphs. We set up Google Search Console before launch and watch Core Web Vitals on real phones.

Moving from one platform to the other is where SEO most often suffers. Every old URL needs a redirect to its closest new page, and that map should be tested before switching DNS. Nobody can guarantee rankings after a move, and we do not. Planning a relaunch? Read website relaunch SEO first; ongoing shop SEO starts at US$150/mo.

Migration effort: moving from Shopify to Shopware

Moving from Shopify to Shopware is a medium-sized project: products, customers and orders export cleanly, but apps have to be replaced with extensions or plugins and the theme is rebuilt from scratch.

The typical order of work: export the catalogue, customers and order history from Shopify; map product options and metafields to Shopware properties and custom fields; import on a staging shop; rebuild the storefront on the Shopware theme; replace each Shopify app with a Store extension or custom plugin; set up payment and shipping providers; and write the redirect map from Shopify’s fixed URL patterns to your new Shopware URLs.

Customer passwords cannot be carried over from Shopify, so customers set a new one; plan a friendly email for that. Gift cards, subscriptions and loyalty points need their own plan because they usually live in apps.

Merchants usually make this move when trade customers or custom checkout logic outgrow Shopify, or when a preference for hosting in Germany wins. Coming from Magento instead? See Magento to Shopware migration.

Migration effort: moving from Shopware to Shopify

Moving from Shopware to Shopify is usually lighter on development and heavier on process change: custom plugins either become apps, get replaced, or get dropped.

Data moves through Shopware’s API or exports into Shopify’s import tools or apps. The harder part is honesty about custom features. Each Shopware plugin needs one of four answers: an existing Shopify app does it, a Shopify Function can do it, a small custom app is needed, or the business stops doing it. Merchants are often surprised how many custom features they can drop.

Watch three areas. B2B price lists and customer groups have to map to Shopify’s companies and catalogues, and on non-Plus plans the catalogue limit may bite. Shopware SEO URLs must redirect to Shopify’s fixed paths. And any checkout rule you relied on must be checked against what Shopify’s checkout allows.

This move usually makes sense for merchants who find self-hosting and updates a burden and whose ordering rules are fairly standard. The shop team gains independence; the developer budget shrinks; the platform decides more for you.

In-house skills: who will run the shop every day?

Pick the platform your team can operate without calling a developer for routine work. This single factor settles more Shopware vs Shopify debates than any feature table.

On Shopify, marketing staff create landing pages, change banners, launch discounts and install apps on their own. On Shopware, the admin and the Shopping Experiences editor handle content and promotions well, but anything involving plugins, hosting, updates or template logic needs a developer. That is fine if you have one, or pay for maintenance; it is frustrating if you expected Shopify-style independence.

Ask yourself who, by name, will do each of these jobs in a normal month: add products, change prices, run a promotion, check a failed payment, update the software, respond to a security notice. Where the answer is “nobody”, pick the platform where that job disappears, or budget for someone to do it.

• Shopify fits a team of marketers and customer-service staff with no developer
• Shopware fits a team with an in-house developer or a maintenance contract
• Both need someone who owns product data quality
• Both need someone who reads the order and payment reports weekly

Working with a team in India on your Shopware or Shopify project

It works like any remote project, with one advantage: our day starts before yours. India is three and a half hours ahead of Germany in summer and four and a half in winter, so a question you send at 9:00 usually gets an answer before your lunch.

The first two weeks look like this. You send your current shop URL or a short brief, your order volume and payment mix, and any trade-customer rules. We reply on WhatsApp or email with questions, then send an itemised quote in USD within about two working days, usually with a Shopware option and a Shopify option side by side, each with its third-party costs listed. After your written approval, you create the platform account, hosting or plan in your company’s name and invite us. Week one builds the staging shop and imports sample products; week two brings the theme skeleton, checkout and payment tests, with a staging link you can open on your phone.

Calls happen in English over video during your morning and early afternoon. You pay in USD or EUR by Wise or bank wire, by milestone, and invoices come from India; your Steuerberater advises on how to book them. Anything not stated in the quote falls under our terms.

Worked example: a tea wholesaler in Hamburg weighing Shopware vs Shopify

This is a hypothetical scenario to show the reasoning, not a client story.

Say a Hamburg tea importer sells about 400 teas to consumers online and supplies 150 cafés and delicatessens by phone and email. The owners want one system for both. Cafés need their own prices, minimum order quantities per tin size and payment on invoice with 30-day terms. Two people run marketing; nobody codes.

On the Shopify side, companies, net payment terms and up to three catalogues cover a lot, but 150 cafés with individually negotiated prices would push them toward Plus for company-specific catalogues. On the Shopware side, Community Edition with customer groups, advanced prices and one small plugin for minimum quantities covers the trade rules, with hosting in Germany, but the owners would need a maintenance plan because nobody in-house can update the shop.

Our quote would show both routes: a shop from US$750 on either platform, the Shopware minimum-quantity plugin as its own line, the recurring third-party costs for each option over five years, and maintenance from US$120/mo after the two free months. The owners then decide with the numbers in front of them.

Shopware vs Shopify decision checklist

Work through these questions with your team before you ask anyone for a quote. Write the answers down; they become the brief.

• Share of revenue from business customers, and how many have individual prices
• Payment methods your customers use, with approximate share of orders
• Integrations required: ERP, PIM, DATEV, warehouse, marketplaces
• Checkout behaviour that a standard shop does not offer
• Hosting preference of your data protection officer
• Who makes routine changes, and who handles updates
• Countries and languages you sell into over the next three years
• Expected order volume, to model Shopify’s fees against Shopware hosting
• Current URLs and rankings you must protect during a move
• Budget for five years, not only for launch

Selling to consumers? Add the accessibility items on our BFSG requirements page to the checklist.