Campground Midweek Packages Without a Revenue Manager

Paste three cards. Stop inventing a yield desk.

Local Tue–Thu 2 nights · Mon–Thu arrival only · ZIP or town ID at check-in · firewood bundle included · not valid Fri–Sat or named holidays

Quiet Week Sun or Mon arrival · 4 nights · 5th night free · shoulder months only · no OTA code stacking

Stay & Play 2 midweek nights on a 30-amp or pull-through · partner day-pass or boat hour from the marina next door · book on the guest site, same words on the phone

A midweek campground package must be a named product with nights, fences, and usually one add-on — not a public 10% off and not a revenue-manager dashboard. Write two or three packages once. The calendar enforces the nights. The guest site sells the SKU. Saturday still costs Saturday.

TL;DR

  • Public systems already sell “come midweek.” South Dakota GFP pushes quieter Mon–Thu stays and rewards a 2-night weekday block. California State Parks tell guests midweek is easier to book.
  • Private parks ship packages as products: Indian Creek weekly includes a free night and blocks further discounting; Lagoon is pay-6-get-7 plus park tickets; Beachcomber names a midweek 5th-night-free escape on listed dates.
  • Campland fences a resident 20% behind City of San Diego ID. That is a who-fence, not a billboard cut.
  • Hotels call the mechanism rate fencing. At a park it is who, which nights, how long, and what is bundled.

What is a midweek package at a campground?

A midweek package is a bookable product for slow nights. It has a name, eligible dates, a length-of-stay shape, and often one included add-on. It is not a sticky note that says “ask about Tuesday.”

A rate is a number on a night. A length-of-stay rule decides whether Friday can sell alone. A package ties nights together and tells the guest what they get. Confuse the three and the office invents a fourth price at the gate.

At a 40 to 80 site park the empty inventory is usually Tuesday through Thursday on a back-in or 30-amp, sometimes a pull-through that will not sell until Friday. The package’s job is to make those nights a trip, not a coupon.

ObjectJob
Weekday rateWhat one night costs
LOS fenceWhich nights can sell alone
PackageNamed trip for slow nights
DepositMoney if they cancel

If your “package” is only a lower number with no nights and no name, it is a discount wearing a costume.

Why do packages beat a public midweek rate cut?

Because a bare cut trains the people who already book you, and it leaks onto nights that did not need help. A package makes the guest accept a trade: slower nights, a longer stay, an ID check, or a fixed add-on.

Hotels write this as rate fences: conditions so the guest who would pay full price cannot grab the cheap path. Smartness splits physical fences (what is included) from non-physical ones (when, how long, who, how flexible). A park needs the same clarity without a corporate RM team.

Public parks already market the midweek trip as a different product. South Dakota sells quieter loops, open water, and a 2-night Mon–Thu reward. California tells people midweek is when the reservation opens up. Guests know the shape. You are not inventing culture. You are naming the product your empty pads already are.

Deals without ADR damage covered membership and weekday coupons. Keep those fences. Packages go one step further: the guest buys a trip card, not a secret percentage.

What fences does a package need so Saturday stays expensive?

A package needs four fences written once: who can buy it, which nights it covers, how long the stay must be, and what is bundled. If any fence is missing, the midweek deal becomes the new rack rate and Saturday inherits Tuesday’s price.

  1. Who. Resident ZIP, returning guest list, military/first responder ID, or “book direct only.” Campland wants City of San Diego ID for the 20% resident path. Beachcomber runs a Hometown Hero special on ID. No ID, no fence.
  1. Which nights. Mon–Thu arrival, or Sun–Thu only. Named shoulder months. Black out the holiday blocks you already protect with a weekend LOS rule.
  1. How long. 2-night midweek minimum, or 4 nights with a free 5th, or weekly 6-for-7. Indian Creek makes weekly the biggest discount and blocks stacking. Lagoon is pay six consecutive, seventh free. Keeprstay vendor copy says the same 6-for-7 shape. Treat that as pattern, not a census.
  1. What is bundled. Firewood, bag of ice, kayak hour, partner day-pass, late checkout on a Thursday. Bundle something you already control or can voucher. Do not promise a third-party tour you cannot rebook when it rains.
