DARM 2026 · Atlanta
Panel resources

Parent, child and lock-off units

1 + 1 ≠ 2

A 4BR made of two 2BRs is still a 4BR. It has its own guest, its own booking window and its own comp set. Price each configuration in its own bedroom class, let the calendar do the linking, and judge the whole house.

The one-page playbook

Seven steps, in order. Most problems we see come from skipping the first three.

First, the words

  • Parent: the whole space as one listing, for example the 4BR.
  • Child: a part with its own door, sold as its own listing. Two children can host two parties at once, for example 2BR + 2BR.
  • Lock-off: one space, sold in different sizes. Book any size, even the smallest, and the rest locks. A 3BR sold as a 3BR, 2BR or 1BR: book the 1BR and the other two bedrooms stay locked and unsold. One guest at a time.

The words move. Resorts and timeshares often say "lock-off" for a unit that splits into two self-contained parts, which is what we call a parent and its children. Some software uses "parent and child" for identical units instead. Check what your PMS and pricing tool mean before you set anything up.

  1. Draw the map

    List every listing on the property and the physical space each one uses. Then write down what each booking must close. That table is your block matrix, and everything else depends on it.

    Only a part with its own entrance and facilities can host a second guest at the same time. Anything else is a lock-off: one guest, whatever size they book.

  2. Wire the calendar

    • One source of truth. The PMS owns the blocking, not the pricing tool.
    • Every booking closes exactly the space it uses, no more and no less.
    • Test it: put a block on each listing in turn and check what closes.
    • Watch channel sync. Delays between the PMS and the channels are where double bookings come from.
  3. Match the rules, or break them on purpose

    Match check-in and check-out days, cancellation policy, fees, pets and occupancy across every listing that shares the space. Different by accident is how a guest ends up with a policy you never meant to offer.

    Minimum stay is the one to make different on purpose. It works as a price fence: a lower rate in exchange for a longer stay.

    ListingExample minimumWhy
    4BR parent3 to 4 nightsBig groups often stay longer, and fewer turnovers protect the whole.
    2BR child2 nightsFull rate for short stays. A lower nightly rate only from 4 nights up.
    1BR lock-off1 to 2 nightsFills the midweek gaps the big bookings leave.

    Example settings. Test them against your own length-of-stay data.

  4. Price each configuration in its own bedroom class

    The 4BR competes with other 4BRs. The 2BRs compete with other 2BRs. Give each its own comp set, base price and minimum.

    • Anchor the parent to a full house: what all the parts would earn on that date if every one sold. Price the parent from there.
    • Hold the lock-off: keep it at the price of the space it locks until a set number of days out, then price it as itself.
    • Give each its own calendar: events and holidays on the big ones, weekends in the middle, midweek and last-minute rules on the small one.
  5. Plan by season and booking window

    Season sets the goal: ADR in peak, occupancy off-peak. The booking window tells you who is still shopping. Big configurations tend to book further out. Pricing the whole below has a starting point to test against your own data.

  6. Track the whole house

    Whole-house revenue per available night, each booking counted once. Then the mix of parent and child nights, the booking window for each configuration, turned-away parent demand and cost per stay. Details below.

  7. Change one thing at a time

    Save a baseline, change one rule, and judge it on completed stays against the same dates last year. Decide in advance what result means keep, undo or inconclusive.

Example setups

Three common layouts, the block matrix for each, and where the settings live in PriceLabs and Wheelhouse.

A. Two 2BRs that also sell as a 4BR

A parent and two children. Each half has its own door, so two unrelated parties can stay at once.

When this books4BR (parent)2BR A2BR B
4BRbookedclosescloses
2BR Aclosesbookedstays open
2BR Bclosesstays openbooked

B. A 3BR sold as a 3BR, 2BR or 1BR

A lock-off. One space in three sizes. Whichever size books, even the 1BR, the other two close and the unused bedrooms stay locked. One guest at a time.

