Plate-up_400_wmMost medium to large food service operations now use some sort of professional restaurant software which allows multiple users to accomplish a variety of tasks, all of which can help in controlling the financials of a restaurant. Popular programs include Red Rock, ChefTec, EGS (Enggist & Grandjean Software), and IT Chef (note: I am not necessarily recommending any of these, they are simply a few of the programs available). This type of software package typically includes recipe & menu costing analysis along with inventory control. Some also have the ability to give nutritional analysis, sync with your POS system, provide current pricing bids and synchronize all of your ordering with your vendors.

Although these foodservice software programs are powerful, the old adage “too many chefs in the kitchen” certainly impacts how efficiently (or chaotically) the software works. The more people with “hands in the system”, the more problems you will have with the effective functionality (and frustration level) of the software.

Here is a typical scenario for a larger operation with multiple staff. The Chefs give their food orders to Purchasers who create PO numbers in the system for orders placed. Then they transmit those orders either via the software or through traditional methods. Invoice prices for all products are entered (sometimes by someone other than the person who created the PO) on a daily basis. Chefs enter recipes into the system which are automatically updated with current prices from the info the Invoicer has entered. At the end of the budget period Chefs (or their staff) take their period end inventory. Someone (often a person in Accounting) enters the physical counts into the system which calculates the food cost. With so many hands in the pot it is inevitable to create inconsistencies.

Here is an all too common consequence of improperly trained people entering new items into the system, creating names for items which are not logically designed. The inventory and order sheets generated by these programs will usually sort alphabetically, which is very helpful. But people put names into the system without intelligent thought. For instance, if I am inventorying my produce walk-in I would think that Tarragon would be found under “Tarragon” when sorted alphabetically. No…depending upon who created the item name it could be under “Fresh Tarragon”, “Fresh Herb Tarragon”, “Herb Tarragon”, or perhaps “Herb Fresh Tarragon”. And all the fresh herbs may use a different variation depending on who created it…WTF?!

Only a chef should decide how to name an item into the system. But in every establishment I’ve been at it is multiple people who enter new items, and they do so with no understanding, no food knowledge. They are often data entry people who are very good at most of their job but were not properly trained on how to name new items into the system in a manner which makes culinary sense.

7 Ways to Better Manage your Foodservice Recipe & Inventory Software

  • 1. Properly train all personnel…especially in each of the following steps

    Sounds obvious, but too often the data entry people are simply trained to enter the data…not how to enter it in a logical, consistent, “foodservice intelligent” manner. To make matters worse, they seldom have much culinary background in regards to costing recipes and taking inventory.

  • 2. Data entry and naming of items MUST follow the Chef’s direction

    This is important because the Chef is the one searching for the info in the system to create recipes, do menu analysis, and take inventory. S/he knows best what units of measure will be used both in recipes and for inventory taking. And s/he will know best how to differentiate between similar products.

    Accountants/Purchasers think differently than chefs do and do not understand the products as chefs do. They therefore enter info into the system incorrectly, creating product names with errors (or misspellings), creating unnecessary duplicate items, combining items which should be separate, and assigning units of measure which are wrong.

  • 3. ALWAYS name items in the system by category from general name to specific name

    For instance:

    • Salmon King Fillet Fresh
    • Salmon King Whole Fresh
    • Salmon Sockeye Copper River Fillet Fresh
    • Salmon Coho Fillet Frozen (if you only serve fresh salmon then there is no need to use the word “Fresh” because it is redundant. Same thing if you only use one species of salmon…”Salmon Fillet” is all you need
    • Tarragon Fresh
    • Lemons 115 CT
    • Potato Yukon Gold #1
    • Potato Russet 80 CT
  • 4. Don’t make things too specific

    • Name items according to how you will identify it in a recipe…but stop short of over-specificity.
    • If you regularly order King Salmon Fillets then you may receive a range of sizes. If you don’t actually order by the different sizes (because all you care about is getting King Salmon and the size is irrelevant) then there is no need to have:
      • King Salmon Fillets 7/11
      • King Salmon Fillets 11/18
      • King Salmon Fillets 18-Up

Adding the size to the item name only clutters and confuses the process, unless you specifically have a use for 2 or more sizes and regularly purchase those different sizes for different recipes. If you create a recipe, which size King Salmon will you use? If don’t choose the most recent purchase then it will pull in the price from the last time you purchased that size Salmon…which could have been months ago! And if you do add the correct size now but in 4 months you are using a different size then your cost analysis for the recipe will be wrong in the future. King Salmon Fillets is therefore the best name.

  • 5. NEVER name items simply using the invoice or vendor name!

    First, all vendors will have variations on the name for the same product. Second, invoice names are often HORRENDOUS for inventory and recipe software because they frequently say something like “fresh tarragon”. Great, I’m standing in my produce cooler doing inventory and half the items begin with the word “fresh”…utterly useless info to have at the start of the name because everything in the produce cooler is fresh!

    Here are some examples of how NEVER to name an item:

    • Fresh Tarragon (should be Tarragon Fresh)
    • Fresh Herb Basil (should be Basil Fresh…or Herb Basil Fresh if all Herbs begin as such)
    • 115 CT Lemons (should be Lemons 115 CT)
    • Fish Ahi (why would someone use “Fish” in the item name? Yet I’ve seen it done!)
    • Fillet Sockeye Salmon (should be Salmon Sockeye Fillet)
    • Kumamoto Oysters (should be Oysters Kumamoto
    • Fuji Apples (should be Apples Fuji)
    • Chicken Base (should be Base Chicken, or Soup Base Chicken, or whatever makes sense to the Chef)
    • Fresh Peeled Cloves of Garlic (should be Garlic Cloves Peeled)
  • 6. Always use spell check!

    It is very difficult to find an ingredient if someone created its name with an incorrect spelling (I’ve seen “Scollop” instead of “Scallop!”

  • 7. Always consider the best Units of Measure for Recipes & for Inventory

    • The best units of measure for recipes generally break down into weight (pounds/oz) and volume (cups/tbl),
    • The best unit of measure for counting inventory generally break down into either weight, or cases and its pack units (cans, containers, etc).
    • Proteins should always be inventoried by the pound, not by the case.

It sucks when you are inventorying sugar packets and your only unit of measure is by the each! Or, vice versa, you’re creating a recipe and the only option is by the case.



 

Download the 7 Ways to Manage your Recipe/Inventory Software PDF

Click on the button to download the sheet for free. No pop-ups or other BS.

Download 7 Ways to Manage your Foodservice Software