This is the sequence that actually clears a bulk GPSR block.
What is actually happening
Amazon's GPSR compliance feed has a hard dependency order. Layer 1 — the EU Responsible Person, set account-wide in the Manage Your Compliance dashboard — is the unlock. Until it is active and propagated across all 8 EU marketplaces, no per-ASIN data moves. Seller reports suggest the error is often not obvious from the feed report, which makes teams debug the wrong layer.
Once Layer 1 is confirmed, the bulk-feed challenge is consistency across marketplaces. The master sheet has to be keyed on manufacturer reference (the product model number or SKU) — not on ASIN. Multiple ASINs map to one manufacturer reference. The reverse — same ASIN with different RP details per marketplace — is what triggers cross-marketplace audit flags and partial rejection loops.
What to check now
Run through this before touching the feed again:
| Check | Where to find it | Common failure |
|---|---|---|
| Responsible Person set at account level | Manage Your Compliance | Not set — feed rejects everything regardless of data quality |
| RP propagation timing | Dashboard status, 1–3 days post-onboarding | Submitted feed before RP propagated — wait, then resubmit |
| Master sheet keyed on manufacturer reference | Internal product master | Keyed on ASIN — same product ends up with mismatched RP data across marketplaces |
| GPSR fields at child ASIN level | Category Listing Report | Fields on parent ASIN only — Amazon requires child-level |
| Per-marketplace language coverage | Feed template per marketplace | Warning text in English only — fails DE/FR/IT/ES/NL/PL/SE marketplace checks |
| File encoding | Spreadsheet export settings | Not saved as UTF-8 with BOM — non-Latin characters corrupt |
| Manufacturer address fields | Feed columns | One-line concatenated address — Amazon parser requires separate street/city/postcode/country columns |
Red flags
- 100% rejection rate. Layer 1 is almost certainly missing. Not a data issue — go back to account level.
- Partial rejection across marketplaces for the same ASIN. Master sheet keyed on ASIN not manufacturer reference — same physical product, mismatched RP data.
- Warning-text rejections in German. German safety text runs longer than the field limit. Truncate in the master sheet, not the feed.
- "RP not registered" error after onboarding. Layer 1 has not propagated yet. RP service onboarding typically takes 1–3 days before the dashboard reflects active status.
- Parent ASIN rejections. Move GPSR feed fields to child ASIN level — parent-only population does not satisfy Amazon's field mapping.
The master sheet is the single source of truth. The marketplace feeds are outputs. Agence Octo Periscope applies the GPSR Bulk Feed Sequence: confirm Layer 1 is active in Manage Your Compliance, build a master sheet keyed on manufacturer reference with 8 language columns (DE, FR, IT, ES, NL, PL, SE + EN), derive per-marketplace feeds from the master sheet. Submit one marketplace as a test batch first. Read the full error report line by line before submitting remaining marketplaces. The error report is the diagnostic; the rejection count is not. See how Periscope applies the GPSR Bulk Feed Sequence →