Date and time

Two types collect a point in time: Date (a calendar date) and Date and time (a date plus a time, for booking slots).

Both require the Advance plan or above.

Both support flat fee, percentage of product price and quantity tiers — a fixed charge for supplying a date at all, or a charge that scales with the product’s price or the line quantity.

There is no per-day or per-slot rule, and no formula rule. A formula cannot reference a date because a date is not a number: the expression would fail closed and charge nothing, which looks exactly like it worked. If a rush date should cost more, model that as a separate choice option such as Delivery speed, priced per choice.

What the customer sees

The field uses the browser’s native date picker, which means it is shown in the customer’s own locale format. A shopper in the United States sees 09/29/2026 and one in the United Kingdom sees 29/09/2026 — for the same date.

The value recorded on the order is unambiguous regardless of what the customer saw, so your fulfilment team is never guessing between day and month.

Bounds

Set an earliest and latest date wherever the answer has real-world limits. A delivery date field with no lower bound accepts dates in the past, and that reaches your fulfilment queue as an order you cannot fulfil.

What this is not

Optivo does not check the date against your capacity, blackout days, or existing bookings. It collects a date; it does not manage a calendar. If you need to stop customers booking a full slot, that is a scheduling app’s job.

Worked example

An Event date option, earliest date set to seven days from today, on a made-to-order cake. The customer cannot pick a date you could not bake for, and the date appears on the order line for your kitchen.