FAQ: questions and answers on Shopware, integrations, SEO and AI

Minofinder runs as a plugin in Shopware 6 (versions 6.5 to 6.7), Shopware 5 and WooCommerce. A direct integration for JTL-Shop and Magento is in preparation. Until then, and for other shop systems, you add Minofinder via an embed snippet.

An ERP integration for Shopware 6 connects the online shop with the enterprise resource planning system (ERP). Products, prices, stock, customers and orders are synchronised automatically between both systems instead of being maintained twice. It is built with a connector from the ERP vendor or a custom integration via the Shopware API.

Usually the ERP leads for product master data, prices and stock, while the shop leads for orders and new customers. This can be decided per data type. If you use a PIM system, product texts and images often come from there, while prices and stock still come from the ERP.

Then we build a custom integration. Shopware 6 has a complete API, and most ERP systems offer an interface or at least an export as CSV or XML. The integration then runs directly or through middleware that translates between both sides.

The most common causes are full syncs instead of syncing only changed data, batches that are too large per request, or an interval that does not suit the product range. Plugins that rebuild indexes on every import also slow things down. We check logs and processes and adjust the integration accordingly.

Shopware 6 sends orders with line items and customer data to 42 ERP. 42 ERP sends stock levels and prices to the shop. Customers register returns in the shop, and the label and credit note are created in 42 ERP. We agree on the exact field list with you before the project.

Yes. 42 ERP creates invoices and delivery notes directly from the imported Shopware orders. The documents are produced where your accounting runs and do not have to be maintained in the shop.

Yes. Orders from Shopware 6, Amazon, eBay and other platforms can be processed centrally in 42 ERP. Stock then applies to all channels, and a sale on one channel reduces the available quantity everywhere.

The customer registers the return in the Shopware customer account. 42 ERP creates the return label and, once the goods have arrived, the credit note. The customer then sees the status in the shop again.

An API integration enables direct data exchange between two or more systems. Information is transferred automatically, without manual imports. Online shops use APIs, for example, to sync products, stock levels, prices, orders or customer data with ERP systems and external platforms.

We develop integrations for shop systems such as Shopware, ERP and inventory management systems, supplier portals, marketplaces, CRM systems, shipping providers and internal company software. Custom-built and older systems can often be connected too.

Yes. Many manual processes can be fully or partly automated via integrations. Prices are updated automatically, stock levels synchronised or orders transferred directly to an ERP system. This reduces errors and saves working time.

Yes. With extensive product catalogues and large supplier feeds, efficient processing is key. For this we use delta syncs, automatic synchronisation and optimised import processes, among other things.

Not in the classic sense. Billbee is cloud software for order processing, shipping and returns across several sales channels. It also manages warehouse and stock, but not financial accounting or production in the depth of a large inventory management system. For many small and mid-sized retailers, that is enough.

Shopware 6 sends orders and returns to Billbee. Billbee sends tracking numbers and credit notes back, and we synchronise stock in both directions. We agree on the exact fields with you before the start.

Yes. Billbee bundles orders from Shopware 6, Amazon, eBay and other channels in one interface. You ship all orders from there, and stock stays the same across all channels.

You create the shipping label for DHL, Hermes or another carrier in Billbee. The integration writes the tracking number to the order in Shopware 6 automatically, and your customers find it in the shipping email.

Shopware 6 sends orders and the related customer data to GDI Software. Stock levels and prices go back to the shop from there. Invoices, delivery notes and credit notes are created in GDI. We agree on the exact fields with you before the start.

We connect GDI Software and Shopware 6 through an API or through files in JSON, CSV or XML format. What makes sense depends on what your GDI installation provides and how up to date the data in the shop needs to be.

Yes, orders from Shopware 6, Amazon, eBay and other marketplaces can be brought together in GDI Software. Your team then handles all orders in one interface. We clarify which channels to connect at the start of the project.

Shopware 6 sends orders with the customer data to Gevis ERP. Gevis reports stock levels, shipping status and tracking numbers back to the shop. Invoices are created in Gevis. We agree on the exact fields with you before the start.

Gevis ERP reports stock levels to Shopware 6 at regular intervals. When an item is sold out, the shop shows this with the next sync. We set the interval to suit your product range: shorter for fast-moving goods than for items with large stocks.

