NightstroBack to operations preview

Event & menu proposal

Prepare event details and a food or alcohol menu. This is a local proposal, not a published event, approved price or permission to sell.

Nothing is sent to a server. Editing works offline; publishing, payments, reservations and legal activation remain unavailable.

Event & venue

Use an IANA time zone such as America/New_York. State selection is a planning field, not legal approval.

Schedule

Use explicit-offset timestamps with seconds, for example 2029-06-01T20:00:00-04:00. Dates are not converted automatically. End must follow start.

Menu · 0/100

Proposed USD cents are not checkout prices. Production units use exactly two decimal places, such as 1.00.

No products yet. Add food or alcohol when you are ready to plan the menu.

Resource planning

Proposed stock and capacity are planning values, never live availability. These edits do not allocate inventory, reserve capacity or publish anything. Local IDs stay unchanged when you edit names and values.

Inventory · 0/100

Quantities use exactly three decimal places, such as 1.000. Zero stock is allowed.

No inventory proposed. Add an item before assigning product requirements.

Stations · 0/100

Give each proposed station a unique name. Station names do not create real work queues.

No stations proposed. Add a station before planning a capacity window.

Capacity windows · 0/100

Use positive units with exactly two decimal places, such as 1.00. Dates need seconds and an explicit offset, for example 2029-06-01T20:00:00-04:00. End must follow start, both must stay within the event, and windows for the same station cannot overlap.

No capacity windows proposed.

Add a station to enable capacity-window planning.

Removal is reviewed first. Referenced inventory and stations must keep their dependencies until you explicitly remove or reassign them.