FW Rental for WooCommerce – Documentation

Catalogue Pages and the Date Picker

On catalogue and category pages, a rental product shows how long it can be rented for. Once dates have been chosen site-wide, it also shows whether the item is free for those dates and what it would cost. The site-wide date picker is what lets a shopper enter their dates once, before they have settled on a specific product, and have every rental listing answer for those dates.

Placing the Picker

The picker is available in three forms, all named Rental date picker and all identical in behaviour:

• Block — find it in the WooCommerce category of the block inserter.
• Shortcode — paste [fwrental_date_picker] into any page or text area.
• Widget — add it via Appearance > Widgets.

Options

All three forms take the same two options:

• title — a heading displayed above the date fields.
• show_periods — whether to show the shortest and longest rental available anywhere in the shop.

As shortcode attributes:

[fwrental_date_picker]
[fwrental_date_picker title="When do you need it?"]
[fwrental_date_picker show_periods="yes"]

How the Dates Are Shared

Dates entered in the picker are stored in the WooCommerce session. Every rental product in the catalogue reads from that session, so listing and category pages immediately show prices and availability for the chosen period without any further action from the shopper.

Two Deliberate Design Limits

It uses the browser's own date control, not a calendar. The site-wide picker is asking when do you want something, not when is this particular item free. Because no single product's availability applies at that point, there is nothing meaningful to draw in a calendar. The browser's date control handles the input cleanly without implying availability information that does not exist.

It does not appear on single product pages. Once a shopper is viewing a specific product, that product's own rental form is the right control — it shows the product's actual availability in a calendar, highlights booked days, and works out the price in real time. Placing the site-wide picker there as well would duplicate and conflict with that form, so the picker is deliberately suppressed on product pages.