Yes. Gevis ERP creates the invoice for the Shopware order and can pass the booking data on to accounting systems such as DATEV via interfaces. We check at the start which interface is active in your Gevis installation.

Shopware 6 passes orders with customer, payment and invoice data to IN:Software. The ERP sends products, prices, stock levels and, after dispatch, the tracking numbers back to the shop. We agree on the exact list of fields with you before the project starts.

Yes, if IN:Software provides an availability or delivery time for them. We map these values in Shopware 6 so customers can see whether an item ships immediately or later. We check how this is handled in your setup beforehand.

Yes. You create labels for DHL, DPD and other carriers in IN:Software. We transfer the tracking number to the matching order in Shopware 6 so that it appears in the shipping confirmation and in the customer account.

Yes. Orders from Amazon, eBay and other marketplaces are collected in IN:Software together with the Shopware orders. All channels use the same stock.

JTL-Wawi sends product master data, prices, customer group prices and stock levels to Shopware 6. The shop sends orders and new customer data to JTL-Wawi. Shipping status and tracking numbers go back to the shop after dispatch. We agree on the exact fields with you before the project starts.

For many shops it is: products, stock and orders work without custom development. An extension makes sense if you use custom data fields, custom products, loyalty points or several sales channels in one installation. We check this against your data before we develop anything.

We set the interval to match your product range. Fast-moving goods need a short cycle so the shop does not sell items that are out of stock. For large catalogues we only sync changed products, which keeps the load on shop and ERP low.

Yes. JTL-Wawi can run several sales channels at once. Shopware 6, marketplaces such as Amazon and eBay and a store POS then use the same stock. A sale on one channel reduces the available quantity on all others.

Shopware 6 sends orders and customer data to Lexware, where you create invoices, delivery notes and credit notes. Lexware reports stock levels back to the shop so that sold-out items can no longer be ordered.

Yes. Lexware creates the invoice for every transferred order and the credit note for returns. The documents are produced in your accounting software, not in the shop.

Mainly small and mid-sized online merchants who already run accounting and inventory in Lexware and no longer want to reconcile the shop by hand. If order volume grows strongly, we also discuss whether a larger ERP makes more sense.

Business Central sends products, stock levels, B2B discounts and tiered prices to Shopware 6. We synchronise customer data in both directions, and orders flow from the shop to the ERP. If you wish, we also transfer the total revenue per customer. We agree on the fields with you before the start.

Business Central is the successor to Microsoft Dynamics NAV, which used to be called Navision. If you still work with NAV and want to connect Shopware, please get in touch. We review your installation and discuss which route fits where you are now.

Yes. You control discounts and tiered prices for B2B customers in Business Central, and the shop displays them automatically. We also transfer prices for entire product groups that sit above the customer group discounts to Shopware 6.

Depending on the project, we use a connector such as the one from Firebear Studio, the iPaaS platform Alumio or a custom interface via the API. For large catalogues, delta synchronisation transfers only the data that has changed. We choose the route based on your data and processes.

Shopware 6 sends orders, customer data and payment data to microtech. microtech sends stock levels and prices back to the shop. We agree on the exact fields with you before the start.

Yes. microtech creates the invoice and delivery note directly from the order that the shop passes on. Credit notes and payment reconciliation also run in the ERP, so your accounting works with one system.

Yes. You manage orders from Shopware 6, Amazon, eBay and other marketplaces centrally in microtech. Stock and prices for all channels come from the same system.

Odoo sends products, variants, prices and stock levels to Shopware 6. The shop sends orders and new customer data to Odoo. If you wish, we also transfer customer revenue and stock per warehouse. We agree on the exact fields with you before the start.

Not always. For many shops, a ready-made connector or an integration platform such as Alumio is enough. Custom development pays off if your Odoo installation is heavily customised or you need special logic for prices, taxes or warehouses. We check this against your data before we develop anything.

Yes. We transfer the stock per warehouse from Odoo and show it separately in the shop, for example with the note "Available in Berlin warehouse". You decide whether to show the quantities individually or as a total.

