Advanced order schedule
Advanced order schedule has no stable numeric category ID or fixed form schema in current client source. Dashboard consumes a project-returned Pro category under /all-settings; do not open or deep-link it for documentation. Current API source catalogs pro_preorder under key_pro, but this source catalog is not proof of a deployed category, ID, values, or validation behavior.
The preserved reference capture records Enable Preorder Feature and Set Maximum Preorder Days labels from its audited fixture. Current API source associates preorder_status_enabled with pro_preorder and makes max_days_preorder dependent on that key having value 1; current Dashboard source renders returned configs dynamically. These fixed-source associations do not establish a deployed form, numeric ID, configured values, units, validation outcomes, or customer/order effects.
Before sequential save, fixed client source blocks a staged max_days_preorder value below 1. It does not establish integer-only validation, API acceptance, deployed units or effects, or successful slot availability.
Potential consumers include Business/menu schedules, timezone, order availability, and customer checkout. These are effect classes only; no business, menu, schedule, order, customer, or timezone state was read.
The shared editor saves changed configurations sequentially, so later failure can follow earlier persistence. Source-only evidence does not prove whole-day validation, available slots, rollback, or final order-window behavior.
Why is runtime blocked?
Re-entry requires synthetic businesses, menus, schedules, timezone, orders, and customers; intercepted reads/writes; and immutable receipts for every computed availability and checkout effect.
Why is the category missing?
The Pro group requires Pro or Enterprise source state and returned categories. A missing category does not identify entitlement, deployment, or configuration cause.
Related guides: Pro settings · Available order types