How Gatemi Delivery Slots Works

Three rules govern the plugin. The first and third are in both editions; the second is about time slots, which are the full edition's.

Rule 1: a day that is offered must still be there when the order is placed

The checkout field shows the days the calendar offers when the page was drawn. A shopper can leave the checkout open for an hour — across the cutoff, or past midnight. So when the order is placed, the chosen day is checked again against the same calendar, worked out at that moment:

  • still offered: the order goes through;
  • no longer offered: the order is refused with "That delivery date is no longer available. Please choose another." and the shopper picks again.

On the classic checkout this check runs before the order is created. On the Checkout block it runs through WooCommerce's own validation of the field, and the day is only saved onto the order if it is still offered. The browser's copy of the list is never trusted: a date edited into the form by hand is refused the same way.

Rule 2: capacity is claimed, never counted — Full edition

A time slot that holds twenty deliveries has exactly one twentieth place. Two shoppers pressing Place order in the same second must not both get it. A plugin that counts the bookings, checks the count is under the limit, and then writes a booking loses that race on a busy Saturday morning.

Here the booking is one database statement: it inserts the booking row only if the number of bookings for that day and slot, counted inside the same statement, is still below the limit. If the statement wrote no row, the slot was full at that instant, and the order is refused with "That delivery time has just been taken. Please choose another." An order taken with nowhere to put it is exactly what the plugin exists to prevent.

The bookings table has one row per order (UNIQUE on the order id), so an order cannot hold two places.

When an order is cancelled or refunded, its row is deleted and the place is free again. A slot with a limit of 0 has no limit; it is never full.

On the classic checkout WooCommerce gives a brand-new order its id only after it saves it, so the day and time are written onto the order first and the place is claimed the moment the order has an id; a refusal then deletes the unpaid order WooCommerce had just saved. On the Checkout block the order already has an id. A retried payment resumes the same order, which keeps the place it already holds.

Rule 3: the clock is the warehouse's

Every date is worked out in your site's time zone, not the shopper's.

  1. Start day. Today — unless today is not a delivery day, or it is at or after the cutoff, in which case the next delivery day.
  2. First day offered. The start day plus Notice you need delivery days, skipping days you do not deliver and days you are closed.
  3. Last day offered. The first day plus How far ahead they may book calendar days.
  4. Offered: every delivery day between the two that is not a closed day.

The cutoff moves the start, not the end. A cutoff nobody can parse is treated as not passed — the safe direction is the later day. A closed day nobody can parse is dropped, rather than kept as a day the calendar would silently treat as open.

A worked example

Delivery days Monday to Friday, cutoff 14:00, notice 1 day, window 21 days.

Shopper at the checkout Start day First day offered
Tuesday 10:00 Tuesday Wednesday
Tuesday 15:00 Wednesday Thursday
Saturday 09:00 Monday Tuesday

Time slots on a day — Full edition

A slot is offered on a day when it is Offered, it runs on that weekday (or has no days ticked), and it is not full for that day.

On the classic checkout, every time is in the page with the days it runs on, and a small script hides the times that do not run on the chosen day — no extra request. That is a hint only: the server decides again when the order is placed, and a time that does not run on the chosen day is refused. On the Checkout block, the time list holds every time that runs on any offered day; a time that does not run on the chosen day is refused when the order is placed.

What is saved on the order

Meta key What
_gmds_date The day, as 2026-03-18. Both editions.
_gmds_slot The slot id. Full edition.
_gmds_label The slot's label as it was shown, e.g. "Morning". Full edition.

The label is stored beside the id so renaming a slot next month does not change what a past order says was agreed. The day and time show on the order confirmation page, My Account → Orders, the order emails (HTML and plain text) and — full edition — the Delivery box on the order screen.

The free edition and booked slots

The free edition offers a day only. If the full edition booked an order into a time slot, the free edition still shows that time on the order, from _gmds_label: it is a record of what the customer was promised, not a setting. Upgrading turns time slots on with nothing to re-enter.

Shopping Cart
Scroll to Top