SAMPLE-1 · DRAFT
Toronto–Niagara · 1 cases
No payment
ADMINISTRATION / READ-ONLY PREVIEW
Behind the scenes.
No authentication or persistent storage is configured. All controls are disabled. Nothing here can activate ordering or save changes.
Edit the typed configuration in src/config/drops.ts through the repository review workflow. This is a public, non-sensitive configuration preview, not an administration endpoint.
Capacity is one shared order limit across both routes. Accepted order counts and capacity confirmation are unknown. No inventory or available-place count is asserted.
Upcoming configuration
Simulated orders · sample data only
Fictional lifecycle and payment states. No real customer records, payments or allocations exist. Shared capacity is 50 orders per Drop; actual usage is unconfirmed. These samples do not consume capacity.
SAMPLE-2 · PENDING_PAYMENT
Toronto–Ottawa · 2 cases
Simulated pending
SAMPLE-3 · PAID
Toronto–Niagara · 3 cases
Simulated completed
SAMPLE-4 · CONFIRMED
Toronto–Ottawa · 1 cases
Simulated completed
SAMPLE-5 · CANCELLED
Toronto–Niagara · 2 cases
No payment
SAMPLE-6 · REFUNDED
Toronto–Ottawa · 3 cases
Simulated refunded
SAMPLE-7 · FAILED
Toronto–Niagara · 1 cases
No payment
SAMPLE-8 · FULFILLED
Toronto–Ottawa · 2 cases
Simulated completed
No form submission, server action, writable API, payment, reservation, email or order persistence exists. OPEN in the scheduling module never enables live checkout in this application.