Dynamic Pricing for Campgrounds That Isn't Airline Nonsense

Saturday in July is gone by Tuesday. The 50-amp pull-throughs went first. A Tuesday in October is half empty at the same $55 you charged the holiday weekend. Someone forwards a hotel revenue-management demo and says you need “real dynamic pricing.” That usually means a black box that would price site 14 like seat 14A.

Dynamic pricing works at a 40–80 site park only when it is a short list of rules you can say at the gate: weekend versus weekday, holiday versus not, pull-through versus back-in, pets, length-of-stay. Occupancy sliders and airline-style fare engines come later, if ever. If the PMS cannot enforce the rule on the guest site and the phone, it is not a rate strategy.

TL;DR - Start with a ladder, not an algorithm. Keepr’s campground guide goes seasonal, then weekend, then events, then occupancy last. - Guests already know the demand shape. California State Parks says midweek is easier and names a shoulder season. - Protect Saturday with rate and stay rules (LOS playbook). Do not cut Friday to fill Wednesday (shoulder-night post). - Occupancy automation exists. Even the vendors selling it say owners did not want a black box. - A small park can start on a spreadsheet (Campground Accounting). Software only helps if it can actually apply the rule. - Related: property-type booking strategy.

What dynamic pricing actually works at a 40–80 site park?

Dynamic pricing that works at a 40–80 site park is humble yield: written differences between nights and site types that a guest, a seasonal clerk, and the booking engine can all apply the same way. It is not a fare that rewrites itself every time someone in Ohio searches.

Keepr’s operator guide is useful because it refuses to start at the fancy end. Their ladder is seasonal rates, then day-of-week, then local events and holidays, then occupancy automation (dynamic pricing guide). Campground Accounting says the same starter move in accountant English: cheaper slow weekdays, dearer weekends and holidays, and a metric that is site revenue over available site-nights, not vanity ADR (dynamic pricing for RV parks).

For an independent, that looks like this:

You are not under-pricing because you lack a revenue scientist. You are under-pricing because Saturday and Tuesday share a Sharpie number.

Why does airline-style yield fail on irregular sites?

Airline-style yield fails on irregular sites because a 40-foot 50-amp pull-through is not interchangeable with a 30-amp back-in under the oak, and a black box that treats them like seats will lie to the guest or leave the wrong pad empty.

Hotels and airlines optimize a pile of near-clones. You sell constraints: length, hookup, pets, slide-outs, river view, “that one site the big fifth-wheels actually fit.” Parks are not hotel room nights (property-type strategy).

What breaks when you import the airline story:

• The guest cannot explain the price. “It went up because someone in a dashboard blinked” does not survive the Facebook group.
• Staff cannot explain the price. Seasonal help will override until the rule is fake.
• The phone and the website disagree. After hours that is a fight at the gate, not a clever yield win (after-hours booking).
• The wrong site sells. A cheap tent pad does not substitute for the last 50-amp pull-through on Friday.

Demand shape is not a secret. Public parks already tell visitors midweek is easier and name April, May, September, and October as shoulder months (CA Parks camping tips). Your job is to price that shape, not to pretend you have a 200-room forecast model.

Even vendors building occupancy tools are reacting to the same allergy. RoverPass’s occupancy feature is sold as visible, configurable rules — presets or up to ten tiers, percent or dollars, scoped to a rate, a site type, or the whole park — because their CEO said owners wanted smarter pricing without handing control to a black box (Modern Campground report). CampLife’s public pitch is four occupancy levels, not a mystery fare (CampLife dynamic pricing). If the people selling automation lead with “you can see the rule,” believe that part.

Which rate rules should you encode first?

Encode first the rules you already argue about at the window: season, weekend, holiday, site type, pets, and length-of-stay. Those five or six lines move more money than an occupancy slider on a park that still has one nightly rate.

Keepr’s published examples are examples, not a national tariff. Treat them as a shape, then write your own dollars:

Source for the shape: Keepr dynamic pricing. They also warn that a $45 October night jumping to $120 in July feels arbitrary, and they prefer roughly 20–30% steps. That is taste, not physics. The useful test is: would you say it out loud to a regular?

Stay rules are rate rules. A Saturday-only at the cheap number can block a two-night weekend. Peak weekends often want a 2-night minimum. Weekdays often want none (minimum stay guide). If you raise Saturday and still allow a one-night that orphans Friday, you did half the job.

Pets, extra vehicles, and extra adults belong on the same card. They are not “fees we remember if someone looks like a dog person.” They are inventory costs. If the guest site cannot add a pet fee, the phone will invent one.

Write the stack in one place the office grid and the booking widget both read (markdown config). A rate that only exists in last year’s Word doc is a rumor.

When is occupancy-based pricing worth turning on?

Occupancy-based pricing is worth turning on after the calendar rules are live, staff can explain them, and you still have a repeatable pattern: the last ten 50-amp sites on a sold Saturday are underpriced, or a dead Tuesday never moves. It is not worth turning on to hide the fact that you never set a weekend rate.

The product category is real. CampLife documents up to four occupancy levels (CampLife). RoverPass documents presets plus up to ten tiers and a visible timeline (Modern Campground). Those are vendor capabilities, not a homework assignment for a 60-site family park.

A fair test before you flip a slider:

1. Season, weekend, holiday, and site-type rates already publish on the guest site.
2. Phone and web quote the same number for the same pull-through.
3. You can name the occupancy scope. Whole park is a blunt instrument. Last three river sites filling should not raise the empty tent loop.
4. You have a floor (do not go below what the night costs you) and a ceiling (do not look like a gouge to the regulars).
5. Confirmed reservations lock. Keepr is explicit: once they book, the rate does not move (Keepr).

