Supply API June Update: Smarter Tax Handling and Faster Settings Sync for Booking.com

Three new Supply API capabilities give property managers and PMS partners finer control over taxes, fees, and channel settings — starting with Booking.com.

June brought three notable upgrades to the NextPax Supply API, all focused on a theme our partners care deeply about: getting taxes, fees, and channel configuration exactly right, with less effort.

Charge VAT on the rent only — not on your cleaning fee

By default, Booking.com applies most percentage-based taxes not just to the room price but also to property fees and charges, such as cleaning or service fees. In many markets that's simply not how the tax works: VAT, for instance, may need to be charged on the rent alone. A new channel setting solves this. With taxes_net_room_price_only ("Tax types not applied to fees" in the dashboard), you list the tax types that should be calculated on the net room price only — for example VAT — and NextPax ensures Booking.com applies them accordingly. All other taxes keep their default behaviour. The result: guest prices that match local tax rules, without workarounds.

Push settings changes to Booking.com without a full content sync

Updated your channel settings or payment preferences? Previously, there was no way to re-export just your channel settings — now there is. The partial content sync for Booking.com gains a settings scope: send a partial update with contentScope: ["settings"] and only your stored channel configuration is re-exported. Images, fees, and policies stay untouched, and scopes can be combined (for example settings plus fees-taxes) when needed. It's a faster, safer way to keep channel configuration in sync.

Fair pricing for families: age-based fees and taxes

Per-person fees and taxes can now vary by guest age. The new ageMultipliers field lets you define age brackets with a multiplier per bracket — infants aged 2 and under free, children aged 3–11 at half price, adults at the full rate, for example. Alongside it, the new amountType field for taxes specifies exactly how a flat tax applies: per night, per stay, per person per night, or per person per stay. Together, these make family-friendly and age-dependent charging structures — common across European markets — natively expressible through the API. Distribution starts with Booking.com, with Vrbo and Marriott support for amountType in progress.

Available now

All three features are live in the Supply API. Full technical documentation, endpoint details, and example requests are available in the NextPax Developers Portal release notes.