Skip to main content

Import your batch history

Use the guided import to bring in your production history from any CSV or Excel file, fill in the two-sheet import template, or use the quick CSV import for files already in the batch format.

There are three ways to bring batches into FourFoxes in bulk. All three start from Setup in the top navigation, under Import.

The guided import (admin or owner) is built for moving your history in from any spreadsheet. Your column names do not need to match ours.

  1. Open Import data from the Setup menu.
  2. Under Import your data, choose your CSV or XLSX file, up to 25 MB or 50,000 rows, and click Upload file. Older .xls files are not supported; re-save as .xlsx or .csv.
  3. If your workbook has more than one sheet, pick one and click Use this sheet. Check the header row FourFoxes detected, or click Pick a different row, then click Looks right to parse the file.
  4. On Review your rows, check any rows held for review, then click Continue to product matching.
  5. On Confirm your products, check how rows were grouped into products, fix any we got wrong, and give every product a type. Then click Continue to column mapping.
  6. On Map your columns, check which of your columns fills each field, look at the preview, and click Confirm mapping & continue.
  7. On Import your batches, check how many batches will be imported and click the Import button. Nothing is saved until you do.

The Import complete page shows batches committed, products and product types created, batches skipped because they were already imported and unchanged, and rows quarantined for review. Products are never created silently from a name; you confirm each one. Re-running the same file is safe: unchanged batches are skipped, and a batch whose values changed is set aside for review instead of overwritten. Historical rows do not trigger compliance alerts, and imported batches draw no ingredient or packaging stock. If your account has a pH CCP and the import carried pH values, you can click Generate pH monitoring records from this import to backfill them. That step is optional, and those records cannot be edited or deleted afterwards.

Would rather not do it yourself? Choose your file and click Have us set it up instead. Your file comes to us and we set up your products and batches for you.

The import template. On the Import data page, click Download a starter template (.xlsx). It has two sheets, Batches and Packaging, and the Packaging sheet is optional. Fill it in and upload it under Already filled in our template? with Upload filled template. A filled template skips the header and column steps: you confirm your products and it imports. Each row's Batch Key becomes its batch code. Packaging rows are saved as packaging runs; if you leave the Packaging sheet out, a packaged count goes to the batch's amount produced.

The quick CSV import is for a CSV that already matches the FourFoxes batch format. Open Quick CSV import from the Setup menu. It is in the menu for every role except Production Team. The CSV takes columns like product_name, fermentation_start (or production_date), packaging_date, batch_code, batch_ph, batch_condition, batch_yield, and general_notes, up to 5 MB and 5,000 rows. Dates are YYYY-MM-DD. The page lists every column and a Download a starter CSV link. If a batch code already exists for that product, the batch is updated, and blank cells leave stored values alone. The upload runs in the background; rows that fail come back in an error CSV you can download for 24 hours, fix, and re-upload.

On the Free plan, imported batches count toward your 5 batches a month, but an import is never blocked by the limit.

Guided import: Map your columns Step 4 of 5 of the guided import. Each FourFoxes field, such as Packaging date and pH, has a dropdown showing which spreadsheet column fills it, with Condition left as Ignore / unmapped. A Confirm mapping & continue button sits at the bottom. Step 4 of 5 · Map columns Map your columns Each field below pulls from one source column. We pre-filled our best guess. Mapped fields Suggested by header matching Fermentation start (production date) Start Date Packaging date Bottled On pH Final pH Condition (good / bad) — Ignore / unmapped — Actively fermenting — Ignore / unmapped — Yield Bottles Notes Notes Confirm mapping & continue 6
Map your columns: check which spreadsheet column fills each field, then confirm.
One guided import at a time

Each account can have one guided import in progress. Opening Import data again resumes where you left off rather than starting over. To start fresh, click Discard this import.

Related