Appearance
Menu — recipes & products
How to build it and why the POS id matters: Build a menu.
Cookbook → Menu has Recipes and Products. Switch with the row under the Menu tab.
Recipes
What you make — not always what the guest orders. Example: 18" dough ball, house sauce portion, shredded mozzarella portion.
Each recipe lists inventory ingredients and amounts. Unit costs come from Store → Costing → Inventory.
Diary on a recipe puts it in the matching experiment log:
- Baker — dough, baked bases, fermentations
- Chef — sauces, proteins, batch prep
Only tagged recipes show in Cookbook → Diary.
Products
What you sell, built from recipes and linked to Square or Toast.
The name is what Orders shows once mapped. Put size in the name when the POS variation is generic (Cheese Pizza 18", not Regular).
| Field | Purpose |
|---|---|
| Category | Folder in Parsley only — not a Square or Toast category id |
| Recipes / components | Prep and waste roll-up |
| Square catalog id | Square variation id (not the parent item or category) |
| Toast catalog id | Toast menu item GUID |
| Weekly par | Include in Store → Plan, prep, and waste |
Match is by catalog id, not ticket text. One Square variation or Toast item = one product.
Import from Square
Cookbook → Menu → Products → Load Square catalog → Import selected.
- Each row is a sellable variation, already mapped (
Square linked). - Draft name uses variation, else SKU, else weight. Skips generic names (Regular, Default, Standard).
- Square category name becomes the Parsley folder.
- Re-import skips already-mapped variations. Does not overwrite recipes or par.
Needs live Square Connect. After adding ITEMS_READ, Disconnect and Connect again.
To map by hand, paste the ITEM_VARIATION id. Do not paste the item or category id.
Toast
No catalog import. After Connect Toast, paste the item GUID on the product. Use Toast catalog links for add-on GUIDs.
Sauce batches and dough trays are products with Weekly par, same path as menu items.
Cookbook → Overview tracks recipes added, products with recipes, and Square or Toast mapping. Unmapped lines also banner on Orders.
After a supplier price change, update Inventory costs. Recipe and product costs follow.
If it looks wrong
- Ticket still says Regular — variation not mapped, or name on the product is still generic.
- Prep qty is 0 — Weekly par off, or no recipe on the product.
- Waste $0 with leftover pizza — missing unit cost on the SKU.