KeHE UDR: The 48-Hour Deduction Response Playbook

If you distribute through KeHE and have been doing the mental math on unexplained short-pays, there is a good chance a UDR is somewhere in the picture. Deductions routinely consume 2–5% of gross sales for natural and specialty CPG brands — and the UDR is one of the fastest-moving clocks in the business.

This guide walks through exactly what a KeHE UDR is, how the 48-hour response window works, and the step-by-step process for disputing a deduction through K-Solve inside KeHE CONNECT. It is written for founders and part-time controllers at brands doing $1.5M–$5M in revenue — the people handling a thousand things at once and only finding a deduction when the check comes in short.

What Is a KeHE UDR?

UDR stands for Unloading Discrepancy Report. When KeHE's receiving team identifies a problem at one of their distribution centers — a quantity shortage, an overage, product damage, or insufficient date codes — they file a UDR. The report captures the products affected, the quantities at issue, and the reason for the discrepancy.

Under KeHE's Supplier Policies and Procedures, the UDR governs the dispute: KeHE's own case count at the DC is the authoritative record, and if their deduction is supported by a filed UDR, KeHE will not repay a supplier for shorted quantities unless the supplier successfully disputes the report.

That last sentence is the reason the 48-hour window matters so much.

The 48-Hour Clock: What It Is and When It Starts

Once a UDR is filed, KeHE's policy requires suppliers to respond in writing within 48 hours of notification and any disposition request. The 48-hour window applies to any shipment where a UDR is triggered — shortages, overages, damage, insufficient date codes, and similar receiving exceptions.

A few things to understand about how this window works in practice:

The notification is not always obvious. KeHE communicates with suppliers through the KeHE CONNECT Supplier portal (connectsupplier.kehe.com). Verify: Whether KeHE sends a separate email notification when a UDR is filed, or whether suppliers must proactively monitor the portal. Multiple sources indicate CONNECT is the primary communication channel; confirm with your KeHE broker contact or Vendor Performance team whether email alerts are enabled for your account.

48 hours is real-time, not business days. The policy language does not carve out weekends or holidays. If a UDR is filed on a Friday afternoon, the clock does not stop at 5 PM.

What you are responding to. Your 48-hour response is not a formal K-Solve dispute submission — it is an initial written response to the discrepancy claim. You are telling KeHE that you dispute the receiving count and attaching your evidence. The K-Solve formal dispute process follows separately.

Required documentation for a UDR response:

Signed Bill of Lading (BOL)
Packing Slip

If you cannot produce a signed BOL from the carrier, your UDR dispute is essentially over before it begins. This is the single most common reason UDR claims become permanent deductions: the BOL was not retained, was unsigned, or cannot be located within the 48-hour window.

Prepare Before the Clock Starts

The fastest way to lose a UDR dispute is to start your document hunt after notification arrives. Here is the pre-shipment and on-delivery checklist that puts you in a position to respond within the window:

At time of shipment:

Retain the signed original BOL from your carrier or 3PL — do not file and forget it
Scan or photograph the BOL immediately after driver signature
Retain a copy of the packing slip with case counts and SKUs matching the BOL
Note the PO number and invoice number tied to each shipment
If using a 3PL, confirm their document-retention SLA in writing

At time of delivery:

Request a copy of the receiving log or delivery receipt from your carrier
If a shortage or damage is flagged at delivery, note it in writing to your carrier the same day
Log the delivery date and DC location receiving the shipment

After payment arrives:

Reconcile every check against your open invoices before it is deposited — short-pays tied to UDRs will appear as deduction line items
Match deduction codes on your remittance to the invoice prefixes in KeHE CONNECT (shortage and damage deductions will carry specific prefix codes) Verify: KeHE uses an alphanumeric prefix system for deduction codes — your remittance should show codes tied to each deduction line; confirm the specific prefix codes used for UDR-related shortages in your current KeHE CONNECT account
If any deduction appears that you cannot match to an authorized allowance or known compliance issue, flag it immediately — do not let it age

Standing infrastructure:

Designate one person (even if that person is you) who receives KeHE CONNECT portal alerts
Set a calendar check — minimum weekly — to review K-Solve for any new deduction activity
Keep a shared folder (Google Drive, Dropbox, or equivalent) where all KeHE BOLs and packing slips are filed by PO number and delivery date

Step-by-Step: The K-Solve Dispute Submission Process

Once you have identified a deduction you want to contest, K-Solve is where the formal dispute lives. K-Solve is KeHE's built-in deduction dispute and ticketing system, accessed through KeHE CONNECT.

