farm guide
Running a farm gate in a field with no signal
Reviewed: 2026-08-09
The offline model is real: a signed manifest downloaded before doors, scans validated on the device with no network, a replay when you are back on wifi and a conflict queue for anything two devices disagreed about. What bindro does not ship is the scanner itself. Plan for that, and for the one refusal that surprises farms — an unnamed place on a family booking does not admit.
What does the offline door actually do?
Before the gate opens, your device pulls a signed manifest for that session: who is due, and what their credential hashes are. From then on it needs no network at all. A scan is validated locally against the manifest, an entry not on the list is refused on the spot, and everything the device admits is recorded with a timestamp and its own device sequence.
When the device is back on wifi — in the farmhouse, at the end of the morning — it replays what it recorded. A replay applied twice counts once, so a flaky upload is safe. Where two devices admitted the same visitor, the later one is flagged as a conflict and lands in a queue you read afterwards, decided by timestamp rather than by which device happened to upload first.
What do I have to supply myself?
The scanner. bindro ships no camera app: the manifest, the replay and the scan itself are an interface, and the device that reads a code is yours or your integrator. That is the single most important sentence on this page, because "works with no signal" is easy to read as "here is an app".
What you get without writing anything: the console can check a visitor in one at a time from any browser, and it works fine for a small gate or as the fallback when a device has a bad morning. Wristband binding is in the same position — the door admits a bound band exactly as it admits a code, and a band is bound from the visitor list in the console or through the interface.
- A device with a camera and something that reads a QR code into the scan endpoint.
- Wifi somewhere on site for the manifest download and the end-of-session replay.
- A fallback: the browser check-in in the console, and a printed list if you want belt and braces.
- A decision about wristbands, which need a small integration before they are worth anything.
Why did a family four entries not scan?
Because the places were never named. Any order for more than one entry becomes a roster of places, and a place with nobody on it is refused: it is left off the offline manifest entirely and a live scan returns a plain refusal. The booking page never asked the booker for those names, because this vertical asks its questions of the order — party size, vehicle, access needs — rather than of each visitor.
What the booker got instead is an email with a link to their roster, where they can name each place, or send a per-place link to whoever is coming. If they ignored it, their four entries do not work, and you find out at the gate.
Live with it deliberately. Put the roster link in the front of your own confirmation copy and your reminder; keep a phone at the gate on the roster page so a place can be named in twenty seconds; and if your patch is mostly walk-up families, consider selling single-entry orders so no roster is ever created.
How should I staff the gate?
Put the rota in bindro so today shifts show on the day-of page beside the numbers you are watching: who is on, in what role, from when to when. Re-rostering somebody edits their shift rather than stacking a second one, and inverted times and unknown sessions are refused rather than saved.
One thing a shift does not do is grant access. Being on the rota gives nobody permission to see anything; what a member can do is their role in your organisation, which is how you give gate staff check-in without showing them the money.
What should I check the week before opening?
Do the whole thing once, on the farm, with the actual device and the actual signal you actually have. Every failure worth finding is a failure of your particular field, and none of them show up from an office.
- Download a manifest, then put the device in airplane mode and admit a real entry with it.
- Replay from where your wifi actually reaches, and confirm the scans landed.
- Buy a multi-entry order, leave the roster unfilled on purpose, and watch it be refused.
- Fill that roster from a phone and confirm the same entry then admits.
- Check the conflict queue after scanning the same entry on two devices, so you know what it looks like before it matters.
What should I take away?
- The offline model is real and complete: signed manifest, local validation, replay, conflict queue.
- bindro ships no scanner app — budget for a small integration or use the browser check-in; wristband binding is on the visitor list.
- An unnamed place on a multi-entry booking is refused at the gate; chase the roster in your own emails.
- The rota reaches the day-of page, and a shift never grants permission on its own.
- Rehearse the whole loop in your own field, in airplane mode, before the first Saturday.
Reviewed: 2026-08-09
What else should I read?
Pumpkin patches and corn mazes: the overview
Gate ticketing that works in a field with no signal.
Pumpkin patches and corn mazes FAQ
24 questions from farms and visitors.
bindro vs Square
Reviewed 2026-08-09.
bindro vs Roller
Reviewed 2026-08-09.
bindro vs Eventbrite
Reviewed 2026-08-09.
bindro vs FarmSpread
Reviewed 2026-08-09.
Opening a six-weekend season of timed entry without typing 200 slots by hand
Reviewed 2026-08-09.
What to do when the field is a swamp on Saturday morning
Reviewed 2026-08-09.
Pricing a pumpkin patch so the quiet weekdays pay for themselves
Reviewed 2026-08-09.
Run your visits on bindro
Nothing to pay until you sell. 2.5% + $0.99 per paid entry; free visits cost nothing.
Start selling — free