When this books3BR2BR1BR
3BRbookedclosescloses
2BRclosesbookedcloses
1BRclosesclosesbooked

Say in the smaller listings that some bedrooms are locked. Guests take a closed door better when they knew about it before booking.

C. Three 3BR floors (the Charleston house)

Each floor has its own entrance. Each floor sold as a 3BR (the child). Two floors made a 6BR (the parent). The whole house was a 9BR (parent prime). And a floor could sell as a 1BR lock-off that kept the rest of that floor locked.

When this books9BR6BR (floors 1+2)Floor 1Floor 2Floor 3
9BRbookedclosesclosesclosescloses
6BR (floors 1+2)closesbookedclosesclosesopen
Floor 1, 2 or 3closescloses if it uses that floorits own floor closes; the others stay open
1BR lock-off on a floorclosescloses if it uses that floorthe whole floor closes, the same as a 3BR

Each extra 6BR pairing adds another row. List only the pairings you actually sell.

Watch the word "parent." In PriceLabs, Map Listings uses Parent Listing and Child Listings, but it is built for identical units in the same location. A mapped child copies the parent's minimum, base and maximum prices, customizations and date-specific overrides. Map a 2BR to a 4BR that way and the 2BR inherits 4BR prices.

PriceLabs

PriceLabs prices each listing. The PMS or channel does the blocking, and we found no setting that ties a combined listing's price to its parts. So set up each configuration as its own listing in its own bedroom class.

  • Group by bedroom class. The Group Creation Wizard can group by Bedroom, or City and Bedroom. The 4BR parent joins your 4BR group. The 2BR children join your 2BR group.
  • Compare against the right homes. Use the bedroom filter in Listing Neighborhood Data, set the Neighborhood Profile Data Source, or build a comp set in Market Dashboards under Create Comp Set.
  • Booking window. Customize Far Out Prices and Customize Last Minute Prices per configuration. A common pattern is a far-out premium on the children in peak so only a strong request takes them early, and a last-minute curve on the children off-peak. Minimum Far Out Pricing sets a separate floor.
  • Minimum stay. Build Min Stay Profiles and apply them through Custom Seasonal Profile. The stay restrictions also include Last minute bookings, Far-out Booking, Orphan Gaps and Check-in / Check-out Restrictions.
  • Gaps. Customize Orphan Day Prices for the price and Orphan Gaps for the minimum stay.
  • Occupancy. Occupancy Based Adjustments per listing, or Portfolio Occupancy Based Adjustment across a group.
  • How far out each listing opens is set in the PMS or channel. We found no PriceLabs setting for it.
  • Reporting. The Combined Listings tab (enabled on request) groups a combo with its parts in Portfolio Analytics. It does not change pricing.

Setting names as of November 2026, checked against each tool's help center. Tools change, so check yours before you rely on a name. Richer Logic is not affiliated with PriceLabs or Wheelhouse.

Pricing the whole against its parts

Two 2BRs at $230 a night make $460 together. Where should the 4BR sit? There is no fixed answer. It moves with the season and the booking window.

A · Below the pair · occupancy play

$420

One booking fills the house: fewer turnovers and no empty half. Use it off-peak, close in, or when one half is hard to sell.

B · Equal to the pair · the neutral start

$460

A guest pays the same either way, so nobody games it. Move off it once you know each configuration's demand.

C · Above the pair · ADR play

$500

Peak and far out, with strong big-group demand or something only the whole has. Comes with a catch (below).

When the halves win

2BR + 2BR > 4BR

Smaller units often earn more per bedroom than big ones. If two 2BRs together outsell the 4BR on a date, let them. Check your market's rates by bedroom count.

A starting point by season and booking window

Far outClose in
Peak · goal ADRAbove the pair. Groups shop early. Keep the 2BRs high enough that the pair never undercuts the whole.At or below the pair. The groups have booked. Price each open half to its own market.
Off-peak · goal occupancyBelow the pair. A group that commits early fills the whole house. Don't block the halves for it.Each to its own market. Last-minute pricing on the halves to fill the gaps.

