Determinism plus AI, under the same rules.
For B2B commerce leaders
The pricing rule is written once and applies on every channel.
Each rule carries role, customer type, priority and source in the Commerce Rules Engine; the portal, the seller and the agent all follow it.
Illustrative scene with a real CWS Platform screen in a demo version. People, stores and on-screen data are fictitious.
For sales teams
A discount above the limit asks for a reason and escalates inside the order.
The rep sees the role’s ceiling on every line; anything above goes to the approver, with a record of who granted it.
Illustrative scene with a real CWS Platform screen in a demo version. People, stores and on-screen data are fictitious.
For buyers on the portal
The order closes on her contract’s credit and terms.
Credit limit, open balance and payment terms show at checkout, straight from the ERP; with available credit, the order is approved on the spot.
Illustrative scene with a real CWS Platform screen in a demo version. People, stores and on-screen data are fictitious.
For counter teams
The right part shows up by the customer’s vehicle application.
The catalog filters only what fits the chosen vehicle, with stock and the account’s price, and the filter is saved in the customer’s garage.
Illustrative scene with a real CWS Platform screen in a demo version. People, stores and on-screen data are fictitious.
Platform
You don't have an e-commerce problem, you have a negotiation problem: price, credit, freight and mix decided case by case, today scattered across a spreadsheet, the ERP and the rep's head, and now under the threat of an AI that hallucinates rules. CWS Platform digitizes the whole decision on a deterministic engine, with governed AI layered above.
11 deterministic modules + 6 AI Agents + 4 layers + 1,029 parameters + 5 dimensions.
Inside the platform
Three modules from the inside, beyond what the top shows
Three CWS Platform screens this page sums up in text: stock and the customer's price at the counter, reordering by color and size run, and one account for the whole network.
Stock at the counter
At the counter, the part that fits, how many are on the shelf and the customer's price
The rep searches by the customer's car and sees only the parts that fit, with the store's stock and that shop's price. Stock comes from Distributed Inventory (Inventory Hub), and the price from the customer's rule.
Pain it removes: stock checked over the phone before promising the part to the customer.
CWS Platform demo screens, completed with fictitious data to show the use.
Reorder by size run
The retailer reorders by color and size, in one order
The size run shows each color in the collection with quantities from S to XL and the total per size, at the retailer's contract price list. The order goes out by size run, and the size run is what the brand reads back.
Pain it removes: reorders on spreadsheets, without knowing which color and size sold in the store.
CWS Platform demo screens, completed with fictitious data to show the use.
Network account
One account for headquarters and every linked branch
The buyer signs in with the tax ID of the location that is buying and sees their company's prices, availability and terms. Who gets in and what they see is a Commerce Rules Engine (CDL Workspace) rule.
Pain it removes: one login per branch, and the headquarters buyer with no view of the locations.
CWS Platform demo screens, completed with fictitious data to show the use.
A platform, not a toolbox
One rules engine, not eleven
The 11 modules and 6 agents run under the same Commerce Rules Engine (CDL Workspace).
And what does that prevent?
Approval limits, credit and tax rules apply the same everywhere, with no standalone-tool silo.
Determinism underneath, AI on top
The Core executes the rule by code, at zero inference cost.
And where does AI come in?
The AI Agents interpret intent and orchestrate the Core via MCP, under exactly the same rules as a human seller.
A layer over the ERP, not a replacement
The platform orchestrates negotiation over the ERP, through APIs and webhooks.
And what happens to the ERP?
The ERP remains the vault; CWS Platform is the commercial manager. Public integrations include SAP, TOTVS, Senior, Sankhya and Microsoft Dynamics.
The platform in 1 minute
Price comes from a rule, not a spreadsheet
The Pricing Rules screen: each row carries priority, type, value, whether it stacks, and the commercial policy it came from.
- Every rule has an originAll four rows point to the same commercial policy v4, approved by the margin committee.
- Priority settles the tieWhen two rules reach the same order, the ordering decides, not whoever opened the spreadsheet first.
- Stacking is a decision, not a side effectNone of the four stack by default: piling up discounts becomes a declared choice.
This is the mechanism underneath the approval matrix. The four rules are not screen examples: they are the same commercial policy v4 written as four tiers, with explicit priority so there is no tie — which is exactly what a spreadsheet does not have.
In real production
Company founded in 2012; platform in production since 2013.
+10 points of margin
at Tracbel, on portal orders, with ~131k SKUs (100% of the portfolio) and 6 years integrated with SAP.
3x more customers
at Imdepa, 153 customers activated in 3 years on the B2B portal, without growing the team in the same proportion.
Governance by infrastructure
the rule blocks what isn't allowed before it happens, for the human seller and for the AI.
In-depth content
Estimate the margin gain on your order volume
Leave your email to unlock.
Calculate my gain →The 11 deterministic modules
The Core that executes the business rules by code. The four that underpin the negotiation have a dedicated page.
Commerce Rules Engine
CDL Workspace
The rules of the game in executable form. 1,029 configurable parameters.
View module →Contextual Pricing
Pricing Engine
Price by product, warehouse, profile and tax rule, in milliseconds.
View module →Credit-First B2B Checkout
Checkout & Payments
Credit as native payment (Net Terms 30/60/90) and 4-Point Checkout Validation.
View module →Product Catalog & MDM
Catalog Engine
Cross-cutting catalog with 4 compositions, Global vs. Local governance.
View module →Distributed Inventory
Inventory Hub
Multi-warehouse inventory, physical and logical, in real time.
View module →Shipping & Fulfillment
Logistics Engine
Multi-DC freight, CIF/FOB, split delivery, Freight Negotiation Thresholds.
View module →No-Code Storefront Builder
CMS Builder
No-code portal, single dynamic template, native SEO.
View module →Marketplace Management Platform
Marketplace Center
Multi-seller 30+, buybox, split, anti-disintermediation.
View module →Order Management System
OMS (also Seller Center)
Orchestrates the order across 10 states. READY requires the ERP order number, SHIPPED requires tracking. The operation can configure the Nota Fiscal as mandatory.
View module →To see where this architecture fits among the categories of solution, read what a B2B ecommerce platform must do.
The 6 AI Agents with Business Guardrails
They consume the deterministic Core via MCP, under the same rules (CDL) as human sellers. If the AI goes down, the Core keeps operating.
Rules Auditor Agent
Audits 1,029 parameters in 45s, detects conflicts, prevents leakage. It suggests, the human decides.
View agent →Sales Copilot
Account ranking, margin and inactivity alerts, builds the quote.
View agent →Procurement Agent
Semantic search, multi-seller comparison, builds the cart, reorders.
View agent →Merchandising Agent
Monitors the store, incomplete listings, suggests campaigns.
View agent →Catalog Enrichment Agent
A 7-step pipeline, from photo to publication per SKU.
View agent →Replenishment Agent
Redistributes across DCs, stockout alerts, suggests purchases.
View agent →
Persona · CEO
I stopped fearing an AI that makes up rules: it follows the same ones as my reps.
The AI Agents orchestrate the Core under the same Commerce Rules Engine (CDL Workspace): the rule blocks what isn't allowed before it happens.
Persona · Sales rep
I no longer rework over the phone the terms the digital channel already showed.
All five dimensions run through the same rules engine, and the Assisted Selling Platform (Sales Hub) is the rep's digital negotiation table.
5 negotiable dimensions
Negotiated at the same time, in the same order, under intelligent rules.
- Price
- Delivery
- Payment
- Quantity
- Composition
Autonomy Gradient
AI governance by infrastructure, not by prompt.
- Green: the agent executes on its own (reversible, low-risk action).
- Yellow: the agent proposes, the human confirms with one click.
- Red: the agent never acts. It informs and escalates to the human.
Autonomy Gradient
What each AI Agent does alone, proposes, or never does.
In the Commerce Rules Engine (CDL Workspace) panel, every action of every agent has its band: green runs on its own, yellow proposes and a person confirms with one click, red never acts and escalates.
See the Commerce Rules Engine →
The concept behind it all
CWS Platform treats the cart as a negotiation table, where each dimension moves within rules the company defines and that record every decision. This is what we call Governed Negotiation.
AI Agents
The AI Agent builds the quote. The rep decides.
Sales Copilot reads the account book, points to the right customer for today and leaves the quote ready, with the reason and the variables in plain sight. Approving, editing or discarding it is up to the rep, within the same rules.
How the AI Agents work →
Frequently asked questions
What exactly does the platform digitize in a negotiation?
The five dimensions a B2B sale negotiates at once: price, delivery, payment, quantity and composition. All of them run through the same rules engine, so the terms the digital channel shows are the terms that close, not a number a sales rep has to rework later over the phone.
Why a platform and not standalone modules from several vendors?
Because the 11 modules and 6 AI Agents run under the same rules engine (Commerce Rules Engine). Standalone tools create silos, each with its own pricing rule and approval limits; here the rule is a single one, applied the same to the human seller and to the agent.
What runs by code and what does the AI orchestrate?
The deterministic Core executes the rules by code, at zero inference cost, and negotiation runs on it. The AI Agents orchestrate that Core via MCP, under the same rules engine as the 11 modules.