OwnerRez adds a child safety field before Airbnb retires its toggles on 1 October

Airbnb is switching off its children and infant safety toggles on 1 October 2026. OwnerRez has added a replacement field, and any host who used those toggles to warn that a property is not suitable for young children needs to move that information across.

The change landed in OwnerRez's 23 September update: a new Airbnb special considerations field for safety information about children and infants, built specifically to replace the deprecated toggles.

What to do before 1 October

Check every listing where the children or infant safety toggles were set, and write the same warning into the new special considerations field.

The update does not say whether existing toggle settings carry across automatically. Until that is confirmed, treat each affected listing as something to check by hand rather than assume the data followed. With the Airbnb deadline this close, a property with an unfenced pool or an open stairwell is the wrong place to discover the warning quietly disappeared.

Why this is more than a field swap

A toggle is structured data. A free text note is not.

A toggle could be read by Airbnb's own systems, which means it could feed filters and warnings a guest sees while browsing. A sentence in a special considerations field is something a guest reads if they get that far down the listing. Hosts who used the toggles as a soft screening tool, steering families with infants away from a property that genuinely is not safe for them, are trading a machine readable signal for prose.

That is Airbnb's decision, not OwnerRez's, and OwnerRez has done the sensible thing by mirroring it rather than leaving hosts with a dead control. But the practical effect for operators is a weaker signal, and it is worth saying so plainly. If a property is unsuitable for infants, the special considerations text is now the only place that lives, so it should be unambiguous.

Also in the 23 September update

Two changes will save time for anyone deep in the admin. The Seasons grid drops its separate Min and Max Nights columns for a single consolidated Rules column. The QuickBooks sync actions grid gains filtering by action, queued date, entity type and property, which makes chasing a stuck sync considerably less tedious.

Among the fixes, three stand out for operators rather than for the changelog completists. Support for Igloo AlgoPin door locks now covers the IGB4A, SK4X and RG1X models, which were missing. Tax calculation errors on Airbnb and Booking.com syncs involving night capped percentage taxes are fixed, so anyone in a jurisdiction that caps a percentage tax after a set number of nights should re-check recent bookings. And security deposit status now reflects collected, partially refunded and fully refunded amounts accurately, having previously been able to misreport them.

There are also fixes for Vrbo listings being blocked for far future dates when idle for more than a day, and for canceled Vrbo bookings not being canceled during an initial channel connection. Both are the kind of quiet problem that costs nights before anyone notices.

The full update sits in the OwnerRez changelog.