Step 1 — Log in to KeHE CONNECT

Go to connectsupplier.kehe.com and log in with your supplier credentials. Verify: If you do not have supplier credentials or your account is not yet activated on CONNECT, contact your KeHE broker or reach out to [email protected] to get access established. Do not wait until a dispute is urgent to sort out portal access.

Step 2 — Navigate to K-Solve

From the KeHE CONNECT dashboard, navigate to Sales Orders → Credits → K-Solve. K-Solve has its own dashboard that organizes credits and debits by individual check and check date from KeHE.

Step 3 — Find the Deduction

Use the transaction grid to locate the deduction you want to dispute. The grid is organized by date, amount, deduction type, and invoice details.

For recent deductions (within the last 90 days), use Quick Search
For older deductions, use the Advanced Search (accessed via the Filters icon) — K-Solve retains up to two years of historical transaction detail
Export the filtered view to Excel using the Export button if you need to work through multiple deductions at once

Step 4 — Review the Deduction Detail

Click the Document icon (View Backup) next to the deduction line to pull up KeHE's supporting backup documentation. For UDR-related deductions, this will show the receiving team's count versus your invoice count.

Use the Notes icon to view any existing communications tied to that deduction.

Step 5 — Submit the Dispute

Click the Dispute icon to open the dispute submission form. Fill out the K-Solve form thoroughly:

PO number tied to the shipment
Invoice number and invoice date
Exact deduction amount you are disputing
Clear written statement of why the deduction is not valid — be factual, not argumentative. Example: "Our signed BOL from carrier [name] on [date] confirms delivery of [X] cases of [SKU] to [DC location]. We dispute the [Y]-case shortage reflected in this deduction."
Upload all supporting documents: signed BOL, packing slip, any carrier delivery confirmation or proof of delivery (POD)

The more complete your submission, the less back-and-forth. Incomplete disputes are the most common reason resolutions drag beyond the 21-day standard window.

Step 6 — Record Your Ticket Number

K-Solve generates a unique dispute ticket number when you submit. Write this down. You will need it if you follow up or if KeHE requests additional documentation.

Step 7 — Monitor and Follow Up

Log back into K-Solve periodically to check the status of your dispute. KeHE's standard resolution timeline is approximately 21 days. If you have not received a response by then, follow up referencing your ticket number. Verify: Whether K-Solve sends email notifications when case status changes, or whether you must actively monitor the portal for status updates.

The 180-Day Hard Deadline: What It Means for Your Deduction Backlog

A separate but related clock governs all KeHE deductions — not just UDRs. Suppliers have 180 days from the date of a deduction to dispute it. KeHE updated this policy, and as of the October 2025 enforcement change, they now remove the dispute option entirely for any deduction older than six months. The functionality disappears from K-Solve; there is no exception process.

This is a significant shift from prior practice, when the 180-day window existed in KeHE's terms but was rarely hard-enforced. Suppliers who had been accumulating a backlog of uncontested deductions and planning to address them "eventually" lost that runway.

What this means for you:

If you have a stack of KeHE remittances that you have not fully reconciled, the 180-day window is the most pressing issue on your deduction desk right now — more pressing, even, than individual UDR responses. Six months sounds long until you account for the time it takes to track down a two-year-old BOL, reconcile the invoice, and build the dispute packet.

Immediate triage steps if you have aging deductions:

Export all KeHE deductions from the past six months from K-Solve using the Advanced Search and Export function
Sort by age — anything approaching 150 days should be your first priority
Identify which deductions are UDR-related, which are compliance-related, and which may be invalid MCB or promo charges
Gather whatever documentation you still have and file disputes before the window closes, even if your file is incomplete — a filed dispute with partial documentation is better than no dispute at all
For deductions already beyond 180 days: accept that those are gone and use the loss as the internal justification to build a weekly deduction-monitoring routine

KeHE Deduction Types: Know What You Are Disputing

Not every KeHE deduction is disputable on the same grounds. Understanding the category before you open K-Solve saves time and improves outcomes.

UDR-related deductions (shortage, damage, overage, date code): Disputable with signed BOL and packing slip. These are the highest-volume dispute category for most brands. The 48-hour initial response window applies here.

Invoice Adjustments (IA prefix): Pricing or quantity discrepancies between your invoice and KeHE's PO. Dispute by submitting a comparison showing your PO confirmation versus KeHE's stated terms. Include the original KeHE PO and your invoice side by side.

