Virtuosos of Price

Fix Your Base Price

PriceLabs is a dynamic pricing tool, not an autonomous revenue manager. It takes the inputs you give it, applies its algorithms, and produces output prices. When those output prices feel wrong, the instinct is to blame the algorithm. In most cases the algorithm is doing exactly what it was told. The problem is what it was told.

The base price is the single number that anchors everything else in PriceLabs. Seasonal adjustments, day-of-week rules, last-minute discounts, and far-out premiums are all calculated as movements relative to that anchor. If the anchor is wrong, every price the tool produces is wrong in the same direction, and no amount of rule-tuning will correct it. Before you touch a single customization, you need to know whether your base price is set correctly and why it is set where it is.

Identifying the Base Price Discrepancy

The first task is to confirm that a base price problem actually exists, rather than assuming it from a handful of bookings that felt cheap or a few nights that did not sell.

What a discrepancy looks like in practice. Open PriceLabs and look at your calendar for a period of at least four weeks that has already passed. Compare the prices PriceLabs recommended against what you actually charged (if you accepted overrides) and against what comparable listings in your area were charging during the same period. If your prices were consistently lower than comparable listings on high-demand nights, or consistently higher on slow nights where you sat vacant while others filled, the base price is a plausible cause. Note the word plausible: other settings can produce the same pattern, so you are building a hypothesis, not a conclusion.

Separate the symptom from the cause. A base price that is too low will produce prices that are too low across the board, but the gap will be most visible on nights where demand is high and PriceLabs is trying to apply a premium. A base price that is too high will produce prices that are too high across the board, but the gap will be most visible on slow nights where the tool's discounts cannot bring the price down far enough to attract bookings.

Checklist: confirming a base price problem

• Pull at least four weeks of historical recommended prices from PriceLabs.
• Record the prices for at least five comparable listings on the same nights.
• Note whether your prices were consistently above or below comparables, and by how much in relative terms (not a dollar figure, but a directional pattern).
• Check whether your minimum price setting is overriding the base price on slow nights. If your minimum is set above what the algorithm wants to charge, the minimum is the problem, not the base price.
• Check whether your maximum price setting is capping the base price on high-demand nights. If your maximum is set below what the algorithm wants to charge, the maximum is the problem, not the base price.
• If neither the minimum nor the maximum is binding and prices are still consistently off, the base price is the most likely culprit.

Decision rule. If the pattern is consistent across multiple night types (weekdays, weekends, shoulder season, peak season) and neither your minimum nor your maximum is binding, treat the base price as the primary variable to investigate. If the pattern only appears on certain night types, look at your day-of-week adjustments and seasonal rules before touching the base price.

Checking Your Property Details in PriceLabs

PriceLabs uses information about your property to calibrate its recommendations. If that information is incomplete or inaccurate, the calibration will be off before you have made a single manual adjustment.

What to check in your property settings. Log into PriceLabs and open the settings for your listing. Work through each of the following fields and verify that the value recorded matches reality.

• Bedroom count. PriceLabs uses this to position your listing relative to others in your market. A studio recorded as a one-bedroom will be compared against a different set of properties.
• Bathroom count. Same logic applies.
• Guest capacity. If your listing sleeps more guests than recorded, PriceLabs may be anchoring your base price against smaller properties.
• Property type. A cabin recorded as an apartment will be compared against a different demand curve.
• Location. Confirm the map pin is placed correctly. A listing placed in the wrong neighborhood or the wrong side of a city boundary can pull in market data that does not reflect your actual competitive set.

Worked example. A host with a three-bedroom house in a lakefront area had their property recorded in PriceLabs as a two-bedroom. The base price recommendation was calibrated against two-bedroom comparables, which in that market were priced meaningfully lower than three-bedroom lakefront properties. Every price the tool produced was anchored too low. The fix was not a rule change. It was correcting the bedroom count, waiting for PriceLabs to recalibrate, and then reviewing the new base price recommendation against the updated comp set.

Checklist: property details audit

• Bedroom count matches your listing on Airbnb.
• Bathroom count matches your listing on Airbnb.
• Guest capacity matches your listing on Airbnb.
• Property type is the most accurate available option, not the closest approximation.
• Map pin location is correct to the neighborhood level.
• Any amenity inputs that affect pricing tiers (pool, hot tub, parking) are recorded accurately.

Decision rule. If any property detail is wrong, correct it before making any other changes. A corrected property record changes the market data PriceLabs pulls for your listing. Any base price adjustment you make before correcting the record is an adjustment to a broken foundation.

Validating Your Comp Set and Market Data

