Amazon Co-op Agreements for Vendors: Accruals, Deductions, and the AVN Trade

A co-op line on your remittance

You open a remittance, and between the payments against your POs sits a deduction labeled with a co-op program. The amount is big enough to matter, but the label doesn't say how it was calculated, so you end up asking the same two questions every time: where did this number come from, and is it right?

Co-op, short for cooperative marketing agreement, is the vendor-funded share of your Amazon business that Amazon deducts from what it pays you, under the marketing, freight, and damage terms your vendor agreement commits you to. Practitioners also call it Contra CoGS, and you'll see the terms referred to as the Vendor Manager Agreement (VMA). Our co-op agreement glossary entry covers the definition and each agreement type. This guide picks up where that entry stops and follows a co-op dollar from the rate set at the Annual Vendor Negotiation (AVN), through the accrual calculated against your business and the line that posts to your remittance, to the check you run on that line and the evidence it gives you for next year's negotiation.

Where the rate comes from

You won't find your co-op rates set anywhere in the console. They come out of the AVN, the yearly terms discussion with Amazon, and once agreed they apply to everything you ship until the next one. Inymbus, which recovers deductions for vendors, describes the rates as typically expressed as a percentage of shipped or received cost and applied automatically at the time of remittance, with no separate notice.

Your terms split co-op into separate lines, and each line is negotiated on its own with its own calculation base. Some lines are figured on net receipts, others on net sales or on the purchase price Amazon paid, while a straight payment is a fixed amount that doesn't move with volume. The freight allowance depends on who moves your inbound freight: Wake Commerce draws the line between WePay vendors, who rely on Amazon to pick up their goods and pay the allowance for it, and PrePaid vendors, who arrange their own freight and aren't charged one.

So before you can check any deduction, you need two facts written down for every co-op line: the rate, and the base it runs against. Pull both from the agreement itself, because rates vary by category and by vendor, and a rate another vendor quotes tells you little about your own terms. What Amazon typically asks for in the negotiation, and how to prepare for it, is in our AVN preparation guide.

How the accrual is calculated

The arithmetic is rate times calculation base, for the period the terms specify. Wake Commerce describes freight and damage allowances as calculated on receipts into Amazon's fulfillment centers each month and billed on the schedule set out in your terms. Promotional allowances follow the promotion instead: Wake Commerce describes them as based on units sold during the promotional period and paid on a schedule set after it ends.

Here's a worked example. The numbers are invented to show the method, so they aren't a real vendor's figures or a rate Amazon publishes, and you should plug in your own.

• Agreed terms: freight allowance at 3% of net receipts, damage allowance at 2% of net receipts.
• Net receipts into Amazon's fulfillment centers for March: $200,000.
• Freight accrual for March: 3% of $200,000, which is $6,000.
• Damage accrual for March: 2% of $200,000, which is $4,000.
• Expected co-op deductions against March receipts: $10,000.

That $10,000 is the figure you should be able to find across the remittances that settle those invoices. A marketing allowance that runs against net sales moves with what sold, so pull the sales figure for the same period before you compute its expected accrual. A straight payment should appear at its agreed amount whatever your volume did.

Where each piece lives in Vendor Central

What you agreed to and what Amazon actually deducted live on different screens, so you'll be moving between four places.

1. Payments, then CoOp. This page holds your agreements and the rates attached to them. It records what you agreed to and says nothing about what was taken.
2. Payments, then Remittance. This shows one payment at a time, and you can search it by remittance number or PO number. Each line carries the gross invoiced amount, the deductions applied against it, and the net that landed, and deduction lines name the program that generated them.
3. Reports, then Analytics, then Remittance. This report category holds Invoice Payments and Paid Invoices, and it's the pull you want when you reconcile a full month or quarter against your own ledger.
4. Payments, then Dispute Management. This is where you contest a specific deduction.

Menus and labels differ across regions and account types, so confirm each path inside your own account before you build a process around it. Our remittance advice glossary entry explains how to read the rest of the statement, and the Vendor Central invoices guide covers how an invoice gets to the point of being paid.

Reconciling the co-op line

Co-op comes off your payments the same way a chargeback does, but the risk runs differently. A chargeback traces back to one operational miss on one shipment, whereas co-op is agreed once and then applies to everything you ship for twelve months, so a wrong rate repeats on every remittance until someone catches it.