With delta sync, the integration only transfers products, prices and stock levels that have changed since the last sync. This takes load off Odoo and Shopware 6 with large catalogues and shortens the run time. Sync errors are written to a log so they do not go unnoticed.

Usually Order Management for orders, Inventory for stock and Receivables for invoice and payment status. Oracle Advanced Pricing is added for contract prices. We clarify at the start which modules you use and which data the shop needs.

A platform such as Oracle Integration Cloud or MuleSoft Anypoint bundles the data flows, logs errors and can be monitored. In large system landscapes this is clearer than many direct connections. If you already have a platform, we use it.

Yes. Tax rates such as VAT or GST are applied according to the rules in Oracle EBS. Shop and ERP then calculate the same way, and you maintain the tax logic in one place. We define the countries and special cases in advance.

Yes. Stock per location comes from Oracle Inventory and is shown separately in the Shopware storefront, for example as availability in a specific warehouse. We agree with you on how it is displayed.

Shopware 6 sends orders and customer data to orgaMAX, where you create invoices and delivery notes. orgaMAX reports stock levels and shipping status back to the shop.

Yes, that is one option. In a client project, we connected the order import from Shopware 6 to orgaMAX using the Oscware connector. Whether a ready-made connector is enough or a custom integration fits better, we decide based on your processes.

Yes. Orders from marketplaces such as Amazon or eBay can arrive in orgaMAX as well. We clarify before the project which channels are worth connecting.

No. Pickware is built specifically for Shopware and runs directly in the Shopware 6 admin. Orders, stock levels and payment status share the same database. The effort lies mainly in setting up warehouse, shipping and modules.

Pickware WMS is the warehouse management module of Pickware. It lets you manage stock, goods receipt and picking directly in Shopware 6, including barcode scanners.

Yes, with Pickware POS. In-store sales then also run through Shopware and use the same stock as the online shop. Both channels can be evaluated centrally.

We set up Pickware in Shopware 6: warehouse structure, shipping methods, returns, payment reconciliation and the WMS and POS modules. If further systems such as marketplaces or accounting software are to be connected, we plan the integrations for them.

pixi takes over the order from Shopware 6 and prepares it for dispatch: picking, packing and the shipping label are handled in pixi. pixi then reports the tracking number and the current stock level back to the shop.

pixi synchronises stock levels with Shopware 6 automatically. If goods are sold or booked out on another channel, the available quantity in the shop drops as well. We adjust the sync interval to your product range.

Yes. The return is registered in the Shopware customer account. pixi creates the return label and, once the goods arrive, the credit note, and the status goes back to the shop.

Yes. Orders from Shopware, Amazon, eBay and other marketplaces are consolidated in pixi. The warehouse then works through one shared list.

Both. plentymarkets, now PlentyONE, combines inventory management, order processing, warehouse, marketplace connections and its own shop in one platform. With Shopware 6 as your shop, you use plentymarkets for master data, warehouse and marketplaces, but sell in your own shop through Shopware.

plentymarkets sends products, variants, prices and stock levels to Shopware 6. The shop sends orders and new customer data to plentymarkets. If you wish, we also transfer customer revenue and product group prices. We agree on the exact fields with you before the start.

Yes. The marketplaces stay connected in plentymarkets, and Shopware 6 is added as another channel. All channels draw on the same stock, so a sale on Amazon reduces the quantity the shop displays.

You maintain tiered prices, customer group discounts and product group prices in plentymarkets. The integration transfers them to Shopware 6, and each customer group sees its price after logging in. We agree with you beforehand how product group prices and customer group discounts interact.

No. Plytix is a PIM system (product information management). It manages product data such as descriptions, variants, attributes and images. Orders, warehouse and accounting belong in Shopware 6 or in an ERP, which we can connect in addition.

Plytix sends product details, variants, attributes, images, prices and category assignments to Shopware 6. When you change something in Plytix, the shop picks up the change automatically. We define the exact fields with you beforehand.

Yes. Plytix can supply the same product data to marketplaces such as Amazon, eBay and Google Shopping. Shopware 6 is then one of several channels fed from the same data source.

A PIM pays off when you maintain many products, many variants or several sales channels. A central data source then relieves the team. For small product ranges, maintaining products in Shopware 6 is often enough.

