Odoo
€499per month, from
ERP
Your salespeople already configure in pCon. Stop retyping it into the quote.
pconnector embeds pCon.basket Online in the quotation screen of the ERP you already run. Configure from the quote, get the items back as quotation lines, and reopen the exact configuration when the customer changes their mind. Connecting an ERP to a configurator is normally a custom project. Here it is an adapter on a contract that already exists.
SO-2041Draft
Open in pCon.basket| Description | Qty | Unit | Total |
|---|---|---|---|
pConDesk 1800 x 800, oak, RAL 7016
| 8 | 1.284,00 | 10.272,00 |
| Delivery and assembly | 8 | 180,00 | 1.440,00 |
Total excluding VAT€ 11.712,00
- Opens
- pCon.basket Online
- Returns
- quotation lines
- Stored as
- OBK
- Reopen
- from the quote, any time
What this replaces
Not a missing configurator. Your sales team almost certainly has one already, and the problem is what happens after they close it.
The desktop round trip
- The salesperson configures in pCon.basket on their own machine
- They export a PDF, or a file, or a screenshot
- They retype the lines and the prices into the ERP quotation
- The quote and the configuration are now two unrelated things
- A revision means doing the whole thing twice
- Nobody can tell from the ERP what was actually configured, so the reorder a year later starts from scratch
With pconnector
- The configurator opens from the quotation, carrying its context
- The items come back as quotation lines, priced
- The component articles land underneath the line, for purchasing
- The configuration is stored on the line itself
- A revision reopens exactly what was configured
- So does the reorder, a year later
How it works
Four steps, none of which asks your sales team to learn a new configurator. They already know this one.
The quotation opens the bridge
A button on the quotation opens pCon.basket Online in a panel, carrying the context of the quote it was opened from. No separate application, no separate login for the salesperson to remember.
They configure in pCon.basket
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.
The items come back as quotation lines
Description, article number, quantity and price per line, with the component articles listed underneath so purchasing can order against them. Your ERP keeps doing the pricing, margins and approvals it already does.
The configuration travels with the quote
It is stored on the line as an OBK, so reopening gives back exactly what was configured. That is what makes a revision cheap, and what makes a reorder a year later possible at all.
The bridge does not know what an ERP is
This is the part that decides what a second ERP costs, so it is worth being precise about.
- Your ERP
- Thin adapter
- The bridge
- pCon.basket Online
The browser component that talks to pCon.basket knows nothing about Odoo, or about any other ERP. It speaks one documented message contract: open with this context, here are the items back. Everything ERP-specific sits in a thin adapter on the page that hosts it, and that adapter does three things: open the panel, receive the items, write the lines.
Odoo is the reference adapter and it ships today. A second ERP is an adapter against a contract that already exists, not a second product to build, which is the difference between a project measured in weeks and one measured in quarters. If your ERP is not Odoo, that is the conversation to have, and it is a realistic one.
Which ERP systems
One adapter ships today. The rest is a list you can put yourself on, and that list is how we decide what gets built next.
Available now
Planned, and you can put your name down
These do not exist yet and they carry no date. Registering counts for something: the bridge is already ERP-neutral, so what decides the order is demand rather than difficulty. Tell us which one you run and you hear about it before anyone else.
What you need, and how it differs from the webshop product
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.
A licensed pCon.basket gatekeeper
Unlike the webshop configurator, this one is licensed per named user and 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.
A pCon.login client
The salesperson signs in interactively the first time, and the session is reused after that. No shared credential sits in your ERP.
No catalogue import needed
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.
Running both is deliberately possible. A dealer who sells online and quotes from the back office can take both products, on two subscriptions, and they meet in the same connector. That is the only place they touch: there is no shared credential and no shared session between them. The webshop product is here.
What it costs
This side goes on quotation, so the two amounts below are floors rather than prices: never less, and higher where your installation asks for more.
The connection, per month
€499per month, from
- The bridge and the adapter for your ERP
- Updates and support
- A test environment at no extra cost
Implementation, one off
€3,500from
Why there is no price list on this side. Because there is no standard installation to put one on. Which ERP version you run, who hosts it, whether 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, and you would be the one finding that out. You get a fixed amount in writing after one call about those four things.
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 reaches into your quotation process, and that is never a copy and paste job. There is no trial period.
Which ERP do you run?
If it is Odoo, there is an adapter waiting. If it is something else, tell us what it is and we will tell you honestly what building the adapter looks like.