Noctivion

Phase 1 pricingCampaign-to-Order Flow

Campaign-to-Order Flow

Menu. Order. Pickup slot. Checkout.

You post, customers order. They browse the menu, add items, reserve a pickup slot, and check out — before the phones start ringing. You get structured orders, a prep list, and catering inquiries that aren't DMs.

RestaurantsFamily kitchensFood trucksCaterersMeal prep operatorsPop-up food vendorsBakeries with preorder windowsGhost kitchens

The system · pane by pane

Scroll the build end to end.

Current broken path01 / 09

What operators deal with today.

  • Orders come through Instagram comments and DMs

    No record, no queue, no deposit. One person handling DMs while running the kitchen.

  • Catering inquiries with no structure

    Guest count, pickup time, menu preferences — none of it collected before the first phone call.

  • No preorder window control

    Menu goes out, phones ring, no way to cut orders off when capacity is reached.

  • Customers don't know when or how to pick up

    Pickup chaos. No slot reservation, no confirmation, no coordination. Every order is a separate conversation.

Customer action captured02 / 09

What the customer does.

Customer browses a live menu, builds an order, reserves a pickup slot, and checks out — no phone call required.

  1. 01

    Browse the menu

    Categorized items with photos, pricing, and add-to-order buttons. Preorder window status visible: open · closing soon · closed.

  2. 02

    Build the order

    Item tray builds in real time. Quantity controls, running total, add or remove — fast and clear on mobile.

  3. 03

    Reserve a pickup slot

    Time locked before checkout so the kitchen can plan. Slot capacity controlled by the operator.

  4. 04

    Checkout and confirm

    Order summary, contact info, payment path. Confirmation sent to the customer. Order appears in the operator log.

What ships in V103 / 09

Front-end + backend.

Front-End V1

  • Preorder / drop window with live status: open · closing soon · closed
  • Full menu with categories, photos, pricing, and add-to-order flow
  • Order tray with quantity controls and running total
  • Pickup slot reservation — time locked before checkout
  • Catering inquiry path — separate lane from pickup orders
  • Customer contact capture: name, email, phone, pickup intent
  • Checkout path: Stripe-ready (activate when ready)
  • Mobile-first ordering UX, fully responsive

Backend / Admin V1

  • Google Sheets order log: items, quantities, pickup slot, contact, payment status
  • Operator email alert on each new order
  • Catering inquiry routed to a separate Sheets tab
  • Order reference number generated on each submission
  • Order window open/close controlled by operator from config
Operator command layer04 / 09

What the operator receives.

  • Order intake summary

    Customer, items ordered, pickup slot, and total — formatted for operator review.

  • Pickup prep alert

    Operator notified when the order window closes. Kitchen knows what's coming.

  • Catering inquiry brief

    Event date, guest count, menu notes, and contact — formatted and routed separately from pickup orders.

  • Next-action prompt

    Review orders by pickup slot. Confirm catering inquiry availability.

  • Reply template

    Draft catering response for operator review and send.

Semi-automation V105 / 09

What happens automatically.

  • Order confirmation email to customer on submit
  • New order alert to operator email
  • Google Sheets row created on each order
  • Catering inquiry alert to operator email
  • Order reference number auto-generated
Support layer06 / 09

Supervised layer. Honest boundary.

Included · operator reviews output

  • Order intake summary → structured order, pickup slot, customer details for operator review
  • Catering inquiry brief → formatted event scope for operator review
  • Reply template → catering response draft for operator to approve and send
  • Follow-up prompt → day-of pickup reminder draft for operator approval
  • Backend organization → orders structured by pickup slot and date

Not included · do not advertise

  • Autonomous customer order modification or cancellation
  • AI responses to customer order questions without operator review
  • Real-time inventory management or POS sync
  • Autonomous catering quote generation
  • POS system replacement
  • AI receptionist handling customer calls
Add-ons07 / 09

What you can add later.

  • Operator SMS alert on new order

    V1 · Buildable now

    Text notification to owner or kitchen staff when an order lands

  • Automated order confirmation email

    V1 · Buildable now

    Styled confirmation with order items, pickup slot, and reference number

  • Google Calendar fulfillment scheduling

    V2 · Requires setup

    Pickup slots synced to operator calendar — requires Google Calendar setup

  • Automated day-of reminder to customer

    V2 · Requires setup

    Email reminder on pickup day — requires email platform configuration

  • AI-generated catering proposals

    V3 · Do not advertise

    Autonomous catering scope and pricing — not included, do not advertise

  • Autonomous order routing to kitchen staff

    V3 · Do not advertise

    AI-directed kitchen task assignments without operator review — do not advertise

Honest guardrails08 / 09

What not to promise.

  • Real-time inventory sync with existing POS (Toast, Square, etc.)
  • Automatic refunds or order cancellations without operator action
  • Full restaurant management replacing existing software
  • Guaranteed pickup slot availability from the intake form
  • AI customer service without operator review

← Drag · swipe · arrow through the system →

Proof

This system is live and working.

Kabba's Kitchen PDX — live Campaign-to-Order system. Portland, OR. Restaurant order and preorder flow built by Noctivion.

View the proof →

Start your Campaign-to-Order Flow

Reserve your build path. After review, we confirm fit and send the payment link or next-step setup.

Reserve this build →See all 5 flow types →

Not sure which flow fits?

Reserve a $30 Build Audit →