Wholesale and trade
One set of trading rules, applied everywhere
Keep your wholesale pricing rules, discount limits and trade credit decisions in one place. Every branch, rep, counter and web order gets the same answer, and you can see why.
Incoming request
evaluatingCan this rep give 14% off to a Silver trade account?
- Silver accounts can have up to 10% at rep level.
- Orders over 5,000 GBP add 2% to the rep's limit.
- Anything above the rep's limit, up to 20%, needs the branch manager.
- Above 20% needs the commercial director.
Answer, with the reason
Needs the branch manager. The rep's limit for this order is 12% (10% for Silver plus 2% for an order over 5,000 GBP). 14% is above that but below 20%, so the quote is routed to the branch manager with the reason attached.
Sound familiar?
Your price list says one thing. Your branches do another.
Wholesale margins are won and lost in small decisions: a discount here, a credit extension there. When those rules live in people's heads, every branch runs its own version.
Discounts that depend on who you ask
One rep knows the 10% ceiling. Another gives 15% because a manager said yes once, by email, last year. Nobody can see the pattern until margins slip.
Trade accounts opened on a hunch
A new builder wants a 5,000 GBP account today. The branch manager decides on the spot, because the credit checklist is in a shared drive nobody opens.
Price bands in a spreadsheet only Sarah understands
Customer tiers, volume breaks and exceptions sit in one workbook with hidden columns. When Sarah is on holiday, pricing questions wait.
The quiet cost
What inconsistent trading rules quietly cost
- Margin leaks one discount at a time, with no single place to see why.
- Customers notice that another branch gives them a better deal, and ask for it everywhere.
- A trade account opened without the right checks becomes a bad debt.
- Every price change means updating the spreadsheet, the ERP and the reps' memories.
Before and after
From branch-by-branch habits to one set of rules
Today
- Discount limits are known by some reps and guessed by others.
- Trade credit is decided by whoever is on the counter.
- Customer price tiers live in a fragile spreadsheet.
- Exceptions are approved by email and forgotten.
With Condexa
- Every quote checks the same discount limits and routes exceptions to the right approver.
- Every new trade account runs through the same credit decision.
- Price tiers sit in a lookup table the commercial team updates and publishes.
- Every exception is recorded with who approved it and which rule applied.
How you get there
How wholesalers make their trading rules consistent
- 1
Put the rules in one place
Build your discount, pricing and trade credit decisions on a visual canvas. Keep tiers, volume breaks and rep limits in lookup tables the commercial team can edit.
- 2
Check it with real quotes
Run last month's quotes through the decision and read the trace for each one. You see exactly which tier, limit and rule gave each answer before anything changes live.
- 3
Every channel asks the same question
Your ERP, CRM, quoting tool and web shop all call the same published decision over a REST API. One answer, whichever door the order came through.
A worked example
Worked example: can the rep give this discount?
A rep is quoting a Silver trade account for a 7,800 GBP order and wants to give 14% off.
The rules, in plain English
- R1Silver accounts can have up to 10% at rep level.
- R2Orders over 5,000 GBP add 2% to the rep's limit.
- R3Anything above the rep's limit, up to 20%, needs the branch manager.
- R4Above 20% needs the commercial director.
Condexa answers
Needs the branch manager. The rep's limit for this order is 12% (10% for Silver plus 2% for an order over 5,000 GBP). 14% is above that but below 20%, so the quote is routed to the branch manager with the reason attached.
FAQ
Questions people ask
How do wholesalers manage pricing rules across branches?
The reliable way is to keep wholesale pricing rules in one decision service that every branch and channel calls, rather than in each person's head or a local spreadsheet. With Condexa, tiers and discount limits sit in lookup tables, and every quote gets the same answer with a record of why.
What is a discount approval matrix?
A discount approval matrix sets how much discount each role can give, often by customer tier and order size, and who must approve anything above that. Condexa turns the matrix into a decision your quoting tool calls, so exceptions are routed to the right approver automatically.
Can Condexa decide trade credit for new accounts?
Yes. You build the trade credit decision from your own criteria, such as requested limit, trading history and any checks you require, and your systems call it when an account is opened or a limit is raised. Every answer is recorded with its trace, so you can show why a limit was granted.
Who can change the rules once they are live?
The people you choose. Workspaces have members with roles, so for example the commercial team can edit price tiers while only a publisher can make a new version active. Earlier versions are kept, so you can see what changed.
Does it work with our existing ERP or web shop?
Any system that can make a REST API call can ask Condexa for an answer, including ERP and CRM systems, Dynamics 365, Power Apps and custom web shops. The answer comes back as JSON in milliseconds.
Keep exploring
Related decisions and guides
Use cases
Pricing and discounts
Stop discount requests bouncing round by email. Apply price bands and limits consistently and route only the exceptions.
Read moreUse cases
Credit decisions
Decide who gets credit, and how much, the same way every time, without waiting for the one person who knows the rules.
Read moreProblems
Spreadsheet decision logic
Your approval matrix lives in Excel, one file has three versions, and no system can ask it anything.
Read moreFeatures
Lookup tables
Every limit change is a dev ticket? Put thresholds and bands in tables your business team edits and publishes.
Read moreIntegrations
REST API
Your app needs an answer, not another rules module to maintain. Send the facts, get the decision back as JSON.
Read moreGive every branch the same answer, starting with one decision
Bring a decision your team makes every week. We will build it with you, live, test it against your own examples and show your systems calling it.
No slides. Your decision, built live. No obligation.