Mandatory e-invoicing: is your online store really ready?

What nobody tells you about the upcoming deadline

One of our clients called us in a panic a few weeks ago. He runs an online shop selling Norman regional products — 200 orders a month, PrestaShop running smoothly. His question: “I’ve heard about a mandatory e-invoicing requirement. Does it apply to me?”

The short answer: yes. And he wasn’t ready.

The long answer is this article.

France’s e-invoicing reform is not a topic reserved for accountants or large corporations. It directly affects your online store, your CMS, and your order process. And if you think “it’s for later,” the deadlines have been pushed back — but they are coming, and achieving compliance takes time.

Here is what you need to know, without unnecessary jargon.

What the reform concretely requires

The Direction Générale des Finances Publiques (DGFiP — the French tax authority) has been driving a fundamental reform of invoicing between French businesses for several years. The goal: move to a system of structured, mandatory e-invoicing for all B2B transactions between VAT-registered entities established in France.

This is not simply “sending a PDF by email.” A PDF, however well-formatted, does not meet the reform’s requirements. Structured data is needed, in a machine-readable format (Factur-X, UBL, CII), transmitted via a certified dematerialisation platform (PDP — Plateforme de Dématérialisation Partenaire) or via the public portal Chorus Pro.

Two distinct obligations coexist within this reform:

E-invoicing applies to invoices issued between French VAT-registered businesses (domestic B2B). These invoices must go through a certified platform.

E-reporting applies to transactions not covered by e-invoicing: sales to consumers (B2C) and transactions with foreign businesses. Data from these sales must be transmitted to the tax authority on a set schedule.

For an e-commerce merchant who sells primarily to consumers — which is true of the majority of online stores — e-reporting is the priority obligation. And it is often the least well understood.

Is your CMS technically capable of meeting this requirement?

That is the real question. And the answer depends on your stack.

PrestaShop and WooCommerce: two very different situations

PrestaShop has a relatively mature module ecosystem on this topic, and each major version evolves its native capabilities — we’ve detailed elsewhere what the PrestaShop 9.1 update really changes. Publishers like Factur-X and various third-party solutions already offer compliance modules. But — and this is where our clients are caught off guard — a module alone is not enough. Your theme, customer data and VAT configuration must all be consistent with the format’s requirements. We’ve seen PrestaShop stores with 5 different modules installed, and not a single compliant invoice generated.

WooCommerce presents a more variable level of maturity. The richness of the WordPress ecosystem is also its weakness: invoicing plugins are plentiful, but their compatibility with the required structured formats (Factur-X in particular) is uneven. If you use WooCommerce with a generic invoicing plugin, it is probably insufficient.

The on-the-ground truth, as we experience it with our clients: the majority of French online stores are not ready. Not because their owners are negligent, but because the reform is complex, deadlines have shifted, and technical service providers have not always anticipated it.

What your store must be able to do

To be compliant, your e-commerce system must be able to:

1. Generate invoices in a structured format (Factur-X is the standard adopted in France — it combines a human-readable PDF and a machine-readable XML)
2. Transmit B2C transaction data to a PDP or directly to the tax authority via e-reporting
3. Retain and archive electronic invoices under legal conditions (duration, integrity, readability)
4. Correctly manage mandatory fields (SIREN number, VAT details, buyer status)

If your store currently generates “homemade” PDFs without an integrated XML structure, you have a long way to go. It’s not insurmountable — but it can’t be fixed in an afternoon.

The BarkBox case: when identity goes beyond the product

You may be wondering what BarkBox has to do with an article on e-invoicing. Bear with us.

BarkBox is an American company that sends monthly boxes of toys and treats for dogs to its subscribers. Its CEO publicly stated: “BarkBox is not a box.” The company does not define itself by its physical product, but by the emotional relationship it builds with its customers — and their dogs.

This positioning has direct implications for their e-commerce model: recurring subscriptions, rich customer data, high personalisation. And therefore: thousands of monthly transactions to manage, invoice, and report.

Why does this matter to you? Because if you sell online with recurring orders, subscriptions, or volume, tax compliance becomes an operational issue, not just an accounting one. BarkBox cannot afford to have shaky invoicing — and neither can you, regardless of your store’s size.

