If you sell to a national retailer such as Target, Best Buy, or Walmart, the payment that arrives is often smaller than your invoice. The gap is deductions: compliance chargebacks, shortage and pricing claims, damaged goods, returns, and markdown money. You can dispute the ones your agreement and the law do not support. Your vendor agreement and the documents it incorporates decide most of these disputes, and, unless the agreement validly chooses another state’s law, Minnesota’s version of the Uniform Commercial Code (“UCC”) supplies the default rules and some limits no agreement can remove. When a supplier brings me a deduction dispute, my first questions are what the signed terms say and whether the retailer’s numbers follow them.

What counts as a retailer chargeback or deduction?

A retailer deduction is any amount a retailer subtracts from what it pays on your invoices, and “chargeback” usually means a deduction the retailer assesses as a fee or fine. Each one is a claim against money the retailer otherwise owes. Minnesota’s UCC sets the baseline: “The buyer must pay at the contract rate for any goods accepted” (Minn. Stat. § 336.2-607(1)).

Deductions fall into four families:

  • Compliance chargebacks are fixed charges for a missed delivery window, a routing or labeling error, or an advance ship notice that does not match the shipment.
  • Shortage, pricing, and damage deductions claim that fewer units arrived than you billed, that your invoice price exceeds the agreed cost, or that goods arrived damaged.
  • Return deductions are credits for goods sent back, or an allowance taken instead of returning defective goods.
  • Markdown money and allowances cover margin support, margin true-ups after a season, and promotional allowances collected by deduction instead of by invoice.

Each family raises the same first question under Minnesota business contract law: which term of the agreement, or which rule of law, lets the retailer keep the money?

What do the vendor agreement and its incorporated terms let a retailer deduct?

A retailer may take the deductions that your vendor agreement and the documents it incorporates authorize. Minnesota’s UCC allows the parties to set those terms: subject to exceptions, including the duty of good faith, “the effect of provisions of the Uniform Commercial Code may be varied by agreement” (Minn. Stat. § 336.1-302(a)). The agreement therefore decides most deduction disputes, and the UCC’s default rules fill the gaps.

In my practice, the agreement is rarely one document. The national-retailer vendor agreements I have analyzed start with a short signed document that incorporates longer standard terms and portal-posted policies, alongside purchase orders and separate allowance contracts. Their terms run heavily in the retailer’s favor, with broad setoff and chargeback rights, liability limits that protect the retailer, and short contractual windows for bringing a claim. Those liability limits are subject to the UCC in a sale of goods. An exclusive or limited remedy that fails “of its essential purpose” gives way to the UCC’s general remedies (Minn. Stat. § 336.2-719(2)), and consequential damages “may be limited or excluded unless the limitation or exclusion is unconscionable” (Minn. Stat. § 336.2-719(3)). The same subsection does not treat a limitation of damages where the loss is commercial as prima facie unconscionable.

The practical step is to collect that whole set, including the vendor manual and routing guide, as it stood when each shipment went out, and to match each deduction code to the clause that authorizes it. Categories with no clause behind them are the first place to look for recoverable money. Whether a manual or portal policy is part of the deal depends on how the signed document refers to it, the question of how incorporation by reference pulls a separate document into a contract. Before you sign, the chargeback schedule, setoff clause, and dispute window belong on the list of vendor-agreement terms worth negotiating.

When does Minnesota’s UCC let a retailer deduct without a contract term?

When the vendor agreement is silent, Minnesota’s UCC lets the retailer deduct on three conditions: notice of its intention, damages resulting from a breach of the contract, and a deduction from the price still due under the same contract. The statute reads: “The buyer on notifying the seller of an intention to do so may deduct all or any part of the damages resulting from any breach of the contract from any part of the price still due under the same contract” (Minn. Stat. § 336.2-717).

