RPP registration vs SCRAP membership vs annual declaration in Spain

Direct answer: RPP registration, SCRAP membership and annual declarations are three connected parts of Spanish packaging EPR, but they are not substitutes. RPP registration identifies the producer in MITECO’s state register and can result in an ENV number. SCRAP membership places the producer in a collective system that organises and finances the packaging-waste obligations within its authorised scope. Annual declarations report what the producer placed on the Spanish market during the previous calendar year—separately to MITECO and under the selected scheme’s own process.

A foreign seller may therefore need all three. Having an ENV number does not prove that scheme membership is current; a SCRAP contract does not create an ENV number; and filing one annual return does not automatically complete the other. If you want the connected route rather than one isolated task, start with the complete Spain packaging EPR service.

Think of the file as three layers: identity in the public register, waste-financing coverage through a responsibility system, and recurring quantity reporting.

RPP vs SCRAP vs annual declaration: the complete comparison

The legal connection between the first two columns is unusually concrete: Article 15 of Real Decreto 1055/2022 requires evidence of belonging to an individual or collective responsibility system when registering. MITECO’s current guidance asks producers to attach the scheme certificate, not merely the adhesion contract. That is why scheme onboarding and RPP preparation normally run in parallel rather than as unrelated projects.

The correct sequence from first sale to recurring compliance

1. Identify the producer. Map the legal entity, brand, importer or intra-EU acquisition route, distance-sale flow and any Spain-established distributor. Do not register a company simply because its name appears on a marketplace account.
2. Map the packaging scope. List product, grouped and shipment packaging by component; distinguish household, commercial and industrial packaging and single-use from reusable formats. Record who supplies each shipment component.
3. Set the Spanish filing identity. Confirm the company data, any Spanish NIF requirement and, for a producer established outside Spain, the authorised-representative route required by Article 17.2.
4. Select a responsibility-system route. Spanish law provides individual and collective routes. Most e-commerce files consider a collective system, but the selected SCRAP must actually cover the relevant categories and use model. Review the current public authorisation information and the scheme’s own admission terms.
5. Obtain the correct scheme evidence. If the SCRAP accepts the producer, retain its participation certificate and contract separately. The current RPP guidance specifically distinguishes the certificate used for the register from the contract.
6. Complete the RPP procedure. Submit the same legal entity, representative, packaging categories and system evidence to MITECO. Retain the final authority-issued evidence and ENV number if issued; an application reference or scheme number is not a substitute.
7. Use the number in the right places. Article 15 requires the registration number on invoices and other commercial documentation accompanying covered transactions. A marketplace may also request the number and supporting document under its own process and makes its own acceptance decision.
8. Build the annual data model immediately. Connect each SKU and shipment configuration to material weights, Spain-only units, channels, returns and documented assumptions. Waiting until March turns a reporting task into a reconstruction exercise.
9. Prepare the two reporting outputs. Reconcile one controlled source dataset, then map it separately to the SCRAP declaration and the MITECO annual information. Keep the submitted version and receipt for each route.

If the gap is specifically the state record, review the RPP registration service. If the record exists but scheme coverage is missing or mismatched, use the SCRAP membership service. If both are active and the issue is prior-year data, go directly to the annual declarations service.

Visual explainer

Which evidence should exist at each layer?

Keep the evidence with the exact version of the source dataset used. A clean PDF without the supporting entity, year, material weights and reconciliation trail is difficult to defend when the next filing or a correction is prepared.

Who decides what?

• The producer supplies and approves accurate company, product, channel and packaging data. Outsourcing preparation does not transfer responsibility for false or incomplete source records.
• The authorised representative acts within the documented mandate for a producer established outside Spain and retains evidence of that representation. The mandate does not let the representative invent missing data.
• MITECO administers the packaging section of the RPP, its annual-information procedures and the resulting state records. Only authority-issued evidence should be described as RPP evidence.
• The selected SCRAP decides whether to admit the producer, which contract and contribution method apply, and what participation evidence it issues. Its scope must match the packaging facts.
• The competent public authorities authorise and supervise responsibility systems. MITECO publishes current lists and coverage, which should be checked rather than assuming one scheme covers every category.
• Amazon or another marketplace independently decides what it requests and whether the information submitted satisfies its platform process. A green platform status is not a substitute for the underlying legal file.
• A compliance provider can analyse, prepare, reconcile and coordinate. It cannot issue an ENV number, accept a SCRAP application or guarantee a marketplace outcome.

The deadlines—and the nuances sellers miss

Live example, not a permanent rule: MITECO’s page states that the operative window for reporting 2025 data ran from 2 January to 2 April 2026 inclusive. That campaign-specific extension does not rewrite the general statutory wording “before 31 March” for future years. Always record both the legal deadline and the live portal notice used for the filing.

Scenario 1: a foreign seller using only Amazon.es

Assume one foreign legal entity sells packaged consumer products directly to customers in Spain through Amazon.es. The seller should not begin by pasting a number into Seller Central. The first question is whether that legal entity is the producer for the relevant packaging flows.

1. Document the seller entity, supply chain, brand and the party introducing each packaging component into the Spanish market.
2. If the foreign entity is the producer, confirm the authorised-representative and company-identification route.
3. Select a responsibility system whose current scope covers the packaging categories and obtain its participation evidence if admitted.
4. Complete the RPP process with the aligned entity, representative, categories and scheme certificate; retain the final ENV evidence if issued.
5. Submit the identifier and supporting document Amazon actually requests. Amazon independently reviews them and may request further information.
6. For the annual cycle, reconcile the producer’s covered Spanish Amazon units with the packaging bill of materials and separately prepare the scheme and MITECO outputs.