The example illustrates a simple truth: the e-commerce businesses that succeed over the long term are those that treat their technical infrastructure — including tax compliance — as a competitive advantage, not a reluctant constraint.

What our audits consistently reveal

Across the e-commerce projects we have run and audited over recent years in Normandy and beyond, three problems come up systematically when we address invoicing compliance:

Misconfigured VAT. Rates applied at product level without consistency with territoriality rules, poorly coded exemptions, intra-community VAT rules ignored. The result: invoices generated with incorrect data, even if the format is correct.

Non-existent archiving. Invoices are generated on the fly and stored in WordPress’s uploads folder or in an unsecured PrestaShop directory. No integrity guarantee, no traceability. This does not comply with legal archiving obligations — and it won’t comply with the reform either.

The accounting / technical divide. The accountant knows their obligations. The developer knows their CMS. But nobody has bridged the two. The invoicing module was installed by a service provider three years ago, and nobody has checked whether it is still maintained, compatible with the current CMS version, or compliant with new requirements. This is exactly the kind of blind spot that a proper website maintenance contract is supposed to cover — and almost never does.

“Tax compliance for an online store is 30% technical and 70% organisational. The CMS can do everything — but it must be correctly configured and someone must be responsible for maintaining it.”

How to prepare your store: the concrete steps

No miracle list. Here is what we actually do when we help a client through this process.

Step 1: audit your current configuration

Before touching anything, we take stock. Which CMS, which version, which invoicing plugin, what the current output format is, how invoices are stored, who has access to what. This diagnostic typically takes half a day. It prevents spending money on ill-fitting solutions.

Step 2: upgrade the invoicing module

We identify the solution best suited to your stack. For PrestaShop, certain specialist modules can generate Factur-X natively. For WooCommerce, the selection is more delicate — we test before deploying. In some cases, an external solution (ERP or invoicing software connected via API) is more robust than a native plugin.

Step 3: choose your dematerialisation platform

You will need a PDP (Plateforme de Dématérialisation Partenaire — certified dematerialisation platform) or to use Chorus Pro depending on your profile. This choice depends on your transaction volume, your legal structure, and your existing accounting ecosystem. Your accountant must validate this choice — our role is to make your store technically compatible with the chosen platform.

Step 4: testing and validation

We generate test invoices, verify the XML embedded in the Factur-X, and validate the transmitted data. This step is non-negotiable. A format that “looks correct” visually can contain structural errors that render the invoices non-compliant.

Step 5: documentation and training

Your team must know what to do if something goes wrong. We always deliver concise, operational documentation tailored to your technical level. Not an 80-page manual — a 5-page guide that answers the real day-to-day questions.

What you need to remember

Three actionable points, straight to the point:

Check your invoicing module right now. Which version? What output format? Is it actively maintained by its publisher? If you don’t have the answer in 5 minutes, nobody is looking after it — and that’s a problem.

Talk to your accountant before talking to your developer. Tax compliance is defined first on the business side, not the technical side. Your accountant tells you what you need to produce. Your developer tells you how to produce it. In that order.

Don’t delay. The deadlines have moved several times, that’s true. But every extension has been accompanied by more complex requirements, not simpler ones. The longer you wait, the more expensive compliance will be — technically and organisationally.

Compliance is not a constraint, it’s infrastructure

BarkBox is not a box. And your online store is not just a website. It is a commercial infrastructure that must function over the long term, within a legal framework that evolves.

The e-commerce businesses that treat compliance as a technical priority — on a par with loading speed or security — are the ones that avoid last-minute crises, tax audits, and emergency migrations at 3,000€ carried out in 48 hours because the deadline is tomorrow. It is a requirement we build in from the creation of your e-commerce store, not as an afterthought.

At GDM-Pixel, we support PrestaShop and WooCommerce stores through these compliance processes. Technical audit, upgrade, connection to dematerialisation platforms, documentation. No miracle package — an honest diagnosis, transparent pricing, delivery on time.

Is your store ready? If you’re not sure, it probably isn’t yet. Contact us for a compliance audit — we’ll tell you what’s missing, without selling you a full rebuild if it isn’t necessary.

---

Sources: DGFiP — e-invoicing reform; Chorus Pro official documentation; FEVAD — French e-commerce figures 2024.