Case Study: How a Medical Device Distributor Managed Dealer, Distributor, and Retail Price Tiers

A medical device distributor supplying diagnostic equipment, surgical tools, and consumables across Central Europe was managing product pricing rules for three distinct customer tiers — dealer, distributor, and retail — across 2,800 SKUs. Each tier had contractually defined margin floors. In January 2026, an audit by their largest dealer account uncovered 47 SKUs where the dealer had been invoiced at distributor-tier prices, triggering a contract dispute and a credit note obligation of approximately €11,400.

The Challenge

The distributor’s business model required strict price tier separation. Dealer accounts — typically hospital procurement departments and large medical practices — held multi-year supply agreements with fixed discount percentages relative to the retail price list. Distributor accounts — regional resellers who in turn sold to smaller clinics — held a separate agreement tier with deeper discounts that were commercially sensitive and not to be disclosed to dealer accounts. Retail pricing was the public list price, used for direct online sales and as the reference point from which all other tiers were calculated.

The catalog covered four product families: diagnostic equipment (blood analyzers, imaging accessories), surgical consumables (gloves, drapes, sutures), patient monitoring accessories, and laboratory supplies. Across these categories, the margin structure differed significantly. Diagnostic equipment carried a 40% gross margin at retail, with dealer pricing at retail minus 22% and distributor pricing at retail minus 35%. Consumables had different tier percentages because the supplier cost structure was different. Laboratory supplies had a further variance because some lines were own-brand and others were imported third-party.

Managing product pricing rules manually across this structure required four spreadsheet files: a master cost and retail price list, and three derived tier price lists. Each tier file contained formulas that pulled from the master and applied the tier discount percentages. The formulas worked correctly when the files were static, but the catalog was not static. The company averaged 34 new SKUs per month and had approximately 180 price changes from suppliers per quarter.

When new SKUs were added, the data entry process required updating the master file first, then manually extending the formula range in all three tier files. When that range extension was missed — or when a row was inserted in the middle of the master rather than appended at the bottom — the tier files would produce a reference error or, worse, silently carry forward the wrong product’s data.

The January incident was caused by a row insertion in the master file that shifted product IDs by one row in a section of 120 consumable SKUs. The tier formulas that used row number as a lookup reference rather than product ID all pulled data from the wrong product. Because the price differences within the consumables category were small — often less than €2 per unit — the error was not visually obvious in the exported price list.

[SCREENSHOT: MicroPIM pricing tier dashboard showing three customer segment rows — Dealer, Distributor, Retail — with calculated prices, cost, and margin percentage displayed side by side for a single diagnostic equipment SKU]

What They Tried First

Following the January incident, the pricing team rebuilt the tier files using VLOOKUP formulas keyed to product ID rather than row position. This eliminated the row-insertion failure mode. They also added a validation sheet that cross-checked each tier price against expected discount range boundaries and flagged any result outside the normal band.

The rebuilt system ran without a pricing incident for approximately 10 weeks. Then a supplier updated product codes for a line of surgical consumables — renaming 63 SKUs with new catalog numbers while keeping the products substantively identical. The product code change broke the VLOOKUP references in all three tier files simultaneously for those 63 products, replacing calculated prices with #N/A errors. The team caught the errors before the next price export but spent 6 hours tracing and correcting the references.

The team also investigated whether their ERP system — which managed inventory and invoicing — could handle the tier pricing logic. The ERP had a customer group pricing module, but it required prices to be entered as absolute values rather than calculated as percentages of a base price. That meant any change to the master retail price list would require recalculating and re-entering 2,800 prices in three customer groups — essentially 8,400 manual entries per price cycle. The ERP module was ruled out as operationally impractical at that catalog size.

A third option considered was engaging a developer to build a custom pricing service that would generate tier price lists from a maintained database. The developer estimated 3-4 weeks of build time and an ongoing maintenance requirement. Given the relatively predictable structure of the pricing logic, this seemed disproportionate — the problem was not complexity, it was the absence of a dedicated tool that handled tiered B2B pricing at catalog scale.

