Shopware 6
A Shopware plugin that imports your manufacturer catalogue from pCon, loads the 3D configurator on the product page, and writes what the customer configured into the order. It installs through Composer like any other plugin, and it needs no build step on your server.
This is the part that decides whether a configurator is a toy or a sales tool. Per configured line, Shopware receives:
Every configuration is its own line. Two desks built from the same product stay two lines with two prices, which is the difference between an order you can fulfil and one someone has to phone about.
A private Composer repository, added to your project once. After that it is a normal plugin: refresh, install, activate. You paste the key you created in the portal and the connection registers itself.
Browse the manufacturer tree in the administration, pick articles and import them as Shopware products: title, specifications, price, the render as product image, the features as properties you can filter on, and the brand as a real manufacturer.
Nothing is baked into the product. The page builds the configurator URL at render time from the article reference and the instance your account holds centrally, so changing instance is a setting and not a data migration.
The configurator posts the OCI fields to a signed route on your own shop. The plugin verifies the signature, verifies the price, imports the render and puts the visitor in their own cart with the configuration on the line.
What it asks of your environment: Shopware 6.7, self hosted rather than on Shopware Cloud, on PHP 8.2 or newer, and max_input_vars raised to 5000. That last one is a hosting setting rather than a plugin setting, and it is what decides whether a configuration of twenty articles or more can reach the cart in one piece.
Architecture
Worth being precise about, because it decides what an update costs you later. No core changes, no replaced templates, nothing that a Shopware agency has to take on faith.
A cart processor puts the configured price back on the line at every recalculation, in the tax state of that cart. Shopware recalculates on every page view and once more when the order is placed, so this is the difference between a price that holds and one that falls back to the catalogue.
The article reference and the manual URL override are custom fields on the product, created when the plugin installs. Visible in the administration, editable by hand, and gone again when you uninstall.
Features become properties, so filtering works on the configuration options themselves. The brand becomes the manufacturer entity Shopware already has, instead of a category pretending to be one.
The administration bundle ships compiled and Shopware builds the storefront styling in PHP, so there is no Node on your production machine and nothing to rebuild after an update.
Performance and trust
Shopware caches product pages, and that cache is a large part of why the shop is fast. A configurator should not be the reason you give it up.
The import runs server to server behind a key that never reaches the browser, the configurator is authorised by a domain whitelist, and add to cart carries a signature your own shop verifies. Those are three separate channels that never share a credential. How that is put together.
The plugin is not in the Shopware Store, so it has its own channel: a private Composer repository you add to your project once. After that composer outdated lists new versions and composer update installs them, like any other package, and Composer verifies the checksum before it unpacks anything.
The download address deliberately does not expire. Composer writes it into your composer.lock, and a link that died after a day would break the deploy you run next month from a lock file you committed today. There is no licence key in the plugin, no countdown and no kill switch: if a subscription lapses the plugin says so to the administrator and the shop keeps selling.
You need a pCon.ui instance of your own from EasternGraphics, and they need to whitelist your storefront domain by hand. That is one live domain plus two development domains, no wildcards, and every subdomain listed separately. Ask them for a shop instance rather than a lead instance: a lead instance has no add to cart button, so nothing can reach your shop. Your manufacturers also need to publish OFML data and have shared their catalogue with your account. If you are not sure whether they do, that is exactly the question to put to us.