PrestaShop vs Shopify: an accountant's take for 2026

The choice between PrestaShop and Shopify is almost always made by the marketing or development team. Accounting comes last — and that is precisely where the most expensive risks accumulate for a growing e-commerce business.

Two questions now dominate the 2026 decision: can your CMS produce the fiscal data needed for multi-country VAT compliance, and is it ready for the French e-invoicing obligations rolling out through September 2027? Design and SEO are reversible; accounting misconfigurations leave a trail through every return.

The short answer: Shopify offers a more standardised accounting integration ecosystem and more straightforward OSS/IOSS compatibility out of the box. PrestaShop gives greater technical flexibility but demands rigorous VAT configuration and more frequent module audits. Neither platform is "plug and play" for French e-invoicing 2026 — compliance runs through an approved PDP (Partner Dematerialisation Platform) in both cases, entirely separate from the CMS.

France's e-invoicing reform (ordonnance 2021-1190) mandates receipt of electronic invoices for all businesses from 1 September 2026. Issuance becomes mandatory for large companies and mid-sized groups (ETI) on the same date, and for SMEs, micro-enterprises and sole traders from 1 September 2027.

Neither Shopify nor PrestaShop functions as a PDP. Compliance depends on a connector to an approved platform that generates and routes invoices in the required formats: Factur-X, UBL, or CII. The PPF (Portail Public de Facturation) no longer routes invoices since the architecture change confirmed in late 2024; it now serves as a directory and data concentrator.

For B2C flows — sales to private individuals — e-invoicing does not apply directly, but B2C e-reporting does: periodic transmission of transaction data to the tax authority. This is where CMS configuration becomes critical, because the data exports must be clean, complete, and properly timestamped.

Our read: Shopify produces more homogeneous transaction exports, which makes building the e-reporting feed more straightforward. PrestaShop, depending on the version and installed modules, can present gaps in order metadata — delivery country, VAT rate applied — that complicate aggregation. A configuration audit before September 2026 is recommended in both cases.

For a full overview of French e-invoicing obligations, see our 2026 guide for SMEs.

The question deserves a direct answer. EU e-commerce VAT has operated since July 2021 on a single threshold of €10,000 in intra-community B2C distance sales per year. Beyond that, VAT is due in the customer's country and declared via the OSS (One-Stop Shop) single return. For imported goods valued at €150 or less, the IOSS (Import One-Stop Shop) regime applies.

Shopify applies per-country VAT rules more systematically once delivery zones and rates are correctly entered. PrestaShop can generate inconsistencies if tax modules are not kept current with national rate changes across EU member states.

Across our e-commerce client files, the most frequent VAT regularisations involve PrestaShop merchants whose tax modules had not been updated when a rate changed in a destination country, or whose shipping zones did not map cleanly to OSS brackets.

For more detail on OSS and IOSS obligations, see our dedicated article on EU VAT for e-commerce 2026 and our multi-country VAT flow analysis for marketplaces.

The smoothness of reconciliation depends heavily on the quality of available integrations.

Shopify's advantage lies less in the tools themselves than in the quality of the data they receive. A Stripe or PayPal feed exported from Shopify arrives in Pennylane or Sqalie with the metadata needed for clean reconciliation: order number, country, currency, VAT. With PrestaShop, an additional validation step is often required to confirm the fields are populated consistently.

See our tool pages for more: Sqalie, Pennylane, Qonto.

The question comes up regularly before a platform change or a fundraising round. A CMS accounting audit covers VAT configuration, transaction export consistency, PSP reconciliation reliability, and compatibility with e-invoicing obligations.

These figures are indicative and vary by provider and case complexity. They are not published tariffs.

A CMS accounting audit is not an optional expense: it prevents VAT assessments whose individual cost typically exceeds the prevention by a significant margin. For merchants above €500,000 in e-commerce revenue, an annual audit is standard practice in specialist accounting firms.

Consider a representative client: a French fashion e-retailer, €1.2 million in revenue, selling to France, Germany, Spain, Belgium, and the Netherlands. Running on PrestaShop since 2019, it crosses the €10,000 intra-community threshold in its third month of trading each year.

Starting position: tax modules not updated for 18 months, PrestaShop delivery zones configured by carrier rather than by fiscal country, no structured export feeding the OSS return. Outcome: German VAT under-declared by €23,400 across two financial years, late-payment penalty of €1,800, retrospective regularisation via OSS.

After restructuring the accounting layer through Sqalie with a reformatted PrestaShop export, and establishing a monthly per-country OSS dashboard review, the file is now under control. The same architecture would have been simpler to deploy from Shopify — not because Shopify "does VAT better", but because the exports are more normalised from the outset.

A CMS migration is one of the highest-risk operations for an e-commerce merchant's accounting continuity. Three risk zones to anticipate.

1. Order history migration: order numbers, VAT amounts, and payment methods must transfer without gaps to maintain clean ledger matching.
2. PSP reconciliation continuity: Stripe and PayPal maintain their own transaction identifiers, independent of the CMS. The risk is losing the correspondence between the CMS order and the PSP settlement if the mapping table is not exported before the switch.
3. VAT configuration on the new CMS: a migration is not an opportunity to start fresh on VAT. Rules in force at the time of the switch must be reconfigured identically, then audited before the first live order.

Across our e-commerce files, a migration without a prior audit generates two to four months of additional manual reconciliation on average. A clean migration requires six to eight weeks of preparation.

For context on accounting for e-commerce businesses, see our overview here.

For a DTC launch with limited technical budget and rapid multi-country ambitions: Shopify Basic with a Pennylane or Sqalie connector is the path of least accounting resistance.

For a technical B2B catalogue with complex invoicing and high customisation needs: PrestaShop allows flexibility that Shopify cannot match without expensive third-party applications, provided an initial VAT configuration audit is built into the project.

For a marketplace architecture with IOSS flows: both platforms require a dedicated middleware layer; the choice of CMS becomes secondary to the quality of the marketplace-to-accounting connector.

See our e-commerce accountant sector page and our PrestaShop-specific accounting analysis for further reading.

When the French tax authority (DGFiP) reviews an e-commerce file, it asks for the same evidence regardless of the CMS: transaction-level exports, the OSS reconciliation by destination country, the invoice-numbering audit trail, and the match between payment-provider settlements and the bank. The platform only changes how quickly you can produce that evidence.

A cleanly scoped Shopify file usually answers these requests in hours, because the exports are granular and the OSS data is already split by country. A PrestaShop file that was never audited can take days to reconstruct, and any gap in the numbering sequence or in the VAT mapping tends to widen the scope of the review.

Our advice is the same on both platforms: keep the OSS reconciliation current every quarter, never delete test orders from the live store, and store the structured exports that tie each sale back to its VAT treatment.

Current as of 26 May 2026. This comparison is for information purposes and does not replace a personalised audit of your e-commerce stack. For your specific situation, consult a qualified chartered accountant.