Why Most Industrial Sales Comp Plans Break at the Branch Level

If you're a VP of Sales Operations or RevOps leader at an industrial company, you've probably spent more Q4 hours than you'd like defending a comp plan that technically does what it was designed to do — and yet leaves three reps angry every quarter. The angry reps aren't wrong. The plan is broken. It's just broken in a way that only shows up when one parent company runs 30 plants across five reps' territories.

Territory rebalance takes three weeks, four Excel versions, and two rep complaints per cycle. The comp-plan conversation that follows makes the rebalance look easy.

This post is for sales ops and RevOps leaders who own the comp plan at industrial sales organizations. Field rep leaders will find it relevant as a framing document for credit-splitting conversations with their teams. The premise is narrow: most industrial comp plans were designed around an assumption — one logo equals one territory — that breaks the moment the account in question is a multi-plant parent. Which, in industrial sales, is most of the time.

We'll walk through three failure modes, three modern patterns that resolve them, and the facility-level data prerequisite that determines whether any of the modern patterns are actually implementable.

The problem in one paragraph

Rep X lands a $400K equipment deal at the Cleveland plant of Berry Global. Berry Global operates roughly 290 locations globally and built much of that footprint through the $6.5 billion acquisition of RPC Group in 2019, which added 153 manufacturing locations across 33 countries on top of Berry's existing 140. Rep Y covers the Atlanta plant. Rep Z covers three Texas plants. The VP of Procurement at Berry's Evansville HQ, who ultimately signed off on the Cleveland purchase, sits in national-account rep W's patch.

Who gets paid? If the answer is "Rep X only, because Rep X found the Cleveland opportunity," then Reps Y, Z, and W have no incentive to share intelligence, introduce contacts at their plants, or support the corporate procurement relationship that made the deal possible. If the answer is "everyone gets full credit because this is a national account," you've just quadrupled your cost of sale on one deal. Neither answer is right.

This is the branch-level comp problem. Every industrial sales organization hits it. Most handle it with informal rules that shift quarter to quarter, depending on who complains loudest.

Why this is harder than SaaS comp

SaaS companies built modern comp plans around a clean assumption: one company equals one contract. Sign the master agreement, and every seat, every division, every subsidiary is covered. National-account motion is for the Fortune 500. Everyone else gets a single logo-level quota.

Industrial sales doesn't work that way. Industrial purchases are usually plant-level. A conveyor for the Bloomington plant, a dust collector for Houston, a safety system for Fort Wayne — each purchased independently, with its own PO, often its own approval chain, sometimes off different plant-specific budgets. The same parent might standardize on a preferred-vendor list at corporate but leave the actual buying decision to each plant manager.

So you have a structural mismatch. Corporate procurement can set vendor-qualification rules that affect all 30 plants. Each plant manager decides what and when to buy. And the rep team is organized geographically, not by account. Any given deal can touch three to seven comp plans simultaneously — national account, corporate procurement, the geographic rep who owns the plant, the specialist rep who owns the product category, and sometimes an inside rep who sourced the opportunity.

If you design the plan for one of those channels, the others lose incentive. If you pay everyone, you blow the margin on the deal.

The three failure modes

Failure mode 1: Geographic-only credit (pay the rep who owns the zip code)

This is the simplest model and still the most common. Every deal credits one rep: the one whose territory contains the ship-to address. No splits, no exceptions.

The failure case: Rep X spends six months nurturing the corporate procurement director at the parent's Evansville HQ. She builds the business case, navigates corporate approval, and wins vendor qualification. The resulting POs flow from 22 plants across eight states. Rep X gets credit on two of them (the ones in her territory). Eight other reps get credit on the rest. Rep X quits within the year because the effort-to-reward ratio is broken.

Alexander Group describes this as the "ship-to" problem: global accounts purchase products on a worldwide basis, but the accounting system only recognizes the ship-to location for sales-crediting purposes. The person who actually sold the account — built the corporate relationship, won the vendor qualification, navigated the procurement committee — receives credit only for orders that happen to ship to their geography. Every other shipment goes to the rep who owns the destination zip code and did none of the selling work.

Failure mode 2: Account-ownership credit (pay the rep who "owns" the logo)

The mirror image: assign each parent account to one rep — usually based on HQ location or historical relationship — and that rep gets credit on every deal, regardless of where it ships.

The failure case: Rep X "owns" a parent headquartered in Ohio. Rep Z has a great relationship with the plant manager in Fort Wayne and gets her an introduction to evaluate a new product. The deal closes. Rep X gets paid. Rep Z gets nothing, and her next manager-introduction request at a plant Rep X "owns" gets a polite decline.

This model also fails the field-service dimension. Account managers and CSMs working expansion at the plant level have no incentive when they know the geographic rep will be credited. The expansion never happens.