"Far out" and "close in" should come from your own data: the typical days from booking to arrival for each configuration. Prompt 2 below works them out.

The catch: charge a premium, and some groups book both halves

With the 4BR at $500 and each 2BR at $230, a group of 8 saves $40 a night by booking both 2BRs. It happens less often than you might fear on the OTAs, because a 2BR that sleeps six won't appear in a search for eight. It mostly happens on your own site, or with guests who know the building. Four ways to keep the whole worth booking:

  1. Compare totals, not nightly rates

    Guests pay for the whole stay. Two bookings mean two cleaning fees, which can erase a small nightly premium.

  2. Lift the halves too

    If the 4BR carries a far-out premium, put one on the 2BRs as well, so the pair never undercuts the whole.

  3. Make the whole different

    The connecting door open, shared spaces, one check-in. Only claim what is true for the property.

  4. Watch for it

    Flag the same guest or group booking both halves for the same dates, and review your direct site's search results for groups.

Take the 2BR, or hold for the 4BR?

Put in what you know about the dates. The page estimates the chances from the season, the booking window and your expected occupancy, then compares taking the booking with holding out for the whole. The defaults are the panel's fictional peak weekend. Switch the season to see the answer change.

The stay
The 4BR (the whole)
The 2BRs (the parts)
Chance the 4BR still books0%
Chance the other 2BR sells0%
Take the 2BR
$0
Hold for the 4BR
$0

How the estimate works

Use each listing's own numbers, not the whole-house occupancy, and never add them together: if a 4BR listing sells 30% of nights and the house is 70% full, the 4BR's number is 30%. Prompts 2 and 3 below work both out.

The share you enter, raised for peak (×1.35) and lowered for low season (×0.6), gives the chance a listing books those dates at all. The booking window says how much of that demand is still to come: at the typical window, about half; well beyond it, nearly all; a few days out, very little. The page combines the two, given the dates are still open today. Take = request in hand + the chance the other half sells × its price. Hold = the chance the 4BR books × its price + otherwise both halves selling late at the discount.

It is a rough guide for one decision, not a forecast. Use your own booking windows (prompt 2 below) and revenue after turnover costs if they differ a lot.

Ways to say yes without giving the house away

  • Accept the 2BR at a premium rate.
  • Accept it with a longer minimum stay.
  • Set a decision date: hold until the 4BR's booking window closes, then release.

Track the whole house

Five numbers, every month, for each property that sells more than one way.

MetricHow to work it out
Whole-house RevPARRental revenue from every listing on the property ÷ nights the whole property was available (owner and maintenance blocks out). Count each booking once, on the listing it was booked on.
MixShare of sold nights sold as the parent vs as each child.
Booking window by configurationMedian days from booking to arrival for each listing, by season.
Turned-away demandInquiries or requests for the parent on dates a child had already closed, if your PMS or channels record them.
Cost per stayCleans and turnovers per sold night. More stays can mean less profit.

Busier halves can mean a loss, or a win. Ask before you judge.

  • Costs: revenue up 1% with turnovers up 25% is probably a net loss.
  • Mix: did the children sell nights the parent never would? Then it's a gain.
  • Market: if similar homes fell, flat is a win.
  • Timing: did children book inside the parent's booking window and block groups?
Don't add occupancies together. A 4BR at 50% and two 2BRs at 50% is not 150%. Count the property's nights once, and compare the same months year on year.

One row per booking: property, listing, configuration, bedrooms, booking id, booked date, check-in, nights, rental revenue, channel, turnover cost. The prompts below read this format.

Prompts to check your own setup

Export your reservations in the template's columns and, for prompts 3 and 4, a calendar export with owner and maintenance blocks. Remove guest names, emails and phone numbers. Then paste a prompt into the AI tool you use and fill the [brackets].

