Bulk upload
If you have an existing ingredient or consumable list in a spreadsheet, you can import everything in one go rather than adding items one by one. This is particularly useful when setting up Brikly for the first time or when onboarding a new supplier with a large product range.
How it works
- Go to CostingBrik > Ingredients (or Consumables).
- Open the More actions menu (the three-dot button) and choose Bulk upload.
- Click Download template.
- Fill in your items following the template format.
- Upload the completed CSV.
- Review the preview table and confirm.
Brikly checks every row before importing. If any row breaks a rule, the file stops at Validation errors:, which lists each problem by row number, so you can correct the file and upload it again. A file saved from Excel reads correctly, £ signs and accents included.
CSV template columns
Download the template from the import modal to get a pre-formatted file with the correct headers. Here is what each column does:
Required columns
| Column | Description | Example |
|---|---|---|
| name | A clear, descriptive name for the ingredient | Semi-skimmed milk |
| supplier | Supplier name - matched to an existing supplier or auto-created | Brakes |
| cost_per_pack | The price you pay per pack, a number above 0. It may carry your own currency sign (£5.99) but no other | 5.99 |
Measurement columns
| Column | Description | Example |
|---|---|---|
| usage_type | How this ingredient is measured: weight, volume, or unit. If omitted, Brikly infers it from pack_unit | volume |
| pack_size | Numeric size per unit (e.g. 500 for 500ml). Required for weight and volume items | 500 |
| pack_unit | Unit of measurement for the pack size. See accepted units below | ml |
| units_per_pack | Number of individual units in each pack, a whole number of 1 or more. Defaults to 1 when blank | 12 |
Per-unit measurement columns
These columns give the actual weight or volume of each individual unit. Give one of them, never both, of the kind the item is used by: weight_per_unit_grams for a weight item, volume_per_unit_ml for a volume item. They are required for a weight or volume item bought by the count (a pack_unit of each, unit, piece, pieces, pack or packs), such as canned drinks or bottled sauces, and optional otherwise.
| Column | Description | Example |
|---|---|---|
| weight_per_unit_grams | Weight of one unit in grams | 330 |
| volume_per_unit_ml | Volume of one unit in millilitres | 330 |
If you buy Coca Cola in cases of 24 cans and each can is 330ml, set usage_type to volume, pack_size to 24, pack_unit to each, units_per_pack to 24 and volume_per_unit_ml to 330, as in the template's last row. Brikly then knows both the purchase format and the actual volume per serving.
Other optional columns
| Column | Description | Example |
|---|---|---|
| category | Category for organising your ingredient library. A category you don't have yet is created | Dairy |
| brand | Specific brand, if relevant | Yeo Valley |
Always enter your cost_per_pack as the ex-VAT price. This is the price shown on most trade supplier invoices (Brakes, Bidfood, etc.). Brikly uses ex-VAT prices for all recipe costing and margin calculations.
Accepted pack units
| Type | Units |
|---|---|
| Weight | g, kg, oz, lb |
| Volume | ml, cl, l, fl oz, uk fl oz, us fl oz, gal, uk gal, us gal, pt, uk pt, us pt |
| Count | each, unit, piece, pieces, pack, packs |
A bare fl oz, gal or pt is read as your region's.
When you omit usage_type, Brikly infers it from the pack_unit:
- Weight units set
usage_typeto weight - Volume units set
usage_typeto volume - Count units set
usage_typeto unit
Example CSV rows
Here are examples covering the most common ingredient types:
name,supplier,usage_type,pack_size,pack_unit,units_per_pack,cost_per_pack,weight_per_unit_grams,volume_per_unit_ml,category,brand
Flour,Local Supplier,weight,1,kg,1,5.99,,,Baking,Baker's Choice
Milk,Dairy Farm,volume,1,l,12,2.50,,1000,Dairy,
Eggs,Fresh Farms,unit,,,12,4.75,,,Dairy,
Olive Oil,Food Wholesale,volume,500,ml,6,8.99,,,Oils,
Coca Cola (330ml cans),Drinks Supplier,volume,24,each,24,20.99,,330,Cold Drinks,
How each row works
Flour - a weight-based ingredient. Bought in 1kg bags, one bag per pack, at £5.99. Brikly converts this to a cost per gram automatically.
Milk - a volume-based ingredient sold in cases of 12 one-litre bottles. The volume_per_unit_ml of 1000 tells Brikly that each bottle is 1000ml, so it can calculate cost per ml.
Eggs - a unit-based ingredient. No pack size or unit needed - just 12 eggs per pack at £4.75.
Olive Oil - a volume-based ingredient. Bought in cases of 6 bottles, each 500ml, at £8.99 per case. Brikly derives the volume from the pack size and unit.
Coca Cola - a volume item bought by the unit. The pack_unit is each because you buy individual cans, but usage_type is volume because you track drinks by volume. The volume_per_unit_ml of 330 tells Brikly each can is 330ml.
Validation rules
Brikly checks every row against these rules before importing:
| Rule | Detail |
|---|---|
| name and supplier cannot be empty | Every ingredient must have both |
| cost_per_pack must be more than zero | Blank, 0 or a cost that is not a number is refused. Mark a free item as free on the ingredient after uploading, see Free ingredients |
| units_per_pack must be a whole number of 1 or more | Blank counts as 1 |
usage_type must be weight, volume, or unit | If provided, it must be one of these three values |
| pack_unit must be a recognised unit | See accepted pack units above |
| pack_unit must suit the usage_type | A weight item needs a weight unit (g, kg, oz, lb) and a volume item a volume unit (ml, cl, l, fl oz, pt, gal), so weight with ml is refused. Count units (each, unit, piece, pack) are allowed with either, with the per-unit measure (below), and a unit item may use any. The error names the row, for example "Row 3: pack_unit kg is a weight unit but usage_type is volume. Use a volume unit such as ml or l, or change usage_type." |
| Weight and volume items need pack_size + pack_unit | Both are always required for a weight or volume item |
| pack_size must be positive | If provided, it cannot be zero or negative |
| weight_per_unit_grams must be positive | If provided, it cannot be zero or negative |
| volume_per_unit_ml must be positive | If provided, it cannot be zero or negative |
| One per-unit measure per row | Give weight_per_unit_grams or volume_per_unit_ml, not both, and the one that matches the item's usage_type |
| A weight or volume item bought by the count needs its per-unit measure | For example pack_unit each on a volume item needs volume_per_unit_ml |
| Size and measure cells must be numbers | 330ml is refused: write 330 and put the unit in its own column |
- Entering VAT-inclusive prices - always use the ex-VAT figure from your supplier invoice.
- Leaving
pack_sizeandpack_unitblank for weight or volume items - Brikly needs these to calculate cost per gram or ml. - Using an unrecognised unit like "litre" instead of "l" - check the accepted units list.
Preview and confirmation
After uploading your CSV, Brikly shows a preview table with all parsed rows. Check that:
- Names and suppliers look correct.
- Pack sizes and units are what you expect.
- Cost per pack values are right.
- Weight and volume per-unit values appear where expected.
If everything looks good, click Upload ingredients to confirm. Brikly then processes each row and reports back under Upload completed:
- "N items added successfully" - the number of ingredients created.
- "N items restored (previously removed)" - items you had previously removed that have been brought back, with their supplier price updated from the CSV. This line only appears when a row restored something.
- "N items skipped (duplicates)" - rows that matched something already in your library and were not imported. See Duplicate handling below.
- Some items had errors: - any rows that failed while saving, with the row number and reason. A row that fails does not stop the others, and nothing from a failed row is saved.
Duplicate handling
Brikly checks each name in your CSV against your existing library (case-insensitive) and decides what to do with the row from what it finds:
- The item is already in your library. The row is skipped. Nothing is created and nothing is overwritten, so an import cannot quietly change a price you have already set.
- You removed the item earlier. The row brings it back rather than adding a second copy. The item is restored in place, its supplier offering is restored with it and repriced from your CSV, and any recipe still holding a line for that item starts costing again.
A restored item keeps the details your CSV does not carry: its own category, unless the CSV names one, and, for ingredients, its density and the weight or volume it already had recorded per unit. An ingredient you had marked as Free comes back free, so it keeps showing as Free rather than taking the price in your CSV. A consumable keeps the base unit it was set up with, and comes back uncategorised where the category it used to sit in has since been deleted. To change a restored item's weight or volume per unit, edit it after the import rather than relying on the CSV columns.
Two situations are still skipped even though the item is not live:
- The item is location-specific rather than shared. Brikly leaves the row alone instead of creating a shared copy of something that only ever existed at one site.
- The supplier link is still live. The item was removed but its link to the supplier named in your row was not, so there is nothing for the import to restore.
Skipped rows are counted separately in the results summary. They are not treated as errors.
Consumable files
The consumables upload has its own template, from Download template in its window. Its columns are name, supplier, units_per_pack, cost_per_pack, category, pack_size (a description, such as "box of 500"), tax_inclusive and tax_rate, and the same rules apply to cost and count:
- name, supplier and cost_per_pack are required.
- cost_per_pack must be a number above 0, and may carry your own currency sign but no other.
- units_per_pack is a whole number of 1 or more, and counts as 1 when blank.
- Put
yesin tax_inclusive when the cost includes VAT, with tax_rate as a decimal (0.20 for 20%). A blank tax_rate uses your region's standard rate. Brikly takes the VAT off the cost per item. - category is matched to your existing consumable categories. A category you don't have is skipped.
Suppliers
Suppliers referenced in your CSV are matched by name. If a supplier does not already exist in your Brikly account, it is created automatically during the import. You can review and update supplier details later in CostingBrik > Suppliers.
After importing
Once your import is complete:
- Review categories - check that ingredients are in the right categories. To file several at once, tick them on the Ingredients list and use Move to category (see Moving ingredients to a category).
- Check measurement types - Brikly sets each ingredient's base unit from its
usage_type: grams for weight, millilitres for volume, one item for unit. See Managing units. - Link to recipes - your imported ingredients are now available in the recipe builder.
- Verify pricing - spot-check a few items to make sure pack costs and per-unit costs look correct.
If you have hundreds of ingredients, consider importing in batches - one category or supplier at a time. This makes it easier to review and catch any issues.