Failure mode 3: Everyone gets full credit (double-count everything)

Also common, especially at companies that tried failure mode 1 and got rep attrition, then tried failure mode 2 and got account manager attrition. The "solution" is to credit everyone: the national account manager gets 100%, the local rep gets 100%, the specialist rep gets 100%.

The failure case: you've just tripled your cost of sale. The 20% commission rate on a $400K deal becomes 60% after you credit three parties. Margin on that deal collapses. After two quarters, finance notices. Comp plan gets rewritten mid-year. Reps lose trust in the plan. Everyone is worse off than they started.

Three modern patterns that actually work

All three depend on the same prerequisite: you must have facility-level data. If your CRM shows one record for Berry Global at the Evansville HQ and 289 other plants are invisible, none of these patterns can be implemented. You can't credit a deal to the rep who owns the Fort Wayne plant if Fort Wayne doesn't exist as an account in your system.

We'll return to that prerequisite after walking through the three patterns.

Pattern 1: Double quota / double credit (with honest quota inflation)

This is Alexander Group's preferred model for horizontal crediting. Both the national-account rep and the local geographic rep carry quota on the deal. Both get paid in full. The catch: the company-level quota budget is inflated to reflect the fact that one dollar of revenue may be counted twice.

In practice:

• National account manager has a $5M quota covering all activity at the parent company, anywhere it ships
• Local geographic rep has a $800K quota covering the Fort Wayne plant (and other accounts in her territory)
• A $400K Fort Wayne deal credits $400K against the NAM quota and $400K against the local rep quota
• Total quota across the team is inflated to reflect the expected overlap — if historical data says 30% of revenue is double-counted, total quotas add up to ~130% of revenue target

The benefit: both sides are incentivized to collaborate. The NAM brings corporate approval; the local rep brings plant-manager intelligence; neither is penalized for the other's involvement.

The cost: the company must model double-counting honestly in its quota-setting process, and the finance team must understand that quota attainment above 100% is the correct signal for the right amount of collaboration — not a signal that quotas were set too low.

Pattern 2: Fixed credit splits by deal type

Instead of paying everyone fully, predefine the split for each deal category. Alexander Group lists this as one of the cleanest solutions: fixed, unambiguous rules that don't require field negotiation.

A common industrial-sales structure:

The benefit: no negotiation. Every deal fits a category; every category has a rule. Reps know before they pursue a deal how it will be credited.

The cost: you need crisp enough deal categorization to assign the right rule. And you need facility-level data so the "pro-rated across affected plants" math actually works — if you don't know how many plants the deal touches, you can't pro-rate.

Pattern 3: Accelerators for multi-facility wins

The third pattern layers on top of either of the first two. Beyond base credit, reps earn accelerated commissions when a deal expands across multiple facilities of the same parent — regardless of whose territory those facilities are in.

Example structure:

• Base commission: 8% on plant-level deals
• Accelerator: +2% on any deal that includes 3+ sites of the same parent
• Further accelerator: +2% more on any deal that includes 10+ sites
• Multi-site bonus pool: 1% of multi-site revenue split among all reps who contributed (confirmed by activity logs)

The benefit: direct incentive for reps to look up from their zip code and pursue the parent-level expansion. Rep X, who lands the Cleveland deal, is incentivized to pull in Rep Y and Rep Z to expand to their Berry Global plants — because the accelerator on a 20-site rollout is bigger than what she'd earn keeping the deal to herself.

The cost: you need real-time visibility into which plants belong to which parents. This is the prerequisite we've been circling.

The facility-level data prerequisite

All three modern patterns share one requirement: your comp system must know, at the facility level, which plants belong to which parent. Not at the logo level — at the physical-plant level.

This is where most industrial sales organizations are stuck. Their CRM holds one record per parent company. Plant-level activity lives in rep notes, Excel shadow systems, or the rep's memory. The comp plan can't implement Pattern 1 (double credit) without knowing which local rep owns the plant. It can't implement Pattern 2 (fixed splits) without a clean deal-type classification tied to a plant record. It can't implement Pattern 3 (multi-site accelerators) without knowing how many plants a given deal touches.

The data problem compounds when parents grow through acquisition. Berry Global added 153 RPC plants in 2019. Illinois Tool Works runs more than 500 facilities globally, assembled through roughly 100 acquisitions in the 1990s alone. Parker Hannifin acquired CLARCOR in 2017 — a $4.3 billion deal that brought in more than a dozen brands (Baldwin, Fuel Manager, PECOFacet, Airguard, Purolator) across filtration product lines. Each of those acquisitions added plants that often still operate under the pre-acquisition brand internally. Your comp system, working off CRM data, sees only the parent logo and maybe a corporate HQ address. The 290 Berry Global facilities, the 500+ ITW sites, the dozen CLARCOR brands — none of those are visible as individual records.

