Things we do
- Convert vendor information to Products, since you can now have different pack sizes per vendor
- Convert recipe units to Equivalents. Equivalents will contain current recipe unit information (like cups per lb, shrinkage) and can also accept preps (like 1/4" dice) as well as Book of Yields information.
- Eliminate special characters from recipe unit measures (!@##$%, etc.)
- If an item's current price doesn't match a vendor's bid, or if you're not using vendors at all, the conversion will create a new vendor (called CostGuard Import Vendor) and assign that price to that vendor.
- Import allergens if they are used with ingredients
Things we don't do
- Import transactions such as counts and invoices. Only fields and information required for Recipe processing will be imported.
- Import locations or other fields not needed for Recipe and Nutrition management.
- There may be some nutritional codes that don't work
- reciProfity uses an updated USDA database (#28) that no longer includes a few items that were in CostGuard's version (#23).
- Custom USDA items are not imported; they must be re-entered.
- Fractions in recipes are converted to decimals.
- Multiple units in a recipe are not supported (e.g., 1 cup 1 tbl converts to 1 cup).
- No prep portion, BUT, that's converted to the expanded equivalents for prep recipes.
- We do import the recipe method as text with some formatting but not the graphics! So check your recipe method and remember to add the graphics.
- Prep recipes in reciProfity cannot have a selling price. If your CostGuard prep recipe has pricing just create a serving recipe for it in reciProfity ( you can use the Save and Copy feature) and price it.
What to look for after converting
- This kind of inventory item entry in CostGuard can create costing problems in reciProfity. The Pack size (case) is the same as the case size/description. CostGuard uses the pack cost ($5.10), while reciProfity uses the case cost ($61.20). If you have items entered like this example, it's best to edit the item in CostGuard, and make the pack size (case) correspond to the pack description (e.g, 1 qt).
- reciProfity rounds recipe ingredients to 3 digits instead of 2. So a muffin tin costing .22309 each would show as .22 in CostGuard and .223 in reciProfity. That is a difference of 3/10ths of a penny to the cost of each muffin. Not a biggie! We just want you to know.
- Recipe units with 0 in 'number per' are ignored when converting. That would cause items in reciProfity to have a higher cost than in CG. This is very unlikely to occur, unless you have CG recipe units with 'Number Per' as 0, AND are using a compatible unit in a recipe.
- Check for nutrition exceptions (see above explanation about USDA database versions).