Group Ordering for Offices — Corporate Catering Without a Marketplace

A group order is one cart that ten people contribute to, paid for once, delivered together. The classic use case is the office Friday lunch — one HR person sends a link, the team picks dishes individually, the order goes in as a single ticket with one delivery and one payment. The operator sees a €150 ticket instead of ten €15 ones.

The economics of this are dramatically better than ten individual orders. Same delivery run, same packaging consolidation, much higher average order value, much lower customer-acquisition cost (one HR person becomes a repeat weekly customer). The problem is that most restaurants don't offer group ordering on their own site — so the corporate buyer defaults to a third-party catering marketplace that takes 15–25% commission.

What "group ordering" actually has to do

A shared cart isn't enough. For a corporate buyer to use the direct channel instead of a marketplace, the experience has to handle the workflow they actually have:

• •Shared cart link the host sends to colleagues by Slack/email
• •Per-person item attribution so it's clear who ordered what
• •Deadline lock — at 11:30, no more items can be added; the order submits
• •Single delivery to one office address, single payment by the host (or invoice billed to a corporate account)
• •Invoice with company VAT/EIK details, not a customer receipt
• •Recurring schedule — "same group order every Friday at noon"

Buyers weigh these differently. A team that orders once a month needs the first four: a link, names on the dishes, a clear moment the order closes, one delivery and one payment. An office that orders every Friday starts asking for the last two — and that is where a marketplace usually keeps the account.

Where the marketplaces actually win — and where they don't

Corporate catering marketplaces (Forkable, Cater2.me, Sharebite, etc.) won the segment in the US by solving HR's problem of curating restaurants across cities. For a 500-person company with offices in five markets, the marketplace adds real value. For a 15-person team that orders from the same three restaurants every week, the marketplace adds only commission.

The honest framing for restaurants: don't try to take the enterprise multi-city accounts from marketplaces. Take the local, repeating, single-office accounts that are over-paying for marketplace convenience they don't need.

Three sub-features that make or break the direct channel

Per-participant cart attribution. The host needs to see "Anna picked the salmon, Boris picked the salad, Maria picked nothing yet — send reminder" on one screen. Without this, the host can't close the order with confidence and reverts to a spreadsheet.

Recurring orders. The biggest cost of "Friday lunch" is the planning, not the food. If the restaurant can offer "same group order every Friday at noon — sent to the same five people automatically," they capture the relationship for months at a time instead of competing for it each week.

Invoice with VAT details. Corporate buyers expense the order against their company, not a personal card. They need a real invoice with the company VAT/EIK number, not a customer receipt with "John Smith, Visa ending in 4242."

How Ordering.Tools handles this

Group Orders covers the core of that workflow from the restaurant's own ordering page. The host starts a group order from the cart and shares the link. Colleagues sign in and add their own dishes, each line tagged with their name, and the group page shows who ordered what with a subtotal per person. When everyone is in, the host checks out once — pickup, delivery or a table — and pays for the whole order by card or on site. The kitchen gets one order with the dishes grouped by person. Where the restaurant issues invoices for online orders, the host can ask for one at checkout, with the company details saved on their profile.

What it does not do: there is no automatic deadline — the host closes the order when everyone is in — and a group order does not repeat itself. For a standing weekly office lunch, the restaurant can use a recurring catering contract instead: an accepted catering order that repeats every week, every two weeks or every month.

See the Group Orders feature page for the full workflow, or the Catering Orders page for the quote-and-accept flow and the recurring contracts that handle larger and repeating functions.