PriceLabs uses a comp set to understand what the market around your listing is doing. The comp set informs the market data that feeds into your base price recommendation. If the comp set is wrong, the market data is wrong, and the base price recommendation built on that data is wrong.

How the comp set works (and what is unknown). PriceLabs allows you to define a custom comp set or to use its automatically generated one. The exact methodology it uses to build the automatic comp set is not fully documented, so treat any assumption about how it selects properties as plausible rather than confirmed. What you can verify is which properties are in your comp set and whether they are genuinely comparable to your listing.

How to audit your comp set. Open the market dashboard for your listing in PriceLabs. Look at the properties included in your comp set. For each one, ask:

• Is this property in the same general area as mine?
• Does it have a similar bedroom and bathroom count?
• Does it serve a similar guest profile (families, couples, business travelers)?
• Is it on the same platform or platforms as my listing?
• Is it currently active, or has it been inactive for an extended period?

Inactive or poorly managed listings in your comp set will drag your market data toward lower prices. Luxury properties included in a budget comp set will drag it toward higher prices. Neither outcome reflects your actual competitive environment.

The table below describes what to record during a comp set audit.

Worked example. A host in a coastal town found that PriceLabs was recommending prices well below what neighboring hosts were charging. On auditing the comp set, she found that it included several listings from a town roughly thirty kilometers away that had a weaker demand profile. Those listings were pulling her market data down. She rebuilt the comp set manually using only properties within a tighter geographic radius and with matching bedroom counts. After the comp set update, the base price recommendation moved upward to a level that was consistent with what she observed in her immediate market.

Decision rule. If more than a small number of your comp set properties fail the comparability checks above, rebuild the comp set manually before adjusting the base price. A base price calibrated against the wrong comparables will need to be recalibrated again once the comp set is corrected.

Adjusting Base Price Inputs vs. Reconfiguring the Tool

Once you have confirmed that your property details are accurate and your comp set is valid, you are in a position to make a deliberate decision about the base price itself. There are two different interventions available, and choosing the wrong one creates new problems.

Adjusting the base price input. The base price is a number you set directly in PriceLabs. You can raise it or lower it. This is the right intervention when the market data and comp set are sound but the recommended base price does not reflect your property's actual position in the market. For example, if your listing has a feature (a private pool, a unique location, a recent renovation) that is not captured in the comp set comparisons, you may need to manually set the base price higher than the tool recommends.

Reconfiguring the tool. Reconfiguration means changing the settings that govern how PriceLabs interprets market data and applies adjustments. This includes things like the aggressiveness of last-minute discounts, the size of far-out premiums, the day-of-week multipliers, and the minimum stay rules. This is the right intervention when the base price is correct but the prices on specific night types are wrong.

Why confusing the two causes problems. If you raise the base price to compensate for a last-minute discount that is too aggressive, you will fix the last-minute price but break the far-out price. If you lower the base price to compensate for a far-out premium that is too high, you will fix the far-out price but break the near-term price. The base price and the adjustment settings need to be calibrated independently.

Checklist: before changing the base price

• Property details are confirmed accurate.
• Comp set has been audited and corrected if necessary.
• You have compared your current base price against the prices of verified comparable listings on a neutral week (not a holiday, not a local event week).
• You have identified whether the problem is consistent across all night types or specific to certain night types.
• If the problem is specific to certain night types, you have ruled out day-of-week adjustments and seasonal rules as the cause.

Worked example. A host with a two-bedroom apartment in a city center found that his far-out prices (more than sixty days ahead) were higher than comparable listings, while his near-term prices (within two weeks) were lower. He initially assumed the base price was too high. On investigation, his far-out premium multiplier was set aggressively high and his last-minute discount was set aggressively deep. The base price itself was reasonable. The fix was reducing the far-out premium and reducing the last-minute discount depth, not touching the base price at all.

Decision rule. If prices are consistently wrong across all time horizons, adjust the base price. If prices are wrong only on specific time horizons or specific day types, adjust the relevant multipliers and rules, not the base price.

Validating Changes Before You Commit

Making a change to the base price and immediately moving on is how errors compound. A change that looks correct in isolation can interact with existing rules in ways that produce new problems.

How to validate a base price change. After making any change to the base price, do the following before accepting it as correct.

• Look at the PriceLabs calendar for the next thirty days and the next ninety days.
• Identify at least three nights you would consider high demand and three you would consider low demand.
• Compare the recommended prices on those nights against the prices of your verified comparable listings.
• Check that your minimum price is not binding on the low-demand nights (if it is, the minimum may need adjustment too).
• Check that your maximum price is not binding on the high-demand nights (if it is, the maximum may need adjustment too).
• If the prices look reasonable across both high and low demand nights, the change is likely sound.

