Advanced Production

Modified on: 2018-03-21 11:40:48 -0400


Overview

Advanced production brings recipe functionality to the location level. Accounts that have advanced production enabled build recipes in locations rather than in the account level catalog. Reports which rely on recipes or compositions will use the advanced production recipe as the basis for reporting when enabled. 


Benefits

This feature allows an account to customize recipes in each location and to take advantage of all of Supplyit's advanced inventory functions.  


Prerequisite 

Advanced production is enabled for the account. This must be done by Jera Support.


Navigation

Location Console => Administration => Catalog


Building Recipes

Select edit and advanced production for a product. The header of the recipe is where the recipe yield is set and where you determine if the product will be restorative (increased) when its ingredients are increased (purchased). If this option is selected, the product is referred to as a generic product and will be the basis of building recipes. Generic products have a unique relationship to vendor products and a vendor product can only be associated to one generic ingredient. The relationship between a generic product and a vendor product is known as a restorative relationship because the generic product increases (replenishes) when the related vendor product is purchased. Recipes can be built from generic ingredients or from other products that may contain their own recipes. Add each ingredient or another recipe product to the recipe. Each ingredient in a recipe needs to have an associated quantity that is required to build the recipe to the specified yield. Add all ingredients required to make the product and set the quantity required to produce the yield. 


Best Practice

  • Add items (referred to as ingredients or generic items) to an account catalog that represent all of the generic products needed to build location recipes. 
  • Place all of your generic products in the same category, which is usually a category named ingredients. 
  • Append a unit abbreviation to the generic product name: each (ea), ounces (oz), grams (g), pound (lb).  This makes the basis for the ratio between the generic ingredient and the recipe yield evident. 
  • Add all generic and vendor products to your location before building the location recipes. 
  • Build a recipe for each generic product by adding the vendor products to your generic product as ingredients. 
  • Use the relationship between the generic product unit and the vendor product unit to determine the correct ratio. 
  • Build common core recipes and use these in recipes. For example, if a cake batter is used in many products, add a cake batter product to your catalog and build a recipe for it in the location. Use the cake batter product as an ingredient in other products that use this batter.


Tips and Tricks

  • A product must first be added to an account catalog before it can be brought into a location and used in a recipe. 
  • All products used in recipes must be in the location where the recipe is being built. 
  • Recipes can be copied and synchronized between many locations in an account. This is particularly valuable for networks that have locations that produce for themselves and use the same recipes across one or more locations.
  • Units can be assigned to an assembly product. This allows a generic ingredient pull to report in a larger quantity, such as a case, instead of the products base unit which might be difficult to translate into the number of cases to pull.
  • Generic product prices can be set in the recipe based on their relationship to a vendor product. By using the pricing calculator and the the vendor product purchase price, a generic item price can be calculated and set.

   


Did you find it helpful? Yes No

Can you please tell us how we can improve this article?