How Allspice is intended to work

What Allspice is

Allspice is being built to become an AI Director of Operations for independent multi-unit restaurant groups: one place to ask questions across the systems a group already runs on, and to approve the actions that follow. It is not designed to replace your point of sale, your scheduling tool or your reservation book — it is designed to sit on top of them, so they can be asked one question together.

Who we are building it for

Independent restaurant groups running more than one location: the operators, general managers and owners who answer for labor, sales and cost across several sites at once, without the central analytics team a national chain can afford.

The problem it is meant to address

A multi-unit group runs on a stack that does not talk to itself — point of sale, shift scheduling, reservations, accounts payable, email marketing, the website, distributor ordering. Answering an ordinary operating question, such as why labor was high at one location last week, means exporting from several of those systems and reconciling them by hand, every week. The result is late answers, no single view across locations, and time spent assembling data rather than acting on it.

The intended workflow

Three steps, and the third one is the point.

1 · Ask

You type a question in plain English — no query language, no filters, no dashboard to navigate to first.

2 · Allspice renders

Allspice is designed to pull from your connected systems and render the right panel for the question you actually asked: a chart, a schedule, an invoice table, a recommendation. That is what we mean by just-in-time UI — the view is assembled for the question rather than waiting for you in a standing dashboard. Answers are designed to cite the source system and time range they came from, and to say so when the data is stale.

3 · You decide

Nothing is designed to move on its own. When Allspice recommends an action — adjusting a schedule, flagging a reorder — the intended model is that it stages the change and waits for your approval before anything is written back to the underlying system. Human review is not a setting to be switched off; it is the step the workflow is built around.

The systems we are designing for

Point of sale, shift scheduling, reservations, accounts payable, email marketing, the website, and food distributor systems. Which of those land first is being decided with our early partner operators. None of them is generally available yet, and no integration described on this site is connected, certified or ready to use.

What exists today, and what is planned

Allspice is in early development. We are in partnership and MVP-definition work with a small group of operators, deciding together which problems the first release should solve.

• Exists today: this website, the early-access list, and the design and partnership work behind the product described above.
• Planned: everything else on this page — the integrations, the natural-language answers, the staged approvals, the cross-location view.

What you cannot do yet

Stated plainly, because the rest of this page is about intent:

• There is nothing to buy. No pricing, packaging or trial exists.
• There is no application to sign into, and no account to create.
• No system can be connected to Allspice today.
• Allspice holds no data from any restaurant system — no sales, labor, reservation or supplier data passes through anything we run today. See the privacy notice.

How to get involved

The early-access list is how we stay in touch with operators who want to shape the first release. Joining it is free, is not a purchase, and does not commit you to anything — see the terms.

Join the early-access list , read more about where the product stands, or see other ways to reach us.