The questions below are the ones evaluators of B2B commerce platforms actually ask. Each answer states what xMatix does — the mechanisms are documented in depth across this section and the Sales documentation.
Common questions
Is Commerce a separate product with its own order pipeline?
No — and that is a feature. Commerce is the B2B layer of the platform: merchandised store catalogues, cart-style capture, the dealer purchase-order handoff and portal storefronts, all producing standard sales orders. There is no integration seam between "the shop" and "the ERP" because they are the same system — one order table, one pricing engine, one receivables ledger.
How do dealers actually place orders?
Four verified channels, all landing in the same pipeline: cart-style entry from the merchandised Product Catalogue on a document; the dealer handoff, where a dealer's purchase order becomes the supplier's sales order with outstanding quantities tracked line by line; direct entry in the Sales app; and field-sales capture during visits, including van sales. Dealer ordering walks through each.
Is there an online storefront with a checkout?
There is an online storefront; there is not a portal checkout. Portal storefronts deliver merchandised catalogue browsing, self-service signup and signed-in account surfaces on your own hostname, with data exposure controlled view by view. Order capture happens through the platform channels above. If a public self-checkout is central to your evaluation, that is the honest current boundary.
Can each dealer have its own prices and discounts?
Yes, modelled rather than typed: price lists scope to a customer account, a price-tier account group, a selling company or a branch, and the most specific active list wins; discount groups fill contract discounts the same way. A negotiated rate lives as a dated rule, so it survives repricing and is auditable. See Catalogue and pricing.
Are trade schemes applied automatically, or computed after the fact?
Automatically, at save: the scheme engine evaluates approved schemes when a document is saved, writes scheme discounts and free lines onto it, and enforces scheme and per-account budgets live against a consumption ledger. Recommendations show how far an order is from the next slab while it is being built. Details in Schemes and credit and the trade schemes reference.
What stops an over-extended dealer from ordering more?
A credit limit per customer per selling company, checked against live open receivables when an order is created and again when an invoice is created. A breach blocks the document with the open amount, document amount and limit in the message. Because the check runs on the document, it holds across every capture channel. See credit limits.
How are new dealers brought on?
A dealer onboarding record type carries the application — the applicant's identity and business details, dealer code, category and lead status — through staged approvals (channel, regional sales and legal sign-off fields, with a recorded rejection reason when declined). Once trading, the dealer is a customer account like any other, carrying its account groups, price list scope, credit limit and store association.
What happens after the order is placed?
The standard order-to-cash pipeline: stock allocation, picking and fulfilment, delivery, invoicing and payment — documented start to finish under the sales order lifecycle and invoicing and payments. Commerce adds nothing proprietary downstream, which means reporting, finance and inventory see dealer business with no translation layer.