FenceWeak versionStrong version
Who“Locals welcome”ZIP list or ID at check-in
Nights“Weekday deal”Mon–Thu; holidays excluded by date
Length“Stay longer”2-night min or 6-for-7 written
Bundle“Ask the office”Named add-on on the confirmation

KOA’s Stay 3 / 4 / 5 Nights and Save is a length fence at chain scale: availability, possible LOS rules, blackouts, and often no stacking with other discounts. Copy the discipline, not the franchise paperwork.

Which three packages can a small park run without a revenue manager?

Three packages are enough for a 40 to 80 site park with no revenue manager: a local 2-night midweek, a free-night quiet week, and one optional stay-and-play with a single partner. More than five and the office freestyles again. Pick from this menu and delete the rest.

1. Local midweek (2 nights)

Arrival Monday through Thursday. Two nights. Resident or in-county ID. One cheap bundle (firewood, s’mores kit, dump fee waived). Not valid Friday, Saturday, or named holidays.

This is the empty-pad product for people who already drive past your sign. Campland proves guests accept an ID fence when the perk is clear. Your version can be smaller and still real.

2. Quiet week / free-night shape (4–7 nights)

Shoulder months only. Sun or Mon start. Four nights with fifth free, or six paid with seventh free. No stacking with club codes. Cabins can use a tighter version than pads.

Beachcomber publishes a Midweek Super Saver Escape on listed spring/fall dates with a free 5th night, plus a separate 7th-night-free after six consecutive nights. Indian Creek and Lagoon both sell weekly as a free-night product. Guests already understand “stay longer, night free.” You do not need software to count to seven.

3. Stay & play with one local partner

Two midweek nights plus one external value: marina hour, museum pass, brewery flight, trail shuttle, mini-golf. You sell the stay. The partner honors a simple voucher code or stamped card. Settlement is a monthly invoice or a stack of prepaid passes — not a dynamic commission engine.

Lagoon is the clean extreme: camp next to the amusement park and buy discounted park passports as a camper. Most independents will not own a theme park. One partner is enough. One. If the partner flakes, the stay package still has to book without them.

PackageNightsWhoBundleKill switch
Local midweek2ID / ZIPWood or dumpHolidays + Fri/Sat
Quiet week4–7Anyone directFree nightPeak Jul weekends
Stay & play2–3Anyone directPartner passPartner out of stock

Do not build a fourth package called “dynamic.” If July Fridays sell out, your LOS fence already did the hard job.

How do you work with local partners without a sales team?

Work a partner package with one page, one contact, and one redemption rule. If it needs a joint P&L or a custom app, you do not have a midweek product. You have a project that will still be open in October.

  1. Pick a partner guests already drive to from your gate: marina, outfitter, brewery, museum, golf, ice cream, bike rental.
  2. Agree on a fixed voucher: “one free hour,” “two admissions,” “$20 credit.” Not “up to 25% subject to availability.”
  3. Cap inventory. Twenty vouchers a month beats unlimited promises.
  4. Redemption is a code or a printed card the partner can train a teenager on.
  5. You collect the stay money. Partner is paid on redeemed vouchers monthly, or you buy a block of passes up front.
  6. Write the rain rule. If the boat does not run, the stay still stands and the voucher extends 30 days or converts to firewood. Put that sentence on the confirmation.

Skip revenue share on gross stay. That is how you spend August reconciling. Skip exclusive contracts. You want a product for slow Tuesdays, not a tourism board marriage.

If you cannot name the partner in one breath, sell Local midweek and Quiet week first. Partner packages are optional spice, not the spine.

Where does the package have to live to actually sell?

In the booking engine as a real rate plan or package SKU, on the guest site as a bookable card, and in the mouth of whoever answers the phone. A PDF in the office drawer is a wish.

This is the markdown config argument with a product name on it. One text. Eligible nights. Bundle line. Blackout dates. The guest site has to finish the reservation without a call-back to “confirm the special.” The voice path recites the same three packages, including the ID fence, instead of inventing a courtesy rate.

Enforceable means:

  1. The package is visible before pay, on dates it applies.
  2. Friday–Saturday peak rates do not inherit the midweek package price.
  3. OTA listings either map the same fences or do not carry the package. A Hipcamp hole that sells “Local midweek” without the ID check is not distribution. It is a leak.
  4. Staff override exists for a true dead week, and it writes the calendar. A verbal “just this once” that never hits the grid trains regulars.
  5. Confirmation email repeats the package name, nights, and bundle. Guests screenshot that, not your Facebook post.

