Bundles on the Chef Docket: List the Contents, or Show the Bundle as One Item
By Andrew Hemphill · 6 October 2026
A bundle is one item made of other items in your catalogue: a breakfast box, a morning tea tray, a lunch box. The chef docket has always broken a bundle into its contents, one row per dish. That is still how it works by default, and you can now choose to keep a bundle together instead.
Choose it on the item
Open a menu item that is a bundle. Under This item is a bundle there is a new setting, On the chef docket and kitchen reports, with two choices:
- List each content item separately. Each dish prints as a row of its own, tagged with the bundle it came from. The bundle’s name is not shown as an item of its own. This is the default, and it is how bundles have always worked.
- Show the bundle as one item. The bundle prints as one row with its contents listed underneath, the same way the driver docket shows it.
How it looks on the docket
Here are two bundles on the same order. The Healthy Start Box is set to show as one item, so it is a single row of 12 with its contents underneath. The Morning Tea Tray lists its contents separately, so the scones and the coffee are rows of their own, each tagged with the tray they belong to.
| Under a bundle shown as one item, each content says how many go into each bundle: Chia Pudding (2 x for each box). Twelve boxes of two is 24 chia puddings. The count is per bundle because a kitchen report adds up the same bundle across several orders, and “2 x for each box” stays true however many boxes the row totals. The word comes from what you call each one on the item (box, platter, tray and so on). Each content keeps its dietary codes and allergens on its line, for example **Chia Pudding (2 x for each box) (gf | df) contains ALMND, RYE**, so nothing the chef needs to know is lost by grouping it. |
Every kitchen document follows the same choice
Set it once on the item and it applies everywhere the kitchen looks:
- the chef docket
- the consolidated docket
- the kitchen reports (summary, weekly, daily, item and production reports), on screen and as PDF and CSV
- the order cards on the kitchen dashboard
The prep panel on the kitchen dashboard still adds up the contents, so you always see how many of each dish to make.
The trade-off
Showing a bundle as one item keeps the box together, but its contents are no longer rows of their own on the kitchen reports. They sit under the bundle’s name instead.
That matters when the same dish is sold in more than one way. If chia pudding is also in a different bundle, or ordered on its own, those show as a separate chia pudding row, while the ones in this box are only listed under the box. The chef has to add them together to know how many to make, and it is easy to miss.
If your kitchen batches dishes across orders, keep List each content item separately for bundles that share dishes with other items. Then every chia pudding is counted in one row. The prep panel on the kitchen dashboard always totals the contents either way.
A few smaller changes
- Ticking This item is a bundle now also unticks Include in customer menu, as well as Include in chef & driver docket. Untick the bundle and both are ticked again.
- Include in chef & driver docket is locked on a bundle. The new setting decides what the kitchen sees instead, so there is only one place to set it.
- Chef notes follow the bundle. On a bundle shown as one item, the bundle’s chef note prints on its row, and a content’s own note prints in brackets after that content.
- The quote builder tells you. When you add or edit a bundle on a quote, the note under its name says which way it prints for the kitchen.
-
On the API, the setting is
chef_docket_bundle_display:contentsorcombined.
Everything about bundles is on our Bundles help page, and our article Options, Includes, Bundles and Packages: Which One Do You Mean? compares bundles with Options, Includes and packages.