Non-Compliance deductions (freight, routing, labeling): These are harder to dispute successfully because KeHE's Inbound Routing Guide is detailed and the compliance standard is clear. Dispute is possible if you have documented proof of compliance — photographs, carrier receiving logs, time-stamped confirmation. But the honest answer is that if a routing violation occurred, the deduction is likely valid.

MCB / Promotional deductions (various prefixes by retailer or program): Mandatory Co-op / Marketing Co-op Budget deductions and promotional allowances are largely non-disputable if they were agreed to in your trading terms. Dispute only when the amount does not match your signed promotion authorization.

Unsaleable deductions: Disputable with POD and documentation about product condition at the time of transfer. Photographs from the shipping point help considerably.

Verify: The KeHE deduction code prefix system is documented internally and in your remittance detail — confirm with your KeHE vendor performance contact which specific codes correspond to UDR-generated deductions in your account, as prefix assignments can vary by DC region and account setup.

Frequently Asked Questions

Q: What exactly triggers a UDR? Is it always KeHE's error?

A UDR is triggered whenever KeHE's receiving team records a quantity that differs from the purchase order — shortage, overage, damage, or date code issue. Sometimes the discrepancy is a legitimate receiving error on KeHE's side; sometimes it reflects a real fulfillment gap. The important thing is that KeHE's policy makes their receiving count the authoritative record unless you dispute it with a signed BOL. The UDR does not automatically mean you made a mistake — it means the counts do not match and you have 48 hours to produce your evidence.

Q: Can I dispute a UDR after the 48-hour window has closed?

The 48-hour window governs your initial written response to the UDR notification. Once that window closes, the deduction generally becomes final for that specific UDR claim. However, the K-Solve dispute portal remains available for up to 180 days for formal submission of disputes across all deduction types. In practice, the closer to the 48-hour window you respond, the stronger your position — but you can still file a K-Solve dispute if you discover the deduction later, as long as you are inside the 180-day hard deadline. Verify: Whether KeHE treats a UDR dispute differently in K-Solve if the 48-hour initial response window was missed — confirm with [email protected] whether K-Solve dispute rights persist past the 48-hour window for UDR-originated deductions.

Q: How do I know when a UDR has been filed against my account?

KeHE CONNECT is the primary communication channel. The best practice is to monitor the portal proactively rather than waiting for a notification. Verify: Whether KeHE pushes email notifications when a UDR is filed, or whether suppliers must log in and check K-Solve manually. Confirm with your broker contact or KeHE's Vendor Performance team whether your account has email alerts configured.

Q: What is the realistic win rate on UDR disputes?

Win rates on UDR disputes are heavily document-dependent. If you have a clean, signed BOL that shows full case count delivery and KeHE's UDR claims a shortage, a well-documented dispute has a reasonable chance of success. Disputes filed without a signed BOL, or with a BOL that has ambiguous case counts, are unlikely to succeed. No reliable aggregate win-rate data exists for this dispute category across suppliers; any specific percentage you see cited in vendor marketing should be treated skeptically.

Q: Do I need to dispute through K-Solve, or can I email KeHE's Vendor Performance team directly?

Both channels exist. You can email [email protected] or submit through K-Solve in KeHE CONNECT. K-Solve is the preferred and increasingly mandatory channel — KeHE's November 2025 documentation update explicitly expanded the mandate to use CONNECT and K-Solve for all disputes and transactions. Using K-Solve also gives you a ticket number and a documented paper trail, which matters if a dispute escalates or is later reviewed.

The Downstream Cost of Ignored UDRs

At 2–5% of gross sales, deductions can represent $30,000–$250,000 per year for a brand doing $1.5M–$5M through KeHE. UDR-related shortages and damages are one of the highest-volume deduction categories for brands shipping to KeHE distribution centers, particularly for brands managing their own freight or working with smaller carriers where documentation disciplines vary.

The brands that recover the most on UDR disputes share three practices: they have someone designated to check CONNECT at least weekly, they keep BOLs filed and accessible by PO number, and they treat deduction reconciliation as a weekly task rather than a quarterly cleanup.

The brands that consistently eat UDR deductions share the inverse: they catch the short-pay weeks after the check arrives, the BOL is buried or unsigned, and the 48-hour window is long gone.

KeHE distributes to approximately 8,500 brands through its natural and specialty network. The deduction management infrastructure gap is widest in the $1.5M–$5M tier, where there is no AR clerk running daily reconciliations and no enterprise trade promotion system generating dispute packets automatically. If that describes your operation, the playbook above is the manual version of what a well-run deduction desk does every week.

This guide is part of a free deduction-defense resource series for emerging CPG brands.