When a big retailer pays less than your invoice, you can dispute the deductions it has no right to take, and you have more ways to do it than a lawsuit. The options run from a conversation with the buyer and the retailer’s own dispute process, through fixing the cause of valid chargebacks and renegotiating your vendor terms, to a demand letter and arbitration or suit. The first step is the same on every path: a ledger of every deduction matched to the clause the retailer relies on, because the documents decide what you can recover.
Your vendor agreement and the documents it incorporates are the first source of the rules in these disputes. 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, and Minnesota common law fills in the rest. Deduction disputes are part of my Minnesota business contract work, and this page is written for the supplier whose payments are coming in short.
What Should You Do First When a Retailer Takes Deductions?
I suggest building one ledger of every deduction, collecting the agreement documents as they stood when each shipment went out, and disputing each invalid deduction in writing before the agreement’s window closes. Written disputes matter because deductions you accept repeatedly, with knowledge of them and an opportunity to object, can be used to show a waiver or modification of any contract term inconsistent with them (Minn. Stat. § 336.1-303(a), (f)). That rule is subject to the UCC’s modification and waiver rules in Minn. Stat. § 336.2-209.
These steps preserve your position without committing you to any later option:
- Build the ledger. The ledger should show, for each deduction, the date, amount, invoice and purchase order, the retailer’s reason code, and the clause it relies on.
- Sort by type. Compliance chargebacks are fees 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 a problem with what you shipped or billed. Return deductions are credits for goods sent back. Markdown money and allowances cover margin support and promotions collected by deduction.
- Collect the agreement set. The set includes the signed agreement, the standard terms, vendor manual, routing guide, purchase orders, and any allowance contracts, in the versions in effect at each shipment, because those versions decide what the retailer could deduct.
- Dispute in writing, on time. I suggest using the channel the agreement requires, before its dispute window closes, and keeping your own copy outside the retailer’s portal, because the portal is the retailer’s record. A produce seller also has the federal trust notice described in the section on how far back you can dispute deductions.
- Reserve your rights when you deposit. A remittance you deposit with an explicit reservation of rights is the subject of the first question in the FAQ below.
A check tendered in good faith as full satisfaction of a disputed claim has its own rules. The statute protects an organization that, “within a reasonable time before the tender,” sent the retailer a conspicuous statement designating a person, office, or place for communications about disputed debts, if the check or its accompanying communication “was not received by that designated person, office, or place” (Minn. Stat. § 336.3-311(c)(1)). It also protects a claimant that tendered repayment of the check’s amount “within 90 days after payment of the instrument,” unless the claimant is an organization that sent that designation (Minn. Stat. § 336.3-311(c)(2)). Neither protection applies if the claimant, or an agent with direct responsibility for the disputed obligation, knew of the full-satisfaction tender within a reasonable time before collection began (Minn. Stat. § 336.3-311(d)). I suggest checking the statute’s current text before relying on that repayment period.
Silence carries a legal cost. Minnesota’s UCC treats repeated performance as a course of performance when the other party, “with knowledge of the nature of the performance and opportunity for objection to it, accepts the performance or acquiesces in it without objection” (Minn. Stat. § 336.1-303(a)). Subject to the UCC’s modification and waiver rules, such a course “is relevant to show a waiver or modification of any term inconsistent with the course of performance” (Minn. Stat. § 336.1-303(f)). A written dispute of each invalid deduction is the practical way of protecting against an implied waiver, and it supports accepting a payment under protest.
If you have already tolerated a deduction practice, you can retract a waiver going forward. A party that 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 the 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 Do Your Options Compare, From the Buyer to a Lawsuit?
Your options run roughly from least to most costly: a conversation with the buyer or account manager, the retailer’s dispute process, fixing the compliance cause, renegotiating terms, outside help with the volume, a demand letter, and arbitration, conciliation court, or a lawsuit. Each fits a different situation and carries its own risk.
- The buyer or account manager. It fits a relationship you want to keep and a dispute about calculations or terms. It costs your team’s time. The risk is a friendly answer with no written follow-up.
- The retailer’s dispute process. It fits deductions with a clear error at the reason-code level. It costs staff time per claim. The risk is a missed window or a record that lives only in the retailer’s portal.
- Fixing the compliance cause. It fits valid chargebacks that keep recurring. It costs process changes. The risk is low, and it stops the next charge.
- Renegotiating the vendor terms. It fits a renewal, a new program, or a pattern you cannot fix operationally. It costs negotiating time. The risk is that the retailer orders less.
- Outside help. It fits a deduction volume your team cannot work through. It costs fees. The risk is paying for recovery work on deductions the agreement allows.
- A demand letter. It fits documented amounts that negotiation has not resolved. It costs a lawyer’s fee for the letter. The risk is strain on the relationship.
- Arbitration, conciliation court, or a lawsuit. It fits when the money matters more than the account, or the account is ending. It costs the most of these options. The risk is the expense of proof and the retailer’s defenses.
The Buyer or Account Manager
A conversation through your account manager fits a dispute about how the retailer calculated a charge or applied a term. In one margin true-up dispute, the questions I raised were how the retailer calculated the margin and whether that was what the supplier had agreed to. I suggested that the supplier’s account manager open the conversation with written talking points, rather than putting them on letterhead to look more official, and focus on what a mutually beneficial relationship looks like. I suggested starting with the account manager rather than escalating, because escalating can be adversarial and starting there leaves room to escalate later.
The request should be specific: the disputed dollar amounts, the calculation behind any allowance or true-up, and the term each deduction relies on. Any agreement you reach is worth confirming in writing, for the reasons in the FAQ about a buyer’s promises.
The Retailer’s Dispute Process
Where the agreement or vendor manual sets a dispute process, such as a filing through the retailer’s vendor portal, that process and its window come first. The process fits code-level errors: a shortage claim your signed delivery receipt answers, a price your purchase order contradicts, a fine for a delay the retailer’s own carrier caused. I suggest keeping your own copy of every dispute and response, because the portal is the retailer’s system and your record of a timely written objection is what protects you against a waiver argument.
Fixing the Compliance Cause
A valid chargeback can trace to a process problem: a label format, an advance ship notice that did not match the cartons, or a missed routing instruction. Fixing the cause is a business move rather than a legal one, and it can be the cheapest step, because it stops the next charge. Your logistics provider or electronic data interchange vendor can help trace the mismatch.
Renegotiating the Vendor Terms
A renewal or a new program is the time to ask for terms that limit future deductions. Useful requests include documentation for each deduction before it is taken, a cap on compliance fines, a setoff clause limited to the same purchase order, and a fixed period after delivery for the retailer to raise receiving claims. Minnesota’s 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)). An agreed change “needs no consideration to be binding” (Minn. Stat. § 336.2-209(1)), but between merchants, a signed agreement that requires changes in a signed writing or record “cannot be otherwise modified or rescinded” (Minn. Stat. § 336.2-209(2)). Payment timing is a separate term, covered in net-60 and net-90 terms with large customers.
The risk is commercial. In one analysis I prepared of two national retailers’ vendor agreements, neither agreement obligated the retailer to issue any specific purchase order. A retailer that dislikes the request can order less, the situation covered in what happens when a major retailer ends the vendor relationship. The chargeback schedule, setoff clause, and dispute window belong on the list of vendor-agreement terms worth negotiating before you sign.
An Accountant or a Deduction-Recovery Service
When deductions arrive by the hundreds, an accountant or a deduction-management service can build the ledger, match deductions to remittances, and file portal disputes. That help fits high volume and recurring codes. I suggest giving that provider the agreement set and the clause behind each deduction category, because a dispute filed against a deduction the agreement allows costs fees and recovers nothing.
A Demand Letter
A demand letter puts the amount, the basis, and a deadline for payment in writing. In one demand letter I sent for a supplier that had kept filling orders while invoices went unpaid, an exhibit listed each overdue invoice. The legal claim behind the letter is simple: when the buyer fails to pay the price as it becomes due, Minnesota’s UCC lets the seller recover the price “of goods accepted” (Minn. Stat. § 336.2-709(1)(a)).
Except as otherwise provided by contract or allowed by law, a written notice of claim can also start preverdict interest on your damages (Minn. Stat. § 549.09, subd. 1(b)). The same paragraph, subject to that exception, bars preverdict interest on “judgments or awards not in excess of the amount specified in section 491A.01,” the conciliation-court limit (Minn. Stat. § 491A.01). The statute adds a condition: “The action must be commenced within two years of a written notice of claim for interest to begin to accrue from the time of the notice of claim.” Settlement offers can also change the calculation, so I suggest checking the statute’s current text before relying on a demand’s date. Attorney fees are a separate question. The Minnesota Supreme Court, quoting an earlier decision, has said that the general rule in Minnesota is that “attorney fees are not recoverable in litigation unless there is a specific contract permitting or a statute authorizing such recovery” (Dunn v. National Beverage Corp., 745 N.W.2d 549, 554 (Minn. 2008)).
If the retailer offers to settle, a write-off or release of part of your claim should be in writing. Minnesota’s UCC provides that a claim arising out of an alleged breach “may be discharged in whole or in part without consideration by agreement of the aggrieved party in a signed record” (Minn. Stat. § 336.1-306).
Arbitration, Conciliation Court, or a Lawsuit
The agreement’s dispute clause decides where a claim is heard. In the two national-retailer agreements I analyzed, each gave the retailer, and only the retailer, an option to elect binding arbitration. Minnesota makes an agreement in a record to arbitrate a controversy “valid, enforceable, and irrevocable except upon a ground that exists at law or in equity for the revocation of contract” (Minn. Stat. § 572B.06(a)). The Federal Arbitration Act says the same of a written arbitration provision in a contract involving interstate commerce (9 U.S.C. § 2).
For a smaller claim, conciliation court is an option if the dispute clause allows it. Minnesota’s conciliation court hears civil claims where the money at stake does not exceed “$20,000” (Minn. Stat. § 491A.01, subd. 3a). A company may be represented there “by an officer, manager, or partner,” or “may appoint a natural person who is an employee” to appear on its behalf (Minn. Stat. § 491A.02, subd. 4). For an officer or employee, “an authorized power of attorney, corporate authorization resolution, corporate bylaw, or other evidence of authority acceptable to the court must be filed with the claim or presented at the hearing” (Minn. Stat. § 491A.02, subd. 4(a)). The county matters too: except as the statute otherwise provides, “the territorial jurisdiction of conciliation court is coextensive with the county in which the court is established,” and an action against a foreign corporation “may be commenced” in the counties the statute lists, such as “the county where the corporation’s registered agent is located” (Minn. Stat. § 491A.01, subd. 3a(c), 7(a)). The retailer may answer any claim with its own claims about the same shipments, the recoupment defense explained in the setoff and recoupment section.
What Do the Vendor Agreement and Its Incorporated Terms Let a Retailer Deduct?
A retailer may take the deductions 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 UCC’s default rules fill the gaps.
In one analysis I prepared of two national retailers’ vendor agreements, each started with a short signed document that brought in longer standard terms and policies hosted on the retailer’s vendor portal. Their terms were heavily buyer-favorable, including setoff and chargeback rights, limits on liability running in the retailer’s favor, and short windows for bringing a claim. Those liability limits remain 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)). Consequential damages “may be limited or excluded unless the limitation or exclusion is unconscionable,” and a limitation of damages “where the loss is commercial” is not prima facie unconscionable (Minn. Stat. § 336.2-719(3)).
Categories of deductions 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.
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)).
The baseline is that “The buyer must pay at the contract rate for any goods accepted” (Minn. Stat. § 336.2-607(1)). A deduction for a fee no clause creates, or for a breach the retailer cannot show, conflicts with that baseline. Whether separate purchase orders under one agreement count as “the same contract” (Minn. Stat. § 336.2-717) depends on how the agreement is built, and a setoff clause can authorize 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 and it can only be utilized to reduce or avoid the plaintiff’s recovery” (Household Finance Corp. v. Pugh, 288 N.W.2d 701, 704 (Minn. 1980)). 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).
That distinction sorts your 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. A deduction of defense costs for a customer’s injury or product suit raises its own questions, covered in when a retailer demands indemnity for a product claim.
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, because Minnesota’s UCC allows agreed damages only at a reasonable amount. The statute 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)). An agreement may “provide for remedies in addition to or in substitution for those provided in this article” (Minn. Stat. § 336.2-719(1)(a)), but that permission is subject to, among other limits, the 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 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 reason code tells you which claim it is making and which of your records answers it.
- Shortage. The answer is proof of delivery: the signed bill of lading, the carrier’s delivery record, and an advance ship notice that matches the cartons. The retailer must pay the contract rate for the goods it accepted (Minn. Stat. § 336.2-607(1)). For units lost in transit, the answer turns on when the risk of loss passed, explained in the paragraph after this list.
- Pricing. 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.
- Damage or quality. A fair first response is a request for the retailer’s photographs, inspection records, and disposition records. Whether the problem should have been caught at receipt begins with a buyer’s right to inspect goods before accepting them.
For goods lost or damaged in transit, the first question is when the risk of loss passed. Unless the agreement provides otherwise, when the contract has you ship by carrier and does not require delivery at a particular destination, “the risk of loss passes to the buyer when the goods are duly delivered to the carrier” (Minn. Stat. § 336.2-509(1)(a)). The section is “subject to contrary agreement of the parties and to the provisions of this article on sale on approval (section 336.2-327) and on effect of breach on risk of loss (section 336.2-510)” (Minn. Stat. § 336.2-509(4)). You can then recover the price of “conforming goods lost or damaged within a commercially reasonable time after risk of their loss has passed to the buyer” (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. Otherwise Minnesota’s UCC requires the buyer to “pay at the contract rate for any goods accepted” (Minn. Stat. § 336.2-607(1)). Unless otherwise agreed, a deal that lets a buyer return conforming goods delivered primarily for resale is what the UCC calls a “sale or return” (Minn. Stat. § 336.2-326(1)(b)).
Defective goods follow different 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 that needs timely notice (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 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” and “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 goods 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 resting on an oral promise faces a hurdle: 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)).
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, 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 allowance 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 one markdown-allowance matter, the retailer had discounted the unit price and charged the lost margin back to the supplier, and the questions I raised were whether there was a contract and what its terms were. In the two-retailer analysis described in the options section, one allowance contract had expired by its own terms, and any current promotional-allowance arrangement would be embodied in a successor contract. I suggest checking, for each allowance deduction, whether the allowance agreement was in force for the period the allowance covers. Margin true-ups raise a different question, because the retailer may set the shelf price and promotions that determine the margin you agreed to support. Promotional allowances raise pricing-law questions of their own, covered in slotting fees and promotional allowances for suppliers.
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). That obligation “may not be disclaimed by agreement,” though the parties may set the standards that measure it if those standards are “not manifestly unreasonable” (Minn. Stat. § 336.1-302(b)).
Outside the UCC, the Minnesota Supreme Court has recognized that every contract includes an implied covenant of good faith and fair dealing under which one party may not unjustifiably hinder the other’s performance (In re Hennepin County 1986 Recycling Bond Litigation, 540 N.W.2d 494, 502 (Minn. 1995)). The same opinion limits the covenant: “In Minnesota, the implied covenant of good faith and fair dealing does not extend to actions beyond the scope of the underlying contract” (Hennepin County, 540 N.W.2d at 503). The Minnesota Court of Appeals, quoting an earlier decision, 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?
For most suppliers, 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 on a contract for sale (Minn. Stat. § 336.2-725(1)). The agreement’s window can be much shorter. Missing it gives the retailer an argument that the deduction stands, even when a lawsuit would still be timely. A seller of fresh fruits or vegetables has a third clock if the retailer’s produce purchases make it a “dealer” (7 U.S.C. § 499a(b)(6)). Federal law then holds the produce, products derived from it, and the proceeds “in trust for the benefit of all unpaid suppliers or sellers.” The seller “shall lose the benefits of such trust unless such person has given written notice of intent to preserve the benefits of the trust to the commission merchant, dealer, or broker within thirty calendar days” after the payment deadline passes or after receiving notice that a payment instrument was dishonored (7 U.S.C. § 499e(c)(2), (3)). I suggest checking the current text of that period before relying on it.
For a lawsuit, the statute provides: “An action for breach of any contract for sale must be commenced within four years after the cause of action has accrued. By the original agreement the parties may reduce the period of limitation to not less than one year but may not extend it” (Minn. Stat. § 336.2-725(1)). The period starts when “the breach occurs, regardless of the aggrieved party’s lack of knowledge of the breach” (Minn. Stat. § 336.2-725(2)). A claim under a separate allowance agreement may fall under a different statute. I suggest reading the current text of § 336.2-725 and your agreement’s dispute and limitations clauses before deciding how far back to go, because the agreement may have shortened the period.
When you sue for a shipment’s price, the retailer can generally still use a claim about that shipment to reduce your recovery, even after the limitations period on that claim has run. That defense depends on the retailer having given the notice of breach the UCC requires (Minn. Stat. § 336.2-607(3)(a)). In a lender’s suit on a consumer loan, the Minnesota Supreme Court let the borrowers use a federal truth-in-lending claim to reduce the lender’s recovery after the time to sue on that claim had run. The borrowers relied on the doctrine, which the court described as “recognized under Minnesota and federal common law,” 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)).
Does depositing a short payment give up our right to the deducted amount?
Not by itself. Under Minn. Stat. § 336.1-308, a party that accepts performance offered by the other side, with an explicit reservation of rights such as “under protest” or “without prejudice,” does not thereby prejudice the rights reserved. That protection does not apply to an accord and satisfaction. Under Minn. Stat. § 336.3-311, cashing a check tendered in good faith as full satisfaction of a disputed claim, with a conspicuous statement saying so, can discharge the claim. The statute’s exceptions for an advance designated address and timely repayment are explained in the first-steps section.
Can a retailer come back years later with a post-audit claim?
Yes, within limits. An audit clause sets the review period. The UCC deduction right covers only the price still due under the same contract (Minn. Stat. § 336.2-717), so an audit claim taken from later invoices may need a setoff clause. Claims about accepted goods also required timely notice of breach (Minn. Stat. § 336.2-607(3)(a)). Under Minn. Stat. § 336.2-725(1), “An action for breach of any contract for sale must be commenced within four years after the cause of action has accrued,” unless the agreement shortened it; check the current text. A separate allowance agreement may fall under another statute.
Does Minnesota law apply if the vendor agreement picks another state's law?
Not if the choice is effective. Minnesota’s Uniform Commercial Code lets the parties to a transaction that bears a reasonable relation to Minnesota and to another state agree that either state’s law governs their rights and duties, subject to listed exceptions (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 on this page 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 record, the buyer’s oral promise does not by itself change the deal between merchants (Minn. Stat. § 336.2-209(2)), though a failed modification can operate as a waiver (Minn. Stat. § 336.2-209(4)). A record intended as the final expression of its terms cannot be contradicted by a prior or contemporaneous oral agreement, but consistent additional terms may supplement it unless it was intended as the complete and exclusive statement of the terms (Minn. Stat. § 336.2-202(b)). I suggest confirming any such promise by email at the time.
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. Some agreements let the retailer change posted terms on notice, sometimes with a supplier right to terminate; others require a signed writing or limit changes to future purchase orders. An agreed modification needs no new consideration (Minn. Stat. § 336.2-209(1)). Using a right to change terms is subject to the duty of good faith (Minn. Stat. § 336.1-304), and, subject to Minn. Stat. § 336.2-209, accepting the fee repeatedly without objection can show a waiver or modification of an inconsistent term (Minn. Stat. § 336.1-303(f)).
Should we stop shipping until the retailer pays the deducted amounts?
Only with care. Minnesota’s UCC states that the seller’s obligation is to transfer and deliver, and the buyer’s to accept and pay, in accordance with the contract (Minn. Stat. § 336.2-301). When reasonable grounds for insecurity about the retailer’s performance arise, Minn. Stat. § 336.2-609 lets you demand adequate assurance in writing and, if commercially reasonable, suspend performance you have not already been paid for until you receive it. Between merchants, commercial standards decide both questions. The agreement’s own supply and termination terms come first, and the retailer may respond by ordering less.
Next Steps on Retailer Deductions
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. It also lets the retailer, after notifying you, deduct damages resulting from a breach of the contract from the price still due under the same contract. A cross-contract deduction generally needs the agreement’s setoff clause or another legal basis. A ledger, a written dispute of each invalid deduction within the agreement’s window, and a fix for the causes of valid ones keep every option open, from the buyer conversation to a claim. A produce seller keeps the federal trust only by giving the timely written notice the federal statute requires.
Deduction disputes are one part of contract work for Minnesota businesses. If you would like me to analyze which of your deductions the agreement does not support, email [email protected] with a brief description of the deduction types, and I can start an intake and conflict check before you send the agreement or any confidential records.