Skip to contentv0.1.0
PIMgate
COMMERCELIVE

B2B commerce, built on the product data you already govern.

PIM Gate Commerce is a headless commerce module on top of the product data in PIM Gate. It adds customer-specific prices, stock, company accounts, carts, a configurable checkout, payments and the order handover to your ERP, and serves all of it to your website, a hosted storefront or your own front end through one Storefront API.

HEADLESS · API FIRSTMULTISHOP · MULTI-CURRENCYADAPTERS FOR ERP + PAYMENT
Trace of the price for SKU MS-12011, quantity 10, for a company buyer of the fictional tenant MESSARA. The shop gate passes, the list price is CHF 212.00, the ERP returns a live customer price of CHF 184.00, which is the first hit; company price, group price and quantity tier are skipped; tax is added at checkout. The buyer sees CHF 184.00.

The price simulator's trace for one SKU and one buyer. Fictional data.

01 · What it is

A commerce layer between your systems and every place you sell.

PIM Gate already holds your validated, translated product data. The commerce module adds everything a B2B shop needs next to the product and keeps every external system behind an exchangeable adapter: prices, stock and orders from the ERP, payments from a provider, documents from a DMS. Front ends read one Storefront API; nothing in the browser talks to the ERP or the payment provider's server API directly.

PIM Gate Commerce architectureOn the left the systems you run: PIM, ERP, payment provider and DMS. They connect through adapters to PIM Gate, which holds the product data and the commerce layer with prices, stock, carts, checkout, orders and company accounts. On the right the Storefront API serves the website with widgets, a hosted storefront, your own front end and the B2B account area. Packets show a price and stock level flowing out, an order flowing to the ERP, and shipment status and an invoice flowing back.Your systemsWhere you sellPIMProduct contentERPSAP · Odoo · MagentoPayment providerStripe · Klarna · MollieDMS · archiveCertificates · invoicesPIM Gate · your tenantProduct dataValidated · translatedCommerce layerPrices · customer pricesStock · availabilityCarts · quick order · listsCheckout · paymentOrders · returnsCompanies · roles · approvalAdaptersAPIWebsiteIbexa bundle · widgetsHosted storefronttenant.pimgate.ai/shopOwn front endREST · GraphQLB2B account areaOrders · documentsEvery external system sits behind an exchangeable adapter

Module, not a second system

Commerce runs inside PIM Gate and reuses its tenants, roles, licences, encrypted secrets and e-mail. A super-admin enables it per tenant; when it is off, no commerce screen, API or widget answers for that tenant.

Any number of shops

One tenant runs several shops on one data basis. Each shop selects its products from the PIM by category, filter or by hand and has its own currencies, languages, prices, checkout and payment rules.

API first

Every function exists in the Storefront API or the Admin API before it appears in a screen or widget. Both are described in OpenAPI 3.1 and are the only way front ends talk to the module.

02 · B2B features

What a B2B buyer and your sales team expect, built in.

The functions below are implemented in the module and covered by automated tests against PostgreSQL. They are configured per tenant and per shop in the back office.

LIVE

Customer-specific prices

Live customer price from the ERP, own prices per company, group prices and rules, quantity tiers and scheduled prices. One resolver answers every price question, and the price simulator shows its trace.

Multi-currency and tax

Explicit price lists per currency or derived prices from a base currency with exchange rate, markup and price endings. Net or gross display per shop and customer group, tax per region.

Stock and availability

Stock per warehouse, available-to-promise from the ERP where it offers it, reservations during checkout and allocation at order placement.

Company accounts and roles

Companies with members, invitations by e-mail or file, admin and buyer roles, address books and a sales contact. New companies apply online; VAT ids are checked before the back office accepts them.

Order approval and credit

Orders above a company's threshold wait for an admin's approval before they reach the ERP. Credit limit, payment terms and the invoice flag come from the ERP; above the limit invoice is blocked or the order is held.

Carts, quick order, lists

