Documentation
Written for the two people who have to live with this: whoever runs the shop or the quotations, and whoever maintains the installation. It covers what the pieces are, what to arrange and in what order, every setting and what it actually changes, and what a given symptom usually means.
pconnector is two products that share a connector and almost nothing else. They run on different pCon licences, authorise in different ways, and the manuals have little in common. Picking the wrong one wastes an afternoon.
On pCon.ui
You import the manufacturer catalogue into your own shop and the customer configures on your product page. WooCommerce, Magento 2 and Shopware 6.
On pCon.basket
Your salesperson configures from inside the quotation and the items come back as quotation lines. Odoo today.
What OFML is, what pCon.ui and pCon.basket are, what a gatekeeper does, and who supplies which part. Read this once and the rest reads faster.
Three channels that each match their platform, what a published release can and cannot do afterwards, and what happens when a subscription lapses.
Symptom first, then what it usually is. Most of these look like a bug in your own configuration and are not one, which is exactly why they cost time.
This is a manual for running the integration, not a specification for building one. The internals stay out on purpose: the call sequence the connector makes to EAIWS, how the webhook token is composed and verified, the field by field shape of the catalogue endpoints, and the message contract the ERP bridge speaks. Those exist and they are documented, they are just not published.
If you are building an adapter for a platform we do not cover yet, that material is what you get under agreement, and it is a real conversation rather than a brush-off. The three contracts are versioned, their shapes are pinned by tests, and every answer carries the version it was built against, so an adapter can tell when the ground moved under it.
What you will find here instead is everything you need to operate, diagnose and maintain a connection without us in the room, which is the part that actually decides whether this is pleasant to own.
Current contract versions. Catalogue catalog/1, bridge bridge/1, updates updates/1. Every gate response carries its version in a header. Fields may be added within a version; renaming or removing one means a new version. These numbers are read straight out of the running configuration when this page is built, so they cannot quietly fall behind.
If you went looking for an answer here and did not find it, that is a gap worth hearing about. It is usually faster to fix the page than to answer the same question twice.
Or write to info@bewisesolutions.com