Tested. We ran all six in Claude on a fictional two-property export in November 2026 and tightened every line that tripped it up. AI tools still make arithmetic and reading mistakes, so spot-check a few rows by hand and approve every pricing change yourself.

1. Map my setup

I manage short-term rentals where one property sells as more than one listing: a parent listing for the whole space, child listings for parts with their own door, or lock-off listings (smaller listings of the same space with the unused rooms locked).

For each listing below I've given: the spaces it uses (including shared areas), whether it can host a different guest at the same time as each other listing, which listings my PMS blocks today when it books, minimum stay, check-in and check-out days, cancellation policy, all fees, and max guests.

1. Build a block matrix: for each listing, which other listings must close when it is booked.
2. Compare it with what my PMS blocks today. Flag pairs that share space but are not blocked (double-booking risk) and pairs that are blocked but share nothing (lost revenue).
3. List every difference in minimum stay, check-in and check-out days, cancellation, fees and max guests between listings that share space. Ask me which differences are on purpose.

Listings:
[paste here]

What you get back: A block matrix, every risky or wasteful block, and each rule that differs between listings sharing a space.

2. Booking window by configuration

Attached are my reservations, one row per booking (booked date, check-in, listing, property, configuration, bedrooms, status).

Seasons: peak = [months or date ranges], shoulder = [months or date ranges], off-peak = everything else. A stay belongs to the season of its check-in date.

For each listing, within each property, and for each season:
1. Use only stays that checked in before today, and leave out cancelled bookings.
2. Work out days from booking to check-in for each stay.
3. Report the median, the 25th and 75th percentiles, and the number of stays. Flag any cell with fewer than 10 stays.
4. Within each property, tell me which listing books earliest in each season, and by how many days.
Show the table first, then three sentences of findings.

What you get back: A booking-window table by listing and season, and which configuration books first. Use the medians in the calculator above.

3. Whole-house results, counted once

Attached are my reservations and, if I have it, a calendar export with owner and maintenance blocks. Listings belong to properties as follows: [property: listing, listing, listing].

For each property and each completed month, compared with the same month last year:
1. Revenue: split each booking's revenue across its nights, count each booking once (remove duplicates by booking id), and leave out cancelled bookings.
2. Nights available: nights in the month minus owner and maintenance blocks. Blocks created automatically because another listing in the same property booked are not owner blocks. If I gave no blocks, use calendar nights and label it "before blocks".
3. Whole-house RevPAR: revenue divided by nights available. Count each night once per property, never per listing.
4. Mix: for each sold night, record whether the property sold as the whole, as one part, or as several parts at once (a lock-off only ever sells one). Report the share of nights in each.
5. Turnovers, and turnover cost per sold night.
Never add listing occupancies together. Show months that haven't finished as on-the-books against the same date last year, not against last year's final numbers. If a number can't be worked out, say it is missing.

What you get back: Whole-house revenue, RevPAR, mix and turnover cost by month against last year, with nothing counted twice.

4. Hold or release, next 120 days

Attached are my reservations, my calendar for the next 120 days with owner blocks (if I have it), and the booking-window table from earlier. Today is [date]. Location: [city, country]. Events I know about: [list].

1. List the date ranges where the whole is still open, and separately the dates where one part is booked and another is still open.
2. For each range, show days to arrival, the season, and the share of the whole listing's past bookings in that season that were made with fewer days to go than now. Split a range where that share changes a lot.
3. Recommend hold (keep the parts priced to protect the whole) or release (price each open part to its own market), with one line of reasoning.
Group consecutive dates. Flag holidays and events separately for me to decide. If I gave no calendar, say the open dates are inferred from reservations.

What you get back: Every open date range for the next 120 days with a hold or release call and the reason.

5. Design one test

Based on the results above, propose ONE change to test on one property.

My current settings for that property: [base prices, minimum prices, far-out and last-minute settings, minimum stays].