Several named carts per account, carts shared with colleagues, a reference per line, quick order by SKU or by CSV and XLSX file, reorder from history and named shopping lists.

Configurable checkout

A checkout is a workflow of steps: identify, addresses, B2B details such as PO number and requested delivery date, shipping, payment, credit check, review and confirm. The review always re-validates prices and stock.

Discounts and codes

Catalog and cart discounts by product, category, quantity or cart value, per customer group and shop, with codes, usage limits and bulk generation. Shops where the ERP calculates discounts skip them, so nothing is discounted twice.

Orders, shipments, returns

Orders with separate payment, shipment and ERP status, cancellation with refund and stock restore, partial refunds, returns with receipt and restock, CSV export.

Documents in the account area

Order confirmations, delivery notes, invoices and certificates from the ERP or a DMS, streamed through PIM Gate to the company they belong to and never stored on the way.

Transactional e-mail

Order, shipment, approval, invitation and account e-mails with default templates in German, English, French and Italian, editable per shop.

Multishop with own identity

Shops with their own number ranges, legal documents in versions, domains and SEO settings. Customer accounts exist once per tenant and are enabled per shop.

03 · An order, end to end

From customer price to ERP order and back.

A buyer at a company customer of the fictional tenant MESSARA reorders pressure transmitters. The sequence follows what the module does at each step: the price comes from the ERP, the cart is validated on every change, the review re-checks prices live, the order is handed over to the ERP and its status and documents come back.

Illustrative scenario · fictional data

Five stages of a fictional B2B order at the tenant MESSARA. One: the product page shows the list price CHF 212.00 and the buyer's ERP price CHF 184.00, in stock. Two: the cart holds two lines, total net CHF 2,158.40. Three: the B2B checkout with company addresses, PO number, invoice payment allowed by the ERP and a live price check at review. Four: order MS-26-001042 is placed, stock reserved and the order is acknowledged by the ERP. Five: the shipment is marked shipped with tracking, delivery note and invoice appear in the account area.

Delivery, tracking and documents flow back from the ERP. The buyer and the company's admins see them in the account area.

04 · Front ends

Sell where your customers already are.

The module is headless. Your website keeps its pages, login and SEO; PIM Gate supplies product tiles, offers, cart, checkout and the account area. Four ways in, all on the same API and the same rules.

Storefront API (REST)
Products, search with facets, offers in batches, carts, checkout, sessions, orders and documents. OpenAPI 3.1, idempotency keys on writes, shop tokens and short-lived customer tokens, cache headers on anonymous reads.
Read-only GraphQL
One round trip for a page: shop, listing with prices, cart and customer. Writes stay on REST, where idempotency and the checkout state machine live.
Embeddable widgets
Custom elements for listing, price, availability, buy box, variant table, mini cart, cart, checkout and account. No framework on the host page; styling through CSS variables.
Hosted storefront
A ready shop front at your-tenant.pimgate.ai/shop/{shop} for shops without their own website, built from the same widgets with server-rendered pages for search engines. Off by default, switched on per shop.
Ibexa DXP bundle
A Symfony bundle connects an Ibexa website: Twig functions, Netgen Layouts blocks, a token endpoint for the site's login and cache purges on price and stock changes.
Embed on any page
// one script, then tags<script type="module" src="https://messara.pimgate.ai/widgets/v1/pg.js"></script><pg-shop token="pgs_…" lang="de" currency="CHF">  <pg-buy-box sku="MS-12011"></pg-buy-box>  <pg-mini-cart></pg-mini-cart></pg-shop>
05 · 05 · Back office

One back office for every shop of the tenant.

The Commerce section of PIM Gate holds everything a shop operator needs, with its own permissions per area and shop. Each change is written to the append-only audit log.

  • Price simulator: product × customer group × currency × quantity, with the trace of every price.
  • Storefront preview: see the shop as a given customer before you go live.
  • ERP message log: every outbound and inbound message with status, attempts and payload, retried with one click.
  • Connection health: calls, error rate, cache hit rate and fallbacks per adapter.
