Recipe Behavior Flow Chart

Recipe Behavior
The Kits/Recipes tab makes assigning behaviors to your kit/recipe items simple with a dropdown menu of recipe item behaviors:
- A Batch Recipe item is made ahead of time but not produced in Yellow Dog using manual adjustments. When added to physical inventories, Batch Recipe Items will bring in their ingredient items, along with any related batch recipes and their ingredient items. Any counts to Batch Recipe items will adjust the ingredients’ on hands. This is the most common recipe type used.
- The POS Menu Item Recipe is not used in most implementations. This behavior was created for 2-way integrations. These recipe items aren’t produced until they are ordered. A burger might have a recipe that includes the bun, patty, and toppings. While the ingredient items are counted separately, they are sold as one unit.
- Production items, made in house to sell, are produced in Yellow Dog through manual adjustments, which is the only time their ingredient items are affected. These items have an on hand and can be counted in physical inventories, but they do not bring their ingredient items in to physical inventories with them.

- The Production Transfer Item behavior allows for a two-step process where one location produces a recipe item and another sells the recipe item as is. The “Production Store” will have ingredients subtract from inventory upon a Transfer. During the transfer, the Store To will receive an on-hand value tied to the recipe item for their use in selling. No ingredients will deduct from the Store To’s inventory when the recipe item is sold; the on hand value of the recipe item will simply decrease
- The Retail Kit behavior allows users to assemble and disassemble the kit, count the kit in physical inventories, and sell or return the kit at a POS. The ingredient items are only affected by manual adjustments. These kits are usually store-assembled gift baskets or bundles of items. This behavior is very rarely used in F&B environments.

- The Purchasing Kit behavior allows users to receive by the recipe and sell by the ingredient. While more frequently used in retail operations, a good example of this would be a mixer assortment purchased together. One “recipe” might consist of the “ingredient items”: 6 bottles of strawberry daiquiri mix and 6 bottles of pina colada mix. These recipes only work if the item count is consistent for each order.
- The final behavior is “Other”. This behavior is used to set non-standard, possibly conflicting, item behaviors and is often very rarely used.
Related Articles
Recipe User Guide
What is a Recipe? This document will provide a comprehensive overview of the Recipe Module in Yellow Dog. Let’s start with the basics – What is a Recipe? A recipe is a group of items that are combined to be sold as a single item in the Point of Sale. ...
Reporting Explained: Inventory Chart on Hand summarized by dimension.
Business Need: These reports are helpful for users who want a report to show on hand item totals summarized by dimension. How it Works: An Inventory>Chart>On Hand by dimension report visually shows a summary of on hand totals by the dimension you ...
Purchasing Flow for Food and Beverage
The Yellow Dog Inventory purchasing flow ensures that all aspects of inventory management, from restocking to adjusting errors in transfers, are covered systematically. Each document type in the flow serves specific functions that collectively ...
Why are my Recipe Cost & Suggested Retail not displaying data?
Issue: Cost and Retail shown in editor but not in recipe list. Cause: The procedure within the software that calculates the average cost & suggested retail looks to find all the stores where ALL ingredients are available to the store. This slice of ...
How do I create a Production Recipe?
This video will demonstrate how to create a Production Recipe How Do I Create A Production Recipe in Yellow Dog? The first thing you will need to do when creating a production recipe in Yellow Dog is create the item that is going to be attached to ...
Recent Articles
How To: Import Interfaces by Level using Balto
This document will review how to import interface settings for a level using the Balto import tool. Prerequisites Items are required to exist in YD already Items cannot be marked as removed. The stores must also exist in YD Yellow Dog user with ...
How To: Update Par & Re-Order Points via the Balto Import Tool
This document will review how to update Par & Re-Order Points via the Balto import tool With all Balto imports, be sure not to change any of the column headers in the template. Unused columns can be removed, but the headers should not be edited in ...
How To: Update Items Store Availability via the Balto Import Tool
This article will review how to update items store availability with the Balto Import Tool With all Balto imports, be sure not to change any of the column headers in the template. Unused columns can be removed, but the headers should not be edited in ...
Yellow Dog/Jonas File Exchange Overview
This document will provide an overview of the Yellow Dog Jonas File Exchange Integration Integration Approach This is a 2Way integration – pull sales and push items • Sales – pulled from a file • Items – pushed to .csv file • Codes – Inserted into ...
Yellow Dog/Jonas API Overview
This document will provide an overview of the Yellow Dog Jonas API Integration Integration Approach This can be set up as a 2Way – Items are pulled from us, and sales are pushed or 1Way sales are pushed. NOTE: Jonas controls the flow of sales and ...