Packaging supplied by a courier or platform needs its own fact check. Article 17.5 contains specific rules for transport packaging supplied by parcel companies or e-commerce platforms in distance sales. Do not automatically count it as seller-supplied packaging, and do not automatically exclude the product’s own packaging. Record who supplied what and how the current scheme and filing procedures treat it. For the platform-specific distinction, see Amazon Pay on Behalf vs own registration.

Scenario 2: a DTC brand selling through Shopify and a 3PL

Assume a non-Spanish brand takes orders on its own store and a fulfilment partner packs them for delivery to Spanish customers. A 3PL handling stock does not, by itself, answer who the producer is. Review the sale, import or intra-EU acquisition route, branding and contracts.

Once producer status is established, the operational file normally needs more than an order export:

• the product packaging supplied by the brand or manufacturer;
• the shipping box or mailer, tape, void fill, labels and inserts supplied by the relevant party;
• the material and weight of each component, linked to the SKU or fulfilment configuration;
• Spain-only completed activity reconciled to returns, cancellations, exports and any other documented adjustments;
• the category, single-use or reusable status and responsibility system applicable to each flow.

The resulting RPP record belongs to the producer legal entity, not to Shopify. The SCRAP covers only the scope it accepts. The annual declarations then use the controlled Spain dataset, not a screenshot of gross store revenue and not a 3PL total that mixes destinations.

Scenario 3: the same company sells on Amazon and DTC

Do not build one legal file per sales channel if the same producer and packaging scope are involved. Start with the producer entity, then reconcile channels underneath it. Marketplace and DTC datasets may use different order identifiers, return logic and fulfilment packaging, but the annual Spanish total cannot omit one channel or count a transferred order twice.

A practical control table should show, for each channel and fulfilment route, units placed on the Spanish market, the applicable packaging configuration, excluded or reversed units with reasons, and the final material totals. The reconciled result feeds two separate outputs: the selected scheme’s declaration and the RPP annual information.

Amazon’s compliance status only describes Amazon’s platform review. It does not validate the DTC dataset, the scheme declaration or the MITECO annual filing.

Nine common errors—and the corrective action

1. “We have an ENV number, so we are finished.” Check the current scheme certificate, registered categories, annual receipts and supporting dataset. Registration is the identity layer, not the complete recurring file.
2. “We signed a SCRAP contract, so we are registered.” Look for authority-issued RPP evidence and the ENV identifier. The scheme cannot issue the state registration number.
3. Uploading the contract instead of the certificate. MITECO’s current guidance asks for the scheme adhesion certificate when adding the responsibility system. Obtain the correct scheme-issued document and keep the contract separately.
4. Treating the SCRAP and RPP declarations as one filing. Build one reconciled source dataset, but retain a separate mapped output and receipt for each portal.
5. Using the 15-tonne threshold as an exemption. Assess eligibility for simplified RPP information; do not use it to skip registration or scheme review.
6. Reporting Amazon but omitting DTC or wholesale. Reconcile the full Spanish scope for the producer legal entity, then document any flows legitimately reported by another responsible party.
7. Multiplying all orders by one “average box.” Maintain packaging configurations by SKU or fulfilment route and preserve supplier specifications, controlled measurements and documented estimates.
8. Assuming a portal extension changes every future deadline. Save the campaign notice that applied, but plan against the statutory deadline and recheck the live procedure each year.
9. Changing SCRAP mid-year without transition controls. Verify outstanding financial obligations, the year from which the new system assumes coverage, certificate dates, RPP profile updates and which system receives each declaration.

A year-round operating calendar

• Every month: close Spain-only units by channel, record returns and exceptions, and flag new SKUs or packaging configurations.
• Every quarter: reconcile channel totals to finance or fulfilment records; sample packaging weights; review changes in legal entity, categories, scheme scope and marketplace requirements.
• Before year-end: confirm which scheme will cover the following year, review any intended system change, and verify access to the relevant portals.
• January: freeze the prior-year population, obtain final channel and fulfilment extracts, and resolve missing packaging mappings.
• Before the applicable February cut-off: approve and provide the information required by the SCRAP, allowing time for the scheme’s own earlier operational deadline where applicable.
• Before the applicable MITECO deadline: approve the RPP output, submit through the operative procedure and retain the receipt and exact filed version.
• After filing: reconcile any difference between outputs, log corrections, archive evidence and roll the final packaging model into the next cycle.

The goal is not to force two portals to show identical labels. It is to make every reported number traceable to the same approved source population and to explain legitimate mapping differences between the authority and the scheme.

Choose the service that matches the missing layer

• No state registration or uncertain ENV evidence? Review the producer-registration service and the legal entity that should appear in the RPP.
• No suitable collective-system evidence, or categories do not match? Compare current coverage through the Spain packaging SCRAP service.
• Registration and scheme are active, but prior-year data is not ready? Build the controlled outputs with the RPP and SCRAP annual-declarations service.

If several layers are missing, do not commission three disconnected fixes. The complete packaging EPR route coordinates producer analysis, representation, RPP, responsibility-system evidence and the recurring reporting model under one documented scope. MITECO, the selected scheme and every marketplace still retain their own decisions.