Understand the movements behind the stock figure
An ingredient appears plentiful in the morning but is unexpectedly short by the evening. The useful question is not simply how much remains; it is what happened since the last reliable observation. A delivery, a batch of preparation, a transfer to the bar and a correction represent different events. If every change becomes only a new closing quantity, kitchen and purchasing staff lose the context they need to plan the next service.
Bonzumo includes product stock information and production and stock functions for base recipes. These provide a starting point for discussing quantities alongside products and prepared components. Which movements are recorded and connected in your installation should be demonstrated using your workflow. The immediate benefit is a common understanding: staff know what a quantity refers to and why it has changed. That understanding is the foundation of useful restaurant inventory management.
Separate purchased goods, stored items and menu products
Guests order dishes, suppliers deliver ingredients and your kitchen makes prepared components. These levels belong together but are not interchangeable. A burger sold to a guest is not the same stock item as a delivered case of meat. A prepared sauce is different from its individual ingredients. Start by describing what purchasing orders, what is physically stored and what service sells through the till. This exposes relationships that are easily hidden by vague product names.
For example, tomatoes may arrive by weight, be used fresh in one dish and become a sauce used in several others. Recording everything under one ambiguous item makes the quantities difficult to interpret. Bonzumo provides product and base-recipe maintenance to support a clearer description of those relationships. The exact connection between sales and stock must be checked within your intended setup; it should not be assumed solely because both functions exist in the same product environment.
Establish a reliable opening position
Before using movements to calculate an expected stock level, establish a defensible starting quantity. This may come from a count or another checked opening balance. Define its date, unit and scope. A figure covering the main storeroom cannot silently be compared with a later count that also includes the bar and preparation kitchen. Many apparent discrepancies come from different boundaries rather than goods actually disappearing.
Review duplicate and outdated product records as well. Two names for the same physical item divide the available quantity unnecessarily. Different pack sizes, however, must remain understandable where they contain different amounts. Avoid merging everything simply to shorten a list. Describe meaningful distinctions clearly. Stock information becomes useful when the data reflects the restaurant's real goods structure and provides a basis on which subsequent movements can be interpreted.
Compare deliveries with the goods actually received
Your restaurant can use what arrived, not merely what was ordered. Delivered quantities may differ, and a replacement product may come in a different package size. Compare the actual goods with the description and unit. Check missing quantities and deliveries arriving in stages. A clear receiving routine prevents the kitchen from planning around ingredients that exist on an order but are not yet on the shelf.
Decide who handles discrepancies and which documents support that conversation. The person receiving a delivery should not have to guess whether a substitute can be treated as equivalent. During Bonzumo setup, clarify which purchasing and receiving steps are represented in your chosen configuration. This article does not assume automatic supplier synchronisation or universal document import. A clear team procedure is valuable in its own right and helps you assess exactly what the software needs to support.
Treat preparation as a distinct quantity change
When raw ingredients become a base recipe, the available quantities change. Trimming, cooking and differences in yield may affect the result. Bonzumo includes a production and stock area for base recipes, giving prepared goods a place in the system. The practical question is how much your kitchen actually produces and in which unit that preparation can later be portioned or counted.
Follow a sauce batch from its ingredients to its finished quantity. Which materials are used, what is the usable output and how will the remaining preparation be measured? If the result differs from the planned amount, examine the recipe assumptions. A pack size may have changed, a method may have been adjusted or the described yield may simply be unrealistic. These questions are easier to address when prepared stock is considered alongside the recipe rather than left as an informal note.
Distinguish consumption, damage and correction
Not every reduction in stock is a sale. Goods may spoil, be lost during preparation or be used for another agreed business purpose. A counting mistake can also require a correction. Keep these reasons distinguishable in your working procedure. If every event ends as “quantity changed”, there may be a current number but little explanation of which operational improvement would help.
Bonzumo's base-recipe stock correction includes a reason field. Use understandable reasons that describe the product, the trigger and the observed situation. A vague word such as “adjustment” adds little. The available movement types and their relationship to reporting should be checked during setup. A general loss figure should not replace investigation. Where the same correction returns repeatedly, examine portion sizes, units and recording times before reaching broader conclusions.
Work through a prepared-sauce discrepancy
Suppose the kitchen produces twelve litres of sauce in the morning and four litres remain in refrigeration later. These two observations do not establish that eight litres were sold. Some may have been portioned, moved to another area or discarded. First check the unit and counting location. Two additional containers might already be at the pass. Only then compare recipe quantities and understandable movements to explain the difference.
This example shows why a stock variance is not an automatic judgement about profitability or individual staff. Reliable interpretation needs context. With Bonzumo, product and base-recipe information can provide a shared starting point. In a demonstration, examine a normal production event and a stock correction. Ask what information remains available to explain the quantity afterwards. That reveals the working information your team needs, rather than merely showing that a number on a screen can change.
Combine stock with planned demand before purchasing
A stock figure answers what is available. A purchasing requirement also depends on your planned offer, expected guests and supplier conditions. Ten kilograms may be plenty for a quiet day and insufficient for a large event menu. A large quantity of a short-lived ingredient may deserve more urgent attention than a small balance of an infrequently used product. A useful quantity picture therefore includes what you intend to do next.
Discuss the coming services in practical terms: which dishes are offered, which base recipes are already prepared and which fresh components remain to be bought? Use recipe quantities as a reference and compare your experience from similar days. Better data improves the discussion, but the purchasing decision remains an operational responsibility. This workflow does not promise automatic demand forecasting or orders placed without review. It should make your assumptions more visible, not present unknown assumptions as certainty.
Introduce a manageable review routine
Start with products whose quantities matter most to your restaurant. These might be valuable ingredients, fast-moving goods or items that repeatedly generate questions. Agree a short process: examine the current information, count the physical quantity when needed, explain an unusual change and allow the responsible person to make a justified correction. A focused routine is more sustainable than checking every item equally without a clear purpose.
Discuss recurring discrepancies with kitchen and purchasing staff. An optimistic yield, an unclear pack conversion or poor coordination between areas may be responsible. Record the finding and improve that part of the setup. Correcting only the final number leaves the same problem ready to return. Restaurant stock management becomes more useful when it helps the team understand the flow of goods rather than treating each new count as an isolated administrative task.
Questions to ask about stock and movements
Is a displayed balance always the physical stock? Stored quantities and actual goods can differ when movements are missing or entered late, so targeted counting remains useful. Does every sale automatically reduce every ingredient? No blanket promise is made here. The specific relationship between products, recipes and stock must be checked for your configuration. This is a practical demonstration question, not something to infer from a list of module names.
Should every difference be corrected immediately? First check the product, unit, place and time. An unexplained correction can conceal an input error. Can Bonzumo represent prepared-recipe stock? Functions are present for that purpose and should be configured around your recipes. What is a sensible starting scope? Choose several real items with different quantity types and one complete preparation process. This exposes the data quality and responsibilities needed before extending the approach to the whole operation.
Test the workflow with your own goods
Bring a purchased ingredient, a base recipe made from it and a dish that uses the preparation to your demonstration. Add a delivery with a quantity difference and a past example where stock needed correcting. Follow each case: which unit applies, what quantity results and what information would support a later question? These examples let you assess the proposed stock workflow against a real day in your restaurant.
Orderly stock information helps kitchen and purchasing staff discuss the same goods and quantities. Changes become easier to explain and follow-up questions become more focused. Bonzumo provides product, recipe and stock functions whose appropriate scope can be agreed during setup. Arrange an inventory demonstration around the goods movement that currently causes your team the most confusion, and use it to establish what the system and your internal routine each need to provide.