Priority ERP sends products, variants, prices, discount tiers and stock levels to Shopware 6. The shop sends the orders to Priority. If you wish, customer revenue and stock per warehouse location are added. We agree on the exact fields with you before the start.

Yes. You maintain customer group prices, discount tiers and minimum order quantities in Priority ERP. Shopware 6 takes them over and shows every logged-in business customer their terms. Your sales team keeps maintaining prices in one place.

Not necessarily. Middleware such as Synesty pays off when other systems are involved, for example marketplaces. With clear processes, a custom interface can be the more direct route. We decide what suits you based on data volume, special fields and your processes.

Yes. We transfer the stock per warehouse location from Priority ERP and show it in the shop, for example as "Available in Hamburg warehouse". Your customers see before ordering whether and where the goods are in stock.

Sage 100 sends products, stock levels, customer group prices and product group prices to Shopware 6. The shop sends orders to Sage 100. If you wish, we also transfer the total revenue per customer back to the Shopware admin. We agree on the exact fields with you before the start.

Yes. You maintain discounts, special terms and tiered prices in Sage 100. Shopware 6 shows each customer group its prices and checks them when an order is placed. We also transfer prices for entire product groups that sit above the customer group discounts.

Yes. Several shops and sales channels can connect to the same Sage 100 installation. For this we use, for example, the multi-shop interface from intellicon, or we build the integration on the REST APIs. We define the rules per shop together with you.

We transfer the total revenue per customer from Sage 100 to the Shopware admin. You can see which B2B customer is close to a cashback tier or a bonus and plan campaigns accordingly, without exporting reports from the ERP.

SAP Business One sends products with variants, images and prices, stock levels and customer group prices to Shopware 6. The shop sends orders as sales orders including payment status and creates new customer accounts in SAP. Tracking numbers flow back after dispatch. We agree on the fields with you before the start.

Yes. Filters let you decide which products are transferred from SAP Business One to Shopware 6, for example by item status, EAN or stock availability. The sync runs automatically, but you can also trigger it manually when needed.

Yes. We also connect SAP S/4HANA and SAP ERP to Shopware 6. This page covers SAP Business One. For SAP S/4HANA, please get in touch with us directly.

Not necessarily. Depending on your setup, we work directly with the REST API, with a connector such as the one from Firebear or with the iPaaS platform Alumio. The right route depends on your data, the number of shops and your special cases. We clarify this before we develop anything.

Yes. We connect Shopware 6 via the interfaces of your SAP system, such as OData services, IDocs or BAPI calls, and a middleware that translates between both sides. Which interfaces are available in your system is something we clarify with your SAP team before the start.

Yes. SAP ERP also provides interfaces for syncing products, prices, stock levels and orders with Shopware 6. If a move to SAP S/4HANA is planned, we design the integration so that it can be adapted afterwards.

SAP sends products, prices, customer-specific terms and stock levels to the shop. Orders go back to SAP as sales orders, together with new customer data. The integration returns the delivery status to Shopware. We define the exact fields before the start.

Orders go from Shopware 6 to SelectLine and are processed further there. Stock levels flow from SelectLine back to the shop, as do tracking numbers after dispatch. SelectLine creates the invoices. We agree on the exact fields with you before the start.

Yes. You create shipping labels for DHL, DPD and other carriers directly in SelectLine. We then transfer the tracking number to Shopware 6 so that your customers can track the shipment.

Yes. You manage orders from Shopware, Amazon, eBay and other marketplaces centrally in SelectLine. All channels draw on the same stock, so a sale on one channel reduces the available quantity everywhere.

Yes. We have already extended existing SelectLine interfaces beyond the standard without blocking updates. First we check what your current integration can do and which fields or processes are missing.

No. Sync4 by Dupp is integration software. It connects Shopware 6 with an existing ERP and synchronises orders, stock, products and customer data between the two. The ERP remains the system in which you manage stock, customers and invoices.

Sync4 makes sense when your ERP has no Shopware connector of its own or when you want to control the data sync in one central place. If your ERP offers a direct connector, that is often the shorter route. We compare both options based on your data.

Shopware 6 passes orders with customer and invoice data to the ERP. Stock levels, product data and prices flow the other way. We agree on the exact fields with you before setup.

Orders go from Shopware 6 to VARIO 8. Stock levels, prices and shipping data flow from VARIO 8 back to the shop. Customers register returns in Shopware, and the label and credit note are created in VARIO 8. We define the exact fields with you beforehand.

Yes. VARIO 8 creates the invoice and shipping label directly from the imported order. We then transfer the tracking number to Shopware 6 so your customers can follow the shipment.

Yes. VARIO 8 is modular, and every company uses different modules and processes. We set up the integration according to your workflows, for example with custom status fields, several warehouses or special pricing rules.

Yes. Orders from Shopware, Amazon, eBay and other channels can be consolidated in VARIO 8. Warehouse and accounting then work with one shared data set.

Orders go from Shopware 6 to the ERP, while stock levels, prices and shipping data flow back to the shop. Returns are synchronised in both directions. Before the project, we check with you which fields are included and which options VARIO Cloud offers for this.

We include the Shopware 6 integration in the move to VARIO Cloud from the very beginning. We document the existing data exchange, check payment and delivery terms and test the new integration in trial migrations before the shop is switched over.

Not necessarily. A complete switch on a fixed date suits some companies. With many users or several connected systems such as the shop, marketplaces and shipping, a step-by-step approach is often safer. We decide together after reviewing your current setup.

We work very closely with OSKO IT, a strong VARIO partner. Together we support the move from VARIO 8 to VARIO Cloud, with Web Labels taking care of Shopware and the integration.

weclapp sends product data, prices and stock levels to the shop. Shopware 6 sends orders to weclapp, where invoicing and shipping continue. Customer groups and customer-specific prices can be synchronised in both directions. We agree on the exact fields with you before the project starts.

Not for weclapp itself: the ERP runs in the cloud and provides an API. Depending on the setup, the integration runs as a Shopware plugin in your shop installation or as a small separate service. Which option fits depends on data volume and sync frequency.

Yes, with our extension. We transfer each customer's total revenue from weclapp to Shopware 6 and display it in the customer account together with the target for a cashback level. This is useful for regular customers and bonus programmes.

Yes. We transfer the product groups from weclapp to Shopware 6 and assign them their own prices. These product group prices take precedence over customer group prices, so nested pricing logic arrives correctly in the shop.

WinLine ERP sends products, variants, stock levels, prices, discount tiers and customer-specific conditions to Shopware 6. The shop sends orders and return requests to WinLine. We define the exact fields with you at the start of the project.

Not necessarily. The MESOshop connector offers a direct connection. A middleware such as Synesty makes sense when other systems besides shop and ERP exchange data, for example marketplaces or a PIM. We recommend an approach after reviewing your data and processes.

Yes. Customer group prices, discount tiers, product group prices and individual customer conditions are taken from WinLine. Logged-in business customers see the prices your sales team has stored in WinLine.

Customers register the return in their Shopware account. The request is passed to WinLine, where the credit note process is created. Your team checks the goods and closes the return in the ERP without entering data twice.

Shopware 6 sends orders and customer data to Xentral. Xentral returns products, prices, stock levels and, after dispatch, the tracking numbers. We agree on any additional fields, such as custom product attributes, with you before the project starts.

No. Xentral is a cloud ERP, so Shopware 6 and Xentral communicate directly through their APIs. There is no office machine that has to run the sync. If your shop is hosted, we only check that the hosting allows connections to Xentral.

Yes. As soon as you create a shipping label for DHL, DPD or another carrier in Xentral, we write the tracking number to the order in Shopware 6. It appears in the shipping confirmation and in the customer account.

Yes. Xentral collects orders from Shopware 6, Amazon, eBay and other marketplaces in one interface. All channels use the same stock, so a sale on one channel reduces the available quantity everywhere.

GEO (Generative Engine Optimization) prepares shop content so that generative search systems use it as a helpful source. AEO (Answer Engine Optimization) focuses on clear answers to specific questions. For Shopware, this means understandable product information, accessible technology and a credible brand.

We decide together, based on your target group and market, which systems matter, for example ChatGPT Search, Google’s AI Overviews and AI Mode, Microsoft Copilot or Perplexity. Each system selects sources differently, so we check technical requirements and observed answers per platform.

