Work / Vlees van Ons

Vlees van Ons, a Dutch beef company, plans every animal in one system, from the farmer's sign-up to its slaughter weight.

My part
I designed and built it, and I keep it online.
When
August to September 2026
Status
In use since August 2026

The problem

Vlees van Ons buys cattle from farmers and sells the beef. The planning was in Excel. That worked, until the company started working with more farmers.

Each farmer had their own numbers, breeds, price agreement and delivery period. On top of that, someone had to keep track of when each animal goes to the slaughterhouse, who arranges transport and what the slaughter weight turns out to be. Contact details were copied more than once, and the transport company also needed an up-to-date planning.

What I built

Farmers sign up their animals through their own link, without an account, and from then on the system follows each animal: the agreed price, the delivery week, transport and, at delivery, its ear tag and slaughter weight. The butcher only sees how many animals come each week, and farmers who prefer to call are entered by the company itself.

What came out

From August to October 2026, 26 farmers were added and 32 sign-ups came in, for 111 animals. I counted them in the database in November 2026.

29 animals were delivered in 13 deliveries, each with its ear tag and slaughter weight.

I have not measured whether it saves time, so there is no number for that here.

“Above all, I wanted to avoid getting more paperwork as we started working with more farmers.”

Robert Krijger, Vlees van Ons

vleesvanons.nl

My LinkedIn post about this project, in Dutch

For engineers

The parts, the figures and the tools. If you do not build software yourself, you can skip this.

How it fits together

Each farmer has a personal link with a token. The sign-up form behind it needs no account, and the company can enter animals for a farmer too.

A sign-up moves through fixed steps: new, price agreed, planned in a delivery week, delivered. The dashboard shows where work is waiting: what still needs a review, a price or a week, and what comes in the next weeks.

At delivery the number of animals, the ear tag and the slaughter weight per animal are entered, and the purchase value is calculated from them. Transport has its own overview per week and per transporter. The planning, transport, farmers and administration can be downloaded for Excel.

Rights are set per employee, 17 on the admin side, and checked on the server on every request. The butcher has one right: the week overview. The app has its own manual, updated with every change a user can see.

  1. Peoplefarmers through their own link, the company in the admin, the butcher: week overview only
  2. ApplicationNext.js 16, API routes, rights checked per request
  3. DataPostgres on Supabase, 4 tables
  4. OutExcel downloads, manual in the app

The app runs on Vercel, the database on Supabase.

The figures

Measured means counted in the code or the system. Estimated means my own estimate, with the assumption next to it.
Farmers in the system26measured, Nov 2026
Sign-ups32measured, Aug to Oct 2026
Animals signed up111measured, Aug to Oct 2026
Animals delivered, with ear tag and slaughter weight29measured, Aug to Sep 2026
Deliveries13measured, Aug to Sep 2026
Screens13measured, Nov 2026
Rights you can give: 17 for staff, 1 for the butcher18measured, Nov 2026

Built with

  • Next.js 16
  • React 19
  • TypeScript
  • Tailwind CSS 4
  • shadcn/ui
  • Supabase
  • Postgres
  • Vercel
  • ExcelJS

Do you have a similar process?

Thirty minutes, video or phone. You describe one process that costs you time. I ask questions. Then I tell you honestly what I would do: automate it, fix it by hand first, or leave it alone. No slides. The 30-minute call is free and commits you to nothing.

Lima time, UTC-5. I reply within one working day, in English or Dutch, or in basic Spanish.

Or explain your problem in the chat