What reasonable means here. Reasonable does not mean identical to comparables. Your listing may justify a premium over some comparables (better amenities, better reviews, better location) or a discount relative to others (fewer amenities, newer listing with fewer reviews). Reasonable means the gap between your prices and your comparables is explainable by real differences between the listings, not by a miscalibrated tool.

Checklist: post-change validation

• Reviewed calendar prices for the next thirty days.
• Reviewed calendar prices for the next ninety days.
• Compared prices on at least three high-demand nights against comparables.
• Compared prices on at least three low-demand nights against comparables.
• Confirmed minimum price is not binding on low-demand nights.
• Confirmed maximum price is not binding on high-demand nights.
• Documented the change made, the date it was made, and the reason for it.

Decision rule. If the post-change prices look reasonable across both high and low demand nights and neither the minimum nor the maximum is binding, accept the change and monitor for the next two to four weeks. If prices still look off after validation, the problem may be in the adjustment rules rather than the base price, and you need to work through those settings separately.

When to Revisit Your Overall Pricing Strategy

Fixing a base price error in PriceLabs is a technical correction. It does not answer the larger question of whether your pricing strategy is suited to your market and your goals. There are circumstances where the base price is technically correct but the strategy it represents is not.

Signs that the strategy needs revisiting, not just the tool. If you have corrected your property details, validated your comp set, and set a base price that aligns with comparables, but you are still not seeing the booking pattern you want, the issue is no longer a PriceLabs configuration problem. It may be a positioning problem, a listing quality problem, or a market timing problem.

Positioning. Your base price reflects where you are trying to sit in the market. If you are priced at the top of your comp set but your listing does not justify that position in the eyes of guests (photos, reviews, amenities, description), you will see impressions without bookings. If you are priced at the bottom of your comp set and filling every night, you may be leaving value on the table. Neither outcome is a PriceLabs problem.

Market timing. Demand in most short-term rental markets is not constant across the year. A base price that is appropriate for your peak season may be too high for your shoulder season, and a base price appropriate for your shoulder season may be too low for peak. PriceLabs handles some of this through seasonal adjustments, but those adjustments work relative to the base price. If the base price is set for the wrong season, the seasonal adjustments will be calibrated incorrectly.

Checklist: strategy review triggers

• You have corrected all property details and comp set issues and the base price still does not produce the booking pattern you want.
• Your occupancy is consistently at the top of your comp set but revenue is not growing proportionally (plausible sign of underpricing).
• Your occupancy is consistently at the bottom of your comp set despite prices that appear comparable (plausible sign of a listing quality issue, not a pricing issue).
• You have not reviewed your overall pricing strategy in more than six months.
• Your market has changed materially (new supply, a major employer arriving or leaving, a change in travel patterns) and your strategy has not been updated to reflect it.

Worked example. A host in a mountain town had a base price that was technically well-calibrated against her comp set. Her occupancy was low. On reviewing her listing, she found that her photos were significantly weaker than those of comparable listings and her review score was lower than most of her comp set. Guests were seeing her listing, comparing it to others, and choosing others. Adjusting the base price downward filled more nights but at a cost that did not reflect the quality of the property. The correct intervention was improving the listing, not repricing it.

Decision rule. If fixing the base price does not produce a meaningful change in your booking pattern within four to six weeks, stop adjusting the price and start auditing the listing itself. Pricing cannot compensate for a listing that guests do not find compelling.

Where this becomes someone else's job

Troubleshooting a base price in PriceLabs is manageable when the problem is isolated. It becomes time-consuming when the problem involves multiple interacting settings, a comp set that needs ongoing maintenance, or a market that changes frequently enough that the base price needs regular review rather than a one-off correction.

Revande offers two products for hosts who want this work handled at a higher level.

Performance gives you a full software stack with dynamic pricing, daily adjustments made by experienced rate strategists, Airbnb listing performance monitoring with email alerts for low visibility or booking conversion issues, and monthly reports. The base price and the settings around it are managed as part of an ongoing process rather than a periodic fix.

Maestro includes everything in Performance, and adds done-for-you listing optimization, proactive Airbnb listing performance monitoring with visibility and booking conversion issues handled for you, compatibility with Airbnb directly or your channel manager, and ongoing listing refinements. If the problem is not just the base price but the listing itself, Maestro addresses both.

If you are spending significant time each month on pricing configuration and still not confident the output is correct, either product removes that work from your plate entirely.

Related articles

• How to audit your PriceLabs comp set
• Minimum and maximum price settings: when they help and when they interfere
• Listing quality and its effect on booking conversion
• Seasonal adjustment rules in PriceLabs: a setup guide
• When to override PriceLabs recommendations manually