Stack map for restaurant ops (Oct 2026): inventory AI seats across POS, reservations, inventory, scheduling, ordering, and chat

What this how-to covers

Restaurants rarely buy one AI tool on purpose. The POS adds an assistant and marketing AI; the reservation platform adds a voice agent and reply drafts; the inventory tool reads invoices and suggests orders; the scheduling tool forecasts sales and fills shifts; the online-ordering or website vendor adds phone answering; a separate phone AI takes takeout calls; and every manager already has a chat assistant. A year later, three tools can quote a pickup time to the same guest and nobody knows which one promised the large-party deposit. This how-to builds one table — Job | Tool | Owner | Cost/mo | Overlap | Decision — for the seven jobs where that overlap is most common.

It is an inventory, not a ranking. Fill Cost/mo from your own invoices, write overlaps in plain sentences, and add who approves: every menu or price change, every supplier order, every schedule, every guest reply or phone answer at scale, and every marketing campaign. AI drafts and suggests; a named person approves. No guest PII, card numbers, or employee SSNs go into a general chat tool.

How to inventory restaurant-ops AI seats

Examples at a glance: each feature has a concrete example from a real job plus a short Try this you can run this week.

1. Build the blank table (primary)

What it is: Start with seven rows and six columns, and leave cells blank until you have a source: an admin seat list, an invoice, or the person who uses the tool. The seven jobs: POS (Toast, Square, SpotOn, Lightspeed), reservations and guest CRM (OpenTable, SevenRooms, Resy), inventory and invoices (MarginEdge, MarketMan, Restaurant365, Crunchtime), scheduling and labor (7shifts, Harri), online ordering and website (Popmenu, BentoBox, or the POS's own ordering), phone answering (Slang, Yelp Host, reservation-platform voice agents, or Presto at the drive-thru), and the chat assistant (ChatGPT, Claude, or Gemini seats — see ChatGPT for restaurant ops and Gemini for restaurant ops).

Concrete example (ops director at a four-unit restaurant group) Illustrative: an ops director fills the table over two afternoons. Phone calls show up in three rows — the reservation platform's voice agent, a separate phone AI for takeout, and the website vendor's answering add-on — and sales forecasts appear in both the POS and the scheduling tool.

Try this

Primary workflow:

Build Job | Tool | Owner | Cost/mo | Overlap | Decision blank for: POS, reservations, inventory, scheduling, online ordering, phone answering, chat assistant.

2. Owners and Cost/mo from invoices

What it is: For each tool, write one owner — the person who can cancel it — and the monthly cost from the invoice, contract, or card statement. If you can't find it, write "Unknown — check bill". Don't fill costs from list prices. Restaurant tools price in units that don't compare: per location, per terminal or station, per cover, a share of card processing, an add-on to another plan, or a quote. Several vendors reviewed today publish no prices at all — SevenRooms, Harri, Presto, Crunchtime, and Restaurant365 among them — and others publish plan amounts that still are not your negotiated contract or your processing bill.

Concrete example (bookkeeper gathering costs) Illustrative: a bookkeeper finds the POS software on one invoice and processing fees netted out of deposits, the reservation platform billing per cover on top of a plan, and the phone AI as an add-on to the website contract. She writes "Unknown — check bill" for the marketing AI bundled into the POS renewal instead of guessing.

Try this

Costs from invoices only:

For each of the seven jobs, name the owner and Cost/mo from invoices only. If missing, write Unknown — check bill. Do not invent prices, cover counts, or location counts.

3. Mark overlaps in plain language

What it is: For each job with two or more tools, write one sentence about what both do — for example, "The POS marketing AI and our email tool both send the Tuesday promo to the same list." Common restaurant overlaps: marketing in a POS-native agent and a separate email or SMS tool; phone answering in a reservation platform's voice agent and a separate phone AI; sales forecasts in the POS and the scheduling tool (7shifts vs Harri); invoice reading in two back-office tools (MarginEdge vs MarketMan); and guest notes in both the reservation CRM and the POS (SevenRooms vs OpenTable).

Concrete example (GM reviewing the table) Illustrative: a GM finds pickup times quoted by the website vendor's phone answering and by a separate takeout phone AI with different lead times. She flags it for a decision first.

Try this

One sentence per overlap:

Wherever two tools share a job, write what both do in one sentence — for example, both answer takeout calls. Ask each tool's owner to confirm it before anyone suggests dropping a seat.

4. Add who approves and the data rules

What it is: Add two columns: Who approves and Data rules. Many restaurant tools can now act, not just draft — update a menu item, mark something out of stock, send a campaign, place an order suggestion, fill a schedule, answer a guest call. For every tool, name the person who approves each action it can take, and write what data may go in: sanitized exports and approved fact sheets, yes; guest PII, card numbers, or employee SSNs in a general chat tool, no. September changelogs show why this matters — see What's new in Toast (Sep 2026) and What's new in Square (Sep 2026).

Concrete example (GM tightening approvals) Illustrative: he finds the phone AI confirms large-party bookings without the deposit rule. He switches large parties to hand-off and names the FOH manager as approver.

Try this

Who approves, what goes in:

For each tool, write who approves menu and price changes, supplier orders, schedules, guest answers, and campaigns, and one line on what data may go in.

5. Write one-sentence decisions

What it is: For each overlap, write one decision: keep both (with a reason), consolidate into one, or pause one for 30 days. Name who owns the follow-up and the renewal date. Start with the three rows where overlap costs the most attention: phone answering, online ordering, and the chat assistant.

Concrete example (owner of a two-unit taqueria) Illustrative: she keeps the reservation voice agent for bookings, pauses the separate takeout phone AI for 30 days with the GM as owner, and moves pre-shift drafting into one chat assistant's project.

Try this

One sentence, one owner:

For the phone answering, online ordering, and chat assistant rows only, write a Decision in one sentence each (keep both, consolidate, or pause). Name who owns the follow-up date and note any renewal date.

Pricing context (October 2026)

This how-to does not quote vendor prices. Fill Cost/mo from your invoices only; use Unknown — check bill when missing. Today's tool reviews note which restaurant vendors publish prices and which are quote-only (Oct 2026).

Our soft offers stay $9 for the toolkit spreadsheet and $19 for the audit — links on /stack and /audit.

Uncertainty: Vendor list prices are not your bill, and card processing is often netted out of deposits rather than invoiced. Several restaurant vendors publish no public dollars. This page invents none.

When it’s useful (honest take)

Useful when you suspect three tools answer the same guest call or send the same promo.

Less useful when you only need a single-product review — start from Toast AI or SevenRooms AI instead.

Related options (educational)

FAQ

What columns does the table need?

Job, Tool, Owner, Cost/mo, Overlap, and Decision — plus Who approves and Data rules once you are ready.

What if I cannot find a price?

Write Unknown — check bill. Do not invent amounts from list prices, directories, or a vendor's sales deck.

Which seven jobs?

POS, reservations, inventory, scheduling, online ordering, phone answering, and chat assistant — the inventory order for this page.

Can AI change menu prices or answer guests on its own in this inventory?

No. The inventory assumes a named person approves menu and price changes, supplier orders, schedules, guest answers at scale, and campaigns.

Where do custom GPTs fit?

On the chat-assistant row. OpenAI says custom GPTs are scheduled to retire on December 11, 2026 — move restaurant SOP work into a project; see ChatGPT for restaurant ops.

Optional next step (if seats overlap)

If restaurant ops pays for a POS with agents, a reservation platform with a voice agent, a separate phone AI, and chat seats that all touch the same guests and menus, finish this inventory before the next renewal. Map the overlap with the $19 AI toolkit audit or the $9 AI toolkit spreadsheet. Email Audit $19 or Toolkit spreadsheet $9.

Checkout is live via Stripe. After you pay, we email delivery (spreadsheet) or intake next steps (audit).

Related: Stack map for hospitality ops · ChatGPT for restaurant ops · Gemini for restaurant ops · What’s new in Toast (Sep 2026) · What’s new in Square (Sep 2026) · Presto AI · Yelp Host AI · MarginEdge vs MarketMan · 7shifts vs Harri · Harri AI · Popmenu AI · BentoBox AI · Slang AI · SpotOn AI · SevenRooms vs OpenTable · Crunchtime AI · Resy AI · OpenTable AI · Toast vs Square · MarketMan AI · Lightspeed Restaurant AI · Square for Restaurants AI · MarginEdge AI · Restaurant365 AI · Toast AI · SevenRooms AI · 7shifts AI · ChatGPT for hospitality ops · Gemini for hospitality ops · Claude · Three checks before another AI seat · How-to: Use Toast IQ to draft a menu or price change, and have the GM approve every one · How-to: Let Square Managerbot and AI ordering channels sync a menu change only after the owner approves · How-to: Ask Lightspeed AI one staffing question, and check Tempo before you change the floor plan · How-to: Answer one profit-and-loss question with SpotOn Profit Assist, and have the bookkeeper verify the explanation · How-to: Turn on Presto Voice for one drive-thru lane, and have the shift manager watch every corrected order · How-to: Let BentoBox draft website copy, and have the chef check every allergen and ingredient line · How-to: Write Popmenu AI Answering scripts, and have the FOH manager approve every answer before go-live · How-to: Let Yelp Host take phone reservations and takeout, and have the GM check every confirmed order · How-to: Approve OpenTable diner Concierge answers and Pro AI review replies before guests see them · How-to: Check what Resy's ChatGPT booking channel shows guests, and fix guest notes before the weekend · How-to: Turn on SevenRooms Voice AI and AI Table Management, and have the FOH manager approve phone answers and seating rules · How-to: Write Slang voice AI policy answers for reservations, and have the GM own every one · How-to: Accept a 7shifts sales forecast and auto-filled schedule only after the GM reviews compliance alerts · How-to: Let Harri's Salli assistant propose a schedule, and have the GM publish every one · How-to: Let MarginEdge's Tom AI process invoices, and keep the bookkeeper on every coding approval · How-to: Use MarketMan Smart Ordering suggestions, and have the chef or GM approve every supplier order · How-to: Run a Crunchtime voice inventory count, and have the kitchen manager own the count and the order · How-to: Let Restaurant365 suggest a purchase order, and have the GM approve every one (bookkeeper owns accounts payable) · ops hub