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 invoice. 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"

Each of those is a hard requirement, not nice-to-have. If any one is missing, the corporate buyer reverts to whatever marketplace handles all six.

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

The Group Orders feature on the platform supports all six requirements above. Host opens a group, shares the link, colleagues add items with their name attached, host sets a deadline, order locks at deadline, single delivery and single invoice with the corporate billing details captured at order creation. Recurring schedules carry the same configuration weekly without recreating the cart each time.

See the Group Orders feature page for the full workflow, the Catering Orders page for the multi-day quote-and-accept flow that handles larger functions, or the Schedule Management page for how recurring weekly orders are configured.