Lorixen.
EN

Pick-your-own farms: timed tickets and daily crop updates

Short answer: Timed entry tickets turn an unpredictable Saturday crowd into a schedule your fields and parking lot can handle, but only if the website answers the questions people ask before they drive out: what's ripe today, what does a ticket include, and what happens if it rains. Most problems come from a handful of avoidable mistakes, from stale crop updates to unclear refund rules. Fix them on the website, mirror them on your Google profile, and weekends get noticeably calmer.

U-pick farms have a problem most businesses would envy: on a sunny weekend at peak season, everyone wants to come at once. The berries, the parking and the staff don't scale. A ticketed booking system solves part of that. The rest is clear communication on the website, updated daily. Here are the mistakes that cause the most trouble, and what to do instead.

Mistake 1: Selling tickets without saying what's actually ripe

A visitor buys a Saturday ticket in the first week of strawberry season, arrives, and finds the rows picked clean by Friday's crowd. That's how one-star reviews get written.

Fix: a crop status page that you update every morning, with a short status for each crop:

  • Picking now / limited / finished for the season / coming soon
  • Which fields or rows are open today
  • A "last updated" date and time at the top, in large text

Link the status page from the ticket page and from the confirmation email. If availability is poor, say so plainly, and offer ticket holders a change of date (see Mistake 5).

Mistake 2: Time slots that don't match how picking works

Slots that are too short leave families rushing; slots that are too long let everyone arrive at opening. Many ticketing tools support multiple timed slots per day. Eventbrite's timed entry feature, for example, is built around creating and selling multiple time slots for an event or experience, and specialist farm and attraction booking tools offer the same idea.

Fix: set slots based on arrival, not duration. A common pattern is arrival windows (for example, 9:00–9:30, 9:30–10:00), with capacity per window based on what your parking and check-in team can handle. State clearly how long visitors may stay once they're in.

Mistake 3: Unclear ticket units

Is a ticket per person, per car, per family, or per container? If the website doesn't say, the entrance becomes a negotiation.

Fix: pick one unit and spell it out on the ticket page, in the checkout and in the confirmation:

  • Per person suits farms with an entry fee plus pay-by-weight picking. Say whether toddlers need a ticket.
  • Per car suits farms where parking is the real constraint.
  • Per container suits farms that sell a set box or bucket. Show the container's size with a photo, and say whether the ticket price includes the fruit.

Whatever you choose, list what's included and what's paid on site.

Mistake 4: No weather plan on the website

Rain, heat or mud will close fields some days. Without a published policy, every closure becomes dozens of individual phone calls and emails.

Fix: write your weather policy once and show it before purchase:

  • Who decides, and by what time (for example, "by 7 a.m. on the day")
  • How ticket holders are told: email or text from the booking system, plus a banner on the website
  • What they get: a transfer to another date, a credit, or a refund, and how long it's valid

Then set up a message template in your booking system so a closure notice goes to every ticket holder for that day in minutes.

Mistake 5: Refusing all changes, or allowing everything

A strict no-changes rule angers people when the crop is thin; unlimited free changes encourage speculative bookings that block real visitors.

Fix: allow free date changes up to a cut-off (say, the evening before) and automatic transfers when you close or the crop is poor. Many booking tools let customers reschedule through a link in their confirmation; turn that on if available, so changes don't land in your inbox.

Mistake 6: Forgetting Google

Many visitors never reach your website. They search the farm's name, see your Google Business Profile and drive.

Fix: keep the profile in line with the website:

  • Special hours. Google's help page on special hours explains how to set temporary hours or closures, for holidays, special events or other exceptional circumstances, without changing your regular hours. It says special hours cover a business that adjusts hours or closes for up to 6 days in a row. Use it for weather closures and short-season openings.
  • Posts. Google's guide to posts on your Business Profile describes posting updates with text, photos or videos that show in the Updates or Overview tabs on mobile. A quick "Blueberries open this weekend" post with a field photo helps.
  • Ticket link. Put your booking page as the website or booking link so people book rather than turn up.

Mistake 7: A mobile ticket page that's slow in the field

People often check tickets in your parking lot on one bar of signal.

Fix: keep the confirmation email short with the essentials at the top: date, arrival window, number of tickets, a scannable code, and a link to directions. Tell visitors to screenshot it before leaving home. At check-in, have a list or app view that works offline if your system offers one.

Mistake 8: Not capturing anything for next season

Season ends, the booking system goes quiet, and next year you start from zero.

Fix: ask in the booking form whether visitors want a "crop is ripe" email or text for next season, separately for each crop if you grow several. Next year, one message on opening day fills the first weekends.

A simple daily routine in season

  1. Walk the fields early and decide each crop's status.
  2. Update the crop page and its "last updated" time.
  3. Post on Google and social media if anything changed.
  4. Check today's ticket numbers against field capacity; close slots if needed.
  5. If closing, send the closure message and set special hours.

FAQ

Should u-pick farms require tickets at all?

Not always. Timed tickets help farms that get overcrowded at peak times; quiet farms may do fine with walk-ups plus a crop update page.

Per person or per car?

Choose the unit that matches your bottleneck: field space suggests per person, parking suggests per car.

How often should the crop page be updated?

Daily during the season, every morning before tickets for that day are used.

What's the best way to tell visitors about a closure?

A message from the booking system to that day's ticket holders, plus a website banner and Google special hours.

Getting ready for next picking season and want ticketing and crop updates that run themselves? Tell us about your farm.

Sources

WhatsAppLet’s talk