AreasShopsCatalogPricingStockCustomers & companiesDiscountsCheckoutOrders & returnsE-mailsIntegrationsERPPreview

06 · Connectors

Connectors and integrations.

Every external system is an adapter behind a port: price, stock, customer, order, documents, payment, shipping, tax, e-mail and identity. A tenant combines them — prices from SAP, documents from a DMS, payment through Mollie.

ERP and shop systems · 7

  • SAP S/4HANAAvailableOData V2 · prices, stock, customers, orders, documentsPrice simulation or replicated condition records.
  • Odoo 17–19AvailablePricelists, stock, partners, sales orders
  • Magento / Adobe Commerce 2.4AvailableREST · OAuth 1.0a
  • APIZOn requestMapping-driven RESTNo public endpoint reference yet; endpoints are configuration.
  • Admin API pushPlatformYour ERP or middleware calls PIM Gate
  • Custom REST facadePlatformSAP CPI, MuleSoft, own middleware
  • File exchangeWith limitsSFTP · CSV, XML, IDoc-XMLConnection and test built; import and export jobs are set up per project.

Payment · 10

  • Invoice and prepaymentPlatformOffline methods, reconciled in the ERP
  • StripeAvailableCards, wallets, SEPA
  • KlarnaAvailableAuthorise in the browser
  • MollieAvailableCards, PayPal, SEPA, Billie purchase on account
  • PayPalAvailableOrders v2
  • PayrexxAvailableHosted gateway
  • Worldline SaferpayAvailablePayment page
  • Worldline DirectAvailableHosted checkout
  • Billie (direct)On requestB2B purchase on account
  • MonduOn requestB2B invoice and instalments

Identity · 3

  • Website login (signed token)PlatformExternal JWT, e.g. from Ibexa
  • OpenID ConnectPlatformAuthorisation code with PKCE
  • Shop accountsPlatformOwn login, Argon2id, verification and reset

Credit and compliance · 3

  • EU VAT id (VIES)AvailableChecked at company application
  • Swiss UIDWith limitsFormat and check digitNo lookup in the UID register yet.
  • CreditreformOn requestCredit check at application and checkout

Documents · 2

  • DMS and archive (REST)PlatformCertificates, declarations, invoices
  • ERP documentsAvailableThrough the ERP adapter

Shipping · 2

  • Rate rulesPlatformFlat, free from threshold, pickup, weight or price tables
  • Tracking linksWith limitsDHL, DHL Express, Swiss PostTracking links from the ERP's shipment data; no carrier label API.

Tax and currency · 2

  • Tax calculatorPlatformRates per region, or tax returned by the ERP
  • ECB and SNB ratesAvailableDaily reference exchange rates

E-mail · 1

  • Platform e-mail (Resend)PlatformTransactional mails, DE · EN · FR · IT

Website and search · 2

  • Ibexa DXP bundleAvailableTwig, Netgen Layouts blocks, cache purgeTwig functions, Netgen Layouts blocks and cache purges for Ibexa websites.
  • Product searchPlatformFull text, similarity matching, facets

What the states mean

Platform
Part of the platform; no external vendor involved.
Available
Adapter available; we set up the connection to your system in the project.
With limits
Available, with the limit named on the tile.
On request
On request; implemented with the vendor in the project.

Specified or asked for, not built yet

  • Marketplace and Google Merchant Center feeds

    Designed for in the data model, not implemented.

  • SAML sign-in

    Planned for a later release; OpenID Connect is available.

  • Carrier label and rate APIs

    Shipping uses rate rules and tracking links today.

  • Requests for quotation

    There is no B2B quote request workflow; carts can be shared with colleagues.

  • External search engines

    Search runs in PostgreSQL; no adapter for a separate search service.

07 · Architecture

Adapters at every external edge, defined behaviour when one is down.

