A B2B ordering portal built around commercial agreements
Qommerce is an own-product development project for wholesalers. It combines customer pricing, customer-specific catalogues, product configurations and repeat ordering in a portal carrying the wholesaler’s brand. A working demo makes these workflows tangible before a pilot is agreed.
See Qommerce in use
These genuine screenshots were captured in Qommerce’s working Nordex demo. Nordex and Van Dijk are sample companies. Prices, stock and delivery information are demo data. The interface shown is Dutch; the explanations below describe the features in English.
1. Find the right product with customer-specific pricing
A buyer can search by product name or article number and see the purchasing price for the selected demo account. Product cards also show the variant, stock information and ordering unit. This helps clarify what is being ordered before the buyer builds an order.
How we work through the decisions with a client: together with sales support staff and buyers, we establish which article codes, names and variants they use in daily work. Which pricing agreement should be visible? Which stock information helps a purchasing decision? Which data comes from the ERP? We document these choices and test them with recognisable sample orders, rather than simply reproducing an existing screen.
2. Make dimensions, units and pricing explicit
For roll film, the buyer selects width, length per roll and the number of rolls. The demo displays the corresponding price. Stock, minimum quantity, related variants and a fixed-content combibox appear in the same window, keeping useful context available while the buyer chooses a configuration.
How we work through the decisions with a client: we discuss permitted dimensions, rounding, minimum quantities and the meaning of each ordering unit. Is pricing based on a roll, a metre or an area? What should happen with a non-standard request? We make normal orders and exceptions concrete with the client, agreeing which inputs the portal can process and when a member of staff should review a request.
From demonstration to a relevant pilot
These screenshots show working software, rather than measured customer results. For a pilot, we select a product category and user group together, agree on data sources and acceptance criteria, and test the purchasing workflow. Administration, error messages and handover are part of that preparation too. This helps the client assess whether the portal fits their work before expanding its scope.
The challenge: a business order involves more than a basket
Buyers do not always pay a public unit price. Customer agreements, quantity breaks, minimum quantities and ordering units determine what they can buy and at which price. Configurable products introduce additional dimensions and options. When these rules exist only in emails or employees’ knowledge, each order needs interpretation.
Qommerce makes those agreements part of the ordering experience. Returning buyers can find their products and prices and use a standing order list. Reducing repetitive data entry is the objective; the actual change needs to be measured in each pilot.
From product concept to working software
- Customer-specific catalogues and pricing: product selection and price calculation reflect the selected customer account.
- Product configurations and units: dimensions, quantities and purchasing conditions become explicit steps in the order flow.
- Repeat orders: shared baskets and standing order lists support recurring purchasing.
- Administration for different roles: access to features and data follows the shop and customer context.
- Integrations within the workflow: APIs and webhooks provide a foundation; connecting a particular ERP requires its own design and validation.
Looking beyond the feature list
Understand how an order is created
The proposed approach starts with sample orders, commercial agreements and the work of the sales support team. Which data comes from the ERP? Which exceptions require a conversation? These answers determine what the first pilot needs to support.
Make decisions concrete together
A pilot starts with a defined customer group and product category. Scope, data sources, pricing rules and acceptance criteria are discussed in advance. This allows a wholesaler to use the demo to assess the intended workflow before setting up the entire catalogue.
Evaluate usability and order quality
Digital order volume is only one consideration. Repeat usage, pricing discrepancies, order corrections and questions to staff also help determine the next step. The time calculator on the Qommerce website presents an assumption-based scenario, rather than a proven customer saving.
The technology behind the ordering workflow
The application combines Laravel with Inertia and React. PostgreSQL stores catalogue, customer and order data, while Laravel Reverb supports real-time collaboration. Domain modules cover areas including catalogues, pricing, ordering, accounts and integrations. This structure supports focused development of commercial rules and the user interface.
Current stage: a functional product demo
Qommerce demonstrates how a B2B ordering platform can work. The demo uses sample data and does not establish a completed customer implementation. Production integrations, real payments and alignment with a specific administration require separate scope and validation.
Explore Qommerce or view the product demo.
Developing a B2B portal or Laravel platform?
Qommerce illustrates how Qualide translates business workflows into software, from pricing logic to a usable ordering journey. Discuss your platform or existing application with Jeffrey. Bring a normal order and a difficult exception so we can make the requirements concrete.