One platform, four ways to sell.
Every model below runs on the same catalogue, the same pricing engines and the same order pipeline. What changes is who is buying — and each page is honest about what that costs you.
Selling to dealers and distributors
Cart-style ordering on agreed terms — per-account price lists, trade schemes evaluated in the cart, credit checked at save, and ordering that works offline in the field.
Explore B2B →Selling to end customers
A published catalogue anonymous traffic cannot slow, guest carts that survive sign-in, and a checkout that freezes the deal before the money moves.
Explore B2C →Going direct without breaking the channel
Launch a direct channel on the catalogue, stock and pricing you already run — and route the orders your distributors should fulfil to them.
Explore D2C →Selling through partners, to their customers
A hyperlocal storefront per partner on your range, orders routed by the pincode each one serves, and commission settled at the rate in force at the time of sale.
Explore B2B2C →Selling, not just listing.
Marketing copy, images, ratings — not a price list
Stores, nested categories and merchandised items with highlights, MRP vs price, tags and review counts — plus clickable exploded-parts diagrams drawn in-app. Droppable on any order, purchase order or page, web and mobile.
One item, the right price for each buyer
Price lists scoped by customer, group, partner and branch, effective-dated to item, SKU and lot type — one resolution path across orders, invoices, quotes and subscriptions.
The bad order stops at save
Per-customer and per-partner limits enforced at order and invoice save, with the arithmetic in the rejection.
Take it to your buyers.
Your catalogue on a customer portal: self-service browsing, carts and checkout with online payment, order history and tracking — on your own domain, governed by the same permissions and pricing engine.
Catalogue to cash — priced at posting, not at browsing.
48 free units added
The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Commerce |
|---|---|
| Merchandised catalogue with offers and badges | Native |
| Exploded-parts diagrams | Native |
| Cart-style ordering, works offline | Offline |
| Barcode-driven reordering | Native |
| Customer-specific pricing | Native |
| Trade schemes live in the cart | Native |
| Credit control at order save | Native |
| Dealer onboarding with KYC | Native |
| Store-scoped catalogues | Native |
| Online payments at checkout | Native |
| Storefront published on your portal | Integrated — Portals |
| Hosted-store connector | Native |
| Direct-to-consumer selling channels | Native |
| Published catalogue for anonymous traffic | Native |
| Guest cart that survives sign-in | Native |
| Checkout that freezes the deal before capture | Native |
| Coupon campaigns with budgets and caps | Native |
| Headless storefront API with signed events | Native |
| Partner microsites with commission settlement | Native |
Everything in Commerce.
The questions evaluators ask.
Who are the portals for — customers, partners, employees?
All three. One tenant runs multiple portals — a dealer portal, a customer portal, a partner portal — each with its own on-off switch, and the same builder turns inward for employee portals and internal tools. Every portal composes visually in the designer, goes live on an instant hostname, and can move to your own domain with the certificate managed for you. Explore xMatix Portals.
Do portal users see only their own data?
Yes. Signed-in customers see their orders, invoices and cases scoped to the person who logged in — nothing else. Published data views carry a chosen filter and cap, so visitors see current data but never more than was granted. Anonymous visitors get the least access possible, enforced by the same security engine that guards your staff, and signup runs through invite rails that never leak who else has an account.
Can portals run on our own domain?
Yes — shop.yourbrand.com, with managed TLS: paste two DNS records and you are live, certificate handled for you. Until domain ownership is proven, nothing routes anywhere. Publishing is equally deliberate — changes stay in draft until you say go, every publish is a version you can point back to, and a one-click kill switch takes the whole portal offline instantly when it matters.
Does commerce share the same catalog and stock?
Yes — the storefront sells the same catalogue, prices and schemes as the rest of the platform, scoped per store so each dealer sees their own assortment. Credit control checks the buyer's real outstanding at save, orders flow into the same fulfilment and invoicing pipeline, and online payments land in the same collection flow finance already runs. Explore xMatix Commerce.
What makes a good B2B dealer ordering portal?
Truthfulness under the surface. A B2B dealer ordering portal earns adoption when every screen is a live window onto the system of record: each dealer sees their own catalogue at their negotiated terms, schemes price in the cart by the same rules invoicing applies, credit is checked against the real outstanding at order save, and despatch, statement and claim status answer themselves. A portal fed by uploads drifts from reality and dealers go back to phone calls within a quarter.
