Shopware agency from Cologne.
Selling instead of maintaining data. We build the shop and the connections behind it.
As a Shopware Silver Partner from Cologne we build new shops on Shopware 6, migrate from Shopware 5 and take over existing ones. As much in the standard as possible, with development where your processes ask for it.
Connections
The shop is rarely the problem.
A Shopware project rarely fails on the shop. It fails on the catalogue that has to go into it, on prices and stock that are meant to stay maintained in the ERP, and on the processes around it. Customer prices, volume prices, approvals, quote processes.
Shopware covers a good deal of that itself, in B2B through the commercial editions, and that is where we start. What decides the effort after that is what hangs off the shop, and ERP, CRM and PIM are only the most common cases. What gets connected is what your processes need.
What can be connected to a Shopware shop
ERP
SAP, Microsoft Dynamics 365 Business Central, proALPHA
Articles, prices and stock come into the shop. Orders and customers go back into the ERP.
Procurement and punchout
SAP Ariba, Coupa, Onventis, Simple System, Jaggaer
We set punchout up, over OCI or cXML, level 1 and level 2. Your catalogue then sits inside the procurement system of your customer.
PIM and DAM
Pimcore, Akeneo
Texts, attributes, images and data sheets come out of the system they are maintained in.
CRM
Salesforce, HubSpot, Dynamics 365
Customers, enquiries and order history land in the CRM. Customer groups and price lists come from there.
Marketing and newsletters
CleverReach, Brevo, Mailchimp
Recipients, baskets and orders, for campaigns and for reminders about baskets left behind.
Payment
Stripe, Adyen, PayPal, Klarna
Payments, credit notes and the payment status, in B2B also buying on account.
Shipping and returns
DHL, GLS, DPD, UPS, FedEx
Shipments and labels go out. Tracking and the status of a return come back into the shop.
Accounting
DATEV, Lexware Office
Invoices and receipts go into accounting. The payment reconciliation comes back.
Marketplaces and feeds
Amazon, eBay, Otto, Google Shopping, Idealo
Articles, prices and stock run out to the channels. Orders from there run into the shop.
Service and portals
Zendesk, Freshdesk, customer portals
An enquiry arrives with the order behind it. The state of the case is visible in the shop.
Your system is not in the list.
For every system above there is a Shopware extension, a connector on our integration platform or a documented API. Over 100 systems are prepared. Everything else is connected over the API of the system, over file handovers or over EDI.
Which shops we build
From the small shop to the large catalogue.
The effort is decided by the range of products and not by the platform. A shop with forty articles needs no interface, it needs a clear structure. With a catalogue in the hundreds of thousands the opposite is true.
The small shop
Up to about 500 articles. The range is maintained in the shop itself, payment and shipping are connected, the standard carries it. After that we hand the shop over to your team.
The shop that grew
From a few thousand articles on, the catalogue comes out of the system it is maintained in. Prices and stock run on their own, and nobody maintains them twice.
The large catalogue
With a range in the hundreds of thousands, import, search and caching decide the speed. For Faust Laborbedarf AG we run a shop with over 200.000 articles that stays in step with ERP and CRM.
The ceiling is higher than that: in a proof of concept we checked a million articles with their variants.
Three ways a Shopware project starts with us.
Your way depends on what is already standing. A shop that is being built new. A Shopware 5 whose maintenance is running out. Or a shop in operation whose care is changing hands. The cut differs, the order does not. First the data and the processes, then configuration, and development only where the standard ends.
A new shop on Shopware 6
We write down what the shop has to do before anything is built. Range and catalogue maintenance, price and customer logic, payment and shipping methods, the pages the law requires, and the systems that deliver data or expect it. After that come theme and configuration, the imports from ERP and PIM, the interfaces, and the training of the people who maintain the shop later.
Migration from Shopware 5 to Shopware 6
A migration is not a move of a database. Articles, categories, customers, orders and the existing addresses have to come along, plugins that grew over the years mostly do not. So we first check what of it is really still needed, set the shop up again on Shopware 6 and take the data over. The old addresses are redirected, so the visibility is not lost in the switch.
Taking over an existing shop
A shop in operation can be taken over without stopping it. It starts with a review. Which plugins are active and current, where does logic sit in a template instead of in configuration, how do articles and prices reach the shop today. Out of that comes an order in which things are cleaned up. After that we take on maintenance, updates and further development, or your team does.
Services
What we take on with Shopware.
The shop as a whole, or the piece your team is missing. What costs the most time is rarely in the quote of an agency. The quality of the data in the catalogue, the price and permission logic in B2B, and the question of who keeps an eye on the imports after launch.
Build
- B2B and B2C shops
- Theme and storefront
- Migration from Shopware 5 to 6
- Taking over a running shop
- Several languages and sales channels
Data and connections
- Catalogue and price imports
- Stock and order synchronisation
- Interfaces to ERP, CRM and PIM
- Customer, volume and contract prices
- Punchout catalogues over OCI and cXML
- Plugin development where the standard ends
Operation
- Hosting and operation
- Updates and maintenance
- Monitoring of the interfaces
- Payment and shipping
- Training and support
Growth
- Performance and scaling
- SEO basics and URL migration
- Visibility in AI answers (GEO)
- Marketplaces and feeds
- Reporting and analytics
- Further development at a steady pace
Shopware compared.
Before a platform is chosen there is usually a comparison with another one. We have written up the four that come up most often in conversations, each with the criteria the choice is decided on in practice rather than with a list of features.
They are not all of them. We build shops on SmartStore as well, and if another platform is the better fit for you, we say so before the project.
Frequently asked questions about Shopware
Which Shopware services does ebiscon offer?
The whole stretch: a look at your range and your processes, building the shop on Shopware 6, theme and storefront, catalogue, price and stock imports, plugin development where the standard ends, interfaces to ERP, CRM and PIM, payment and shipping, hosting and operation, training, maintenance and support. Reinforcing a team that already runs the shop is just as possible.
What does Shopware Silver Partner mean?
Shopware lists the agencies that work with the platform in partner tiers and publishes them in its official partner directory. ebiscon is listed there as a Silver Partner. For a project that means two things. The direct route to Shopware is there when a question sits with the product itself, and the licence side does not run through a reseller.
What does a Shopware shop cost?
The price depends on the range of products, on the quality of the data that has to go into the shop, on the number of connected systems and on how much your team takes on itself. A shop with a clean catalogue out of a PIM is a different thing from 200.000 articles out of several sources with customer specific prices. Licence and hosting costs come on top. After a conversation about your range, your processes and your systems you get a quote with a fixed scope.
How long does a Shopware project take?
The scope decides that, not the platform. A shop with a catalogue from one system and one interface is ready in weeks. As soon as several data sources, B2B price logic, several languages and several sales channels come in, it becomes a project over months that is delivered in stages. So we cut it down to a first version you can sell with and build on from there.
Which systems can be connected to Shopware?
In principle any system that has an interface. ERP, CRM and PIM are the most common ones, and just as usual are marketing and newsletter systems, payment providers, parcel carriers, accounting, marketplaces and price portals, service systems, and the procurement systems of your customers over punchout. Over 100 systems are prepared on our integration platform. Anything without a ready connector is connected over the API of the system, over file handovers or over EDI.
10 more questionsShow fewer
Do you build in the standard or bespoke?
In the standard first. Shopware covers a large part of it, in B2B through the commercial editions, and whatever is configured instead of programmed survives an update without rework. Development goes where your processes differ from the standard, and they do, because no company works like the next one. Then we build it as a plugin, kept small and documented, so the next Shopware release does not run over the change.
How is Shopware connected to an ERP or a CRM?
Over the ebiscon integration platform, where more than 100 systems are prepared, or as a purpose built interface. The usual traffic is articles, prices and stock into the shop and orders, customers and payment status back into ERP and CRM. What matters is less the technology than the question of which system holds the truth. What is maintained in the ERP is not maintained in the shop, and the other way round.
Does Shopware support punchout catalogues for SAP Ariba or Coupa?
Yes, we set that up. Punchout over OCI and cXML, level 1 and level 2, against procurement systems such as SAP Ariba, Coupa, Onventis, Simple System or Jaggaer, and IDS Connect in technical wholesale and in the trades. Shopware carries none of this on its own, in any edition, so it comes either from an extension or from an interface we build for the case. Which way fits is decided by your edition, by the procurement system of your customer and by your price logic, and we settle that before the quote.
Do you build small shops as well?
Yes. A shop with 20 to 500 articles needs no interface and no special logic. It needs a clear structure, clean product data, and payment and shipping that work. Shops of that kind we set up in the standard and hand over to your team. The effort and the quote are smaller than for a catalogue fed by several data sources.
How does a migration from Shopware 5 to Shopware 6 work?
Not as a move of a database. Articles, categories, customers, orders and the existing addresses have to come along, plugins that grew over the years mostly do not. So we first check what of it is really still in use, set the shop up again on Shopware 6 and take the data over. The old URLs are redirected, so the visibility you have is not lost in the switch.
Is Shopware suitable for B2B with customer and volume prices?
Yes, and it is one of the most common reasons companies end up with Shopware. Customer specific prices, volume prices, price lists per customer group, orders on account, quotes and approvals by a supervisor can all be mapped. Part of that sits in the standard, part in the B2B features of the commercial editions, and part is configuration along your own price logic. Where the price finally comes from is usually decided by the ERP and not by the shop.
How many articles can a Shopware shop handle?
More than most ranges hold, as long as import, search and caching are built for it. For Faust Laborbedarf AG we run a shop with over 200.000 products whose prices and stock are kept in step with ERP and CRM. In a proof of concept we checked a million articles with their variants. With a catalogue that size the speed is decided by the search and by the imports, not by the theme.
Do you take over an existing shop?
Yes, and without stopping it to do so. It starts with a review. Which plugins are active and current, where does logic sit in a template instead of in configuration, how do articles and prices reach the shop today, and what was left behind at the last update. Out of that comes an order in which things are cleaned up. After that we take on maintenance, updates and further development, or your team does.
Will the shop be found in AI answers as well?
That is a channel of its own by now. Somebody asking about a product or a supplier gets an answer with sources in ChatGPT, in the AI overviews of Google or in Perplexity, and only what is machine readable shows up in there. For that a shop needs structured product data, answers in whole sentences at the place where the question comes up, category and manufacturer texts a reader can follow, and access for the crawlers of those providers. We set that up along with the ordinary search engine work, and we look at what both channels actually bring in.
Shopware or another platform?
That is rarely decided by a feature list. It is decided by the cost model, by data ownership and by how much you want to keep in your own hands. This page exists for Shopware because we are a Silver Partner there, not because it is the only choice. We build shops on SmartStore as well, and Magento, Shopify and the large SaaS platforms come up in conversations. We have written up the four comparisons that come up most often: Salesforce Commerce Cloud, VTEX, Commercetools and BigCommerce. If another platform is the better fit, we say so before the project.