Final Year Project · Bayero University Kano

Broiler Farm Record Management System

An offline-first Android app and web console that replaces the paper batch book and the spreadsheet with one real-time system — built for a working poultry farm, not a classroom mockup.

Setting up a new business? Access is invite only — email aah2200819.swe@buk.edu.ng to request Admin access, and you'll be added by the Super Admin.

4Roles, each scoped
6Record types
up to 18Staff per business
1Active Manager per business
FCR 1.62 Feed conversion, updating as feed is logged
Every bird accounted for Mortality + harvest can never pass the starting flock
Batch 3 · Day 24 Register, record, harvest, close

Illustrative mock-up of the Android app · sample data, not real farm results

System capabilities

  • Offline-first
  • Role-based access
  • Live break-even
  • FCR tracking
  • Batch lifecycle
  • Supabase RLS
  • Built with Flutter
  • Manual sync
Four roles, one system

Who it's built for

Office roles work in the web console; field roles work in the Android app, online or off. Each role sees and does only what belongs to them.

Super Admin

Owns the platform

One level above every business on the system.

Web console · online only

  • Creates Admin accounts — access is invite-only, never self-serve.
  • Deactivates an Admin when the business relationship ends.
  • Reactivates the same account later without losing anything.

Deactivation is reversible by design, and enforcement lives in the database — Supabase row level security — not only in the interface.

Built for the farm, not just the demo

What it actually does

Six things that decide whether a record book survives contact with a real farm.

Works with no signal

Staff keep recording in the field with no connection. Everything queues on the device and reaches the server the moment it reconnects, or with a manual sync. The home screen shows whether you are online and how many entries are still waiting.

On-device first Auto sync on reconnect Pending count

Live financials, not post-mortem

Break-even price, profit/loss and Feed Conversion Ratio recalculate as entries come in — not once a batch is finished and manually totalled.

Role-based access

Four roles, each seeing and doing only what belongs to them — enforced at the database with Supabase row level security, not just hidden in the interface.

One record of truth

Mortality, feed, weight, vaccination, harvest, expenses and sales live in one place instead of across a notebook and a spreadsheet.

Every bird accounted for

Mortality plus harvested can never exceed the starting flock, so the numbers cannot quietly drift apart.

Closes itself out cleanly

Once mortality and harvest account for the full flock, the Manager is prompted to close the batch — reversible, and never silent.

Illustration · not farm data

Try the math

Move the figures and the break-even price recalculates with exactly the rule the app uses — forward-looking, per bird still to harvest, in Nigerian Naira.

500
18
0
Break-even price per bird
₦3,008

Every naira spent has to come back from the birds still in the house.

Birds still to harvest
482
Expenses not yet recovered
₦1,450,000

How it is worked out. Break-even price = (total expenses − revenue collected so far) ÷ birds still to harvest. Dead birds are excluded from the denominator, but their cost stays in the numerator. Once a batch is already profitable the price is clamped at ₦0, and when no birds remain to price, the result is —.

Illustration only. The figures above are made up to show the rule — they are not results from any real farm, and the app derives the same figure from live entries.

Illustration · not farm data

See the offline queue work

This is the behaviour of the real home screen. Go offline, record entries, then reconnect and watch the queue flush.

Offline · nothing can sync yet
0
entries pending Saved on this device, waiting for signal

On-device queue

    Illustration only — a rehearsal of the app's behaviour, not a real sync against a server.

    A batch, start to finish

    How a flock moves through the system

    Four steps, in order, from an opening bird count to a closed batch with the numbers already there.

    1. Step one

      Register

      The Manager opens a batch with its starting bird count and, optionally, assigns a Staff member on the spot. Everything after this is measured against that number.

      Starting flockStaff assignment
    2. Step two

      Record

      Staff log mortality, feed, weight and vaccinations daily, from the farm, with or without a connection. Each entry saves on the device first, then syncs.

      MortalityFeedWeightVaccinations
    3. Step three

      Harvest

      Harvests are recorded by count, then priced by the Manager — per kilogram, as a flat total, or given away at zero.

      CountPer kg or flat total
    4. Step four

      Close

      Once the numbers account for every bird, the Manager closes the batch. Profit, break-even and FCR are already there, not calculated after the fact — and the close can be reversed.

      ReversiblePrompted, never silent

    Try the system

    Install the Android app for the field-level mobile experience, or sign in to the web console if you've been given Admin or Super Admin access.

    Admin access is invite-only · sample figures on this page are illustrations