E-commerce
Import the manufacturer catalogue into your own shop, load the 3D configurator on your own product page, and let what the customer configured arrive as a real order line: article number, variant code, price, component SKUs, render and a reopen link. A plugin in the shop you already have, not an integration project.
MANUFACTURER|C4|C4-210
Meta-properties
Miscellaneous
Three things, inside the shop you already run.
Browse the real manufacturer catalogue in your own admin, tick what you want and import it. Title, specification table, price, the render as product image, and brand and series as filterable attributes. Articles the manufacturer marks as not orderable are skipped, with a line in the error list saying why.
The pCon configurator loads in an iframe on your own product page, on your own domain, with your catalogue and your prices. No separate configurator site, no second checkout, and nothing for the visitor to install.
One cart line carries the configured price and the full specification, with the component SKUs listed underneath it for purchasing. Reconfiguring reopens the exact same configuration rather than starting over.
Three answers, all of them checkable in the code they install. The full architecture is on the home page.
The catalogue import runs server to server behind a per-customer secret bound to one domain. The configurator in the browser is authorised by domain whitelist only. Two separated worlds, no shared credential.
What comes back out of the configurator carries an HMAC token that your shop verifies before anything touches the cart.
The configurator signs the price and your shop checks that signature against the public key of EasternGraphics. Without it, a desk of €10,165 goes into the cart for €1. We measured that on our own demo. The check is on by default, and the only reason to switch it off is an instance that carries no prices at all.
The pCon side is identical on both. Only the platform glue differs: settings storage, cart and order hooks, product attributes.
Available now
In development, and you can put your name down
These do not ship yet and they carry no date. Each has a page that says where it stands, because enough interest is what decides which adapter gets finished first.
You keep it with EasternGraphics or their distributor. The gatekeeper the server-side import runs on is the same instance with a _wcfsuffix and comes with that same licence, so there is no second licence to buy. Worth confirming for your own contract, but it is the normal arrangement.
And that have shared their catalogue with your account. If your manufacturers are European furniture makers it very likely already exists. If it does not, there is nothing to import, and we will tell you before you pay anything.
WooCommerce or Magento 2 today. No build step on the WooCommerce side, a normal module on the Magento side, and your own agency can read both before installing.
One step is not instant, and we would rather say so here. EasternGraphics whitelists the domain your configurator runs on by hand: one live domain plus two development domains, no wildcards, every subdomain separately. You set everything else up yourself, and the portal reads the real whitelist status straight from EasternGraphics.
That is the question that decides it. If you do, tell us which shop or ERP you run and you hear what we can connect, what it takes and what it costs. If you do not work with pCon yet, you are early: that conversation starts at EasternGraphics, not with us.