All projects

Case study · Booking platform

dobrelowisko.pl

A booking system for commercial fisheries: anglers book a spot and pay online, and the money goes straight to the owner’s account.

Role
Founder / Full-stack
Year
2026
Status
Ready, awaiting its first fishery
Technologies
React, Supabase, Stripe
The fishery owner’s dashboard, “Today” view: who is on the water now and until when, the number of bookings and free spots, the weather, and below it the list of bookings with the selected one’s details - dates, price and verification code.
Owner dashboard - today
The dobrelowisko home page: the line “Dobre łowisko. Dobrze prowadzone.” (a good fishery, well run) over a lake at dawn, a short description - spot bookings, a calendar and online payments for commercial fisheries - and an “Add your fishery” button.
The page for fishery owners
The dobrelowisko home page on a phone: the same line and description, with a full-width “Add your fishery” button.
The same page on a phone
01Problem
Bookings scattered across calls, messages and notebooks make fishery availability hard to manage.
02Solution
One system for anglers and owners: availability, bookings, payments and a management dashboard.
03Result
A complete booking and payment flow, verified in the payment provider’s test mode. The product is awaiting its first fishery.

01 · Context

Why it exists.

The owner of a commercial fishery takes bookings by phone, by Messenger and with a pen. The calendar is a notebook, the proof of payment is a screenshot, and the same spot occasionally gets sold twice. An angler who wants to book a place in the evening has nobody to call.

So the fishery’s rules are kept by the system rather than the owner’s memory: opening hours, length of stay, how many people fit on a spot. The owner can always step around them, because someone calls at six in the morning or pays cash at the gate.

02 · What I built

What is in it.

  • A page for each fishery with its description, rules, directions, gallery, opening hours and the weather. Booking needs no account.
  • Booking by the fishery’s own rules: hours, length of stay, closed days, a required fishing licence, headcount, and prices that change by day and season.
  • An owner’s dashboard designed for a phone: today’s bookings, the week’s calendar, spots, and customers with their history.
  • Online payments: the angler’s fee lands in the owner’s account, and the owner pays a subscription on one of three plans.
  • A confirmation email with a calendar entry and a QR code the owner scans at the gate.

03 · Decisions

The decisions that mattered.

  1. Double bookings are blocked by the database, not the form.

    WhyTwo people can click in the same second and both see a free spot. A check in the browser will not catch that, and a rule that lives in a form can be bypassed.

  2. The owner can enter a booking that skips the rules.

    WhyThey know their fishery better than any rules in the system, and need to add a booking after a phone call, after the fact, or on a closed day. The rules are there to govern self-service, not to get in the way of the person paying for it.

  3. The last days before launch went entirely on checking the payments.

    WhyThree passes in a row found two bugs that could make money disappear, one of them a refund paid out of the platform’s account instead of the owner’s. Every fix was confirmed in the payment provider’s test mode.

04 · Status

Where it stands now.

The whole path works: the angler finds a fishery, books, pays and gets a code, and the owner sees it in the dashboard and can issue a refund. Automated tests and final plan prices are still missing. The system is waiting for its first fishery, because numbers from users cannot be produced at a desk.