The Solution

The distributor implemented MicroPIM’s product pricing rules engine to replace the four-file spreadsheet system. The pricing logic that had been distributed across linked Excel formulas was consolidated into a single set of rules, evaluated against each customer segment channel automatically when product costs or base prices changed.

Step 1: Defining Customer Segment Channels

The first configuration task was creating three publishing channels in MicroPIM corresponding to the three price tiers: Dealer, Distributor, and Retail. Each channel stored the tier’s discount structure and margin floor requirements.

Rather than storing absolute prices, each tier channel was configured with rules relative to the Retail channel base price:

• Retail: Calculated from cost + category-specific gross margin target. This is the reference price.
• Dealer: Retail price minus the contractually defined discount percentage per product category.
• Distributor: Retail price minus a deeper discount percentage per category, with a separate margin floor rule preventing the distributor price from dropping below cost plus 8%.

Category-level discount percentages were stored as channel configuration parameters, not embedded in per-product formulas. This meant a contractual renegotiation — say, the dealer tier discount on diagnostic equipment moving from 22% to 24% — required changing one parameter in the Dealer channel configuration, not editing formulas across hundreds of product records.

Step 2: Building Category-Level Pricing Rules

With the channel structure in place, the team built pricing rule templates for each product category. Each rule template defined:

• The base price calculation from cost (gross margin percentage by category).
• The floor price per tier (absolute minimum sell price, expressed as cost plus a minimum margin percentage).
• Price rounding behavior (prices rounded to the nearest €0.05 for retail, nearest €0.10 for dealer and distributor tiers to reduce invoice line complexity).

The margin floor rule for the distributor tier was particularly important. Because distributor discount percentages were deep — 35% below retail on diagnostic equipment — a cost increase that reduced the retail margin would propagate to the distributor tier and could theoretically produce a distributor price below cost. The floor rule prevented this by flagging any product where the formula output fell below cost plus 8% for human review before publication.

[SCREENSHOT: Pricing rule template editor for the surgical consumables category, showing the three-tier configuration with base margin calculation, per-tier discount percentages, and margin floor rules for each tier visible in a single panel]

Step 3: Migrating the Existing Catalog

The existing 2,800 SKU price data was imported into MicroPIM with cost as the only price input. The system calculated all three tier prices from the rules. After the initial calculation, the team ran a comparison between the MicroPIM-generated prices and the previous spreadsheet prices for 200 randomly sampled products across all categories.

The comparison found 14 discrepancies between the systems. Investigating each one revealed that 11 were cases where the spreadsheet contained manually overridden prices that had not been documented anywhere — the formula had been deleted and replaced with a hardcoded number at some point. These overrides were reviewed with the commercial team, confirmed as intentional exceptions, and recreated as product-level price overrides in MicroPIM. The remaining 3 discrepancies were rounding differences from the old system’s inconsistent rounding behavior.

Step 4: Supplier Cost Update Workflow

Supplier cost updates arrive quarterly as PDF price lists and, for two major suppliers, as CSV files. The CSV updates are imported directly. PDF updates are processed via a simple data entry form in MicroPIM where the cost field is updated per affected product. In both cases, the pricing rules recalculate all three tier prices automatically when the cost field changes.

The team reviews the output of each cost update in MicroPIM’s validation queue before publishing. The queue shows any products where the new tier price breached the margin floor — indicating the cost increase was large enough to compress margin below the contractual minimum. These items get flagged for commercial review before the updated prices are sent to customers.

[SCREENSHOT: Validation queue after a supplier cost update, showing 8 flagged products where the calculated distributor price breached the margin floor, with current cost, calculated price, and minimum floor price shown per product]

The Results

Eight months after implementation:

• Contract violation incidents: zero. The January incident — where dealer accounts received distributor-tier prices — was caused by a row-reference error that the new system’s rule-based approach makes structurally impossible. Tier pricing is now derived from a rule applied to a product ID, not from a formula tied to a spreadsheet row.
• Price update cycle time reduced from 6-8 hours to 45 minutes. Quarterly supplier cost updates that previously required rebuilding and cross-checking four spreadsheet files now take under an hour from CSV import to validated price output.
• Margin floor breaches surfaced and handled proactively. In eight months, the validation queue flagged 34 products across three cost update cycles where distributor pricing would have breached the margin floor. All 34 were reviewed and corrected before any price took effect on customer accounts.
• New SKU onboarding time cut from 40 minutes to 8 minutes. Adding a new product requires entering the cost and assigning a product category. All three tier prices are calculated automatically.
• Rogue price overrides eliminated. The migration discovered 11 undocumented manual price overrides in the spreadsheet system. These are now documented product-level exceptions in MicroPIM with notes on why the override exists and who approved it.
• Audit readiness improved. The pricing team can generate a full three-tier price list with cost and margin data in under 2 minutes, which previously took approximately 3 hours to compile from the four linked spreadsheet files.

The pricing manager noted that the January incident — including the €11,400 credit note, the management time spent on the dispute, and the reputational cost with their largest dealer — would have been prevented entirely if the rule-based system had been in place six months earlier.

Key Takeaways

• Product pricing rules for multi-tier B2B pricing should be stored as channel-level configuration parameters, not as per-product spreadsheet formulas. Configuration is maintainable; thousands of formulas are not.
• The failure mode of spreadsheet-based tier pricing is not obvious arithmetic errors — it is silent reference corruption from row insertions, product code changes, or undocumented manual overrides.
• Margin floor rules are a prerequisite for automated pricing in B2B contexts where distributor discounts are deep. Without a floor, any cost increase can silently produce below-cost distributor prices.
• Documenting product-level price exceptions is as important as the base pricing logic. Undocumented overrides accumulate over time and become a source of errors during system migrations or audits.
• The real cost of a tier pricing error in B2B is not just the margin loss — it is the contract dispute, the credit note obligation, and the damage to the commercial relationship with the affected account.

If your B2B catalog has more than three customer segments or more than 500 SKUs per tier, managing product pricing rules in spreadsheets carries a predictable risk of the type described above. MicroPIM’s pricing rules engine handles per-segment discount structures, margin floor validation, and automated recalculation from a single connected workflow. You can set up your tier configuration and test price outputs before moving any live catalog at app.micropim.net/register.

Related Reading

• B2B Product Catalogues
• Bulk Edit 10,000 Products in Minutes
• Case Study: Supplement Brand Tiered Pricing

Frequently Asked Questions

How does MicroPIM handle product pricing rules for a catalog where different categories have different tier discount percentages?

Discount percentages are set at the category level within each tier channel configuration. When a new product is assigned to a category, it inherits that category’s tier discount structure automatically. If a product needs a different discount from the category default — for example, a high-demand item where the dealer discount is contractually fixed at a specific percentage — a product-level override applies without affecting the category rule for other products.

Can dealer and distributor prices be kept confidential so each tier only sees their own price?

Yes. Each tier channel in MicroPIM is a separate publishing output. The price list generated for dealer accounts contains only dealer-tier prices. The distributor price list is generated separately. There is no shared output that exposes multiple tiers simultaneously. Access controls in MicroPIM can also restrict which team members can view which tier’s pricing data.

What happens when a supplier product code changes but the product is substantively the same?

Product identity in MicroPIM is maintained by an internal product ID, not the supplier’s SKU. When a supplier renames a product, the supplier SKU field on the product record is updated — the pricing rules, tier configurations, and override history remain intact. This is precisely the failure mode that caused 6 hours of rework in the spreadsheet system described in this case study.

Is it possible to schedule tier price updates to go live at a specific time rather than immediately?

Yes. Publishing jobs in MicroPIM can be scheduled for a specific date and time. For this distributor, quarterly price updates are typically scheduled to go live at the start of business on the first working day of the new quarter, giving customer accounts a predictable effective date and allowing the commercial team to send advance notification without managing a manual publishing step.