Two more rules narrow a deduction for goods the retailer accepted. The retailer “must within a reasonable time after the buyer discovers or should have discovered any breach notify the seller of breach or be barred from any remedy” (Minn. Stat. § 336.2-607(3)(a)). The same section assigns the proof: “The burden is on the buyer to establish any breach with respect to the goods accepted” (Minn. Stat. § 336.2-607(4)).

A deduction for a fee no clause creates, or for a breach the retailer cannot show, conflicts with the rule that the buyer pays the contract rate for goods it accepted. Whether separate purchase orders under one agreement count as “the same contract” depends on how the agreement is built, and a setoff clause can make that question moot by authorizing deductions across purchase orders. From the buyer’s side, the same analysis decides when a payment holdback breaches the contract.

How do setoff and recoupment differ for retailer deductions?

Under Minnesota law, recoupment reduces what a retailer owes you using a claim from the same transaction, and it can only reduce or avoid your recovery; setoff uses a claim from an unrelated transaction. The Minnesota Supreme Court has said that a recoupment claim “must arise out of the same transaction that is the subject matter of the plaintiff’s action” (Household Finance Corp. v. Pugh, 288 N.W.2d 701, 704 (Minn. 1980)). Recoupment also “can only be utilized to reduce or avoid the plaintiff’s recovery.” The same opinion distinguished a setoff, “which involves a transaction unrelated to the plaintiff’s action” (Pugh, 288 N.W.2d at 704 n.5).

For you, that distinction sorts deductions into two groups. A deduction for damaged goods in a shipment answers your claim for that shipment’s price, which fits recoupment’s same-transaction requirement. A deduction for a different contract or a retailer affiliate’s claim is more likely a setoff. Because the UCC deduction right reaches only the price due “under the same contract” (Minn. Stat. § 336.2-717), a cross-contract or affiliate deduction generally needs the agreement’s setoff clause or another legal basis. That clause answers three questions: whose claims it covers, which agreements it reaches, and whether notice comes first.

When does a compliance chargeback become an unenforceable penalty?

A compliance chargeback is open to challenge as a penalty when its amount is unreasonably large. Minnesota’s UCC measures reasonableness against the anticipated or actual harm caused by the breach, the difficulty of proving loss, and the inconvenience or nonfeasibility of otherwise obtaining an adequate remedy (Minn. Stat. § 336.2-718(1)). It lets an agreement “provide for remedies in addition to or in substitution for those provided in this article” (Minn. Stat. § 336.2-719(1)(a)), but makes that permission subject to, among other limits, its rule on liquidated damages.

That rule allows damages to be liquidated “only at an amount which is reasonable” in light of those factors, and it adds: “A term fixing unreasonably large liquidated damages is void as a penalty” (Minn. Stat. § 336.2-718(1)). A fixed fee for a late or mislabeled shipment can be argued to work like liquidated damages, so a fee schedule with no relationship to the anticipated or actual harm from the breach invites the argument that it is a penalty. Other Minnesota contracts raise the same question, the subject of Minnesota’s line between liquidated damages and a penalty.

A chargeback also needs the breach it assumes. A fine for a delay the retailer’s own carrier caused, or for a label error its receiving records do not show, is a factual dispute your shipping records can answer first.

How are shortage, pricing, and damage deductions proven?

A shortage deduction turns on proof of what was delivered, and a pricing deduction on the agreed contract rate. A damage or quality deduction turns on proof of a breach in goods the retailer accepted, a burden Minnesota’s UCC places on the retailer (Minn. Stat. § 336.2-607(4)). Asking the retailer for the backup behind each deduction code tells you which of these claims it is making and which of your records answers it.

  • For a shortage, the answer is proof of what was delivered: the signed bill of lading, the carrier’s delivery record, and an advance ship notice that matches the cartons. A shortage reported long after delivery is worth testing against the signed receipt, because the retailer must pay the contract rate for the goods it accepted (Minn. Stat. § 336.2-607(1)), and it cannot have accepted units that never arrived.
  • For a pricing deduction, payment is measured at “the contract rate” (Minn. Stat. § 336.2-607(1)). The answer is the purchase-order price and any price change both sides agreed to.
  • For a damage or quality deduction, a fair first response is a request for the retailer’s photographs, inspection records, and disposition records. The question of whether the problem should have been caught at receipt begins with a buyer’s right to inspect goods before accepting them. For goods damaged in transit, the first question is when the risk of loss passed. Unless the agreement provides otherwise, if the contract has you ship by carrier without requiring delivery at a particular destination, the risk passes to the retailer when the goods are duly delivered to the carrier (Minn. Stat. § 336.2-509(1)(a), (4)). You can then recover the price of conforming goods damaged within a commercially reasonable time after the risk passed (Minn. Stat. § 336.2-709(1)(a)).

