WooCommerce connection
- Catalogue import and the configurator
- Plugin updates and support
- Staging environments are free and labelled as such
WooCommerce
A WordPress plugin that imports your manufacturer catalogue from pCon, loads the 3D configurator on the product page, and writes what the customer configured into the WooCommerce order. It installs like any other WordPress plugin, with no build step and no custom development.
This is the part that decides whether a configurator is a toy or a sales tool. Per configured line, WooCommerce receives:
A normal WordPress plugin, no build step. You paste the key you created in the portal and the connection registers itself.
Browse the manufacturer tree in WP Admin, tick articles and import them as WooCommerce products: title, specification table, price, the render as product image, and brand and series as attributes you can filter on.
Nothing is hard-coded into the product. The page builds the configurator URL at render time from the article reference and the gatekeeper your account holds centrally, so changing instance is a setting and not a data migration.
The configurator posts the OCI fields to a signed webhook on your own shop. The plugin verifies the token, verifies the price signature, imports the render and drops the visitor in the cart.
What it asks of your environment: WordPress with WooCommerce, on PHP 8.3 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.
The plugin is not on wordpress.org, so it has its own update channel. New versions show up in your WordPress updates screen like any other plugin, and the package is checksum-verified before it installs. There is no licence key in the plugin, no countdown and no kill switch: if a subscription lapses the plugin tells the administrator and the configurator keeps working.
You need a pCon.ui instance of your own from EasternGraphics, and they need to whitelist your shop domain by hand. That is one live domain plus two development domains, no wildcards, and every subdomain listed separately. 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.