Tomorrow, France Goes Quiet: The August 1 Congés Payés Wave and What to Confirm Today
31.07.2026
A Second French Deadline Is Landing on Top of E-Invoicing: The 10-Year Archiving Mandate Sellers Haven’t Heard About
03.08.2026
FLEX. Logistics
We provide logistics services to online retailers in Europe: Amazon FBA prep, processing FBA removal orders, forwarding to Fulfillment Centers - both FBA and Vendor shipments.
France's e-invoicing framework has just moved from partially open to fully closed. Decree No. 2026-677, read alongside the Order of 27 July 2026, finalises the operational rules that sellers on Amazon.fr have been able to treat as provisional for the past two years. Until now, gaps in secondary legislation left room to argue that certain invoicing flows, certain seller categories, or certain transitional arrangements were still undecided. That argument no longer holds.
For a seller shipping into France, or fulfilling French orders through a French return address and French customs clearance, this is not an abstract legal update. It changes what counts as a valid invoice, who is responsible for transmitting it, and what happens when invoicing continues outside a compliant Plateforme de Dématérialisation Partenaire. This article sets out what the decree and order actually finalise, what happens operationally to a seller who keeps invoicing outside a PDP, and what a seller needs to check and act on this week, not next quarter.
What Decree 2026-677 And The July Order Actually Close
Before this pair of legal instruments, France's e-invoicing reform existed in a state that practitioners describe as framework-complete but implementation-open. The primary legislation set the direction; secondary texts were still expected to confirm operational detail such as onboarding sequencing, data formats accepted from partner platforms, and how the transition period would be phased for different seller sizes. That ambiguity gave many sellers, particularly smaller Amazon.fr accounts, a reason to deprioritise PDP selection.
Decree No. 2026-677 removes that ambiguity from the regulatory side, and the Order of 27 July 2026 removes it from the technical and procedural side. Together they confirm the operational mechanics: which invoice data must pass through a PDP platform, how that platform must certify and route the data, and what qualifies as a compliant transmission chain for a business selling to French customers. Where previous guidance allowed for interpretation about timing or scope, these two texts remove the interpretive space entirely.
This matters specifically for Amazon.fr sellers because marketplace invoicing sits at the intersection of platform data, seller accounting systems, and now mandatory PDP routing. A seller who assumed there would be further clarifying guidance, or a further extension, is working from a version of the rules that no longer exists. The compliance question has shifted from what will the rules eventually require to what do the rules require right now.
Why There Is No Delay Runway Left To Plan Around
Sellers commonly treat compliance deadlines the way they treat a distant carrier cut-off: something to work backward from once other priorities clear. That instinct made sense while France's e-invoicing timeline still had open variables. It does not make sense now, because the variables that created planning room have been formally resolved.
The phrase no further delay runway describes a specific operational reality: there is no remaining stage of secondary legislation left to wait for, no pending clarification that could reopen the timeline, and no scenario where a seller can reasonably argue the requirement was still unsettled. Decree 2026-677 and the July Order are not incremental guidance. They are the closing instruments. Once a legal framework reaches that state, continuing to treat PDP onboarding as a someday task is not caution, it is exposure.
This shift also changes how internal teams should prioritise the work. PDP onboarding involves selecting a platform, configuring invoice data exports, testing transmission, and confirming acceptance, and each of those steps takes real calendar time, not a single afternoon. A seller who starts this process only after receiving a warning from Amazon, an accountant, or a tax authority has already lost the buffer that made early planning valuable. The runway metaphor is precise: once the door closes, there is no more distance left to build speed before takeoff.
What Happens Operationally If Invoicing Continues Outside A PDP
The practical risk is not abstract legal exposure sitting in a filing cabinet somewhere. It shows up in the operational chain that already exists between a seller's back office, Amazon.fr's transaction data, and the seller's own accounting and reporting systems.
When invoices are generated outside a compliant PDP platform, the transmission chain that regulators and, in practice, marketplace partners expect to see is broken at its first link. That has knock-on effects: reconciliation between marketplace settlement reports and seller-issued invoices becomes harder to defend, audit trails become incomplete, and any downstream reporting that depends on validated invoice data inherits the gap. For a seller running high order volumes on Amazon.fr, this is not a once-a-year problem, it compounds with every invoicing cycle that passes without a compliant platform in place.
There is also a practical seller-account dimension. Marketplaces increasingly build compliance expectations into seller requirements, and a seller whose invoicing chain cannot demonstrate compliant routing may find themselves fielding data requests, correcting historical records, or explaining gaps at a moment when their attention should be on order volume, not remediation. None of this requires a dramatic enforcement action to become disruptive. It only requires an accountant, auditor, or platform review to ask for something the seller cannot currently produce.
The Immediate Steps To Select And Connect A PDP
Selecting a Plateforme de Dématérialisation Partenaire is not a single decision made once and forgotten. It is a short sequence of concrete steps, each with its own lead time, and each worth tracking separately rather than folding into a vague this quarter to-do.
- Confirm your invoicing volume and format against what candidate PDP platforms actually support, since Amazon.fr sellers often run mixed B2C and B2B invoicing that not every platform handles identically.
- Shortlist platforms with confirmed government registration rather than platforms still awaiting certification, since an uncertified platform will not solve the compliance gap it claims to close.
- Map your current invoice data export from your accounting or ERP system to confirm it can feed the PDP without manual re-entry, which is where many onboarding timelines slip.
- Run a test transmission cycle before switching over fully, so errors surface in a controlled window rather than in a live invoicing run.
- Assign an internal owner for PDP onboarding specifically, separate from whoever owns general Amazon.fr account management, since this workstream needs dedicated attention now.
Sellers should treat this as a project with a start date this week, not a research topic. The platforms themselves have onboarding queues, and a seller who begins the selection process only once other compliance work is finished risks joining that queue later than competitors who started when the decree was published.
Where Dispatch Data Readiness Fits Into Getting This Right Quickly
PDP onboarding depends on clean, consistent invoice data, and for sellers using a French fulfilment partner, a meaningful share of that data originates outside the seller's own systems. Dispatch records, order confirmations, and shipment data generated at the warehouse level all feed into what eventually becomes an invoice line. If that data is inconsistent, delayed, or formatted differently across shipments, the PDP transmission inherits the problem before the seller even sees it.
This is where fulfilment operations and compliance readiness intersect directly. A French fulfilment partner running Amazon FC forwarding, customs clearance in France, and outbound dispatch under one operational structure can produce dispatch data in a format that maps cleanly to invoice requirements, rather than requiring a seller's finance team to reconcile mismatched records from multiple sources after the fact. Sellers relying on fragmented supply chains, where prep, storage, and dispatch each sit with a different provider, often discover the data gaps only when they attempt their first PDP test transmission.
Getting this right quickly means treating dispatch data readiness as part of the same project as PDP selection, not a separate concern to revisit later. A seller confirming their fulfilment partner's export format alongside their PDP shortlist avoids a second round of remediation once onboarding is technically complete. This is also where working with a partner already handling customs clearance for e-commerce sellers in France pays off operationally, since the same data trail that supports customs release can support clean invoice transmission.
Operational Control Points To Verify Now
- Confirm which invoices currently bypass any PDP platform entirely.
- Check whether your accounting export format matches your shortlisted PDP's intake requirements.
- Verify your fulfilment partner's dispatch data can map to invoice line items without manual correction.
- Confirm ownership of PDP onboarding is assigned to a named person, not left as shared responsibility.
Common Mistakes Sellers Are Still Making
- Assuming further clarifying guidance is still coming, when the decree and order have already closed that window.
- Treating PDP selection as an accounting-only task with no fulfilment or operations input.
- Waiting for an Amazon.fr account warning before starting the onboarding process.
- Choosing a PDP platform based on price alone without confirming it fits actual invoicing volume and format.
When To Bring In Outside Support
Escalate to a tax advisor when you are unsure whether your specific invoicing setup falls under the new requirements. Revisit your PDP shortlist if a test transmission fails repeatedly. Bring in a French fulfilment partner when dispatch data inconsistency is the blocker, since that gap sits in operations, not accounting.
Treat PDP Onboarding As This Week's Priority, Not Next Quarter's
Decree No. 2026-677 and the Order of 27 July 2026 did not create a new obligation out of nothing. They removed the last remaining reason a seller could point to for delaying PDP onboarding. That distinction matters because it changes the nature of the risk: this is no longer a future compliance date to plan around, it is a closed framework that already applies to how invoices move today.
The seller who benefits most from this moment is not the one who reads the legal text most carefully, it is the one who moves fastest from reading to action. That means shortlisting a compliant PDP platform this week, confirming your accounting export format actually feeds it cleanly, and checking that your fulfilment partner's dispatch data will not become the hidden blocker in your test transmission. Each of these is a concrete task with a concrete owner, not a compliance theme to keep on a watch list.
For sellers whose invoicing gaps trace back to inconsistent dispatch or shipment data, the fix often sits upstream of the PDP conversation entirely, in how a fulfilment operation structures its export data in the first place. This is a good moment to confirm that your French warehouse partner's data output is ready before you finalise your PDP choice, rather than discovering the mismatch during your first live invoicing cycle.
This article is informational and does not constitute tax or legal advice. Sellers should confirm their specific PDP obligations, timeline, and invoicing scope with a qualified tax advisor before finalising their compliance approach.
Reach out to the FLEX. team today via our contact form for a no-obligation quote tailored to your product range and sales volume. A more profitable fulfillment strategy could be closer than you think.
Decree No. 2026-677 and the Order of 27 July 2026 finalise France's e-invoicing framework, closing the interpretive gaps that previously let sellers treat PDP onboarding as a future task. Amazon.fr sellers still invoicing outside a compliant Plateforme de Dématérialisation Partenaire face reconciliation gaps, incomplete audit trails, and marketplace-level scrutiny that only grows the longer the gap continues.
The practical response is a short, concrete sequence: shortlist a certified PDP, confirm your accounting data maps to it cleanly, and verify that dispatch and fulfilment data feeding your invoices is consistent. Sellers using a French fulfilment partner should treat dispatch data readiness as part of this same project, since fragmented supply chains often surface invoicing gaps only once onboarding is already underway.
