> For the complete documentation index, see [llms.txt](https://docs.foodcore.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foodcore.io/ingredients/import.md).

# Import from CSV or Excel

If you've already got your ingredients in a spreadsheet or another tool, you don't need to re-enter them all by hand. FoodCore's import tool lets you bring them in all at once, preview what's coming in before it lands, and resolve any conflicts field by field.

## Supported formats

FoodCore can import ingredients from:

* **CSV** — a plain comma-separated file, typically exported from Excel, Google Sheets, or any accounting, stock management, or kitchen management system.
* **Excel** (.xlsx) — import directly from an Excel workbook. If your file has multiple sheets, FoodCore will ask which sheet to use.

## Prepare your file

Before importing, check your file has at least these columns:

* **Name** — the ingredient name
* **Unit** — the measurement unit (g, kg, ml, unit, etc.)
* **Cost per pack** — the price you pay for the pack
* **Pack size** — how many grams/units are in the pack

Other columns — category, supplier, nutrition values — are optional but will be imported if present. Column headers don't need to match exactly; FoodCore will ask you to confirm the mapping during the import process.

## Run the import

1. Go to **Ingredients** in the left sidebar.
2. Click **Import** (next to the + New Ingredient button).
3. Choose your file format — CSV or Excel — and **upload your file**.
4. FoodCore reads the file and shows you a **column mapping screen**. Check that each column in your file is matched to the correct FoodCore field. If the auto-mapping looks wrong for any column, use the dropdown to correct it.
5. Click **Continue** to move to the import preview.

## Review the import preview

The preview shows every row in your file as it will appear once imported. Take a moment to scan through it:

* **Green rows** — new ingredients that don't currently exist in FoodCore. These will be added.
* **Yellow rows** — ingredients where FoodCore has found a possible match with an existing record (same or very similar name). These are potential conflicts.
* **Red rows** — rows with missing required data (usually no name, or no unit). Fix these in your file and re-import.

## Resolve conflicts

For any yellow (conflict) row, FoodCore shows you what's currently in the system and what's coming in from your file, side by side. For each field, you choose:

* **Keep existing** — the current FoodCore value stays unchanged.
* **Use imported** — the value from your file overwrites the existing record.

You make this decision field by field, not just for the whole row. So you might keep the existing allergen data but update the cost per pack with the imported value — useful if your spreadsheet has fresh prices but you've already set allergens carefully in FoodCore.

If you're confident all incoming data is correct and up to date, you can click **Use all imported** to accept all incoming values for every conflict at once.

## Confirm and check the summary

Once you've resolved all conflicts, click **Confirm import**. FoodCore processes the file and shows you a summary:

* How many ingredients were added
* How many were updated
* How many were skipped (red rows with missing data)

If anything looks off, check the skipped rows — they'll be listed with a reason for each one.

## After importing: what to do next

There are two things you should always do after any import, regardless of how clean your data looks.

**Set allergens manually.** FoodCore does not import allergen data from most file formats, even if your spreadsheet has a column for it. This is a deliberate safety measure — allergen declarations are too important to risk a mapping error during import. After the import completes, work through your newly imported ingredients and set the allergen status on each one. See [Setting allergens on an ingredient](https://docs.foodcore.io/ingredients/allergens.md) for how to do this.

**Check that costs are correct.** Scan the imported ingredients and verify that the cost per pack and pack size look right. A common issue is pack size being imported in the wrong unit (kilograms instead of grams, for example), which will make all your recipe costs look wildly different.

{% hint style="warning" %}
FoodCore helps you organise and manage the information you need, but you should always check official guidance or speak to your local authority if unsure.
{% endhint %}

## Dealing with duplicates after import

If your file contained ingredients that were already in FoodCore under slightly different names, you may end up with duplicates that slipped past the conflict detection. After a large import, it's worth running a quick duplicate check. See [Fix duplicate ingredients](https://docs.foodcore.io/ingredients/duplicates.md) for how to find and merge them.

## What's next

* [Fix any duplicates that came in](https://docs.foodcore.io/ingredients/duplicates.md)
* [Set allergens on your imported ingredients](https://docs.foodcore.io/ingredients/allergens.md)
* [Add an ingredient manually](https://docs.foodcore.io/ingredients/add-ingredient.md)
* [Create recipes using your ingredients](https://docs.foodcore.io/recipes/create-recipe.md)
