Colton's Hot Chicken — private concept

The plan

Colton’s Hot Fried Chicken, from first tap to fry line.

Give guests one clear Colton’s ordering path before they leave for another platform.

Carry heat, allergy, and preparation notes from the order into a readable line ticket.

Turn large-order calls and shift-cover texts into follow-ups and approvals the owner can actually see.

Private concept only: the screens use illustrative sample data until Colton’s confirms the real workflow.

What a first build does

Design a private multi-screen demo for diner, counter, fry line, and owner workflows.
Structure a confirmed menu, heat choices, allergy/preparation notes, and pickup or dine-in order states.
Include a controlled demo of catering enquiry follow-up, rewards, time-off, and shift-cover approval.
Document the approved first workflow and handoff rules before any production build.

What it does not do

Does not replace ChowNow, DoorDash, payments, POS, payroll, or delivery services in the first build.
Does not publish a menu, accept a live payment, or send a real customer message.
Does not claim current inventory, sales, staffing, customer, or order data.
Does not connect to existing systems until access, ownership, security, and cutover are explicitly approved.

Before anything gets built

Which menu items, prices, heat levels, sides, and allergy statements are approved for public display?
Which guest paths must be distinct: dine-in, pickup, direct delivery, marketplace delivery, catering, or pre-order?
What exact information must a kitchen ticket show before the line can start an order?
Who owns shift approval, and what rules apply to swaps, time off, and no-shows?
Where do catering and large-order enquiries arrive now, and who must follow up?
Which existing ordering, payment, POS, or delivery tools must remain untouched in phase one?