Ingredients Sold and What to Buy
Ingredients Sold answers "how much flour, sugar or packaging do the things I sold add up to?" It takes every product sold in the period, opens bundles into the products inside them, opens recipes into their ingredients, and adds it up per ingredient, in the unit you stock that ingredient in. It is on the Reports page, under Sales by Product, and follows the same date range and Channel filter.
How it is worked out
- A bundle sold is replaced by its contents: three gift boxes of two cookies each add six cookies.
- A product with a recipe is replaced by its ingredients, scaled by how many you sold against how many one batch makes. Ten cookies from a recipe that makes twenty use half the recipe.
- Sub-recipes are followed down to what you actually buy. If a cake uses dough and the dough uses flour, the flour is what is reported. Turn off Follow sub-recipes down to what you buy to see the dough instead.
- Each ingredient is added up in its own unit. A recipe that calls for 500 g of flour against flour you count in pounds is converted, so the row reads in pounds.
An ingredient you also sell on its own (a jar of honey, say) is its own row. Sold on its own shows what went out as itself, and In recipes and bundles shows what was used inside other products. Click a row to see which products and bundles each part came from.
A product with no recipe that isn't an ingredient (a mug you resell) has nothing to report. The units are mentioned in a note under the totals so they don't vanish without a word.
What to keep in mind
- This is what the recipes imply, not what left the shelf. A cookie sold from finished stock didn't use flour at the time of the sale; it used it when it was made. The report answers "what do my sales represent in ingredients?" For what was actually drawn from stock, look at stock movements and production runs.
- It uses today's recipes and bundle contents. If you changed a recipe, past sales are counted with the new one.
- Units that don't convert. If a recipe line uses a unit that can't convert to the ingredient's stock unit (11 units of something you count in pounds), the number is used as typed, the row is marked Check units, and a note counts them. Fix the recipe line to correct the figure.
- A recipe that contains itself is stopped where the loop is found, and a note says so.
- Like fulfilment, the report doesn't treat "per run" or "per operator per hour" ingredients differently. They scale with the quantity like the rest.
Export CSV downloads the list in the order shown.
Suggesting what to buy
Turn on Suggest what to buy for the same number of days ahead and Iraca looks forward by the length of the period you chose. If you asked for the last 30 days, the suggestion covers the next 30.
For each ingredient:
Needed = usage in the period, plus your safety margin Buy = needed, minus stock on hand, minus what is already on order
Then:
- The result is rounded up to whole packs if the ingredient is bought by the pack (a 50 lb sack), and to whole units if it is counted.
- Stock on hand is the ingredient's stock in every warehouse except quarantine. On order is purchase orders that haven't fully arrived.
- Ingredients already covered are left out. If nothing needs buying, you are told so.
- Suggestions are grouped by preferred supplier. Ingredients without one are shown in their own group, never hidden.
- Create purchase order opens a draft with that supplier's lines filled in, to review and edit before you save.
The Safety margin adds a percentage on top of the pace you sold at. Use it for supplier lead time or a busy season.
This is a repeat of the last period, not a forecast:
- A promotion in the period will make the suggestion high, and a busy season ahead won't be seen. Edit the quantities on the purchase order before you send it.
- Ingredients already made into finished goods are not counted as stock, so a business that makes to stock may see slightly high suggestions.
- Supplier lead time isn't modelled. The safety margin is the cushion.