Each ERP capability is a separate port, so an adapter implements only what its system offers and publishes what it can do. Data arrives live at request time, by scheduled sync with a cursor, or pushed by the ERP. When a system is slow or down, the module falls back in a defined way and says so.

Live, sync or push

Live calls for customer prices and availability, scheduled sync with a cursor for replicated data, or push from the ERP through the Admin API and signed inbound hooks.

Order handover with a message log

Orders reach the ERP from a transactional event outbox. Every message is stored with status, attempts and payload; failures are retried, raise an alert and can be retried by hand.

Circuit breaker per connection

After repeated timeouts a connection is short-circuited for a cool-down and probed with a single request before it closes again. Price and stock reads fall back while it is open.

Never a silent change

Prices are frozen when the order is placed. If the review finds a changed price or stock level, the buyer sees the difference and must accept it.

BehaviourDefault
Timeout of an ERP call2 s, configurable per connection
Fallback when the ERP does not answerlast cached customer price, at most 24 h old, marked
Circuit opens after5 timeouts within 30 s
Circuit stays open30 s, then one probe
Review stepalways re-validates against the live ERP
Moneyintegers in minor units, ISO currency

08 · Security and performance

Prices and account documents are sensitive. The module treats them that way.

Commerce uses the same isolation as the rest of PIM Gate and adds a shop boundary. These are the mechanisms in the code.

Tenant and shop isolation

Every commerce table carries the tenant and, where shop-specific, the shop. PostgreSQL row-level security enforces both on every request of the Storefront API.

Tokens

Shop tokens are stored only as SHA-256 hashes. Customer access tokens are signed and live 15 minutes. Inbound ERP hooks are signed with HMAC and rejected after 300 seconds.

Idempotency and audit

Writes carry idempotency keys, so a retried order never creates a second one. Changes in the back office go to the append-only audit log.

Personal data

Export of a customer's data as JSON and erasure by anonymisation; orders are kept for the retention period with personal fields reduced to what tax law requires.

Performance target

The Storefront API is designed for a p95 below 300 ms when served from cache.

EU / CH hostingGDPRrevDSGTenant isolationAppend-only audit

09 · How a project starts

From a first workshop to the first order in your ERP.

The module is built; what each project adds is the connection to your systems and the configuration of your shops. We start on a test tenant and move to production only when orders arrive correctly in your ERP.

  1. 01

    Scoping

    Shops, markets, currencies, customer groups, front end, ERP and payment provider. We show which adapters are ready and what is set up for your project.

  2. 02

    Module and shop

    Commerce is enabled for your tenant, the first shop selects its products from the PIM and gets its currencies, tax regions and checkout workflow.

  3. 03

    Connect and map

    Connections with encrypted secrets and a connection test; the ERP mapping — sales organisation, plants, payment terms, tax codes — is agreed in a workshop with your ERP team.

  4. 04

    Preview and test orders

    Storefront preview as real customers, the price simulator against the ERP's test system, and test orders through the whole handover.

  5. 05

    Go live and operate

    The shop goes live; the ERP message log, connection health and alerts show what is moving and what needs attention.

10 · FAQ

Questions about PIM Gate Commerce.

11 · Your projectLIVE

Planning a B2B shop on your ERP? Let us talk.

Tell us about your shops, your ERP and your payment setup; we will answer with what is ready for it and how your shop would start.

  • A scoping session on your shops, ERP, payment provider and front end.
  • A walk through the back office, the price simulator and the Storefront API on demo data.
  • A clear list of the adapters and settings for your project.

// ENQUIRY

Request a conversation

Free text, e.g. "Ibexa DXP 4.6", "Drupal 11".

Pricing will be published in Q1 2027.

LIVE

Translation

Product and website translation with agencies, AI and review rounds — the languages your shops sell in.

LIVE

PIMgate Studio

Maintain product data where your PIM does not reach, or run it as your PIM.

Integrations

PIM sources, delivery channels and systems PIM Gate connects.

Portals

Customer, sales and supplier portals on the same product data.

Put a gate between your catalog and chaos.