Skip to main content
GullySystem
Hospitality

Bill of Materials for Restaurants

Define the materials and quantities needed for a manufactured item.

Manufacturing

Does this function belong in your operation?

Use when output quantities depend on a repeatable material or component list.

A product or production recipe is created or revised.

A biryani or a paneer tikka is broken into rice, spice, paneer and oil, and the cost is worked per plate. The owner sees which dish earns least. Portion changes revise the cost.

Bring the records the workflow depends on.

  • Finished-item codes
  • Component quantities and units
  • Revision and waste rules

Outputs to check

  • Approved material and subassembly list
  • Versioned material cost basis
  • Quantity-exploded requirement sheet

Follow the bill of materials workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define the output

    Identify the finished item, production quantity and unit.

  2. 2. List components

    Record materials, subassemblies and quantity conversions.

  3. 3. Review allowances

    Approve waste factors and permitted substitutes.

  4. 4. Release a version

    Retain the approved definition and its effective use.

  5. 5. Calculate requirements

    Expand the selected version for a planned quantity and pass shortages to planning or purchasing.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Estimator

Defines the material quantities and approved version used to cost a finished item or quotation.

Production in-charge

Sees what a job needs before it is released to the floor.

Storekeeper

Issues against the list. Anything beyond it is asked for in writing.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Component unavailable

Use only an approved substitute and retain its effect on cost and specification.

Design revised after release

Keep existing jobs on their approved version unless a controlled change is authorised.

Unit conversion inconsistent

Resolve the conversion before calculating requirements or issuing material.

Can this work independently?

A bill of materials can be maintained independently for costing and planning. Stock, purchasing and work orders use its approved version when connected. It does not reserve materials or schedule machines by itself, and a rate-based material total excludes labour or overhead unless separately defined.

Systems and records it connects with

  • Production planning: Demand, planned quantities and resource or material constraints.
  • Work orders: Released production jobs, material issues and output records.
  • Purchase orders: Authorised supplier commitments and open line balances.
  • Stock: Item-location quantities and authorised stock movements.

Configure, test and introduce the workflow.

  • You show a few finished items and describe how they are made. You get a written note on how the parent items and sub-assemblies will be laid out. Begin with a few products.
  • You supply item names, units and wastage habits from your sheets. A trial import comes back for you to correct before anything is relied on. Corrections come cheaply here. Recent purchase rates are connected to the lines. A costed list for a few products is laid beside your own working for comparison.
  • The estimator and the storekeeper explode a batch on the trial. You hear what is missing, and the layout is changed. Gaps surface early. New quotations start from the list. The team is shown how to save a version and how to mark alternates.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Component units are consistent.
  • Production uses the approved version.
  • Revisions preserve the earlier material definition.
Restaurants

How the business operates.

Most kitchens already have a decent POS for billing and KOTs. The trouble starts after the bill is printed.

Recipe cards read against sales

Give every menu item its recipe and portion. Rice, chicken and oil issued from the store can then be read against each plate sold.

Store indents and kitchen issues

Raise the kitchen’s indent, issue against it, and keep store counts, so what left the store can be read against what was sold.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Menu, portions and recipe cards. Hold sections, dishes, half and full portions, rates by order type and the recipe behind each dish, so the kitchen and the counter read one menu.
  • Table plan and dine-in orders. Lay out floors, tables and covers, open an order against a table, add items through the meal and move or merge tables as guests shift.
  • Kitchen tickets (KOT) and order status. Send each item to the station that cooks it, show what is pending at the pass and mark dishes ready, served or cancelled.
  • Counter and parcel orders. Take token orders at a counter, record parcel charges and packing, and bill without a table being involved at all.

Operational bottlenecks to check

Food cost is a guess

Recipe cards are not linked to sales, so you cannot tell whether the rice dish margin fell because chicken went up or because the portion grew. The owner simply guesses.

Platform payouts do not add up

Commission, ad spend, promotions and cancellations sit inside one weekly statement, and a short payment on a handful of orders goes unnoticed.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Order taken

    A guest is seated at a table, or orders at the counter, or the order arrives from a delivery platform. Items, portions and any instruction go on the order.

  2. 2. Kitchen ticket

    The order prints or appears at the station that cooks it. Starters, main course, grill and beverages reach their own stations with the table number on each ticket.

  3. 3. Serving and packing

    Each dish is marked ready and served, or packed for a parcel or rider. Items added later in the meal join the same table order.

  4. 4. Bill and payment

    The table bill carries dishes, taxes and any service charge the restaurant applies. Payment is taken in cash, by card, by mobile wallet, or collected by the platform.

  5. 5. Day close

    At the end of the shift the collections are counted against the bills. Store issue, wastage and complimentary dishes are entered before the day is closed.

  6. 6. Follow-up

    Guests who gave a number can be sent an offer or a booking reminder by WhatsApp. Feedback given at the table is kept against the visit.

Industry reports to connect with

  • Sales by dish, section and daypart
  • Dine-in, parcel and delivery platform shares
  • Kitchen ticket times by station
  • Store issue read against dishes sold

Questions before implementation.

When should restaurants consider bill of materials?

Use when output quantities depend on a repeatable material or component list. A product or production recipe is created or revised.

What should we bring to the requirements discussion?

Bring anonymised examples of Finished-item codes; Component quantities and units; Revision and waste rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Define the materials and quantities needed for a manufactured item. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Use only for operations that make, assemble or formulate physical goods; ordinary service delivery needs a different workflow.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Component units are consistent. Use this check when reviewing the first working version.

Talk to us

Discuss bill of materials for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements