Housekeeping asked by the wordpress.org review: nothing changes on your shop.<\/p>","0.7.1":"
A rejected invoice now shows the reason for the rejection, which could previously stay blank for ever. Nothing to configure.<\/p>","0.7.0":"
Fixes two ways a business order could go uninvoiced or unreported: a valid company number refused at the checkout on its check digit, and a filed invoice showing no status on a shop WeInvoice cannot reach. Nothing to configure.<\/p>","0.6.0":"
New invoices are numbered by WeInvoice in one unbroken sequence. A shop that was already connected keeps its own numbering and is not renumbered; the choice is now a setting on the connection screen.<\/p>","0.5.0":"
Shows each invoice's official lifecycle status on the order screen and in the order list, and explains a rejection in plain language. Nothing you have to configure: the status channel is set up when the shop connects.<\/p>","0.4.0":"
Starts sending invoices for orders that reach Processing or Completed, and credit notes for refunds. Orders from private customers are unaffected and still send nothing.<\/p>","0.3.0":"
Adds the checkout SIREN field. Orders from private customers are unaffected and still send nothing.<\/p>","0.2.0":"
Adds the connection screen. Existing installs keep doing nothing until a key is entered.<\/p>","0.1.0":"
First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3668890,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3668890,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3668890,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3668890,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.7.3"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3668890,"resolution":"1","location":"assets","locale":"","width":3360,"height":2100},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3668890,"resolution":"2","location":"assets","locale":"","width":2560,"height":2258},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3668890,"resolution":"3","location":"assets","locale":"","width":3360,"height":2044},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3668890,"resolution":"4","location":"assets","locale":"","width":3360,"height":1830},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3668890,"resolution":"5","location":"assets","locale":"","width":3360,"height":2356}},"screenshots":{"1":"The connection screen: the API key is stored and the company invoicing for the shop is recognised.","2":"The \"SIREN number\" field in the checkout, here on the block-based checkout.","3":"The regulatory status on the order screen: \"212 Encaiss\u00e9e\", with its official French code and label.","4":"The WeInvoice column in the order list: what is settled, and what is still in transit.","5":"The WooCommerce -> WeInvoice screen: the queue, what is stopped and why, and what the plugin does not cover."}},"plugin_section":[],"plugin_tags":[225611,226218,9085,12480,286],"plugin_category":[45],"plugin_contributors":[277880],"plugin_business_model":[],"class_list":["post-358608","plugin","type-plugin","status-publish","hentry","plugin_tags-e-invoicing","plugin_tags-factur-x","plugin_tags-france","plugin_tags-invoice","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_contributors-vswom83","plugin_committers-vswom83"],"banners":{"banner":"https:\/\/ps.w.org\/weproc-french-einvoicing\/assets\/banner-772x250.png?rev=3668890","banner_2x":"https:\/\/ps.w.org\/weproc-french-einvoicing\/assets\/banner-1544x500.png?rev=3668890","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/weproc-french-einvoicing\/assets\/icon-128x128.png?rev=3668890","icon_2x":"https:\/\/ps.w.org\/weproc-french-einvoicing\/assets\/icon-256x256.png?rev=3668890","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/weproc-french-einvoicing\/assets\/screenshot-1.png?rev=3668890","caption":"The connection screen: the API key is stored and the company invoicing for the shop is recognised."},{"src":"https:\/\/ps.w.org\/weproc-french-einvoicing\/assets\/screenshot-2.png?rev=3668890","caption":"The \"SIREN number\" field in the checkout, here on the block-based checkout."},{"src":"https:\/\/ps.w.org\/weproc-french-einvoicing\/assets\/screenshot-3.png?rev=3668890","caption":"The regulatory status on the order screen: \"212 Encaiss\u00e9e\", with its official French code and label."},{"src":"https:\/\/ps.w.org\/weproc-french-einvoicing\/assets\/screenshot-4.png?rev=3668890","caption":"The WeInvoice column in the order list: what is settled, and what is still in transit."},{"src":"https:\/\/ps.w.org\/weproc-french-einvoicing\/assets\/screenshot-5.png?rev=3668890","caption":"The WooCommerce -> WeInvoice screen: the queue, what is stopped and why, and what the plugin does not cover."}],"raw_content":"\n
From 1 September 2026, French businesses must receive electronic invoices, and\nissuing them becomes mandatory in turn. An invoice between two French businesses\nno longer travels as a PDF by e-mail: it travels through a plateforme agr\u00e9\u00e9e<\/em>\n(PA), a platform registered by the tax administration.<\/p>\n\n WeInvoice is one of those platforms \u2014 registered under number 0104. This plugin\nconnects your shop to it directly. There is no intermediary, no third-party\naccount to open and no government API key to request: your shop talks to the\nplatform that files the invoice.<\/p>\n\n B2C orders never leave your shop.<\/strong> An order whose buyer is a private\nindividual, or whose SIREN is not registered in the PPF directory, produces no\nelectronic invoice and no request of any kind<\/strong>. It is counted on the\nWooCommerce → WeInvoice screen so you can see exactly how much of your\nbusiness is not covered, and that count stays on your server. The\nregulation handles those sales through e-reporting<\/em>, which this version does\nnot cover: if you sell to consumers you still owe that declaration by another\nroute, and this plugin will never pretend otherwise.<\/p>\n\n It is also not a cash-register system: it does not take payments, does not keep a\ntill and records no settlement of its own.<\/p>\n\n This plugin connects to one<\/strong> external service, and to nothing else. There is\nno analytics service, no error-reporting service, no relay and no telemetry of\nany kind.<\/p>\n\n Who operates it.<\/strong> Weproc SAS, France \u2014 the plateforme agr\u00e9\u00e9e<\/em> n\u00b00104 that\nfiles your invoices with the tax administration.<\/p>\n\n What it is used for.<\/strong> Filing your electronic invoices and the credit notes\nyour refunds owe, reading their regulatory lifecycle statuses back, and checking\nwhether a business customer is registered in the French PPF directory.<\/p>\n\n When data is sent.<\/strong> Never before you have entered your own WeInvoice API key\non the plugin's settings screen. Once you have, What data is sent.<\/strong> In situation 3, a SIREN. In situation 4, the data an\nelectronic invoice legally carries: your own identification, the business\ncustomer's identification (SIREN\/SIRET, company name, billing address), the order\nlines with their amounts and VAT, the totals and the payment terms.<\/p>\n\n What is never sent.<\/strong> Orders placed by private individuals, orders whose buyer\ncarries no registered SIREN, your shop's traffic, your customer list, your\nproducts, and the count of out-of-perimeter orders itself.<\/p>\n\n In situation 3, the SIREN is checked at most once a day per company<\/strong>: the\nanswer is remembered on your own server, and a customer typing does not trigger\nanything \u2014 the check happens when the order is placed. If it cannot be made, the\norder goes through anyway; nothing at your checkout ever depends on our\navailability.<\/p>\n\n\n No. WeInvoice is itself a plateforme agr\u00e9\u00e9e<\/em>; your shop talks to it, and it\nfiles with the administration. You need a WeInvoice account, nothing else.<\/p><\/dd>\n WeInvoice does, unless you tell it otherwise. An invoice number cannot be reused\nand the sequence must not skip numbers, and a plain WooCommerce order number is\nneither of those: it is a website reference your shop shares with its pages,\nmedia and coupons, so it jumps whenever you publish anything else \u2014 and two shops\nbelonging to the same company would produce the same one. Leaving the numbering\nto WeInvoice gives you one unbroken series.<\/p>\n\n Choose This shop<\/em> only if you already run an extension that gives your orders\nreal invoice numbers; the plugin then sends the number your shop displays, and\nnothing about your series changes.<\/p>\n\n Whichever you choose, the order number always travels on the invoice as your own\nreference, so you can find the order back from it.<\/p><\/dd>\n No. A shop that was already connected keeps numbering its own invoices, exactly\nas before. The new setting is on the connection screen if you want to switch.<\/p><\/dd>\n Nothing leaves your shop. They are counted locally so that you can see them, and\nthat is all. Those sales fall under e-reporting<\/em>, which this version does not\nhandle.<\/p><\/dd>\n In an optional Company SIREN number<\/em> field the plugin adds to the additional\ninformation section of your checkout \u2014 both the classic one and the block one. A\ncustomer who leaves it blank orders exactly as before: the field never blocks a\nsale. A number that is not nine valid digits is refused on the spot, while the\ncustomer is still on the page, rather than after the order is placed.<\/p><\/dd>\n No. A French VAT number contains the company's SIREN, so the plugin reads the\nnumber that extension already stores and uses it. A VAT number issued in another\ncountry is left alone: its digits belong to a company in that country's register,\nnot to a French one, so no invoice is ever built from it.<\/p><\/dd>\n The order goes through and stays on your shop: it is marked out of perimeter and\ncounted, and nothing about it is sent anywhere. If the check itself could not be\nmade \u2014 your server offline, ours busy \u2014 the order is simply left undecided and\nsorted out when its invoice is filed. Your checkout never fails because of us.<\/p><\/dd>\n No. A refund creates the credit note it owes, automatically, for a partial refund\nas well as a full one \u2014 nothing to tick and no e-mail to send.<\/p><\/dd>\n No. Nothing is sent while an order is being saved: the order is put in a queue\nand the sending happens in the background, so a slow or unavailable service can\nnever delay or break a customer's checkout.<\/p><\/dd>\n It is retried on its own, with a growing delay, for up to four days \u2014 long enough\nfor you to sign a missing mandate, settle an account or switch on a setting and\nhave the invoice leave without touching anything. Every attempt is recorded on\nthe order itself, successes and failures alike, and stays there as long as the\norder does.<\/p><\/dd>\n Yes. The plugin declares compatibility with HPOS and reads and writes orders\nexclusively through the WooCommerce CRUD.<\/p><\/dd>\n Yes. Compatibility with the cart and checkout blocks is declared, and the\nbusiness-customer field is registered for both the block and the classic\ncheckout.<\/p><\/dd>\n In your WeInvoice space, under Espace d\u00e9veloppeur<\/em>. The key is displayed once,\nin the Your shop's request never reached WeInvoice: it was stopped by the filtering\ndevice in front of the platform, which the French e-invoicing conformity rules\nrequire. Invoicing data must stay inside the EU, so a shop whose server makes\nits outbound connections from outside it cannot file invoices. Ask your host\nwhich country your site connects out from \u2014 nothing on your WeInvoice account\nneeds changing.<\/p><\/dd>\n On WeInvoice's infrastructure, in the European Union. See the privacy policy\nlinked above.<\/p><\/dd>\n\n<\/dl>\n\n\nWhat it does<\/h4>\n\n
\n
What it deliberately does not do<\/h4>\n\n
Requirements<\/h4>\n\n
\n
External Services<\/h3>\n\n
WeInvoice (api.weinvoice.fr)<\/h4>\n\n
https:\/\/api.weinvoice.fr<\/code> is\ncontacted in five situations, and no other:<\/p>\n\n\n
\n
\n
\n
Do I need an account with a government portal?<\/h3><\/dt>\n
Who gives my invoices their numbers?<\/h3><\/dt>\n
I already had this plugin connected. Did the update renumber my invoices?<\/h3><\/dt>\n
What happens to my orders from private customers?<\/h3><\/dt>\n
Where do my business customers enter their SIREN?<\/h3><\/dt>\n
I already use the EU VAT Number extension. Do my customers have to type their SIREN again?<\/h3><\/dt>\n
What if a customer's SIREN is not in the PPF directory yet?<\/h3><\/dt>\n
A refund happened. Do I have to do anything?<\/h3><\/dt>\n
Does it slow down my shop?<\/h3><\/dt>\n
An invoice did not leave. What happens?<\/h3><\/dt>\n
Does it work with high-performance order storage (HPOS)?<\/h3><\/dt>\n
Does it work with the block-based checkout?<\/h3><\/dt>\n
Where do I get an API key?<\/h3><\/dt>\n
client_id.secret<\/code> form; paste it whole into the plugin's settings\nscreen. It is stored on your own server, is never displayed again and is\nremoved when you uninstall the plugin.<\/p><\/dd>\nThe plugin says my site seems to be hosted outside the European Union. What does that mean?<\/h3><\/dt>\n
Where is my data hosted?<\/h3><\/dt>\n
0.7.3<\/h4>\n\n
\n
SDK-REVISION.txt<\/code> (extension-less files are not permitted in the directory). No functional change.<\/li>\n<\/ul>\n\n0.7.2<\/h4>\n\n
\n
0.7.1<\/h4>\n\n
\n
0.7.0<\/h4>\n\n
\n
0.6.0<\/h4>\n\n
\n
0.5.0<\/h4>\n\n
\n
0.4.0<\/h4>\n\n
\n
0.3.0<\/h4>\n\n
\n
0.2.0<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n