Which VAT rate applies? A decision tree for cross-border selling
Domestic rate, reverse charge, One-Stop-Shop or zero-rated export — four outcomes, three questions. Plus a free calculator that picks the rule for you.
// Blog
Shopware, Node.js, React, performance, AI, cloud and the boring B2B details nobody blogs about. No listicles, no reheated vendor marketing — only things we have actually done.
Domestic rate, reverse charge, One-Stop-Shop or zero-rated export — four outcomes, three questions. Plus a free calculator that picks the rule for you.
Protocols, councils and press releases are multiplying. Underneath the noise, one thing genuinely changes for your shop — and it is not the checkout.
A 50% markup is a 33% margin. Confuse the two and you have quietly given away a third of your profit on every product in the catalogue.
Shopify, Magento, WooCommerce, PrestaShop, OpenCart, Odoo, Wix, Square, Zoho and more — measured against Shopware 6 on the things that actually decide a B2B project.
Not every Shopware 5 shop needs to migrate this year. Here is how to tell whether yours is a healthy earner or a ticking maintenance bill.
AI coding assistants genuinely changed how we work. They also cannot tell you why your customer's pricing rule contradicts itself.
Apps run outside the shop and survive updates. Plugins run inside it and can do anything. The choice decides your maintenance bill for years.
Shopify will have you live in weeks. Shopware will still be doing what you need in ten years. The honest trade-off, with the numbers.
The app manifest is easy. The handshake, the shop secret and verifying every incoming request are where first-time app builders get burned.
Long requirement documents make everyone feel safe and tell you nothing. Three exercises that reveal more than any feature matrix.
Two open, extensible, B2B-capable platforms. One of them needs a devops team just to stay upright. Here is what that actually costs.
The Admin Extension API lets an app add modules, action buttons and notifications through an iframe and a message bridge. Less power, far less pain.
WooCommerce is the cheapest way to start selling and the most expensive way to scale. The exact point where that flips.
Store plugins promise a lot and deliver about 70% of it. Here is the decision framework we use with clients before spending a cent on either option.
App Scripts run inside Shopware's process but ship with your app. They are how you touch the cart without a plugin — and without an HTTP call per line item.
Both are open, both are European, both are free to download. The difference shows up in the second year, not the first.
OpenCart is light, fast to install and costs almost nothing. It is also the system we most often find holding a growing business back.
Shopware lets an external endpoint calculate tax for the whole cart. For cross-border B2B, that is the difference between a rule table and an audit.
Odoo gives you commerce inside the ERP. That solves your integration problem and creates a storefront problem. Which one hurts more?
Comparing these two is like comparing a van to a bicycle. The real question is what you are carrying — and how far.
Data migrates fine. It is the SEO URLs, the custom logic and the plugin gaps that kill migrations. A field-tested checklist from real projects.
Square Online exists to extend a point-of-sale into the web. Judge it as that, and it is very good. Judge it as a B2B platform and it is not one.
If you already live in Zoho, its shop is tempting and integrated. That integration is exactly what you pay for later.
Custom fields are a five-minute solution that becomes a five-month problem. Here is the line at which you must switch to a real entity.
Three German platforms, three different centres of gravity. If you are choosing between them, you are choosing an ecosystem more than a feature list.
Customer groups, scale prices, contract prices, rule builder — four mechanisms that overlap. Here is which one to reach for, and when.
Composable commerce is real engineering, not a buzzword — and it is far more platform than most mid-market companies need or can staff.
Every landing page that needs a developer is a landing page that will not be built. Custom blocks turn your team into people who can ship.
Headless is not automatically faster or better. It buys you freedom and costs you a whole frontend. Four questions that tell you if it pays off.
Teach Shopware one new verb and one new condition, and your non-technical team can automate things you never anticipated.
Most Shopware 6 shops use Flow Builder for order confirmation emails and nothing else. Here are the flows that actually save hours every week.
Context tokens, sales-channel keys and the cart that lives on the server. The three things every headless build gets wrong on the first attempt.
Not everything belongs in the shop. A small Node service between Shopware and your ERP solves problems a plugin never will.
Most integrations fetch far too much data because nobody read the criteria docs. Filters, aggregations and associations, explained by example.
Both are excellent. The right answer depends far less on the framework than on who maintains it after we leave.
One request per product is a 28-hour import. Bulk payloads and the sync API turn it into twenty minutes — if you get the batching right.
GraphQL solves over-fetching. It also hands your clients a loaded gun pointed at your database. When each one is the right call.
Building headless from scratch means rebuilding routing, SEO and checkout state. Frontends gives you those — at the cost of following someone else's shape.
Types do not prevent bugs. They prevent a specific, expensive class of bug — the one that reaches your customer's invoice.
Nothing is broken, nothing errors, and nothing runs. The message consumer is almost always the answer — and here is how to prove it in five minutes.
Redis is not magic. Used badly it serves stale prices to real customers. Four patterns, and how to invalidate without fear.
There is no single cache. There are five, and the one you forgot is the one still serving yesterday's price.
MySQL LIKE queries die at 50,000 products. Here is what Elasticsearch fixes, what it does not, and the fields that decide relevance.
Your firewall is fine. Your accountant, on a Friday afternoon, looking at an invoice from a supplier they know — that is the attack surface.
Time to First Byte is the number your CDN cannot fake. Five causes, in the order we check them on real Shopware shops.
Certificates expire on Sundays. Browsers block the shop entirely. And the renewal reminder went to an inbox nobody has read since 2023.
Layout shift is the vital that costs you conversions directly — buyers click the wrong button. It is also the easiest one to fix.
Not legal advice — an engineering checklist. The technical facts you must be able to state about your shop when someone finally asks.
We have made shops score 98 and convert worse. The score is a proxy; revenue is the target. How to optimise for the second one.
Structured invoicing (ZUGFeRD, XRechnung) is becoming mandatory in B2B. A PDF attached to an email will not satisfy it — and your shop has to change.
Product descriptions, search, support triage, forecasting. Three of those pay for themselves. We separate the working from the pitching.
Your customer searches 'leaking pipe joint'. Your catalogue says 'compression fitting'. Keyword search finds nothing. Vector search finds the product.
The model is the easy part. Chunking, retrieval and the honest 'I don't know' are what separate a useful assistant from a liability.
Buyers increasingly ask an assistant, not a search engine. If your catalogue is not machine-readable, you are simply not in the answer.
Generating catalogue copy with an LLM works — if you never let it invent a number. The pipeline we use in production.
Public funding can carry a meaningful part of a digital project. It can also eat six weeks and change nothing. How to tell which one you are in.
The nightly script that 'usually runs' is a business risk. How to turn recurring work into something you can trust and observe.
Deployment, updates, support and onboarding all collapse into one thing when the app lives at a URL. The exceptions are real, but rarer than people think.
You can run a serious B2B shop on far less AWS than a consultant will sell you. The minimal architecture that scales.
Buying tools is not building an infrastructure. Three mistakes we see in almost every mid-sized company that 'went remote' and never quite arrived.
If deploying is scary, you deploy rarely, so each deploy is huge, so it is scarier. Here is how to break that loop.
The build is the cheap part. Store fees, OS updates, device fragmentation and the second platform are what turn a €60k app into a €200k decision.
Uptime checks tell you the server answered. They do not tell you that checkout has been failing for six hours. Monitor the business, not the box.
Forget keyword density. In a B2B shop, rankings are won with URL structure, faceted-navigation control and pages that actually load.
SEA buys traffic today and stops the moment you stop paying. SEO compounds and takes months. A framework for splitting the budget.
Your B2B customers do not want a monthly newsletter. They want to know their reorder is due and their quote expires Friday.
Get tax wrong and you do not get a bug report — you get an audit. The rules a B2B shop must encode, in plain language.
Your B2B buyer does not want a story. They want to know whether it fits, when it ships, and what happens if it breaks.
Ignore the metaverse. The real shifts are boring, already underway, and they will decide who your customers order from in 2028.
'The code is messy' is not a business case. Translate debt into delivery speed, outage risk and hiring cost — then it gets funded.
No articles in this category yet.
Most of these articles started as a client's broken shop. Tell us about yours.