Running the market day when there is no signal

How does check-in work in a field with no coverage?

The device downloads a signed manifest of the day’s traders before you leave, and after that it needs nothing: names are ticked off locally with no connection at all, and the log uploads when the phone finds signal again. Check-in for a market is a name list rather than a scan, which is what a market manager with a clipboard actually wants — nobody has to remember a code or keep a QR on a cracked screen.

Two properties matter when the signal is bad rather than absent. Re-uploading the same log changes nothing, so a connection that drops halfway through cannot double-count anybody. And if two people with two phones both tick off the same trader, both records survive and the clash appears in a conflict queue for you to settle afterwards — rather than one silently overwriting the other, which is how a disputed no-show becomes unresolvable.

Re-entry is allowed for this vertical, so a trader leaving to move their van and coming back is not an incident. And a trader who booked by invoice is admitted exactly like one who paid by card; only a cancelled booking is refused.

• Download the manifest before you leave the office, on every phone that will use it.
• Tick names off with no signal; the log uploads itself later.
• Re-uploads are ignored, so a flaky connection is safe.
• Two-device clashes go to the conflict queue, not to whoever synced last.

Who should be on the rota, and what does being on it grant?

Roster your people onto the market day from the staffing page — one shift per person per date, with the times checked so an inverted shift is refused — and today’s shifts appear on the day-of page, which is the screen a manager actually works from on a phone.

Being on the rota grants nothing. Access comes from the role, and the two are deliberately separate: a volunteer can be on the list for Saturday without reaching payouts, the financial reports or the trader export, and a finance role can reach the money without going anywhere near the door. Hiding a link is not authorisation here — the check happens in the database on the request itself — so a shared phone in a coat pocket is a smaller problem than it would otherwise be.

What do I do about a trader who turns up unbooked?

Record it as a back-office booking in the console: pick the market day and pitch type, enter their details, and mark the payment as taken outside the platform. It runs through the same money path as a public booking — the same inventory lock, the same ledger entries, the same roster — so your counts and your board report stay true, and the trader appears on the day’s list like everybody else.

The money itself is yours to take. bindro has no market-day point of sale for this vertical and no card terminal, so it is your cash tin or your own reader. The alternative, often easier, is to send the trader to the booking page on their phone and let them pay properly while they unload.

Either way, do record it. A casual pitch taken in cash and never entered is a pitch missing from your occupancy figure and from the income a funder sees.

What happens when I have to cancel for weather?

You refund the bookings, and that is the whole of the mechanism: this vertical resolves neither a credit note nor a transfer to another date, so there is no way to move a trader to next Saturday inside bindro. Refunds reverse in a fixed order — your proceeds, then tax, then the platform fee — and because payouts release two days after a market day has actually run, nothing has to be clawed back from a date that never happened.

Two practical notes. Refunded pitches stay counted against the cancelled date, so if you reinstate a market day you may need to raise the capacity back up. And traders can refund themselves from their own confirmation email at any point before the market day starts, which in practice means a bad forecast on Friday night may empty the date before you have decided anything — there is no notice window you can set against that.