AuditPass

BatchPages — Shopify app in development

Your customers are seeing the wrong COA. A lab-results page for every batch fixes it.

A Shopify file metafield holds one value per product. Upload the lab report for your newest lot and it replaces the last one — so the customer holding a can from three batches ago scans your QR code and is shown a certificate of analysis for product they are not drinking. BatchPages gives every batch its own permanent page, so the result a customer sees is the result that is actually in their hand. No limits on how many batches you run.

Join the early-access waitlist Free. No card. No commitment.

What about Shopify's metaobject limits?

A second, narrower problem — and the one merchants usually hit after they have already built batches the hard way. Here are the actual numbers, straight from Shopify's developer documentation.

128 metaobject definitions per shop on Basic, Shopify and Advanced plans
256 definitions per shop on Plus and Enterprise
1,000,000 entries allowed per definition

The gap between those numbers is where stores get stuck. Definitions are the scarce resource; entries are effectively free. A store that models each batch as its own metaobject definition — the approach that feels obvious when you are setting up your first few lots — spends the scarce resource on the thing there is most of, and runs out at 128 on a standard plan.

Raising the ceiling is not the fix, because the ceiling is not really the problem. BatchPages keeps batches on the entry side of the line, where the allowance is 1,000,000 per definition, and renders each batch page from the app instead of from a per-batch template. Your definitions stay available for the structured content they were designed for.

Limits verified against Shopify's documentation, Metaobject limits (shopify.dev). Shopify raised the per-definition entry allowance to 1,000,000 in October 2025, from 64,000 on non-Plus plans.

What BatchPages will do

One job, done properly: publish the certificate of analysis for every batch you ship, at an address that keeps pointing at that batch.

The right result, per lot

Older batches stop showing the newest batch's COA

A Shopify file metafield stores one value per product, so each upload overwrites the last. Every can already in a customer's hand starts pointing at a lab report for a different lot. BatchPages keeps one page per batch, each holding its own certificate, so a lot printed in March still resolves to March's results in December.

No ceiling

A page per batch, however many batches you run

Model batches as metaobject entries and you get a million per definition. Model them as definitions — one per batch, the mistake that feels natural — and you hit 128 on a standard plan and stop. BatchPages keeps batches on the side of that line that scales, so a new lot never means a new limit.

Print it on the can

QR codes that survive the label print run

Every batch page gets a stable, permanent URL and a QR code sized for a can, pouch or carton label. The code is generated when the batch is, so artwork does not wait on anyone to build a page by hand.

Findable, sendable

Indexed pages retailers and regulators can actually open

Each page is a real, crawlable URL with its own title, description and structured data — not a modal, not a PDF in a Drive folder. Send a buyer or an inspector a link and it opens, on any device, without a login.

Leave the theme alone

No theme surgery, no developer ticket

Pages render from the app, styled to match your storefront. No Liquid edits, no duplicated templates to maintain, and nothing that breaks the next time you change themes or accept a theme update.

How it will work

Four steps, and only one of them is yours to repeat per batch.

  1. Connect your store

    Install the app and pick which products carry batch-level lab results.

  2. Add a batch

    Upload the COA and enter the lot code, test date and panel results — or let the app read the fields off the lab PDF.

  3. Page and QR go live

    BatchPages publishes that batch's own page, generates the QR code, and links it from the product — without touching the page any earlier batch already points at.

  4. Hand off the artwork

    Export the QR at print resolution for your label file. The URL never changes, so printed cans keep resolving for the life of the lot.

Early access

Get BatchPages before the public listing

The app is in development. Tell us how many batches you run and we will build for that number — waitlist members get access first and help set the roadmap. No card, no commitment, and we will not sell your address to anyone, ever.

We will email you about BatchPages and nothing else.

Questions

Why do my customers see the wrong certificate of analysis?

Because Shopify's file metafields hold a single value per product. When you upload the COA for a new batch to the same product, it replaces the previous one — there is no version history and no per-lot addressing. Every unit already sold now links to lab results for product the buyer does not have. It is the correct behaviour for a product photo and the wrong behaviour for a batch record. BatchPages fixes it by giving each batch its own page and its own permanent URL, so the QR printed on a can resolves to that can's results for as long as the can exists.

Can I show Shopify batch lab results without editing my theme?

Yes — that is the design. BatchPages renders each batch's page from the app and links it from the product, so there are no Liquid edits, no duplicated templates, and nothing that breaks when you change themes or accept a theme update. Your COA product page keeps working through a redesign.

Does this work on my Shopify plan?

That is the plan. BatchPages is being designed for Basic, Shopify and Advanced stores first, because those are the merchants who run out of room soonest — Shopify allows 128 metaobject definitions per shop on those plans versus 256 on Plus and Enterprise. Plus stores are supported too; they just tend to feel the squeeze later.

What about the metaobject limit — will I hit it?

Shopify caps metaobject definitions at 128 per shop on standard plans (256 on Plus and Enterprise), and allows up to 1,000,000 entries per definition. Stores hit a wall when each batch is given its own definition, which burns the small number fast. BatchPages is built so batches consume entries, not definitions, and generates pages from the app rather than from per-batch templates. Your definition budget stays free for the things it was meant for.

When does it launch?

It is in development and there is no public launch date yet. The waitlist is how we decide what to build first and who gets access earliest — early-access spots go out before the public listing, and joining costs nothing and commits you to nothing.

Is my COA data mine?

Yes. Your certificates of analysis and batch records are your records. You will be able to export them, and removing the app will not hold your documents hostage. We are a compliance-documentation company; that is a line we do not cross.

What kinds of products is this for?

Anything sold by batch or lot with a test result behind it — hemp and THC beverages, gummies and tinctures, supplements, functional drinks, cosmetics and any product whose buyers or regulators expect to see a current COA.

Still deciding? Join the waitlist — it costs nothing and you can leave at any time.