“You own your data” is easy to put on a homepage. This page says what it means in the product: who can see which beer, who can find you, who decides, when it becomes visible, and how you get everything back out — as a file, or straight into your own systems.
A product record is private to your brewery by default. Three separate gates have to open before anyone else sees it, and you hold all three.
A wholesaler cannot simply add your brewery. The relationship is an agreement between two parties, and it does not start until you accept it.
Partners see the beers you granted them and nothing else. Grant one, grant twelve, revoke one tomorrow — a seasonal you no longer distribute simply disappears from their view.
Prepare a launch in full, grant access up front, and keep the beer hidden until the date you chose; only partners you give early access see it sooner.
Illustrative record. The beer, the partners and the numbers are invented; the three access states are the ones the platform actually has.
Every brewery, wholesaler and partner starts out private: only the organisations you already work with can reach you. Whether the rest of BeerCollab may find you, and start working with you, is a setting your own team changes — and can change back.
A new organisation is never listed. Nobody browsing BeerCollab comes across you until someone on your team decides otherwise, in the organisation settings.
Make your organisation public and the breweries, wholesalers and venues on BeerCollab can find you and start a partnership — no introduction, no waiting for an invitation. That is when the platform works best: the network finds you, instead of you chasing every partner yourself.
Partners and wholesalers can also be listed on request. Every brewery can find them, but a partnership only starts once they accept the brewery’s request on their dashboard.
Public means visible to organisations signed in to BeerCollab — not to search engines. They see your name, your type and where you are. Never your contact persons, your address or who you already work with, and never a product: what a partner sees of a brewery’s catalogue is still granted per product.
Never shown: contact persons, email addresses, street address, KvK number, or which breweries you already work with.
Illustration. The café is invented; the three settings and what a brewery sees are the platform’s own. Breweries choose between private and public in the same place.
There is no step in the product designed to make leaving hard. Export is a normal feature, not a request you have to make of us — and for your own systems, there is an API.
Import your barcode ranges from a spreadsheet and export them again the same way, whenever you want.
Prices and discount rates export as a file you can hand to anyone, on or off the platform.
The template filler produces the wholesaler’s own sheet. That file is yours — it works in an email just as well as in the app.
An export is a copy of how things were. When your ERP, webshop or BI tool has to keep up with what happens on BeerCollab, connect it: webhooks tell it the moment something changes, and an API key lets it fetch the details. Owning your data means it lands wherever you work with it — set up by your own team, without asking us first.
Register an endpoint and choose the events it hears about: a partnership that starts or ends, a product that changes, an information request that is answered, a product a brewery shares with you.
A key lets another system fetch your organisation’s data, so a webhook’s “this changed” becomes the current record in your own database.
Any approved member of your team sets this up under Organisation → API & webhooks. Wholesalers have it from the Connected plan up, breweries on Integrated. Building the receiving side? We share the event catalogue and examples for verifying a delivery. Ask for the technical details →
POST /webhooks/beercollab
webhook-id: 0199a3c2-7e41-…
webhook-timestamp: 1790932443
webhook-signature: v1,K5oZfzN95Z…
{
"type": "product.updated",
"timestamp": "2026-10-02T09:14:03+00:00",
"subject": { "type": "Product", "iri": "/products/0199a3c1…" },
"organizations": [{ "type": "Brewery", … }],
"data": { "changedFields": ["allergenProfile", "ingredients"] }
}GET /products/0199a3c1…
Authorization: Bearer bck_4f1c9e…Illustrative delivery: ids and the signature are shortened. The shape is the real one — the event names the changed fields, never their values.
Your colleagues get their own logins with roles that decide what each of them can change. A user account belongs to one brewery — there is no shared login and no account that spans several companies.
The platform runs in Europe, on infrastructure chosen so that your catalogue does not leave it.
If you believe you have found a vulnerability, write to us before publishing it. We will confirm receipt, keep you updated, and credit you if you want to be credited.
security@beercollab.comGive us a reasonable window before disclosure, and do not access data that is not yours while testing.
A first response within 48 hours, an honest assessment, and word when it is fixed.