# bindro — Christmas attractions and light trails

> bindro sells timed arrival entries for Christmas light trails: every night is cut into arrival slots, each slot holds its own inventory, and a visitor picks a night, picks an arrival time and pays on one phone-sized page. Peak nights and early-bird rungs are separate tiers with their own prices, windows and stock, and the price is derived on the server every time, so a stale page cannot buy a closed rung. The gate scans a wristband or a code with no signal at all. Money reaches the trail two days after the last night of the event it was sold under, never before.

Canonical page: https://bindro.io/vertical/light-trail-ticketing/
Reviewed: 2026-08-09

## Facts
- Inventory model: seasonal nightly.
- Pricing models: flat, tiered, early bird, group rate.
- Fees: 2.5% + $0.99 per paid entry; free nights 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 night sold as a run of dates pays out once, after the final date.
- Check-in: wristband, works offline.
- 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 trail can absorb it or split it per night; 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 operating night. Also tracked: slot utilisation curve, weather-refund rate, parking attach rate. The console computes the north-star figure and prints the arithmetic under it, beside this trail'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 night, live remaining capacity during the night, 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
- bindro will not decide the weather for you. Calling a night off is one control on the night itself — it comes off sale, you choose refund, credit or keep-their-booking, and every entry on that night is settled that way in one action — but nothing watches a forecast and nothing calls it for you. There is no weather provider anywhere in the product, so the decision, and its timing, are yours.
- There is no general message tool. The only mail bindro sends to a night's visitors is the one that goes with calling that night off, and only if you tick the box asking for it: one mail per person, after the money has actually moved, saying what happened to it. There is no "message this night" control for anything else — a change of parking, a late opening — so that still goes out from your own mail tool, off the visitor CSV.
- A part-refund is not a part-cancellation. The bulk settlement applies one policy to the whole night; a goodwill gesture to the family who queued in the rain is still one refund at a time, from the console.
- No season pass. This vertical's configuration lists a season pass among its pricing models, but the capability behind it is not enabled here, so the checkout refuses one and no page offers it. Unlimited-entry passes, resident passes and "come as often as you like" products are not something a trail can sell on bindro this season — a price ladder rung or a gift card is the nearest real thing.
- No transfers and no date changes. A visitor who cannot come on the Friday cannot hand their entry to a neighbour and cannot move it to the Saturday: this vertical resolves neither ticket transfer nor deferral, no name on an entry can be changed after payment, and there is no credit note to issue. The only lever is money out — a refund, and then they book again at whatever price is on sale.
- No donation box and no charity receipts. Many trails raise money for a hospice or an air ambulance; bindro does not resolve the donation add-on for this vertical, so there is no "add a donation" control at checkout, nothing totals gifts separately from entry income, and nothing issues a receipt for one. Charitable giving has to run alongside bindro, not inside it.
- No waiting list. When an arrival slot is full the page says sold out and stops. Nobody joins a list, nobody is emailed when an entry is refunded, and a refunded entry does not return to sale on its own. If you want to resell it, raise that slot's capacity by one.
- bindro does not stop a wristband being used twice. Trails are configured for single entry, but nothing in the engine refuses a second scan: it is recorded and flagged as a conflict for you to read afterwards, whichever gate makes it, and that gate is told the band has already been used to get in. Two devices in a field with no signal cannot agree in real time, so keeping people from walking the trail twice is a rope-and-staff problem.
- There is no bindro scanner app. The door is an API: an offline manifest your gate device downloads before the night, a replay call that reconciles its scans afterwards, a conflicts page to read what disagreed, and an online scan route for a gate that has signal. In the console itself you get a searchable visitor list with a tap-to-admit button and a day-of dashboard. Binding a wristband to a visitor is an API call with no console screen at all, so plan for someone technical before your first night.
- Every place on a multi-entry booking has to be named before the gate will admit it. Buying four entries creates a booking with four places and no names — this vertical asks nothing about each visitor at checkout — and the engine refuses a place nobody has named, on the offline door list and the online scan alike. The booker is emailed a link to fill the names in. A family that ignores that email arrives with entries that do not work.
- Parking is a question, not a controlled product. The vehicle registration box is stored and shown to you; it does not reserve a space, does not price anything and is not checked at the gate. You can sell parking as a paid add-on with its own stock, which is a real limit on how many are sold in total, but nothing caps parking per arrival slot and nothing reads a number plate.
- Money taken on site never enters the platform ledger and is never paid out to you — it is already yours. Mulled wine at the F&B till, hats at the merch till and walk-up card sales at the gate are recorded so your numbers are complete, and cash-recorded entry sales are deliberately not implemented at all: crediting your balance for money bindro never held would pay you for it twice.
- bindro does not pay out mid-season and you cannot choose the schedule. One event gets exactly one payout, scheduled only once its last night has ended and released two days later. A whole season published as a single event therefore pays once, in January. Publish shorter events if you need the money sooner — the pricing guide explains how — because there is no weekly payout option to turn on.
- 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 arrival 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.

## Questions the landing page answers
- Should I publish the whole season as one event, or one event a week?
- What actually happens on the night the fog comes down?
- What has to be in place before opening night?
- Can a trail sell a season pass, or move an entry to another night?
- What can I take with me if I decide bindro is not for us?
  https://bindro.io/vertical/light-trail-ticketing/

## Pages
- FAQ (22 questions): https://bindro.io/vertical/light-trail-ticketing/faq/
- bindro vs Eventbrite: https://bindro.io/vertical/light-trail-ticketing/compare/eventbrite/ (reviewed 2026-08-09)
- bindro vs Roller: https://bindro.io/vertical/light-trail-ticketing/compare/roller/ (reviewed 2026-08-09)
- bindro vs See Tickets: https://bindro.io/vertical/light-trail-ticketing/compare/see-tickets/ (reviewed 2026-08-09)
- bindro vs ACME: https://bindro.io/vertical/light-trail-ticketing/compare/acme/ (reviewed 2026-08-09)
- Opening a six-week light trail season without building 500 slots by hand: https://bindro.io/vertical/light-trail-ticketing/blog/opening-a-six-week-season-without-building-500-slots-by-hand/ (reviewed 2026-08-09)
- What to do when fog closes the trail tonight: https://bindro.io/vertical/light-trail-ticketing/blog/what-to-do-when-fog-closes-the-trail-tonight/ (reviewed 2026-08-09)
- Pricing a light trail season so November pays for December: https://bindro.io/vertical/light-trail-ticketing/blog/pricing-a-light-trail-season-so-november-pays-for-december/ (reviewed 2026-08-09)
- Selling Christmas entries as gifts when nothing can be transferred: https://bindro.io/vertical/light-trail-ticketing/blog/selling-christmas-entries-as-gifts-when-nothing-can-be-transferred/ (reviewed 2026-08-09)