```json { "title": "Multi-Distributor Pricing Schemes in ERPNext: Managing Slabs, Discounts and Margins", "url": "https://aavatto.com/blog/multi-distributor-pricing-software-fmcg-erpnext/", "datePublished": "2026-10-12", "dateModified": "2026-10-19", "language": "en-US", "description": "How multi distributor pricing software works inside ERPNext — structuring slabs, discounts and margins across distributors without rule conflicts.", "author": "Aavatto", "publisher": "Aavatto - Frappe & ERPNext Experts | Custom Development, Implementation & Support" } ``` # Multi-Distributor Pricing Schemes in ERPNext: Managing Slabs, Discounts and Margins **Multi distributor pricing software works by layering rules — customer tier, order quantity, product group, and scheme period — on top of a base price list, then resolving which rule applies when more than one qualifies. Done well, a sales order or invoice shows the correct distributor price automatically. Done badly, it turns into a spreadsheet of exceptions that nobody fully trusts, including the person maintaining it.** That gap between "we have pricing rules" and "our pricing rules actually hold up" is where most FMCG manufacturers and distributors run into trouble — not in the concept of slab pricing itself, which every distribution business already understands, but in the software layer meant to enforce it consistently across dozens or hundreds of distributor accounts. ## Why Distributor Pricing Breaks Before It Reaches the Invoice Most FMCG businesses don't lack a pricing policy. They have one — often a detailed one, worked out over years of negotiation with distributor tiers, regional variations, and seasonal schemes. What they lack is a system that applies that policy the same way every time. The typical failure pattern looks like this: a distributor is meant to get a 4% slab discount above a certain order volume, plus a seasonal scheme discount that month, minus a deduction for an unmet display commitment. If that logic lives in a spreadsheet or in a sales executive's memory, it gets applied inconsistently — sometimes generously, sometimes not at all, and almost never in a way finance can reconstruct later when a distributor disputes an invoice. This is also where margin actually leaks. Not through big pricing mistakes, but through small, repeated inconsistencies that never show up as a single line item — a scheme applied twice, a slab discount given at the wrong quantity break, a distributor quietly given "last time's rate" because nobody checked the current one. ## How ERPNext Structures Multi-Distributor Pricing Software Rules ERPNext doesn't handle this through one big pricing table. It separates the pieces that vary independently, which is the only way multi-distributor pricing scales without turning into an unmanageable list of one-off exceptions: **Price Lists** hold the base selling price per item, and a business can run separate price lists for different distributor tiers, regions, or channels (modern trade versus general trade, for instance). **Pricing Rules** sit on top of price lists and apply conditional adjustments — a percentage or flat discount triggered by customer, customer group, territory, item group, quantity break, or a validity date range for time-bound schemes. **Customer Groups and Territories** let a rule target "all Tier-2 distributors in this region" rather than requiring a separate rule per distributor account. The result is that a single sales order can pull from a base price list, apply a quantity-slab discount, and layer a time-bound scheme on top — without three separate manual calculations. The pricing appears correctly at the point of order entry, which is what actually prevents disputes later, rather than a discount getting reconciled after the invoice is already out. ## The Part Generic Feature Lists Skip: Rule Conflicts Almost every distribution software vendor advertises "slab pricing" and "scheme management" as checkbox features. Fewer explain what happens when two rules could both apply to the same order — because that's where most real-world pricing setups actually go wrong. ERPNext resolves this through rule priority and specificity: a rule that names a specific customer takes precedence over one that targets a customer group, and rules can be sequenced so a business controls whether slab discounts and scheme discounts stack or whether one should override the other. Getting this configured correctly — deciding up front which combinations are allowed to stack and which aren't — is implementation work, not a settings toggle, and it's the step that's usually skipped when a business tries to set this up without ERP implementation experience specific to distributor pricing. This is also the point worth checking closely if you're evaluating any FMCG pricing scheme software, not just ERPNext: ask a vendor to show you what happens when a customer-specific rule and a quantity-slab rule could both apply to the same line item. If the answer is vague, the conflict-resolution logic probably wasn't built with multi-distributor complexity in mind. If your current pricing setup has more manual exception-handling than automated rules, that's usually a sign the rule structure needs rework before adding more schemes on top of it — not a reason to keep patching it manually. ## Connecting Pricing Rules to Real Margin Visibility The other half of this problem is distributor margin management — not just applying the right discount, but knowing what that discount actually costs the business once it's aggregated across hundreds of distributor accounts and dozens of active schemes in a given month. Because ERPNext's pricing rules sit inside the same system as sales, inventory valuation, and accounting, a scheme's real cost is visible as it accrues, not reconstructed at quarter-end from separate discount and sales reports. A manufacturer can see, by distributor tier or by scheme, whether a promotional discount is actually driving the incremental volume it was meant to justify, or whether it's just eroding margin on volume that would have happened anyway. Industry data on FMCG distribution margins suggests scheme mismanagement is a common, not rare, source of leakage — automated scheme tracking and consistent slab application are commonly cited as recovering a few percentage points of margin that manual processes lose to error and inconsistency. The exact number varies by business, but the mechanism is consistent: margin erodes fastest where pricing and accounting are two separate systems that get reconciled after the fact rather than one system that reflects both in real time. ## What to Check Before You Commit to a Pricing Setup A few questions are worth answering honestly before assuming your next pricing engine will solve this: Can you name your current rule-conflict policy? If two discounts could apply to one order, do you know today which one wins — and is that decision documented anywhere? Is your pricing tiered by more than just quantity? Most FMCG distributor structures need customer tier, region, and time-bound schemes to combine — a system that only handles quantity slabs will need workarounds within a year. Does a discount show up in your margin reporting the same month it's given? If margin impact is only visible at quarter-end reconciliation, the pricing system and the accounting system aren't actually connected. None of this requires exotic software. It requires configuring the pricing layer deliberately, with the conflict rules decided upfront, rather than adding schemes one at a time until the structure is unmanageable. ## Frequently Asked Questions [Can ERPNext handle different prices for the same product across different distributor tiers?](#collapse-2671) Yes. Separate price lists per tier or region, combined with Pricing Rules scoped to customer groups or territories, let the same item carry different net prices for different distributor segments without maintaining separate product catalogs. [What happens if a distributor qualifies for both a quantity slab discount and a seasonal scheme at the same time?](#collapse-2672) That depends on how the pricing rules are configured — ERPNext supports both stacking rules and rules that override each other by priority. Deciding which behavior you want for which combination is a configuration decision that should be made deliberately during implementation, not left to default behavior. [Is this different from using a dedicated pricing or CPQ tool alongside our accounting software?](#collapse-2673) The mechanism is similar, but a separate pricing tool still requires syncing discount and margin data back into accounting. Because ERPNext holds pricing, inventory, and accounting in one system, margin impact from a scheme is visible without a separate reconciliation step. [Do we need to migrate all our existing schemes at once?](#collapse-2674) No. Most businesses map their most complex or highest-volume pricing structures first — the ones causing the most manual reconciliation work today — and phase in simpler distributor tiers afterward once the rule-conflict logic is proven. Most of the pricing complexity FMCG distributors deal with isn't unusual — it's the same slab, scheme, and tier logic most manufacturers already run. What determines whether it stays manageable is whether the underlying rule structure was designed to handle overlapping conditions from the start, which is closer to an implementation decision than a feature checkbox. Aavatto's case studies cover how this kind of structured pricing and margin visibility has been set up for other FMCG and distribution businesses. ## Ready to Fix Your Distributor Pricing Setup? If your team spends more time reconciling distributor discounts after the fact than confirming them at order entry, the pricing structure is the thing to fix — not the number of schemes you're running. [Book a free ERPNext consultation](/services/tailored-erpnext-implementation/) with Aavatto to walk through how your current slabs, tiers, and schemes would map onto a rule structure built to handle them without manual patching.