No. Technical accessibility, good content and a clear shop structure remain the foundation. GEO and AEO add answer formats and the monitoring of AI search to this work. Google does not name any additional special optimisation for AI Overviews and AI Mode.

No. The AI system decides on mentions, wording and sources, and answers change with the question, context and timing. We improve verifiable prerequisites and evaluate how things develop. Rankings or revenue cannot be guaranteed from this.

A plugin or an additional text file does not replace helpful content and clean product data. Google’s AI search features require neither special AI files nor a particular schema. Whether an extension makes sense depends on the specific task in your shop.

No. OpenAI distinguishes between the search crawler OAI-SearchBot and the training crawler GPTBot, and both can be controlled separately. You can allow search access and still block crawling for model training.

We separate observed mentions, linked sources, identifiable website visits and measurable enquiries or purchases. Bing Webmaster Tools reports source citations for supported AI services. Google includes visits from its AI search features in the performance report in Search Console.

The scope depends on your product range, existing content, data quality, markets and technical implementation. In an initial call we clarify your goals, and you then receive a quote with clearly defined services. Many start with key categories and selected product groups.

We check new content and technical changes directly after implementation. When search services process them and take them into account in answers varies. We therefore agree on monitoring intervals and assess progress across several samples.

Shopware PageSpeed optimisation looks at the entire delivery: images, fonts, CSS, JavaScript, third-party services, theme, cache, server responses and the Shopware configuration. What matters are the causes behind LCP, INP and CLS on the most important page types, rather than individual scores.

The Media Booster compresses and resizes images in Shopware, creates WebP and AVIF versions depending on server support and can process existing media in bulk. It also maintains alt texts, titles and SEO-friendly file names. The original files are kept.

No. Smaller images mainly improve the loading phase but do not fix slow server responses, blocking JavaScript, heavy third-party scripts or layout shifts. Image optimisation is an important building block, but it does not replace the rest of the PageSpeed work.

Agentic Browsing is a new Lighthouse audit category that checks for an llms.txt, a well-structured accessibility tree and, for interactive applications, registered WebMCP tools, form coverage and valid WebMCP schemas. We assess these points separately from the classic performance score.

Google has not made any statement on this so far. Agentic Browsing is a new Lighthouse audit category for usability by AI agents, not a new Core Web Vital. We therefore only implement measures that make professional sense for the shop in question.

Lab values fluctuate due to server load, network conditions and third-party services. We therefore compare several measurements and different page types and include real field data where available. A single test run is not a reliable basis for decisions.

We start with a short performance check of the most important page types. You then receive a prioritised assessment: which issues can be solved quickly, where the Media Booster helps and which changes to the theme, plugins, hosting or Shopware are also needed.

Structured data describes content in a standardised format, usually as JSON-LD, so that search engines recognise the product, price, availability, rating or breadcrumb path. Rich snippets are enhanced displays in the search results that can be based on such data.

No. Correct structured data creates the technical prerequisite but does not guarantee a special display. Google decides whether and how an enhanced search result appears. Content, guidelines, data quality and the search query also play a role.

The plugin adds Product, Offer, BreadcrumbList, ItemList, Organization, FAQPage and HowTo data as JSON-LD. It also includes features for canonicals, pagination, hreflang, indexing control and optional AI feeds. This largely covers the recurring technical tasks in typical Shopware 6 setups.

A plugin cannot replace missing or incorrect product data. Individual work often remains for data maintenance, special variant logic, conflicts with the theme and plugins, differing sales channels and choosing the right markup. We check and solve these points to suit the shop.

Product and category pages come first. Company data, breadcrumbs, visible FAQ sections and genuine step-by-step guides can also be marked up. The schema type must always match the visible content and the purpose of the page.

We first check representative products, categories and existing markup. We then clarify what the plugin covers directly and where adjustments are needed. You receive a clearly defined scope for setup, corrections and validation.

Both. Web Labels creates a prioritised SEO roadmap and implements the technical measures directly in Shopware, in the theme, in plugins and in the infrastructure. Analysis and implementation are therefore handled by one team.

Yes. We take over existing Shopware 6 setups, review custom themes and extensions and improve the shop step by step. In most cases, a relaunch is not necessary.

