# bindro — Pumpkin patches and corn mazes

> bindro sells timed entry to a pumpkin patch or corn maze: each open day is cut into arrival slots, each slot holds its own inventory, and a visitor picks a date, picks a time and pays on one page that works on a phone in a farm track with one bar of signal. Hayrides, pick-your-own bags and parking are add-ons with their own stock. The gate scans a code or a bound wristband with no signal at all and reconciles when the device is back on wifi. Money reaches the farm two days after the last day of the visit it was sold under.

Canonical page: https://bindro.io/vertical/pumpkin-patch-ticketing/
Reviewed: 2026-08-09

## Facts
- Inventory model: seasonal nightly.
- Pricing models: flat, tiered, group rate, per person addon.
- Fees: 2.5% + $0.99 per paid entry; free visits cost nothing.
- Payouts: one payout per event, released 2 days after that event's LAST session has ended (low risk tier, 0% reserve). Never before delivery, and a visit sold as a run of dates pays out once, after the final date.
- Check-in: wristband, works offline. Visitors can come back in: a scan after they were admitted reads as a re-entry rather than a used code, at whichever entrance they come back to, and says when they first arrived. A second scan within a few minutes of the first is still read as the same code presented twice, so a screenshot passed down the queue does not get anybody in. The visit is counted once however often it is scanned.
- Joining: free, alone, in minutes. No contract, no monthly fee and no card at signup. A payout destination is verified before the first payout, never before the first sale.
- Booking fee default: the visitor pays it. A farm can absorb it or split it per visit; the fee itself does not change with the choice, only which side of the sale it comes from.
- Overselling is structurally impossible: inventory moves only under a row lock inside the transaction that confirms the order, with a database constraint behind that as a backstop rather than as the mechanism.
- The number this vertical is run on: Revenue per weekend day. Also tracked: weather sensitivity, group booking share, add-on attach rate. The console computes the north-star figure and prints the arithmetic under it, beside this farm's own funnel with the drop-off at each stage, where the traffic came from, refund, transfer, turnout, no-show, add-on and repeat rates each shown with its numerator and denominator, gross, fees and refunds per visit, live remaining capacity during the visit, and CSV exports of orders and visitors. A step the platform cannot observe says so rather than reporting a zero.
- Data export: orders and visitors as CSV from the console at any time, behind a fresh one-time code. No export fee, no notice period, no lock-in.

