Setting Up CPU Products
Manage your CPU product catalogue in Edify β add products, allocate them to sites, set pricing, and link each product to its source so Edify can track stock and COGS.
Every CPU product is either:
Something you make at the CPU β linked to a recipe
Something you buy from an external supplier and resell β linked to a supplier product
Both paths need a link. The link is what tells Edify what stock to deduct when a CPU order is fulfilled. The setup itself is similar for both; what changes is what you link to and how Edify uses that link.
Adding a CPU Product
Navigate to CPU β Product List
Click Add new product
Fill in the product details (see field guide below)
Click Save Changes
Find your new product in the table
Click the text in the Customers column
Untick any sites who shouldn't be able to order this product
Click Save
π‘ Note: New products are automatically assigned to all active sites by default, so remember to adjust customer allocation if needed.
CPU products can't be added in bulk via the product list page. If you need to load a lot of products at once, contact the Customer Support team and they'll help.
Field Guide
Set up CPU products around how sites buy from you, not around how the product gets made or how you buy it in. The CPU product describes the sellable thing. The recipe or supplier product behind it is described separately.
Field | Explainer |
Product Name | Name of the product |
Availability | Status of the product |
Supplier Product Code | A unique identifier |
Product Class | The class of this product |
Product Category | The category of the product |
Pack Type | How customers buy the product β Case, Each, Box, Bottle, etc. |
Pack Quantity | How many units come in one pack. A single loaf of bread = |
Single Unit Type | Only needed if Pack Quantity is more than 1. What's inside the pack β bottles, cookies, sleeves, etc. |
Single Item Volume / Weight | The size of each individual unit (500ml, 1kg, etc.). Only needed if sites use this product in recipes or stocktake in that unit |
Unit of Measure | The UoM for the single item volume or weight |
Sale Price | What a customer pays for the product unless custom pricing is set up at customer level |
Tax Rate | If tax applies, set the rate here |
Linked Recipe | The recipe that produces this product (for things you make at the CPU) |
Linked Supplier Product | The supplier product behind this one (for things you buy in and resell) |
Lead Time | A legacy field β always set to |
How Pack Type, Pack Quantity & Single Unit Type Work Together
These three fields define how the CPU product is sold to sites β they apply whether the product is made at your CPU or bought from a supplier.
Pack Type is the outer container customers order in (Case, Box, Each, Bottle).
Pack Quantity is how many smaller units are inside.
Single Unit Type is what those smaller units are.
Single Unit Volume/Weight & UoM is how much one of the smaller units weighs
When You Don't Need Volume / Weight | When You Do Need Volume / Weight |
If sites just sell the product as whole units (a cookie or a bottle), there's no need to set a volume or weight on each unit. It's irrelevant to how they use the product. | If sites use the product as a recipe ingredient by weight or volume, or stocktake by weight/volume, then the size of one single unit matters. |
π‘ Examples
A box of 12 cookies you bake in-house:
Pack Type: Box
Pack Quantity: 12
Single Unit Type: each
A piece of flapjack you sell individually:
Pack Type: Each
Pack Quantity: 1
Single Unit Type: each
A pack of 500g of a slaw you produce on site:
Pack Type: Pack
Pack Quantity: 1
Single Unit Type: Pack
Single Unit Volume / Weight: 500
UoM: g
Linking CPU Products
Every CPU product must have a link β either to a recipe or to a supplier product. The link is how Edify knows what to deduct from stock when an order is fulfilled or when production is recorded in the Production Planner.
To set the link, go to CPU β Product List β Edit on the product, and use the Linked Recipe or Linked Supplier Product dropdown.
Can't find what you're looking for?
Recipes must be assigned to the CPU site and have 'count in stocktake' ticked.
Supplier products must belong to a supplier that's assigned to the CPU, and the product itself must be active.
π The golden rule: the linked unit should always describe one Single Unit of the CPU product β never the whole pack. Edify multiplies the linked unit by the CPU's Pack Quantity automatically on every sale.
Three pitfalls that cause most of the problems
Pitfall 1: Linking or yielding to the pack, not the Single Unit
Both the supplier-link and the recipe link are asking about one Single Unit of the CPU product.
People often link an entire pack or bulk quantity instead and end up with COGS wrong by 12Γ, 500Γ, or whatever the Pack Quantity happens to be.
π₯£ Recipe example
You sell a box of 12 cookies.
The wrong way: Make a recipe that yields 12 cookies (1 box) and link it.
What goes wrong: Edify multiplies the recipe yield by Pack Quantity (12), so it deducts ingredients for 144 cookies β 12Γ too much.
The fix: Recipe yields 1 cookie. Edify multiplies by Pack Quantity (12) and deducts exactly 12 cookies' worth.
π Supplier product example
You sell Lemonade as a 12-pack of bottles
The wrong way: On the link, enter 12 and select Bottle or enter 1 and select Pack
What goes wrong: Edify multiplies your link by the CPU Pack Quantity (12), so it deducts 144 supplier bottles per pack sold β 12Γ too much.
The fix: Enter 1 and select Bottle. One Single Unit of the CPU = 1 supplier bottle. Edify multiplies by Pack Quantity (12) and deducts exactly 12 supplier bottles.
Pitfall 2: Incorrect Supplier Product Setup
When you link a CPU product to a Supplier product you can only link to Pack Type or Single Unit Type β you can't link to the Single Item Volume / Weight.
β
So, to be able to link correctly you should only set two pack levels on the supplier product: the outer pack and the single unit.
If a product has three levels (e.g. Box > Sleeve > Each or Pack > Tray > Each), people often try to capture all three in the supplier fields. The problem is you then can't link to 'Each'.
π Example
You sell a tray of 10 flapjacks.
β
You buy the flapjacks in a box of 50. Inside the box, the flapjacks come in 5 trays of 10 β and your sites want to count by the trays at stocktake.
The wrong way: You set the Supplier Product up as:
β Pack Type = Box
β Pack Quantity = 5
β Single Unit Type = Tray
β Single Item Volume / Weight = 10 eachWhat goes wrong: You can now only link the CPU Product to either 'Box' or 'Tray'.
Link to 'Tray' Edify deducts 10 trays of supplier product per CPU tray sold = 100 flapjacks deducted per CPU sale
The right way: Set the Supplier Product up as:
β Pack Type = Box
β Pack Quantity = 50β Single Unit Type = Each
And utilise 'Alternative Unit of Measurement' to setup the Tray as a countable unit in a stockake.
Pitfall 3: Incorrect CPU Product Setup
Edify multiplies your link by CPU Pack Quantity on every sale, so Pack Quantity needs to be the number of single units in the pack β not the number of trays, sleeves, or layers.
If a CPU product has three pack levels (e.g. Box > Sleeve > Each), people often try to capture all three. The maths then comes out short by whatever's hidden in the middle level.
π Example
You sell a box of 500 disposable cups to your sites. Inside the box, the cups come in 10 sleeves of 50 β and sites want to count by the sleeve at stocktake.
The wrong way: CPU Product set up as:
Pack Type = Box
Pack Quantity = 10
Single Unit Type = Sleeve
Single Item Volume / Weight = 50 eachWhat goes wrong: You link to '1 each' of the supplier product. Edify multiplies by CPU Pack Quantity (10) β only 10 cups deducted per box sold (should be 500). 50Γ too little.
The right way: CPU Product set up as:
Pack Type = Box
Pack Quantity = 500
Single Unit Type = Each\
Then use Alternative Unit of Measurement to set up Sleeves as a countable unit for stocktake for the sites.
π‘ Where to find Alt UoM for CPU products: it doesn't live on the CPU product page. Go via Suppliers & Products β the CPU supplier β Edit Product. Most fields will be greyed out (they're set on the CPU product page), but the Alt UoM field is editable here.
Editing & making products unavailable
Editing a CPU product
CPU β Product List, search for the product, click Edit, make your changes, Save Changes.
Making a product unavailable
Edify doesn't allow permanent deletion of CPU products β historical orders and reports would break. Instead, change the product's Availability to Unavailable. It won't appear on new orders, but historical records stay intact. If the product was used in any recipes, remember to replace it there too.