Yes. We analyse the mobile and desktop views and optimise images, frontend, Shopware configuration, plugins and hosting. Which values are realistic depends on the individual shop, so we do not promise a fixed score in advance.

Not automatically. We first check what reserves there are in the code, cache, database and configuration. Only then can you decide economically whether additional hardware really helps.

Tools deliver measurements, not decisions. In a Shopware SEO audit, we combine crawling, rankings and performance with your actual Shopware setup, assess the causes and turn the findings into a prioritised roadmap.

An SEO audit is worthwhile for existing Shopware 6 shops, before a relaunch or migration and when visibility is stagnating. It is particularly helpful when many individual measures are being discussed but a clear order of priority is missing.

That depends on the agreed scope. Access to or exports from Google Search Console, Analytics and existing SEO tools are particularly helpful. For deeper technical checks, we agree access methods with you that carry as little risk as possible.

The duration depends on the size of the shop, the number of sales channels and markets, variants, custom plugins and the desired scope. After a brief review, we give you a binding schedule.

Yes. Our SEO team works directly with Shopware development, content, UX and hosting. On request, we therefore implement technical and content measures from a single source.

Technical SEO optimisation ensures that search engines crawl a Shopware 6 shop efficiently, recognise relevant URLs and index the right pages. This includes canonicals, status codes, redirects, URL structure, sitemaps, robots.txt, internal linking and the handling of variants and filters.

That depends on the individual shop. Variant and filter URLs, the canonical configuration, redirects after URL changes, unnecessarily indexable parameter pages, internal linking and side effects of themes and plugins are frequently affected.

Yes. Web Labels combines SEO with in-house Shopware development. We therefore implement many technical optimisations directly in the Shopware system, in the theme or through custom adjustments.

No. Large shops in particular should separate relevant SEO landing pages from technically generated URLs. Filters, parameters, internal search pages and certain variants do not need their own place in the Google index.

Yes. Smaller shops also lose visibility through incorrect canonicals, faulty redirects, weak internal linking or indexing problems. The larger the shop grows, the more important a controlled technical structure becomes.

Partly: we always take the overlaps into account, but performance and Core Web Vitals are a separate, extensive topic. We therefore treat detailed Shopware PageSpeed optimisation as a separate module.

ChatGPT Ads are paid ads that ChatGPT shows in relevant conversations about products, services or problems. The ad is clearly separated from the actual answer and labelled as advertising. Businesses get an ad placement right in the middle of their customers’ research.

Yes. Businesses in Germany set up and manage their campaigns in the OpenAI Ads Manager. If you would rather not deal with it yourself, Web Labels takes care of setup and ongoing management.

ChatGPT looks at the whole conversation, not only individual search terms as in classic search advertising. What matters is what the user is talking about and what they want to achieve, for example comparing a product, finding a provider or solving a problem.

Google Ads usually starts with a search query or keyword, while in ChatGPT users often describe in more detail what they need. An ad can therefore match the current question more closely. The two channels complement each other.

Yes. We set up tracking so that you see not only clicks but also whether they lead to an enquiry or an order. We use this data to keep optimising the campaigns.

ChatGPT Ads suit products and services that people ask questions about, compare alternatives for or seek advice on. This applies to online shops as much as to B2B companies and service providers.

No. Web Labels handles setup, campaign structure, ads, budget management, reporting and ongoing optimisation. Instead of a dashboard full of jargon, you get a clear explanation of the results.

In our experience, an AI-assisted prototype costs around 20 percent of classic software development (not a guarantee for your project). The reason is that the focus is on functions, processes and data flows, not elaborate design, perfect architecture or scaling. You can test an idea early and avoid costly mistakes.

The first working functions are usually ready in the first week after the project starts. With AI tools and clearly structured processes, we quickly deliver prototypes for web-based software, integrations, platforms or automations.

Prototypes get a basic security concept that is sufficient for internal use and testing. Many initially run on the intranet, locally or in protected environments. If the solution is to be publicly accessible or process sensitive data, our senior developers secure it thoroughly beforehand.

Yes, and that is the biggest advantage of the approach. After validation, the prototype can be extended step by step, technically optimised, moved to a scalable architecture or rebuilt if needed. The insights from the prototype save time and budget.