## Not supported for this vertical
- Every place on a booking of more than one entry must be named before the gate will admit it. A farm sells "four entries" and bindro makes a roster of four places, emails the booker a link and refuses any place still unnamed — on the offline door list and on a live scan alike. The booking page never asks for those names, because this vertical asks its questions of the order rather than of each visitor, so a family that ignores the roster email arrives with four entries that do not work. Tell your booker to fill it in, or sell single-entry orders, or budget for naming places at the gate on a phone.
- bindro will not tell you the weekend is washed out. Calling a day off is one control — it takes the day off sale and settles every booking on it as a refund, a credit or a kept booking, and emails each family if you ask it to — but nothing in the product reads a forecast, so the decision and its timing are yours. There is no general message tool either: that cancellation mail is the only one bindro sends to a day's visitors, so a change of parking still goes out from your own tool.
- bindro cannot price by weight or by the barrow. A group rate, a per-person add-on and a party price are all real controls now, but pick-your-own sold by the pound is not: nothing reads a scale, and entries and add-ons each have a price you set. Weighing at the gate stays on whatever you use today.
- bindro ships no scanner app. The offline door is an interface — a signed manifest your device downloads over wifi, scans validated on the device with no network, and a replay that uploads them later — and you or an integrator supply the thing that holds a camera. The console can check a visitor in one at a time from any browser, which is enough for a small gate and is not a queue of two hundred cars.
- bindro does not put a wristband on anybody, and does not sell you the bands. What it does is bind one: a band is bound to a visitor from the visitor list in the console or through the API, only its HMAC is stored, and the door then admits that band exactly as it admits a code. A farm not using bands scans the code in the confirmation email and everything else works the same.
- bindro does not sell pick-your-own by weight. Nothing on the platform reads a scale or prices anything per pound: entries and add-ons have a price each, and the till sells items at the price you set them. Weighing the barrow at the gate stays on whatever you use today.
- Money taken at the tills is never paid out to you, because it never left you. The merch till and the food and drink till record what you sold so your numbers are complete, and those takings deliberately never enter the platform ledger — crediting your balance for money bindro never held would pay you for it twice. Cash-recorded entry sales are not implemented at all for the same reason; the gate till takes cards.
- bindro does not remit your sales tax and does not pay it to you. You set a rate per visit, the buyer is charged it on top of the price, and it is held on a remittance account and left out of your payout. Nothing is filed with any state and no return is produced. Treat the rate as a way to show tax on an order, not as a tax service.
- No transfers and no date changes. A visitor who cannot come on Saturday cannot hand their entry to a neighbour or move it to Sunday: this vertical resolves neither ticket transfer nor deferral, and there is no credit note. On a weather-dependent day out that is the request you will get most often, and the only lever is a refund.
- No waiting list. When a slot is gone the page says "Fully booked" and stops — nobody joins a list, nobody is emailed when an entry is refunded, and a refunded entry does not return to sale by itself. If you want to resell it, raise that slot capacity by one.
- No season pass and no autumn membership. A pass that admits all season sits in this vertical optional list, which means the engine refuses it, so "come back any time in October" cannot be sold as one product. A gift card is the nearest real thing — it is stored value, not an entry, and it is redeemed at checkout like any other tender.
- No donation box. A patch raising money for a cause raises it in the entry price: this vertical does not resolve the donation add-on, so there is no "add a donation" control at checkout and nothing issues a receipt for a gift.
- bindro does not pay out mid-season. One visit gets exactly one payout, scheduled only once its last day has ended and released two days later. A whole autumn published as a single visit therefore pays once, in November — publish a visit per weekend if you need the money while the season is still running.
- bindro cannot enforce your refund policy. Every visitor can refund themselves in full from the link in their confirmation email, right up to the moment their slot starts — there is no notice window to configure and no fee to withhold. After the slot has started the decision is yours alone, from the console.
- bindro does not manage your car park, your queue or your access provision. Vehicle registration and access requirements are questions whose answers are stored and shown to you; nothing reserves a space, nothing holds a spot on the tractor and nothing promises a wheelchair-friendly route. Selling parking as an add-on with its own stock is real; directing the cars is yours.

## Questions the landing page answers
- How should a farm split the season so the money does not all arrive in November?
- What actually happens when a family books four entries?
- What does opening Saturday look like, from the lane to the last scan?
- How does bindro sit beside the till and the platform a farm already uses?
- What should a farm read and rehearse before the first Saturday?
  https://bindro.io/vertical/pumpkin-patch-ticketing/

## Pages
- FAQ (24 questions): https://bindro.io/vertical/pumpkin-patch-ticketing/faq/
- bindro vs Square: https://bindro.io/vertical/pumpkin-patch-ticketing/compare/square/ (reviewed 2026-08-09)
- bindro vs Roller: https://bindro.io/vertical/pumpkin-patch-ticketing/compare/roller/ (reviewed 2026-08-09)
- bindro vs Eventbrite: https://bindro.io/vertical/pumpkin-patch-ticketing/compare/eventbrite/ (reviewed 2026-08-09)
- bindro vs FarmSpread: https://bindro.io/vertical/pumpkin-patch-ticketing/compare/farmspread/ (reviewed 2026-08-09)
- Opening a six-weekend season of timed entry without typing 200 slots by hand: https://bindro.io/vertical/pumpkin-patch-ticketing/blog/opening-a-six-weekend-season-of-timed-entry/ (reviewed 2026-08-09)
- What to do when the field is a swamp on Saturday morning: https://bindro.io/vertical/pumpkin-patch-ticketing/blog/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: https://bindro.io/vertical/pumpkin-patch-ticketing/blog/pricing-a-patch-so-the-quiet-weekdays-pay/ (reviewed 2026-08-09)
- Running a farm gate in a field with no signal: https://bindro.io/vertical/pumpkin-patch-ticketing/blog/running-a-gate-in-a-field-with-no-signal/ (reviewed 2026-08-09)