When does a retailer have a right to return goods for credit?

A retailer has a right to send back goods that conform to the contract only if your deal provides for returns, such as a return term in the vendor agreement. Minnesota’s UCC requires the buyer to “pay at the contract rate for any goods accepted” (Minn. Stat. § 336.2-607(1)). A deal that lets a buyer return conforming goods delivered primarily for resale is what the UCC, absent a different agreement, calls a “sale or return” (Minn. Stat. § 336.2-326(1)(b)).

Absent a return or allowance term, defective goods follow the UCC’s default rules. If the retailer rejects them instead of accepting them, the rejection “must be within a reasonable time after their delivery or tender” and “is ineffective unless the buyer seasonably notifies the seller” (Minn. Stat. § 336.2-602(1)).

An allowance for nonconforming goods the retailer accepted is a breach claim, so the retailer must give notice within a reasonable time after it discovers or should have discovered the problem (Minn. Stat. § 336.2-607(3)(a)). Returning accepted goods for a defect requires a revocation of acceptance, which Minnesota’s UCC allows, among other conditions, only for a lot or commercial unit “whose nonconformity substantially impairs its value to the buyer” (Minn. Stat. § 336.2-608(1)). The revocation must also occur “within a reasonable time after the buyer discovers or should have discovered the ground for it and before any substantial change in condition of the goods which is not caused by their own defects” (Minn. Stat. § 336.2-608(2)). A revocation “is not effective until the buyer notifies the seller of it” (Minn. Stat. § 336.2-608(2)).

Where the vendor agreement sets its own return terms, such as who pays freight or whether a percentage allowance replaces individual returns, those terms control. Where the deal is a sale or return and the agreement is silent on the details, Minnesota’s UCC extends the return option to the whole of the goods or any commercial unit only “while in substantially their original condition,” requires the retailer to act “seasonably,” and puts the return “at the buyer’s risk and expense” (Minn. Stat. § 336.2-327(2)). A return right that rests on an oral or side promise faces two hurdles. Minnesota’s UCC treats any “or return” term as a separate contract for sale under the statute of frauds and as contradicting the sale under the parol evidence rule (Minn. Stat. § 336.2-326(3)). A credit taken for conforming goods with no return term behind it leaves part of the price unpaid.

What makes markdown money and margin true-ups enforceable?

Markdown money, margin true-ups, and promotional allowances are enforceable to the extent your agreement, including any allowance contract you accepted and any established practice between you, authorizes them. Without that authority, Minnesota’s UCC requires the retailer to pay “the contract rate for any goods accepted” (Minn. Stat. § 336.2-607(1)). The questions are whether the agreement was in force for the period, whether the amount follows its formula, and whether the deduction was collected the way the agreement provides.

In my practice, these deductions often rest on a separate allowance contract with its own term. An allowance contract can expire while the retailer keeps taking the allowance, so I compare each deduction’s date against the contract’s term. An allowance taken after the contract ended needs a successor contract or another term that authorizes it. Margin true-ups raise a different question, because you have agreed to support the retailer’s margin while the retailer may set the shelf price and promotions that determine it. The first questions are how the retailer calculated the margin and whether you agreed to that calculation. You can ask for the calculation before accepting a true-up demand.

