Ship and debit: distributor claims in Salesforce

Channel Revenue Management pays off for ship and debit when a manufacturer handles many special price claims from distributors and checks them by hand today. Ship and debit means the distributor sells to a named end customer below its own purchase cost and claims the difference. Salesforce validates such claims against programme rules and transaction data and adds price protection for falling list prices. The add-on is listed at $30,000 per org and year, partner access extra. It only holds up when sell-through and distributor stock data arrive, because without them the validation can only check whether the paperwork fits the programme.

What is ship and debit?

Ship and debit is a special price for one deal. The Trailhead unit1 calls it a special pricing agreement: “a contract that defines the discounted price for a specific customer”, with a duration and the products included. Each programme is tailored to one combination of distributor and end customer.

The mechanics in the Trailhead example: a distributor buys sensor modules at $100 and sells them at $90 to end customers who order more than 1,000 units. The manufacturer reimburses $10 per unit. The distributor wins the project, the manufacturer keeps the list price for everyone else.

Price protection is the second use case. Salesforce describes it as protecting partner margins when prices change. When the manufacturer lowers a list price, distributors holding stock bought at the old price want the difference. The product page2 says price protection can be set up by “partner, price type, duration, or eligibility”. The object behind it, PriceProtectionTerm3, exists since API version 63.0.

How does Salesforce validate a claim?

The Trailhead unit on the lifecycle4 describes six steps:

1. 01

   Prepare the org

   Admin

   Enable the features and set up partner collaboration through Experience Cloud.

2. 02

   Design the programme

   Channel manager

   Define special pricing terms, eligibility and claim requirements, then enrol partners and eligible end customers.

3. 03

   Sell

   Distributor

   The distributor sells at the special price.

4. 04

   Submit the claim

   Claim clerk at the distributor

   Submission through the partner portal, with invoices or purchase orders as proof of sale.

5. 05

   Validate

   Automated

   Checks compare the claim with programme rules, special pricing terms and transaction data and flag duplicates, wrong quantities and ineligible transactions.

6. 06

   Settle

   Finance

   Review, adjust and reimburse. The Transaction Journal records approved payouts for audit.

Flows handle submission and approval, the Data Processing Engine handles large volumes. The core object is the rebate partner special pricing term. It holds the special price, the reference price, the reimbursable difference, quantity thresholds, eligibility criteria and products. A claim that passes all checks gets the status System Processed. The first unit also names CRM Analytics dashboards and predefined workflows for claim validation, and lists Business Rules Engine as a prerequisite module.

Payment itself stays where it is today. Salesforce calculates and approves, the credit note is booked in the ERP. That is the same split as for rebate management, and the interface carrying approved amounts to SAP should be planned with it.

Channel Revenue Management costs $30,000 per org and year

Salesforce publishes two different views:

Source	What it says
Manufacturing Cloud add-ons5	Channel Revenue Management for Manufacturing, $30,000 per org and year, available with the Sales editions and Max
Channel Revenue Management pricing6	No price, request a quote. Requires a Sales Cloud or CRM licence. Includes 10 channel manager admin users, channel inventory tracking, deal and design registration, rebate, ship and debit and price protection management. Partner access, additional users and payouts available for purchase
Experience Cloud add-on page7	Rebate Management “from $75”, without a unit

So the $30,000 covers the add-on for the org, and partner access for distributors comes on top. The Manufacturing Cloud add-ons page lists Partner Community for Manufacturing at $20 per login or $50 per member and month. The $75 rebate management listing does not fit the $30,000 figure.

How I would turn that into a five-year comparison against the current process is described under make-or-buy and licence forecasts.

How is ship and debit different from rebates?

Rebates reward volume. A dealer reaches a tier over a quarter or a year and gets a percentage back afterwards, as described in rebate management for dealer rebates. Ship and debit compensates price, deal by deal, for a specific end customer. Price protection compensates price as well, triggered by a list price change instead of a deal.

That difference changes who works with the system. Rebates are calculated by programme managers at period end. Ship and debit claims arrive continuously, from claim clerks at distributors, and someone at the manufacturer has to process them within days. Trailhead promises reimbursements “within hours instead of weeks” for claims that pass automated validation. The claims that fail still need a person.

In my view, many manufacturers selling through dealers only need rebates. Ship and debit matters when distributors hold stock and quote projects for end customers you also know, typical for components, electronics or industrial supplies sold through a two-tier channel.

Claim validation needs sell-through and distributor stock

Sell-through and stock. A claim says: I sold 1,200 units to customer X at $90. To check it, Salesforce needs to know three things:

• That the sale happened. Proof of sale documents or point-of-sale data from the distributor, ideally as a regular file, not as a PDF per claim.
• That the units came from your stock. Channel inventory per distributor, so a claim for 1,200 units does not exceed what the distributor bought.
• That the end customer was eligible. A clean customer master, so “Customer X Ltd” and “Customer X Limited” count as one company when they are one.

Without these, the validation checks whether the documents match the programme, not whether the sale was real. Overpayments in price protection come from the same gap: a distributor claims stock on hand at the old price that it no longer has. Channel inventory tracking is in the package; the data still has to come from the distributors. How distributor stock reaches Salesforce, and how old it is when it arrives, I describe in Agentforce for distributor stock and replenishment.

Worked example: 15 distributors and 600 claims a month

The figures are assumed. A manufacturer of electronic components sells through 15 distributors in Europe. 600 ship and debit claims arrive per month by email, with Excel lists attached. Two people in sales operations check them against special price approvals in a shared folder and pass approved amounts to finance.

With Channel Revenue Management, special prices become pricing terms, distributors submit claims through the portal, and the validation rejects duplicates and claims above the approved quantity before a person looks. Assume 80 percent of claims pass automatically. The two people then handle 120 exceptions instead of 600 claims.

Against that stand $30,000 a year for the add-on, portal licences for 15 distributors and the interface work. For partner access, the customer portal article explains what partners see and which licence covers it. If only three distributors send twenty claims a month, I would keep the current process and tighten the approval rules first. The chapter on the dealer and partner channel shows where ship and debit sits next to rebates, portals and dealer visits.

Count claims per month

1. Count. Claims per month, rejected claims and the average time to payment today.
2. Data. Which distributors can deliver sell-through and stock as files, and how often.
3. Price. Add-on, partner access and payout volume quoted in writing.
4. Process. Who approves exceptions, and how approved amounts reach the ERP.

Sources7

1. 1Trailhead unit (opens in a new tab)trailhead.salesforce.com
2. 2product page (opens in a new tab)salesforce.com
3. 3PriceProtectionTerm (opens in a new tab)developer.salesforce.com
4. 4Trailhead unit on the lifecycle (opens in a new tab)trailhead.salesforce.com
5. 5Manufacturing Cloud add-ons (opens in a new tab)salesforce.com
6. 6Channel Revenue Management pricing (opens in a new tab)salesforce.com
7. 7Experience Cloud add-on page (opens in a new tab)salesforce.com