Skip to main content
Order batching combines multiple orders from the same table into one consolidated order before sending to the kitchen or POS. This reduces ticket noise and gives the kitchen a complete view of what a table has ordered.

How It Works

Without batching, each time a guest at a table orders something, a separate ticket prints in the kitchen. With batching enabled:
  1. Guest places first order → order is held in a batch
  2. Guest places second order → added to the same batch
  3. After the timeout period, the batch closes
  4. All orders merge into one ticket and send to kitchen/POS

When Orders Are Batched

Orders are grouped into the same batch when:
  • Same table - Orders must be from the same table
  • Within timeout window - Orders placed within the configured timeout period
  • In-Store fulfillment only - Batching only applies to dine-in orders
Pickup and Delivery orders are never batched - they always go straight to the kitchen.

Smart Batch Closing

storekit uses a smart algorithm to determine when to close a batch, balancing speed with consolidation.

How It Works

The system monitors whether anyone at the table is still browsing the menu or building an order:
  • Someone still ordering? → Batch stays open (up to the timeout limit)
  • Everyone finished? → Batch closes immediately
This means if one person places an order and no one else at the table has the menu open, the batch closes straight away - no unnecessary waiting. But if others are still deciding, the system waits for them.

Example

Compare this to a simple 5-minute timeout where the kitchen would wait until 12:05:00 - that’s over 3 minutes saved.

Timeout Limit

If guests keep browsing, the batch won’t stay open forever. There’s a maximum timeout (up to 5 minutes) after which the batch closes regardless. This ensures orders always reach the kitchen in a reasonable time. The Batch timeout picker offers 1 to 5 minutes, with a hint for each:

Merged Order Contents

When a batch closes, orders are intelligently merged:

Item Merging Example

Configuration

Store-Wide Settings

Go to Stores → [your store] → Settings → Operations and find the Order batching section:
The Order batching section only appears for Order & Pay (dine-in) stores, and batching applies to In-Store orders only. Include order notes and Include customer names are under Merged ticket contents.

Disabling Batching for Specific Tables

The store-level Batch timeout picker only offers 1–5 minutes; to switch batching off for the whole store, turn off Enable order batching. A table can also have its own batch timeout, including 0 so its orders go straight to the kitchen while the rest of the store keeps batching. There is no setting for this in the dashboard: contact support to set a timeout on specific tables. This is useful for bar seating or quick-service areas where guests typically order one item at a time.

Customer Notes on Batched Tickets

When batching is enabled, customer notes are stripped from the merged ticket unless Include order notes is turned on. This is the most common reason a kitchen or bar stops seeing notes after batching is switched on: the customer types a note at checkout, the note is saved on the order, but the consolidated ticket sent to the kitchen, printer or POS contains no notes at all. Include order notes controls both:
  • The general order note each guest typed at checkout (prefixed with the guest’s first name on the merged ticket)
  • Item-level notes, which are merged into the same notes block as Item name: note

Order notes aren’t reaching the kitchen or bar

Work through these in order:
1

Check order notes are enabled for the store

Go to Stores → [your store] → Settings → Operations → Order Notes and make sure it is set to Optional or Mandatory. Hidden disables order notes entirely, so customers never get a note field at checkout.
2

Turn on Include order notes if you use batching

In the same page, under Order batching → Merged ticket contents, turn on Include order notes. With batching on and this toggle off, notes are removed from the merged ticket even though they appear on the order in the dashboard.
3

For Zonal (Aztec), configure an Order Note Product ID

Zonal only accepts customer notes as a line item. Without an Order Note Product ID in the Zonal integration settings, notes are dropped on the way to the POS. See Zonal order notes.
4

Check the note reached the order itself

Open the order in the dashboard and confirm the note is on it. If the note is on the order but missing from the ticket, the problem is in the steps above; if it is missing from the order too, the customer never entered one (or Order Notes is set to Hidden).
Changing Include order notes only affects orders batched after you save. Tickets already sent to the kitchen aren’t reprinted.

Notes and split printing

A general order note isn’t tied to a specific item, so it prints on every station ticket for that order. With split printing, each printer receives only the items from its assigned categories, but the order note appears on each of those tickets — so a note like “nut allergy” reaches the kitchen and the bar. A printer that receives none of the order’s items doesn’t print a ticket at all, so it won’t see the note either.

Integration with POS Systems

When a batch closes, the merged order is sent to your connected systems:
  • POS systems - Deliverect, Lightspeed, Zonal, Tissl, PointOne, Comtrex, Ikentoo
  • Printers - CloudPRNT enabled printers
The POS receives one order containing all items from the batch, making it easier to manage the table’s bill.

Send Now

When batching is enabled, guests see Is your group ordering separately? after placing their order, with a Send now button. This lets them close the batch early instead of waiting for the timeout. The button shows a countdown of how long until the batch closes on its own. If the guest knows the table is done ordering, they can tap it to send every order in the batch to the kitchen straight away. (The dashboard’s batching settings call this the Send to Kitchen button.) This is useful when:
  • A guest is ordering alone and doesn’t need the full timeout
  • The table has finished ordering and wants their food sooner
  • A quick top-up order that should go straight through

Best Practices

  1. Match timeout to service style - Fast-casual needs shorter timeouts than fine dining
  2. Enable customer names - Helps staff see who at a large table has ordered
  3. Turn on Include order notes - Otherwise allergy and preparation notes never reach the kitchen
  4. Train staff - Ensure servers know batches will be held before going to kitchen
  5. Consider bar vs table - Ask support for table-specific timeouts for bar seating or quick-service areas