Once the agreed rates and bases are written down, you can run the same check every payment cycle.

1. Pull the remittances for the period from Reports, then Analytics, then Remittance, and isolate the co-op deduction lines. Record each line's amount, its program label, and the invoice it posted against.
2. Group the lines by program, so freight, damage, marketing, and any straight payments each have their own total.
3. Pull the calculation base for the same period from your own records: receipts for lines that run on receipts, sales for lines that run on sales.
4. Multiply each base by the agreed rate from Payments, then CoOp, and compare the expected accrual with what posted.
5. For any program that doesn't match, divide the posted amount by the base to get the rate Amazon actually applied, which usually points you to what went wrong.

Inymbus lists the error patterns worth looking for:

• Rate mismatch. The applied percentage differs from the agreed one. Vendors who renegotiate often see the previous year's rate applied for weeks or months after the new rate takes effect.
• Wrong calculation base. The deduction runs against shipped cost when the terms specify received cost, or against gross cost when it should be net of standard trade discounts.
• Duplicate deductions. The same charge is applied twice, either across two remittance cycles or under two different category labels.

Back to the illustrative example: suppose the freight line for March posts at $7,500 where you expected $6,000. Against a $200,000 base, that implies a 3.75% rate. If 3.75% was the rate in your previous agreement, you're looking at a rate mismatch. If 3% is correct and the posted amount matches 3% of your shipped value for the month, the deduction ran against the wrong base.

Inymbus also notes that Amazon's remittance lines often describe deductions in generic terms, without naming the agreement clause behind them, so expect to work backward from the amount more often than from the label.

Anything that doesn't reconcile goes to Dispute Management, which asks for the dispute reason, the justification behind it, and the supporting documents. Inymbus reports that Amazon's analysts review each case manually and that specific references to the agreed terms win more often than generic dispute language, so cite the line, the rate you agreed, the base, and your arithmetic. Dispute windows are short, and Inymbus warns that some co-op categories carry shorter internal review windows still, so run the reconciliation on the same schedule as the payment cycle and file while the window is open.

Taking the pattern into the next AVN

By the time the next negotiation comes around, a year of reconciled co-op lines lets you answer any proposed change with what each co-op line actually cost you, set against what you agreed to pay. Bring these four things to the table:

• Your effective rate per program. Total each program's deductions for the year and divide by the receipts or sales they ran on, which gives you the baseline any proposed increase starts from, in your own numbers.
• What you disputed and recovered. A year of rate mismatches and duplicates is a concrete argument for tighter terms.
• Damage allowance against actual damage. Wake Commerce recommends making sure the damage allowance aligns with the true damage and returns figures for your products. Our AVN guide notes, citing Bellavix, that a vendor isn't required to accept a damage allowance and can instead pay the costs of returning damaged products.
• What you want in return. Feedvisor, as cited in the AVN guide, recommends that every co-op increase come with measurable growth targets or promotional support from Amazon.

The "Turning the Numbers Into a Position" section of the AVN preparation guide covers modeling best, base, and worst cases and setting your give-and-take range before the meeting. Your reconciled co-op figures go straight into those scenarios. That guide's checklist also asks you to compare the co-op rates you agreed to last year with what came off your remittances, and the steps above walk through that comparison line by line.

What Vendor Central will not give you

The reconciliation above is manual because the console never assembles it for you.

• No rate history beside the current terms. Payments, then CoOp records what you agreed to, but it doesn't set this year's rates beside last year's, so record each year's rates before the new terms take effect.
• No side-by-side view. Agreed rates sit under CoOp, deductions sit on the remittance, and the calculation base sits in your receiving and sales data. Nothing in Vendor Central joins them into one view per program.
• Limited history. The console only keeps report history for so long, so if you didn't export the receipts and sales behind last year's accruals, they may be gone by the time you need them.
• It repeats every payment cycle. Each remittance brings a new set of co-op lines, and a missed cycle leaves a gap in the year's evidence.

InsightLeap does the data side of this continuously, keeping historic Vendor Central reports beyond what Amazon lets you see in the console, so the year of data behind your reconciliation is already collected when the AVN kickoff lands. Whatever tool you use, start by writing down every co-op line's rate and base from Payments, then CoOp, before the next negotiation changes them.