A button on the quotation
Configure in pCon opens pCon.basket Online in a dialog inside Odoo. No second application to alt-tab to, and no separate login for the salesperson to remember after the first time.
Odoo
An Odoo module that opens pCon.basket Online straight from the quotation, carrying the customer you already filled in. The configured items come back as quotation lines, and the whole project stays attached to the order so a revision reopens exactly what was configured.
| Description | Qty | Unit price | Total |
|---|---|---|---|
pConDesk 1800 x 800, oak, RAL 7016
| 8 | 1.284,00 | 10.272,00 |
| Delivery and assembly | 8 | 180,00 | 1.440,00 |
It does not replace anything. Quotations, pricing, margins and approvals keep working the way your company set them up.
Configure in pCon opens pCon.basket Online in a dialog inside Odoo. No second application to alt-tab to, and no separate login for the salesperson to remember after the first time.
The items come back as real lines with quantity and unit price, each carrying the article number and the configuration that produced it. Reopening replaces those lines instead of adding a second set.
The full pCon project is stored on the quotation as an attachment, so a revision next week and a reorder next year both start from what was actually configured rather than from scratch.
The point of the integration is that the salesperson types the customer once and the configuration once, and never again.
The customer number, the sold to, ship to and bill to addresses, the quotation reference as project name and number, and the note on the quotation as the footer text. The basket opens with all of that already filled in, so nobody retypes an address into a second system.
The company logo and the colours configured in Odoo are applied to the basket theme. For a dealer who puts a salesperson in front of a customer with the screen turned around, that matters more than it sounds.
The real manufacturer catalogue, the real prices and the full basket behaviour your team already works with. This is the actual pCon product, not a reduced imitation of it.
Title and article number on the first line of the description, the chosen configuration underneath it, then quantity and unit price in the normal columns. If the basket priced something in another currency than the order, the line says so instead of quietly converting it.
Per configured item, Odoo receives:
The lines land on one generic item, deliberately. A configured composition is not a product in your catalogue and pretending otherwise would fill Odoo with thousands of one-off article records. The article number of the real manufacturer article travels on the line itself, so purchasing still has what it needs to order.
Architecture
Worth checking before you install anything in an ERP, so here it is in the open.
The bridge itself knows nothing about Odoo. It speaks one documented message contract, and everything ERP-specific sits in a thin adapter on the page that hosts it. That is why a second ERP is an adapter and not a second product. Why that matters if your ERP is not Odoo.
These are two separate products on two separate pCon licences. Taking one does not give you the other, and we would rather be blunt about that now.
Licensed per named user, and it refuses anonymous sessions. The number of seats you license is the number of people who can configure at the same time, so it is a real cost and worth sizing before you start.
The module depends on nothing beyond standard Sales, and it is built for Odoo 19 Community. Running something older or something customised heavily is not a no, but it is a conversation rather than an install.
pCon.basket brings its own catalogue, so this product does not use the server-side import, the domain whitelist or the OCI punchout that the webshop product runs on. Fewer moving parts, different licence.
No licence key, no countdown, no kill switch. Updates are part of the subscription and they stop when it does. What is installed keeps working either way: there is nothing in the module that can switch your quoting off.
On quotation, so both amounts are floors rather than prices: never less, and higher where your installation asks for more.
Why there is no price list here. Because there is no standard Odoo. The version you run, whether it sits on Odoo.sh or your own hosting, how much your quotation flow has been customised and which pCon.basket licence you hold all change the work. A published monthly rate would promise a fixed scope that does not exist. One call about those four things and you have a fixed amount in writing.
All amounts exclude VAT and exclude the pCon.basket licence you hold with EasternGraphics. Implementation is higher than on the webshop side because this product touches your quotation process, and that is never a copy and paste job. There is no trial period.
Tell us the version, whether it is Community or Enterprise, and how your sales team configures today. You get a straight answer about what installing this looks like on your database.
Or write to info@bewisesolutions.com