B2B commerce platforms for medical technology.
One platform connects product data, pricing, content and customer accounts.
Reorder from your last order
Order 2026-0318 · 4 items · delivered 14 Mar
Representative example — customer, articles and prices are illustrative.
Your products are already described in the PIM, priced in the ERP and sold by people who know them. The shop should not be a fourth place to maintain all of that.
Follow one product through the system.
Every system keeps the job it is good at. The platform moves one record between them, so nothing is typed twice and nothing drifts out of sync.
- PIM
- ERP
- CMS
- Shop
- Portal
- Name & description
- Technical data
- Images
- Instructions for use
- Classification
- List price
- Customer price
- Stock & lead time
- Packaging unit
- Country availability
- Localized page
- Related products
- Application content
- Campaign placement
- Your price
- Your availability
- Quantity & unit
- Add to order
- Order history
- Reorder
- Invoices & delivery notes
- Documents per product
- Users & roles
The product is described once.
Product management and marketing maintain name, description, technical data, images and documents in the PIM. That is the only place they are edited.
- Name & description
- Technical data
- Images
- Instructions for use
- Classification
Source of truth forEverything descriptive
The commercial facts are attached.
List price, customer-specific prices, stock, packaging units and country availability come from the ERP. Nothing commercial is maintained in the shop.
- List price
- Customer price
- Stock & lead time
- Packaging unit
- Country availability
Source of truth forPrices, stock, customers, orders
The page is built from both.
Editors add context — application content, related products, campaign placement, localized copy. They don’t re-enter a single data field.
- Localized page
- Related products
- Application content
- Campaign placement
Source of truth forPages, campaigns, localization
The customer sees their version.
A logged-in buyer sees their own price, their availability and their packaging units. A guest sees the catalogue. Same page, different data.
- Your price
- Your availability
- Quantity & unit
- Add to order
Source of truth forCatalogue, cart, checkout
The order becomes part of the account.
Orders flow back into the ERP with customer number, delivery address and reference. The portal is where the customer returns: history, reorder, documents.
- Order history
- Reorder
- Invoices & delivery notes
- Documents per product
- Users & roles
Source of truth forAccounts, history, documents
One record. Connected platforms. Customers who order themselves.
For customers, for sales, for the people maintaining the catalogue.
Customers
Order without calling.
- See their own price and availability
- Reorder from history in two clicks
- Download instructions for use and certificates per product
- Several users per account, with buyer and approver roles
Sales
Stop re-typing orders.
- Portal orders land in the ERP as ERP orders
- See what each account orders and browses
- Quotes for non-standard requests stay possible
- More time for the conversations that need a person
Marketing & product management
Maintain a product once.
- Edit in the PIM; every page and market updates
- Launch a product page without a developer
- Localize from structured data, not from copies
- Campaign pages link to products people can buy
The details that make medical B2B different.
These are the points where a standard shop template runs out — and where most of the integration work actually goes.
Country-specific availability
A product registered in one market and not in another is shown, or not, depending on the customer’s country — driven by the ERP, not by a manual list.
Documents travel with the product
Instructions for use, declarations of conformity and certificates are attached in the PIM and available in the portal, per version and per language.
Customer-specific terms
Contract prices, discount groups, payment terms and minimum quantities come from the ERP and are never maintained a second time.
Accounts with structure
Hospitals and distributors have buyers, approvers and administrators. The portal models that instead of sharing one login across a department.
Orders go back where they belong
Every portal order becomes an ERP order with customer number, delivery address and order reference. No re-keying, no second order list.
Distributors get their own view
Own terms, own countries and, where you want it, own users — on the same platform, without a second shop.
Your solution. Your infrastructure. Your data boundary.
Before implementation, we agree hosting, access and data flows with your IT, security and privacy teams.
Runs in your environment
Deploy in your cloud tenant, an agreed EU region or on premises where the stack supports it.
Your systems remain the source of truth
We connect the required parts of your PIM, ERP, CRM, QMS or document system.
No dependency on Veren or one model
You receive the code, configuration and documentation. Models and providers remain replaceable.
Data protection is part of the architecture
Data classes, access, retention and transfer paths are defined before implementation.
See regulated delivery
A customer portal and shared commerce workspace for Geuder.
Geuder develops instruments and solutions for ophthalmic surgery. Its products combine measurable performance, surgical workflows, interfaces and configurable hardware.
We connected product and process data in a central workspace so sales and marketing can maintain information without moving between PIM, ERP and CMS interfaces.
AI prepares CMS changes and structures B2B enquiries for further work. The same structured context supplies the customer portal, the VIVOS Product Story and an interactive 3D experience.
The first rule of any technology used in a business is that automation applied to an efficient operation will magnify the efficiency. The second is that automation applied to an inefficient operation will magnify the inefficiency.Bill Gates
Integration first, storefront second.
That is why the visible shop is the smallest part of the work. What decides whether the platform holds up is which system owns which field, and how the record moves between them.
System map
Which system owns which field today. The honest answer is usually “three of them” — that is what we fix before anything is built.
Data contract
One definition per field: where it lives, where it flows, how often, and what happens on conflict. Written down, agreed with IT and sales.
Connected platform
PIM, ERP, CMS, shop and portal wired together on a structured content model — launched market by market, not all at once.
Handover and growth
Your team maintains products, pages and accounts without us. We stay for the next market, the next product line, the next integration.
The practical part.
Does this replace our ERP or PIM?
No. Both stay, and both stay in charge of their data. The platform reads from them and writes orders back. If you don’t have a PIM yet, we help choose one — or model the product data in the CMS until you do.
Which ERP and PIM systems do you connect?
SAP, Microsoft Dynamics and most mid-market ERPs with an API or a scheduled export. On the PIM side Akeneo, Pimcore and custom product databases. If it can hand over a record, we can connect it.
Can customers who don’t order online still use it?
Yes. The portal is useful without a checkout: documents, order history and availability are worth logging in for. Ordering can be switched on per customer group when you are ready.
How do we handle prices that change in the ERP?
They change in the ERP and nowhere else. The platform reads prices per customer at request time or on a schedule, depending on what your ERP can support. Nobody updates a price in the shop.
What is the hard part?
The data, not the shop. Every project like this spends its first weeks discovering that the PIM, the ERP and the legacy content platform each hold a slightly different version of the same product. Settling which one is right, field by field, is the real work. The storefront is straightforward once that is done.
What does launch look like?
Usually one market first, with a defined set of customers who get portal access early. Once ordering works end-to-end for them, the next markets follow on the same platform.
Show us how a product gets from your PIM to a customer today.
One call. We map the systems, the manual steps between them, and what connecting them would change first.
Find the right AI starting point.
Align the business case, governance and first implementation—without starting a large programme.