Family restaurant food cost: price shared plates, refills, bundles, and takeaway

A family restaurant sells an experience as well as a plate. The table may share a bowl, pass a platter, add a side, request another serving, or take part of the meal home. If the costing unit is only one nominal plate, the record can miss the actual promise. Start by writing the offer in plain language: what is served, to whom, in which vessel, with which included components, and through which channel. Then connect that promise to a recipe version and a portion tool. An operator assumption about how many people share a dish belongs in the assumption field, not in a statement about customer behavior.

Separate adult, child, and shared portions

A child plate is not necessarily a smaller adult plate. It may have another side, garnish, allergen control, vessel, or preparation path. A shared platter may contain a mix of components whose edible portions are easier to verify by tray than by guest. Record each version independently, including the food that is included and the food that is excluded. The Restaurant365 article is public operator guidance for thinking about portion size and calculation; it is not a rule for your age bands, weights, or prices. Use scales, ladles, scoops, or counted units that your team can repeat, then review the result when the service promise changes.

• Write the offer definition, serving vessel, included sides, sauce, garnish, and stated audience in the recipe record.
• Give adult and child versions different identifiers when their weights or components differ instead of applying a hidden ratio.
• Cost a platter by component and total usable output, then state how the operator allocates the shared serving across an order.
• Record leftovers, returned food, refills, and takeaway requests as destinations or events rather than silently reducing the original portion.
• Keep dietary and allergen decisions with the responsible local process; a family-style label does not answer those questions by itself.

Model bundles and takeaway packaging by channel

A bundle can look simple on a menu while combining a main, shared side, drink, sauce, dessert, and package. Build a component list with recipe versions and make the bundle rule explicit: included, optional, substituted, or separately priced. Takeaway changes the physical unit. A platter may need a larger container; a sauce may need a cup and lid; a family bundle may need several labels or a bag. The OrderOut page is public language about one dining format, not evidence for your container setup. Preserve packaging as its own line so a dine-in analysis does not silently become a takeaway claim.

Clearly labelled illustrative operator-entered example: one table offer

The service team also needs a handoff language. When a guest asks for an extra side or a refill, the order record should show whether that item was included, substituted, or added. When food is packed, the packing check should confirm the vessel, lid, sauces, labels, and any component that changes the portion. This is not about treating a family table as a prediction model. It is about preserving the difference between the menu promise, the operator’s chosen rule, and what the kitchen actually issued. Review those records together before changing a bundle price or portion.

1. 1Define the serving promise. Write audience, individual or shared unit, components, sides, refill rule, vessel, channel, and exclusions for the offer.
2. 2Version the portions. Create adult, child, platter, and add-on recipe versions where weights or components differ, using the actual portion tools.
3. 3Cost the components. Link current invoices and recipes to usable output, then build the bundle from the exact included components rather than an assumed average.
4. 4Record service events. Capture included refills, substitutions, extras, returns, leftovers, and takeaway requests with the order or shift record.
5. 5Review the channel decision. Add only the packaging and operating costs intentionally in scope, compare with local records, and revise the offer under operator authority.