Good-faith duties apply, with limits. “Every contract or duty within the Uniform Commercial Code imposes an obligation of good faith in its performance and enforcement” (Minn. Stat. § 336.1-304), and that obligation “may not be disclaimed by agreement,” though the parties may agree on the standards that measure good faith, if those standards are not manifestly unreasonable (Minn. Stat. § 336.1-302(b)).

Outside the UCC, the Minnesota Supreme Court has said that “every contract includes an implied covenant of good faith and fair dealing requiring that one party not unjustifiably hinder the other party’s performance of the contract” (In re Hennepin County 1986 Recycling Bond Litigation, 540 N.W.2d 494, 502 (Minn. 1995)). The same opinion limits the covenant: it “does not extend to actions beyond the scope of the underlying contract” (Hennepin County, 540 N.W.2d at 503). And the Minnesota Court of Appeals has said that a party “does not act in bad faith by asserting or enforcing its legal and contractual rights” (Sterling Capital Advisors, Inc. v. Herzog, 575 N.W.2d 121, 125 (Minn. Ct. App. 1998)). A good-faith argument therefore needs a term of the allowance agreement to attach to.

How far back can a supplier dispute deductions?

Two clocks limit how far back you can go: the vendor agreement’s own window for disputing a deduction, and Minnesota’s limitations period for a lawsuit for the price of goods (Minn. Stat. § 336.2-725(1)); a claim under a separate allowance agreement may fall under a different statute. The agreement’s window can be much shorter than the limitations period. Missing it gives the retailer an argument that the deduction stands, even when a lawsuit would still be timely.

For a lawsuit, Minnesota’s limitations statute for a contract for sale lets “the original agreement” shorten the period, down to a floor the statute sets, and provides that the parties “may not extend it” (Minn. Stat. § 336.2-725(1)). A clause that would cut off your right to sue sooner than that floor is open to challenge under the same subsection. Whether a short window to dispute a deduction with the retailer also limits a lawsuit depends on the agreement’s wording. The limitations period starts when “the breach occurs, regardless of the aggrieved party’s lack of knowledge of the breach” (Minn. Stat. § 336.2-725(2)). The time to sue over an underpayment generally starts with the short payment, even if your team finds it later. The current text of § 336.2-725 and your agreement’s dispute and limitations clauses are the two documents to read before deciding how far back to go.

Windows can also protect you. The UCC lets the parties fix the time for an action it requires “within a reasonable time,” as long as the time is “not manifestly unreasonable” (Minn. Stat. § 336.1-302(b)). The retailer’s notice of a defect in goods it accepted is one of those actions (Minn. Stat. § 336.2-607(3)(a)), so you can ask for a fixed period after delivery for the retailer to raise receiving claims.

When you sue for a shipment’s price, the retailer can generally still use a claim about that shipment to reduce your recovery, if it gave the notice of breach Minnesota’s UCC requires (Minn. Stat. § 336.2-607(3)(a)), even after the statute of limitations on that claim has run. The Minnesota Supreme Court has said that a defense in the nature of recoupment is “generally permitted even though the applicable statute of limitations would have barred an independent action on the same claim” (Household Finance Corp. v. Pugh, 288 N.W.2d 701, 703 (Minn. 1980)).

How does silence on deductions weaken a supplier’s claim?

Accepting deductions remittance after remittance without objecting can turn the retailer’s practice into evidence against you. Minnesota’s UCC treats a sequence of conduct in a particular transaction, under an agreement that calls for repeated performance, which the other party knows about, has the chance to object to, and accepts or goes along with “without objection,” as a course of performance (Minn. Stat. § 336.1-303(a)). Subject to the UCC’s rules on modification and waiver, a course of performance “is relevant to show a waiver or modification of any term inconsistent with the course of performance” (Minn. Stat. § 336.1-303(f)).

The protection is a written dispute of each deduction you believe is invalid, sent through the channel the agreement requires, with a copy kept outside the retailer’s portal. That written record is the practical way of protecting against an implied waiver in contract performance, and it supports accepting a payment under protest when you deposit a remittance that carries a disputed deduction.

If your tolerance of a deduction practice operates as a waiver, you can retract the waiver going forward. A party that has waived a term affecting the part of the contract still to be performed “may retract the waiver by reasonable notification received by the other party that strict performance will be required of any term waived,” unless retraction “would be unjust in view of a material change of position in reliance on the waiver” (Minn. Stat. § 336.2-209(5)). A short letter requiring strict compliance with the agreement’s deduction terms can serve as that notification once the retailer receives it.

How does a supplier recover deductions that breach the vendor agreement?

You recover deductions that breach the vendor agreement in four steps: documenting every deduction, fixing the causes of valid ones, negotiating the unsupported amounts, and bringing a claim only for what negotiation leaves unresolved. A deduction breaches the vendor agreement when the retailer keeps money that neither the agreement nor the law lets it keep. That includes a fee no clause authorizes, an allowance under an expired or misapplied contract, a damages deduction with no breach behind it, a penalty-sized fine, and a cross-contract deduction with no setoff clause or other legal basis.

  1. Documentation comes first: one ledger of every deduction, with its date, amount, invoice, reason code, and the clause the retailer relies on, matched to the documents in effect when the shipment went out.
  2. Root cause comes second. A valid chargeback often traces to a process problem, such as a label format or an advance ship notice that did not match the shipment, and fixing it stops the next charge.
  3. Negotiation comes third. In my practice, I suggest that your account manager open the conversation and present a written analysis of the agreement, prepared by your team or your attorney, as the reason you cannot accept the disputed charges. Escalating first can read as adversarial and leaves no room to escalate later. The requests are specific: the unsupported dollar amounts, the calculation behind any allowance or true-up, and better terms going forward.
  4. The claim comes last. An unsupported deduction leaves part of the price unpaid, and when the retailer fails to pay the price as it becomes due, Minnesota’s UCC lets you recover the price “of goods accepted” (Minn. Stat. § 336.2-709(1)(a)). Unless the agreement or a statute provides for attorney fees, each side generally pays its own (Dunn v. National Beverage Corp., 745 N.W.2d 549, 554 (Minn. 2008)). A judgment can also carry interest on the unpaid amount, under the agreement or Minnesota law (Minn. Stat. § 549.09, subd. 1(b)). The agreement’s dispute clause decides where that claim is heard, and some national-retailer agreements let only the retailer choose arbitration.

A retailer that withholds payment for accepted goods without a contractual or legal basis has a breach problem of its own, the buyer-side issue covered in the legal risks of withholding vendor payments.

Does depositing a short payment give up our right to the deducted amount?

Not by itself. Under Minn. Stat. § 336.1-308, accepting the other side’s performance as offered, with an explicit reservation of rights such as ‘under protest’ or ‘without prejudice,’ does not thereby prejudice the rights reserved. That protection does not reach an accord and satisfaction: under Minn. Stat. § 336.3-311, cashing a check tendered in good faith with a conspicuous full-satisfaction statement, on the check or in a note sent with it, can discharge a disputed claim. Exceptions apply: a business that gave the retailer conspicuous notice, a reasonable time before the check, of where disputed-debt communications must go is generally not bound by such a check that never reached that place, and a payee that gave no such notice can generally avoid the discharge by paying the check’s amount back within the statute’s deadline. Minn. Stat. § 336.3-311 covers checks and other negotiable instruments, but an electronic payment offered in full satisfaction of a disputed claim can still settle it under Minnesota’s common law of accord and satisfaction if you accept it as full satisfaction. In Webb Business Promotions, Inc. v. American Electronics & Entertainment Corp., 617 N.W.2d 67 (Minn. 2000), a check case, the Minnesota Supreme Court said that the agreement an accord requires need not be express and “may be implied from circumstances that clearly and unequivocally indicate the intention of the parties.”

Can a retailer come back years later with a post-audit claim?

