Amazon EPR Report: The Packaging Weights You Declare

An Amazon EPR report is the file Amazon generates with the packaging and product data your national Extended Producer Responsibility declaration asks for, aggregated by month, quarter or year. It is not the registration number. It is the thing you file after you have one, and it is the step that gets forgotten because the number is what Amazon asks you to upload.

What the Amazon EPR report actually contains

Amazon publishes three report types, documented in the SP-API regulatory compliance reference:

• GET_EPR_MONTHLY_REPORTS
• GET_EPR_QUARTERLY_REPORTS
• GET_EPR_ANNUAL_REPORTS

All three carry the same 34 columns and the same description in Amazon's documentation: data used to declare EPR compliance to regulatory bodies and pay EPR fees. Amazon's stated reason for publishing them is that they remove manual data compilation across several data sources and manual product classification.

The columns that matter on a declaration are these:

• Seven material weights per row: paper_kg, glass_kg, aluminum_kg, steel_kg, plastic_kg, wood_kg, other_kg.
• total_reported_weight_kg, plus item_weight_without_package_kg and item_weight_with_package_kg so the packaging share is separable.
• registration_number, your LUCID, UIN or equivalent, carried per row.
• epr_category and four subcategory levels, epr_subcategory1 through epr_subcategory4.
• battery_embedded, a flag that splits packaging duties from battery duties.
• ship_to_country_code and ship_to_country, which is how one file serves several national schemes.
• total_units_sold and units_per_asin, the volume side of the fee calculation.

A declaration asks for kilograms of each material placed on the market in a given country in a given period. Those seven columns are that question, already answered from your own order data.

Why the registration number is not the end of it

Uploading a LUCID number to the EPR compliance portal is what stops Amazon from blocking the listing. It is not what satisfies the regulator. Sellers on the Amazon Seller Forums have been told repeatedly that holding a LUCID number does not end the obligation: if you are subject to system participation you still declare your packaging to the scheme and to the German authority, and fees are owed per reporting period. In France the number is a UIN entered per product category, and the same forum guidance says Amazon will pay the EPR fees to the producer responsibility organizations on your behalf and recover them from you if you cannot prove compliance.

That recovery is the cost nobody budgets. It does not arrive as a fee line you recognize.

If you have not registered yet, start with EPR registration across the EU countries Amazon checks. If you sell into the US as well, the packaging rules now run on their own clock there too: see the California SB 54 packaging EPR deadlines.

Which ASINs carry your packaging weight?

See my catalog

The part that costs people a quarter

A generated report does not sit in your account forever. Amazon's report type reference states that report retention varies by type and that where no explicit retention is given, a report is retained for 90 days. After that you request it again.

For an annual declaration filed in Q1 on the previous calendar year, that matters. If you generate the annual file in November and open it in March, it is gone and you regenerate it. Download it the day you pull it.

What to do with it this week

1. Pull the aggregation your scheme actually files on. Monthly, quarterly and annual are separate report types, not views of one report. Filing a quarterly total into an annual declaration is a reconciliation problem later.
2. Check registration_number is populated on every row for every ship_to_country_code you sell into. A blank there is a country where you are selling and not declaring.
3. Check battery_embedded. Batteries are a separate EPR stream in the EU, and a product flagged there has two obligations, not one.
4. Compare item_weight_with_package_kg against item_weight_without_package_kg on your top sellers. If the gap looks wrong, the packaging data on the ASIN is wrong, and the declaration inherits the error.
5. Save the file outside Seller Central with the period in the filename.

What this does not do

Amazon generates the data. Amazon does not file your declaration, does not choose your scheme and does not confirm your classification is right. The epr_category values come from Amazon's product classification, not from your scheme's taxonomy, so a category mapping step stays on your side.

And this is packaging and batteries. Product safety is a different obligation with a different proof: see the GPSR responsible person requirement on Amazon listings. The wider packaging regime that is replacing the old EU directive is covered in PPWR requirements for online sellers.

#EPR#compliance#packaging#Seller Central#reports

👋Hey! I'm Amara

Press at SellerKey.co

☕ Espresso. Never a latte macchiato.

I cover Amazon fee and policy changes: what changed, when it applies and where Amazon published it.

My articlesContact me

← Previous

When to Claim FBA Reimbursements for Holiday Returns