If those five fail, the slider will amplify the mess. If they pass, occupancy is just another written rule: “when this site type is over X booked, add $Y.” That is still humble yield. The airline version is a model nobody on payroll can audit.

You do not need enterprise software to start. Campground Accounting’s starter kit is twelve months of occupancy by day of week and site type, a floor rate, three or four tiers, and a monthly review. They say a spreadsheet is enough for a small park (their framework). Believe the small-park part.

How do you keep guests from feeling gouged?

You keep guests from feeling gouged by making the price look like the calendar they already understand, locking it at booking, and never training them that the real number is the panic discount.

People accept July 4 costing more than a Tuesday in October. They do not accept the same pull-through changing $40 between breakfast and lunch with no story. Keepr’s public advice is to say rates vary by season, day, and demand, to sell weeknights as the value nights, and to lock the booked rate (communication section). Campground Accounting’s warning is the same: swings that feel arbitrary backfire (mistakes list).

Practical fences:

• Publish a weekend rate and a midweek rate. Do not hide Saturday behind “call us.”
• Name holiday weeks on the site.
• Keep steps explainable. A regular should not need a screenshot archive.
• Put the pet fee and hookup difference on the quote, not in the fine print after they arrive.
• Do not run a season-long “10% off weekdays” that becomes the real BAR. Fence the deal or skip it. That is the next essay. For now: shoulder nights are rules and channels, not a public fire sale.

If Facebook is where your rate card actually lives, you do not have dynamic pricing. You have an argument.

What should the PMS actually enforce?

The PMS should enforce every rule you are willing to argue about: which nights cost more, which site types cost more, which stays are allowed, which fees attach, and whether the quoted total is the total the guest pays. If a human has to re-type the rate, you do not have a strategy. You have overtime.

Minimum the engine must do:

If your current tool can only store one nightly number plus a sticky note, the upgrade is “rules the calendar understands,” not “AI that guesses what Ohio will pay.” Readable property truth is how independents keep weekend mins, weekday one-nights, and pet fees from forking into three stories (why config belongs in markdown).

Lunaria Booking’s bias for this ICP: those rules live in the same markdown the guest site and the voice path read. We will not pretend that is an airline revenue-management suite. Judge the product on whether a Friday 50-amp, two dogs, two-night holiday weekend prices the way you wrote it.

What should you do this week?

This week, write the rate card you already believe, put it in the system, and mystery-shop your own Saturday versus Tuesday quote. Do not buy a yield module to avoid that conversation.

1. Export last season by day of week and site type, not just monthly occupancy. You need Saturday 50-amp versus Tuesday tent.
2. Write four numbers: midweek base, Friday, Saturday, holiday weekend. Caps if you want them.
3. Price the scarce pads: 50-amp pull-through, full hookup, anything waterfront or extra long.
4. Attach stay rules to those dollars: peak Fri–Sat minimum, midweek one-nights, holiday 3 if you actually fill it (LOS guide).
5. Put pets and extra vehicles on the quote path.
6. Publish a one-sentence rate note on the guest site: season, weekend, holidays. Lock booked rates.
7. Call your own park as a 38-foot, 50-amp, two-dog Friday arrival. Then book the same stay on the website. If the totals differ, you do not have dynamic pricing. You have a leak.

A spreadsheet is a legal week-one home (Campground Accounting). Move the rules into the PMS when you are tired of typing them twice. Occupancy sliders wait until those quotes match.

FAQ

Is a weekend premium the same as dynamic pricing?

It is the part that actually works at a small park. Seasonal plus weekend plus holiday is already dynamic pricing. Occupancy automation is an optional later layer, not the definition. If Saturday and Tuesday still share one number, you are not “waiting for software.” You have not started.

Should Tuesday drop automatically when occupancy is low?

Not automatically, not all year, and not on the public Saturday widget. A named gap this week can get a fenced offer. A standing slider that cheapens every slow Tuesday will teach regulars to wait, then they will ask for the same number on Friday. Fill midweek with stay rules and who you sell to first (shoulder playbook).

How big should the gap be between weekday and Saturday?

Big enough that Saturday still feels like Saturday, small enough you can say it without wincing. Keepr’s published weekend shape is roughly 15–30% above base, and they dislike giant seasonal jumps (their guide). Use that as a starting sketch. Your sold-out Saturdays and empty Tuesdays are the real data.

Do I need a revenue manager?

No. You need a written card, twelve months of day-of-week occupancy, and a PMS or sheet that applies it. Campground Accounting’s small-park version is tiers plus a monthly review, not a hotel RM desk (their framework). Hire help when you have multiple parks or you are ignoring your own rules.

What about weekly and monthly rates?

They are stay products, not a coupon on Saturday. Weekly and monthly guests expect a volume price. Keepr cites 6-nights-for-7 and a sizable monthly discount off nightly as common shapes (Keepr). Fence them so a Friday-Saturday holiday cannot be built out of the monthly number.

Will guests revolt if Saturday costs more?

They revolt when the number feels random or when last week’s screenshot is cheaper for the same holiday. They already know midweek is easier because public systems say so (CA Parks). Explain season and weekend, lock the booked rate, and keep the steps boring.

Where does Lunaria Booking fit?

As the independent-park path where season, weekend, site type, pets, and stay rules live in readable property truth and price the same on the guest site and the phone. We are not selling a black-box fare engine. If a Friday 50-amp pull-through with two dogs does not price the way you wrote, the config is wrong, not the guest.

---

Airline software is a story parks get sold when they are tired of one nightly rate. The fix is uglier and better: write the differences you already believe, make the PMS enforce them, and keep Saturday expensive on purpose.