Yes, as long as experienced developers stay in control. AI-assisted development is now suitable for most digital projects, including in continuous operation. What matters is less the tool than the review by qualified developers who focus on stability, maintainability and data security.

With machs mit kAI, you translate even large volumes of product texts much faster than by hand. Depending on scope and data quality, the first translations are ready within a few minutes. This saves a lot of time, especially with many products and variants.

Yes. Existing texts and product information serve as the basis. The translations are therefore guided by your existing content, the product attributes and the structure of your shop.

Yes, it pays off especially with large product ranges. Instead of editing each product individually, you prepare large amounts of product data in a structured way and make them available in further languages more quickly.

Yes. Multilingual product content is an important step towards reaching international audiences. With machs mit kAI, you make shop content available in further languages more quickly and prepare new sales channels or markets more efficiently.

A multilingual shop reaches new target groups and international markets. People who read product information in their own language trust the shop more, find their way around more easily and often decide to buy faster.

The product advisor runs on Claude by Anthropic. Search and chat use the same index, which Minofinder fills automatically from your shop. Recommendations therefore come from your real catalogue, with the prices and stock levels from the shop.

In the shop, search and chat work in German, English, French, Turkish and Danish. One language is included in the package, and each additional language adds a surcharge to the monthly price. The admin interface is available in German and English.

Running Modiva costs €29 per month plus VAT. This includes hosting, your domain and your email, as well as daily backups and system maintenance. There are no further running costs.

The website itself is built within a few hours. When it goes live depends mainly on how quickly we receive your information and approval. We agree a go-live date with you in the first conversation.

If laws relevant to websites and subject to EU law change, we update the affected features free of charge. These updates are already included in the €29 per month, with no additional costs.

Yes, absolutely. You replace texts and images yourself and extend, add or delete content in the Modiva CMS. You create new pages at the click of a button, in several languages too.

No. Every customer receives an individual, unique design and their own personal web presence. Only the system behind it stays the same: our Modiva CMS. This combines your own design with technology that we maintain centrally for all customers.

Modiva is a system developed in-house by Web Labels. It produces complete company websites with texts and images in a few hours instead of weeks. You do not get a website builder but a finished website from us.

A regular host mainly provides the infrastructure, while a Shopware hosting agency also looks at the application: Shopware configuration, PHP, caches, Redis, Elasticsearch, database, plugins and real page types. This makes it easier to separate cause and effect in performance problems.

No. We work with various hosting providers and also optimise existing environments. If a move makes sense, we also offer our own servers, which we have been tuning for Shopware, Laravel and WordPress for several years.

Redis is a very fast in-memory store. Depending on the Shopware version and architecture, it is used for the cache, sessions or queues. What matters is the correct connection, a suitable storage strategy and checking whether the shop is actually relieved.

OPcache stores precompiled PHP bytecode so that PHP does not recompile the same code on every request. APCu is a fast local store for suitable application data. Both serve different purposes and are configured to suit the application and the available memory.

NVMe storage is used because database queries, search indexes, cache files, logs and deployments generate a large number of read and write operations. Current NVMe drives offer very short access times and high data rates. They are therefore the technical basis of our new performance servers.

No one can seriously promise a loading time of zero, because the theme, images, third-party services, device and internet connection all play a part. Our goal is very short server responses and a shop that feels instant. We optimise everything we can influence and make the results measurable.

Yes. Alongside Shopware, our own servers and their configuration are also designed for Laravel and WordPress. We always set up PHP, cache, database and web server to suit the application.

ShopSignal monitors availability and response times, SSL certificates, the server with CPU, RAM, disk, PHP-FPM, MySQL and Redis, the message queue and the error logs. It also tracks SEO values from PageSpeed, Search Console and Bing, as well as revenue and orders. From this, ShopSignal calculates a health score per shop.

No. You install the ShopSignal Connector plugin from the Shopware Store for each shop. It sends signed data to ShopSignal via TLS. No additional agent runs on the server, and we do not need SSH access.

No. ShopSignal supports Shopware 6 in versions 6.5 to 6.7. If your shop still runs on Shopware 5, we are happy to advise you on migrating to Shopware 6.