Lunaria Booking keeps package rules in the property markdown the guest site and the voice path both read, then lets the calendar only offer those nights under that product. If your current PMS can already attach a rate plan to Mon–Thu with a min stay and a note field for the bundle, use it. The product is one named trip, not a new speech every Tuesday.

What package mistakes empty the wrong nights?

Five package mistakes empty the wrong nights: a billboard percent off, a deal that still works on Friday, unlimited code stacking, a partner you cannot fulfill, and a phone path that undersells the site. Each one turns a product into a hole.

  1. Billboard percent off. “10% off all week” is not a package. It is the failure mode in the deals post.
  2. Package valid on Friday. Then you discounted peak. Kill switch missing.
  3. Stacking everything. Weekly free night plus Good Sam plus local plus Facebook code. Indian Creek blocks further discounting on weekly for a reason.
  4. Partner you cannot fulfill. Sold twenty jet-ski hours. Marina has three. Now you are a complaint desk.
  5. Phone says yes, site says no. Guests learn the cheap door. Same package, every channel, or do not put it on that channel.

A softer failure: twelve packages. Nobody on staff can recite them. Three cards beat a menu.

What should you do this week?

Do not build a revenue-management spreadsheet this week. Publish two packages and one blackout list, then put both on the guest site.

  1. Pull last July and last October. Count empty Tue–Thu pad-nights on your main loop. That count is the case for a package. Worksheet, not a consultant.
  1. Write Local midweek in plain English. Two nights, Mon–Thu, who-fence, one bundle, holidays excluded by date.
  1. Write Quiet week or 6-for-7 for shoulder months only. Copy the free-night shape guests already see at Lagoon and Beachcomber.
  1. Optional: call one partner you already send guests to. Fixed voucher, monthly settle, rain rule. If they need a week to “run it by corporate,” skip and ship the first two packages.
  1. Put both packages on the guest checkout and in the confirmation template. “See specials” is how people book the wrong nights on the phone.
  1. Audit one OTA listing this afternoon. If it can sell your midweek price on a Saturday in July, close that path or map the fence.
  1. Teach the phone script as three sentences: name, nights, fence. Same sentences the site shows.

If the calendar cannot restrict the package to Mon–Thu, stop decorating the homepage. Fix the rate plan. A package that only lives on a sandwich board will lose to whoever answers after dark and wants to be nice.

FAQ

Do I need revenue-management software to sell packages?

No. You need named nights, a min stay or free-night shape, and a bookable SKU. Software can help later. It is not the prerequisite. Public parks and small private parks already sell midweek products with rules, not black-box yield.

Is a weekly rate a package?

Yes if it is a real product with a free-night or flat week price and a no-stack rule. Indian Creek treats weekly as the biggest discount and blocks further codes. A “weekly” that is just seven times the Saturday rate is not a package.

Should the package include Friday to get people in?

Almost never in peak season. Friday is the scarce attach night. Use the weekend LOS fence for that job. Packages own the soft nights.

What if locals never show ID?

Then the who-fence is theater. Require ID at check-in the same way Campland does for the resident rate, or switch the fence to direct-book only and a returning-guest list you control.

Can I put packages only on the guest site and not on Hipcamp?

Yes. That is a channel fence. Keep the same nights and price integrity on every door that carries it. Different doors can omit the package. They should not sell a looser version of it.

How many packages before guests get confused?

Two live, three max. A fourth belongs in the freezer until one of the first three earns its keep for a full shoulder season.

Does Lunaria Booking invent my packages?

It keeps one copy. You write the package name, nights, fences, and bundle in the property markdown. The guest site can offer only those nights under that product. The voice path can sell the same card. It will not invent a partner voucher you never typed.

---

Guests already understand midweek trips, free-night weeks, and ID-fenced local rates. They buy them on public calendars and private specials pages. What they will not accept is a surprise price at the gate, or a Facebook percent that also hits Saturday. Name the product, fence the nights, put it in the engine, and let Tuesday become a trip instead of a problem.

← All posts
Home Products Demo Blog Register The Problem Try the demos AI Assistant Plans About Get started