It can try, within limits. The vendor agreement’s audit clause, if there is one, defines how far back the retailer may review payments. An audit claim collected by deduction from a current invoice usually reaches a different purchase order, and Minnesota’s UCC deduction right covers only the price still due under the same contract (Minn. Stat. § 336.2-717), so the retailer may need a setoff clause or another legal basis. If the claim is that accepted goods did not conform, Minn. Stat. § 336.2-607(3)(a) required the retailer to give notice within a reasonable time after it discovered or should have discovered the problem, or lose its remedy. Its claims for breach of a contract for sale also face the limitations period in Minn. Stat. § 336.2-725. A claim that the retailer simply overpaid, such as a duplicate payment, may not be a claim for breach of a contract for sale, and Minnesota’s general limitations statute for contract and other obligations may then apply instead (Minn. Stat. § 541.05). A claim barred only by the statute of limitations can generally still reduce your recovery when you sue over the same transaction, as recoupment under Household Finance Corp. v. Pugh (Minn. 1980), if it gave timely notice of the breach. You can negotiate a shorter lookback and documentation for each audit claim before any deduction.

Does Minnesota law apply if the vendor agreement picks another state's law?

Not if the choice is effective. Subject to listed exceptions, Minnesota’s version of the Uniform Commercial Code lets the parties to a transaction that bears a reasonable relation to Minnesota and to another state agree that the law of either state governs their rights and duties (Minn. Stat. § 336.1-301). When the agreement validly picks another state, that state’s law generally governs the contract claims, and the Minnesota sections cited in this article become a guide to the questions to ask rather than the answers.

What if the retailer's buyer promised something the written terms do not say?

If your signed agreement excludes changes except by a signed writing or other signed record, an oral promise by the retailer’s buyer (its purchasing employee) does not by itself change the deal: between merchants, such an agreement cannot be modified any other way (Minn. Stat. § 336.2-209). Without such a clause, an agreed change needs no new consideration to bind either side, though the changed contract must still satisfy the statute of frauds where it applies (Minn. Stat. § 336.2-209(1), (3)). An attempt at modification that fails either requirement can still operate as a waiver (Minn. Stat. § 336.2-209(4)). The agreement may also limit who at the retailer can approve a change. I suggest confirming any such promise by email at the time, naming who made it and when, because that record is what a later waiver argument would rest on. Under Minn. Stat. § 336.2-202, evidence of an earlier agreement, or of an oral agreement made when you signed, cannot contradict written terms the parties intended as final, and can add a consistent term only if the writing was not meant to be complete and exclusive.

Can a retailer charge a new fee its vendor manual added after we signed?

Only if the agreement’s amendment clause allows it or you agree to the fee, and amendment clauses vary. Some let the retailer change its posted standard terms on notice, sometimes paired with a supplier right to terminate. Others require a signed writing to change the contract and let the retailer change only future purchase orders on advance notice. Under Minn. Stat. § 336.2-209, an agreed modification needs no new consideration to bind you. A retailer’s use of a right to change terms is subject to the duty of good faith (Minn. Stat. § 336.1-304), and, subject to the UCC’s rules on modification and waiver, accepting the new fee’s deduction repeatedly without objection can later be used to show a waiver or modification (Minn. Stat. § 336.1-303).

Most deduction disputes turn on documents: the vendor agreement, everything it incorporates, the allowance contracts, and the shipping records that show what you delivered. Where those documents are silent, Minnesota’s UCC requires the retailer to pay the contract rate for accepted goods and gives it a deduction right for damages from your breach of the same contract, after notice. If you log every deduction, dispute the invalid ones in writing on time, and fix the causes of the valid ones, you put yourself in a position to recover unsupported deductions while protecting the relationship. Deduction disputes are one part of contract work for Minnesota businesses. If you would like a second set of eyes on your deductions, email [email protected] with the retailer’s name and the deduction types. I will run a conflict check before you send the agreement or any confidential records.