Define:
1. The stay dates the test covers, and that only bookings made after the change count.
2. The baseline: the same stay dates last year, completed stays only.
3. The one setting that changes, with the exact before and after values.
4. The success measure: whole-house RevPAR, with cost per stay as a check.
5. The smallest change in RevPAR this sample can show, and what result means keep, undo or inconclusive, decided now.
6. What must stay the same during the test.

What you get back: A one-page test plan with before and after values and a keep, undo or inconclusive rule set in advance.

6. Check one stay before you accept it

I run a short-term rental that sells as a whole and as parts (for example a 4BR that is also two 2BRs). Help me decide whether to accept a booking request or hold out for the whole, and whether these dates call for an ADR play (protect the whole) or an occupancy play (take the sure booking).

The stay:
- Dates: [check-in to check-out]. Season: [peak / shoulder / low]
- Days until arrival: [number]
- Request in hand: [which listing], $[amount] for the stay
- The whole: [listing], asking $[amount] for the stay
- The other part(s) still open: [listings], asking $[amount] each
- Typical booking window (median days from booking to arrival): whole [days], parts [days]
- Share of this season's nights booked as the whole: [%]. Share of open nights each part books on its own: [%]. (Listing numbers, not whole-house occupancy, and never added together.)
- If I hold and the whole doesn't book, the parts can still sell late at: $[amount] each
- Same dates last year: [what booked, when, at what price, or "unknown"]
- Anything special: [event, holiday, minimum stay rules, turnover cost]

Please:
1. If I attached a calendar or reservations, confirm these dates are still open.
2. Estimate the chance the whole still books if I hold, and the chance the other part sells if I accept. Show how you got each.
3. Compare the expected revenue of accepting vs holding, after turnover costs.
4. Recommend accept, hold, or accept with a condition (premium rate, longer minimum stay, or a decision date), and say whether this is an ADR play or an occupancy play.
5. List the one or two facts that would change your answer.
Keep it short. If anything I gave you looks inconsistent, say so first.

What you get back: Take, hold, or take with a condition, the play it represents, and the math behind it. Use it on any weekend you're unsure about.

The case for and against lock-offs

For

  • Sells nights the big unit leaves empty, often midweek.
  • Reaches different guests: business, solo travelers, couples.
  • Small units often earn more per bedroom.

Against

  • A 1BR booking locks a whole floor.
  • More turnovers and cleaning cost.
  • Guests notice locked doors.
  • Harder to set up and to report.
Worth it when the small unit fills nights the big one would leave empty. Prove it with whole-house RevPAR.

Should the whole's price follow its parts? Link to start, unlink as you learn.

  • Link when a new listing has no data, the units are identical, or nobody has time to manage it.
  • Unlink when the right gap changes by season, booking windows differ, or one part keeps selling out.
  • Middle ground: link by season, one ratio for peak and another for off-peak, checked monthly.

Related levers to consider

Pull one lever at a time, on one property. Set the baseline first, track whole-house RevPAR on completed stays, and report the result before you pull the next one. Prompt 5 above sets up the test.

Price the big one to book early

In peak, price the parent near what its children would earn together instead of adding a premium, and see whether groups book further out.

Hold the small one late

When a small unit closes a big space, hold it at the bigger unit's price until a set number of days out, then price it as itself.

Split the groups

Move the parent into your group for its own bedroom count, and the children into theirs, so each prices against its own market.

Different minimum stays

A longer minimum on the parent in peak and a shorter one on the children in shoulder season, so each sells the stays its guests want.

Fill the weekday gaps

Off-peak, let the children take last-minute weekday stays around a weekend the parent already sold.

Try the whole below the pair

Off-peak, price the 4BR a little under the two 2BRs together and see whether one booking that fills the house beats two you might not get.

Check the comps monthly

Put the parent next to other homes with its bedroom count, and each child next to its own, once a month.