Manage your CPU product catalogue in Edify—add products, allocate them to specific customers, and set pricing all in one place.
Adding a New CPU Product
Navigate to CPU > Product List
Click "Add new product"
Fill in the product details (see field explanations below)
Click "Save Changes"
Find your new product in the table
Click the text in the 'Customers' column
Untick any customers who shouldn't be able to order this product
Click "Save"
It currently isn't possible to add CPU Products in bulk, but if you reach out to our Customer Support team they'll be able to help.
💡 Note: New products are automatically assigned to all active customers by default, so remember to adjust customer allocation if needed.
Editing Products
To make changes to an existing product:
Go to CPU > Product List
Search for the product
Click "Edit" on the right side
Make your changes
Click "Save Changes"
Product Field Guide
Field | Explainer |
Product Name | Name of the product |
Availability | Status of the product |
Supplier Product Code | A unique identifier for the product, if you don't have a code, just use the product name |
Product Class | The class of this product |
Product Category | The category of the product |
Pack Type | How customers buy the product—'case' if they order by the case, 'each' if they buy individual items, 'box', 'bottle', etc. |
Pack Quantity | How many units come in one pack. For a single loaf of bread it's 1. For a case containing 12 bottles it's 12. |
Sale Price | This is the price that a customer will pay for a CPU product unless custom pricing is setup at a customer level. You can adjust the default price of a CPU product at anytime by editing a product. |
Tax Rate | If tax applies set the rate here |
Single Unit Type | Only needed if Pack Quantity is more than 1. This defines what's inside the pack—bottles, boxes, bags, sleeves, etc. |
Linked Recipe | If this product is something you make, the recipe for the product |
Linked Supplier Product | If this product is something you buy from an external supplier and sell on, the external product |
Single Item Volume or Weight | The size of each individual unit (like 500ml or 1kg). Only fill this in if sites need it for:
|
Unit of Measure | The UoM for the single item volume or weight |
Lead Time | A legacy field that should always be set to 0 |
Understanding Pack Types and Quantities
Pack Type, Quantity, Single Unit of Measure, Single Item Volume or Weight and Unit of Measure all define how you sell a CPU product to your sites/customers and determine how sites can use it in recipes or stocktakes.
Field | Explainer |
Pack Type | How customers buy the product—'case' if they order by the case, 'each' if they buy individual items, 'box', 'bottle', etc. |
Pack Quantity | How many units come in one pack. For a single loaf of bread it's 1. For a case containing 12 bottles it's 12. |
Single Unit Type | Only needed if Pack Quantity is more than 1. This defines what's inside the pack—bottles, boxes, bags, sleeves, etc. |
Single Item Volume/Weight and Unit of Measure | The size of each individual unit (like 500ml or 1kg). Only fill this in if sites need it for:
|
When You Don't Need Volume/Weight
Example: You sell cases of bottled water (24 bottles per case).
Sites sell the water by the bottle
They stocktake whole bottles, not ml
You don't need to set that each bottle is 500ml—it's irrelevant to how they use the product
When You Do Need Volume/Weight
Example: You sell cases of flour bags (10 bags per case, each bag is 1000g).
Sites use flour in their recipes
They need to know "use 250g of flour" when building recipes
You must set the bag size to 1000g so they can add it as a recipe ingredient with gram quantities
Handling Multiple Breakdown Levels
Sometimes products have three levels of breakdown. You can handle this by setting the Single Item Volume/Weight to represent the smallest unit.
Example: You sell cups by the case.
1 case = 4 boxes
Each box = 100 cups
Total cups per case = 400
Setup:
Pack Type: Case
Pack Quantity: 4
Single Unit Type: Box
Single Item Volume or Weight: 100
Unit of Measure: each
This tells the system that each box contains 100 individual items (cups), allowing sites to understand the full breakdown from case → boxes → cups.
Bought-to-Sell Products
If you buy a product from an external supplier and resell it to your sites, the Pack Type and quantities you set on the CPU product don't need to match how your supplier sells it to you.
Example: You buy cups from a supplier in cases (1 case = 100 sleeves, 1 sleeve = 50 cups), but you sell to sites by the sleeve.
Setup:
CPU Product: Pack Type = Sleeve, Pack Quantity = 50
Your stocktakes: Count the external supplier's product (cases), not the CPU product
When linking: Define how many supplier units equal one CPU product sale (e.g., 1 sleeve sold = 0.01 cases used)
💡 Key point: Set up CPU products based on how sites buy from you, not how you buy from your suppliers.
Linking Recipes and Supplier Products
Every CPU Product must be connected to either a recipe or a supplier product—this is how Edify calculates your COGS and live stock levels. When you fulfil an order or produce something in Production Planner, the system needs to know exactly what stock has been used.
Connect to a recipe if you make the product at your CPU
Connect to a supplier product if you buy it in and resell it
To link either one, use the dropdowns on the product settings page to search and select the recipe or supplier product.
Can't find what you're looking for? Check:
Recipes: Must be assigned to the CPU site
Supplier products: Supplier must be assigned to the CPU and the product must be active
Linking Recipes
The recipe yield must match exactly what you're selling in the CPU product.
Example 1: Selling whole items
You sell a loaf of bread through CPU → link to a recipe that yields one loaf of bread
Example 2: Selling specific quantities
You sell 100g portions of sauce → link to a recipe that yields 100g of sauce
Example 3: Selling packs of whole items
You sell a box of cookies and each box contains 10 cookies → link to a recipe that yields 1 box, with the ingredients totalling 10 cookies.
⚠️ You can't link to a recipe for 1kg of sauce and then specify only 100g is used. If your existing recipe is for a larger batch, create a new recipe for the CPU quantity using your batch recipe as a sub-recipe ingredient, specifying the exact amount needed. Edify will calculate the costs and quantities from there.
For Production Planner users:
If you use Production Planner, the recipe must also be setup for Production Planning.
This tells the system which recipe to produce when you set an order to 'production' status.
Linking to Supplier Products
When you link to a supplier product, you define how much of that product is used per CPU sale. This is essential when you break down supplier products and sell them in smaller quantities.
Example 1: Selling as-is:
You buy cases of 12 bottled water and sell them as cases of 12.
CPU product: 12 bottles per case
Link: Supplier product = Still Water, Quantity = 1, Unit Type = Case
The system knows each CPU sale uses exactly 1 case
Example 2: Breaking down products
You buy boxes of 6 wine bottles but sell individual bottles through CPU.
CPU product: 1 bottle
Link: Supplier product = Wine, Quantity = 1, Unit Type = Bottle
The system knows each CPU sale uses 1 bottle from the box of 6
⚠️ Important: Make sure Pack Type, Pack Quantity, and Single Unit Type are set up correctly on the supplier product—these determine what units you can link to. You can only link to Pack Type or Single Unit Type, not to Single Item Volume/Weight and UOM.