Free COA Hosting: Where to Host Your Certificate of Analysis

You paid a lab to test your product and got back a PDF. Now the actual question: where does that certificate of analysis live so a customer, a retailer, or an inspector can open it on demand — and still open it a year from now? Emailing the file and dropping it in a shared folder both work until they don't. Here's what "COA hosting" really needs to do, and how the common options stack up.

The problem with where COAs usually end up

Most brands host their COAs by accident rather than on purpose, and each default has the same failure mode: the link the customer follows isn't stable, or isn't yours.

The common thread: the address printed on your packaging outlives the thing it points to. A batch number that resolves to a dead link, a login wall, or the wrong report is treated by buyers — and often by regulators — the same as having no COA at all.

What to actually look for in COA hosting

Strip away the branding and every good option does the same four things. Use these as a checklist for any host you're considering, including us:

The fixed-URL part is the whole game. Anything that links straight to a file — a PDF in cloud storage, a document on your site — ties the label to a filename. Change the file and the link often changes with it, which is precisely the moment a printed QR code turns into a dead end. A hosted page keeps the address constant and lets the contents behind it change.

The common approaches, side by side

Four ways brands actually host COAs, measured against the checklist above:

Approach Permanent per-batch link? QR code? No login to view? Easy to update?
Drive / Dropbox link Shaky — link can change on re-upload; no batch structure Not built in Depends on sharing settings Re-upload often changes the link
PDF on your website Only if you keep the URL stable through redesigns Only if you generate one Usually yes You own it, but you build and maintain it
Lab portal Per batch, but on the lab's URL — not yours Varies by lab Usually yes Not by you; tied to that lab
BatchLink Yes — one fixed URL per batch, by design Printable QR per batch Yes — no account for viewers Edit the page; URL and QR stay fixed

None of these is wrong for every situation. A PDF on a site you fully control can be perfectly permanent if you're disciplined about never changing the URL. A lab portal is fine right up until you change labs. The reason a dedicated host exists is that the two properties brands most often lose — a stable address you own, organized per batch — are exactly the two that a folder or a portal gives up first.

Where BatchLink fits

BatchLink is a free tool built to do only the four things above and do them permanently. You enter a batch once — product name, batch number, test date, the lab, and the report PDF — and it publishes a hosted page at a fixed address, plus a printable QR code that encodes that address. Scanning it opens the batch page with no login. If you need to correct something later, you edit the page and the URL never moves, so labels already printed keep working.

It's genuinely free to start: your first 2 batch pages cost nothing, no card, no expiring trial — enough to host a real COA end to end before you commit. Once you're tracking more than a couple of products and want them all in one place with your own branding, the unlimited dashboard is $29/mo. That's the entire model.

Host your first COA at a permanent link

Enter your batch once, get a hosted page and a printable QR code that always points to the right report. First 2 batches free, no card. See a live example page →

Create my batch page →

A note on compliance

Some states now expect a hemp or CBD label to carry a scannable link straight to the product's lab results, and marketplaces and retailers increasingly ask for per-batch COAs too. Requirements differ by state and by product, and they change — this page is about hosting mechanics, not the letter of any rule. For specifics, our state-by-state requirements guide and the label checklist are better starting points, and the plain-English COA guide covers what a good report contains. This isn't legal advice — check your state's current rules.

Common questions

What does it mean to "host" a COA?

Hosting a certificate of analysis means putting the lab report at a fixed web address that anyone can open — instead of only emailing the PDF around. Good COA hosting gives each production batch its own permanent link, so a customer, retailer, or regulator can pull up the exact report for the batch in front of them.

Is free COA hosting actually free, or a trial?

With BatchLink your first 2 batch pages are free, with no card and no expiring trial — enough to host a real COA and print its QR code before you decide anything. Once you're managing more than a couple of products, the unlimited dashboard is $29/mo.

Can I just host my COA on Google Drive?

You can, but it's fragile. Drive and Dropbox links can change when you re-upload a file, and the person scanning may hit a sign-in or "request access" wall depending on the sharing settings. There's also no per-batch structure and no QR code — so it's easy to end up with the wrong batch's report behind a printed label.

What happens to my links if I switch testing labs?

A COA hosted on a lab's own portal lives on that lab's system and under their URL. If you change labs, that link is no longer something you control, and older links may look and behave differently from newer ones. Hosting each batch's COA yourself keeps the address on your label under your control, no matter who ran the test.

Does the person scanning the code need an account?

They shouldn't. The whole point of a COA link on a label is that a customer or inspector can scan it and immediately see the result. A hosted batch page opens the report with no login, no app, and no permission prompt.

Can I update a COA after the labels are already printed?

Yes, if the URL is fixed. With a hosted page, you edit the page's contents or swap in a corrected report, and every QR code already printed keeps pointing at the same address — now showing the updated information. That's the main advantage over linking straight to a static file.