A draft order
The configuration becomes a draft order with free line prices, and the customer checks out from there. It works on any plan, and it holds the exact configured price.
In developmentTell us you are on Shopify and you set the order
Shopify
A pCon product configurator for Shopify
The same thing our WooCommerce, Magento and Shopware adapters do: your manufacturer catalogue imported into the shop, the 3D configurator on the product page, and every configuration landing in the order with its own price. For Shopify it is in development, and there is no date on it. What decides the date is a shop that needs it.
Most of it is already built
An adapter is not a product from scratch. The part that talks to pCon is the same for every platform and runs in production today for three of them:
- The connector that holds the EAIWS session and reads the manufacturer catalogue, with the catalogue, article and enrich endpoints behind one key
- The gate that authorises per customer and per domain, counts connections and serves the central configurator settings
- The OCI contract: reading what the configurator posts back, including the group of articles under one configuration
- Verifying the price signature from EasternGraphics, so nothing reaches a cart that pCon did not sign
- The update channel, with the package checksum verified before it installs
What a new adapter adds is the platform glue: where settings live, how a product page is extended, and how a line gets into that platform's cart. On Shopify that last one is the interesting part.
What is specific to Shopify
Shopify derives a line price from a variant. A configured desk has a price that no variant holds, so the price has to be set on the line itself. The clean way to do that is the Cart Transform Function, and Shopify's own documentation limits its update operations to development stores and shops on Plus, checked on 2 November 2026. In this segment almost nobody is on Plus, so an adapter that only works there would be an adapter for nobody.
That is the one thing worth knowing before anyone promises you a Shopify configurator, ours or anyone else's. It is also why this page says in development instead of showing you a price.
The choice being made
Two routes, and they are not equal
Both work on every Shopify plan. Each costs something, and which one we pick decides what the adapter feels like, so we would rather pick it with a real shop than in the abstract.
A variant per configuration
Add to cart creates a variant with the configured price and puts that in the cart. The shopping experience stays exactly as it is.
What moves this forward
A day on a real store decides it
Before anyone can give you a date, both routes need a real configuration driven through a real store. Not a demo article: a desk with accessories, the kind that makes an integration honest.
What we bring
- The connector, the catalogue import and the price verification, already running
- The measurement itself: does the configured price reach the checkout unchanged, does the reopen link survive on the order line, and what happens when the shop changes domain
- The adapter, once the route is picked
What you bring
- A Shopify development store, which is free
- Your pCon setup: which instance you have and what it is allowed to do
- One real article you want configurable, with its accessories
When it ships it joins the same list as the other e-commerce adapters, priced per shop. What the others cost.
Are you on Shopify?
Then you decide when this gets built. Tell us which brands you sell and we will tell you straight whether the data exists and what the cart can do.