If you try to implement double-credit comp without facility-level data, you'll end up negotiating every split by hand — exactly the field-negotiated chaos Alexander Group warns against.

A worked comp-credit scenario

Let's make this concrete. Here's a real-pattern deal and how each comp model treats it.

The deal: Rep X, who covers Ohio and eastern Indiana, lands a $600K order for dust-collection systems at a food-processing parent. The order covers five plants — three in Ohio (Rep X's territory), one in Michigan (Rep Y), one in Illinois (Rep Z). The national account manager, Rep W, spent four months on corporate approval. The specialist sales engineer, Rep S, ran the technical evaluation at the Ohio plants.

The geographic-only model credits $600K total but leaves Rep W — who did four months of corporate work — with nothing. Rep W leaves the company within the year.

The everyone-full-credit model pays $3M of commissions on a $600K deal. Margin gone.

Pattern 1 costs the company more than Pattern 2 or Pattern 3 in absolute commission dollars — but the quota budgets are set to expect it, and every rep who contributed is paid for their contribution. Rep W stays. Reps Y and Z stay engaged for the next multi-site deal.

Patterns 2 and 3 strike a middle ground: the NAM gets the bulk of the credit (rewarding the work that made the deal possible), the local reps get proportional credit (rewarding the access they provided), and the total commission cost stays inside margin.

There is no universally correct pattern. The right choice depends on the company's selling motion — how much of the revenue comes from national-account pursuits versus plant-level selling. What matters is that the rules are explicit, documented, and — critically — implementable, which requires facility-level account data.

How to design the comp plan around a facility-level database

If you have facility-level data in place, the comp-plan design loosens. Here's how the process works.

Step 1: Map every facility to a parent and a territory

Before any quota is set, the facility-level database is the source of truth for which plants exist, which parent they belong to, and which geographic territory they sit in. This map is the comp-plan substrate. You can't run any of the three modern patterns without it.

Step 2: Classify deals by initiation source

Every opportunity in the pipeline gets tagged on creation: plant-initiated, NAM-initiated, specialist-initiated, inbound-marketing, partner-referred. The tag drives the credit-split rule (Pattern 2) and the multi-site accelerator trigger (Pattern 3).

Step 3: Set quotas with honest double-count math

If you're using Pattern 1 (double quota/credit), model the historical overlap from prior-year data. If 30% of revenue is double-counted, total quota budget is 130% of revenue target. Don't hide the double-counting — make it explicit in the plan doc.

Step 4: Rollup reporting by parent + by territory

Every rep sees two views: their plant-level pipeline (deals by facility in their geography) and their contribution to parent-level rollups (deals at plants under parents where they have activity, even outside their territory). The second view is what surfaces the multi-site expansion opportunities Pattern 3 is designed to capture.

Step 5: Quarterly review of credit disputes

Even with clean rules, edge cases happen — a specialist rep who contributed technical work but wasn't formally logged, a former rep who started the relationship before territory rebalance. Budget a small pool (typically 1–2% of commissions) to resolve edge cases quarterly, with sales ops as adjudicator. The existence of the pool reduces field negotiation; reps know there's a formal path for appeal.

The comp plan is a data problem first

If you're a VP of Sales Ops who has tried to design a multi-site industrial comp plan and given up, the usual culprit is the data, not the plan. Clean plans fail because the underlying account data can't support the rules. The NAM's 22-plant rollout can't be credited correctly if your CRM only has 2 of those 22 plants as records.

Facilities Finder indexes every US industrial facility as its own first-class record — 600,000+ across all 50 states, with parent-company rollup that links every plant back to its parent ID. One search on "Berry Global" returns all of the company's US facilities, not just the Evansville HQ — each as an individual account in the built-in CRM, with its own plant manager, operations director, and purchasing contacts. Territory polygons let sales ops assign geographic ownership at the facility level, so every deal in the pipeline has a clean "which rep owns this plant?" answer — the prerequisite for any credit-splitting rule to function. Our AI ingests billions of public signals — satellite imagery, map providers, company websites, EPA filings, permit records, trade publications — and extracts what actually matters: products, capabilities, employees, certifications. Every facility record is the output of that enrichment, not a data entry from a corporate filing.

600,000+ US industrial facilities, rolled up to parent across all 50 states.

Draw your first territory and see the parent rollups — get access to Facilities Finder.

See also: How to Build a Territory List for a New Sales Rep in Under an Hour · How to Find Every Facility Owned by a Target Parent Company · The 6-Month Rep Ramp Problem: How Industrial Teams Actually Shorten It