A code the buyer
can check
An exporter asks what was sprayed on the beans and when they were picked. The answer is already in your spray log and your harvests. Publish that one record and Famu prints a QR code; the buyer scans it and reads your own log in ten seconds, never your prices.
The crop, the plot, the dates, what was applied and what was harvested.
The lot, how it was processed, the crop it came off and what was applied to that crop.
The flock, the house, the dates, and every vaccination and medication it was given.
One record, published on purpose
Nothing is public until you choose it, record by record.
Open the plantation, coffee lot or batch and tap Publish for buyers. Famu tells you exactly what the page will show for that kind of record before you agree. Add a note for the buyer if you like, such as "Lot 3, delivered 12 Feb", and publish.
The code then prints on that record's report PDF and on the receipts for sales from it. Business → Traceability lists everything you are sharing.
The buyer sees
- The crop or flock, the plot or house
- Planting, spraying and harvest dates
- Products applied, and their intervals
- Your farm's name, and your note if you wrote one
The buyer never sees
- A price, a sale, an expense or a cost
- Your other records
- Who on the farm recorded what
Was anything picked too soon?
The question a buyer's compliance officer actually asks.
Every spray has a pre-harvest interval, the days to wait before picking. For each harvest, Famu checks every spray applied on or before it. If each one's safe date had passed, the harvest is clear. A spray applied after a harvest has nothing to do with it.
A product with no interval recorded is not counted as clear: Famu will not vouch for a blank field, so the page says some intervals cannot be checked. And the whole record takes its worst harvest's answer, because one early picking is something a buyer needs to ask about. Change the spray below.
- Mancozeb
- Lambda-cyhalothrin
- Harvest80 kg
- Harvest120 kg
A code you can kill
Stopping is immediate, and it stays stopped.
Tap Stop sharing and the page goes dark at once for anyone holding the code. Publish the same record again later and it gets a new code. The old one never comes back, because otherwise un-sharing would quietly un-do itself on every sack you had already labelled.
The rules for a public page
No money, ever
The buyer's page is built from a fixed list of fields that holds no price, sale, cost or expense. A field added to the farm's records later does not leak onto it.
The code is the only key
Each code is long and random. Knowing one farm's record number gets a stranger nothing; only a published code opens a page.
Who can publish
By default an admin and a manager can publish and stop sharing. Workers cannot decide what the farm shows the world.
Read-only for the buyer
The buyer needs no account and can change nothing. They see the record as it stands when they scan.
Your record, not a certificate
What it does not do
A QR page shows what the farm recorded. It is not a certification and no one has audited it; its value is that the record was kept as the work happened, with dates.
The spray check is only as good as the intervals on your products. Record the interval from the label, or the buyer will be told it cannot be checked.
Earns its keep for
- Coffee, fruit and vegetables sold to exporters or supermarkets
- Contract farming with a spray-record requirement
- Broilers sold to a buyer who asks about drugs and withdrawal
Does little for
- Produce sold loose at the local market
- Sharing a record with one person you trust: share it with them directly instead