The plain-language guide
Why your spreadsheet doesn't have to match our template.
Two testers spent half their onboarding session renaming columns in a spreadsheet before they gave up. The fix wasn't a better template. It was asking one question before anything imports.
The short answer
Keep your own column names. When a file's headers don't match the template, ForeFlux guesses which is which. Branch Name becomes Name. SKU becomes Product ID. It shows you every guess, with the first row of your data next to it, before a single row gets read as data. You confirm or fix the guess. Only then does anything import.
What you do
- Upload or paste your sheet as it is. Do not rename any columns first.
- Check the guesses. Under Match your columns, each template column has a dropdown with ForeFlux's guess. The value from the first row of your file sits next to it.
- Fix any wrong guess from its dropdown, then press Use these columns.
- Read the Left out list. Columns that match nothing, like a notes column, are listed by name. They do not import.
If the guesses are all wrong, or your file already uses the template's names, press Keep the file's own columns. Your grid stays exactly as it was.
A worked example
A branches sheet has these headings: Branch ID, Branch Name, Address, Opened, Days Open, Hours, Floor Area, Staff. The template wants Branch ID, Name, Opens, Closes, Open days. ForeFlux makes these guesses:
| Your column | Template column | Tier | |
|---|---|---|---|
| Branch ID | → | Branch ID | exact |
| Branch Name | → | Name | synonym |
| Days Open | → | Open days | same words |
| Address, Opened, Hours, Floor Area, Staff… | → | left out | no match |
You check that "Branch Name" holds names and "Days Open" holds days, then press Use these columns. Address, Floor Area and Staff stay in your own file and are not imported.
A required column with no match does not stop the import. It comes in empty and tinted, and you type the values into the grid afterward.
Why it works this way
Two testers spent half their setup renaming columns by hand in Sheets, and neither imported a row. So ForeFlux now asks which column is which before anything imports.
For the curious: how the guesses are made
ForeFlux tries three kinds of match for each template column, in this order:
- Exact match, loosely spelled. The same tolerance the header check already grants: case, extra spacing and column order. A file that would have passed anyway is never asked anything.
- Same words, different order.
Days Open,open_days, andOpen daysall fold to the same set of words, so this tier catches formatting differences a strict match would miss. It still counts as a guess, not a pass, because the header check itself would have refused it. - A synonym table.
Branch Name,Outlet, andStoreall mean the header called Name.SKU,Item Code, andProduct Codeall mean Product ID.Unit CostandBuying Priceboth mean cost_price. One flat table, shared across every import screen, because "name" means the same thing on a branches file, a products file, or a suppliers file.
A column is only ever claimed once. If two template columns could plausibly want the same file column, the earlier one, checked first in template order, gets it. A synonym guess on one field can never steal an exact match that belongs to another.
Pasted rows get the same question. ForeFlux used to decide whether a pasted first row was a heading by checking whether two cells sat in the same position as two template headings. A real sheet often had only one, so its heading row was read as data. Now a cell counts as a heading when it matches any template heading or a known synonym, wherever it sits in the row.
What ForeFlux does
Column matching runs on every bulk import: branches, products, suppliers, sales history and stock counts. It only decides which of your columns is which. It does not change any numbers, and the preview and the forecast work exactly as before. The rule is the same everywhere in the product: we suggest, you decide. A guess is not used until you confirm it.
Questions owners ask
Past the basics.
What if none of my columns match?
You pick from a dropdown, one per template column, with the first row of your file shown beside each guess so you can check it before you commit. A required column with no match still imports. It lands empty, and you fill it in on the grid afterward. Nothing is refused outright.
What happens to columns I don't need, like a notes or floor-area column?
They're listed as left out, by name, so you can see nothing silently vanished. They're dropped from the import, not read as data and not flagged as an error.
Does this work if I paste rows instead of uploading a file?
Yes. Pasting used to be riskier. A heading row with your own names could be read as a row of data, so "Branch ID" would import as a real branch. Now a pasted sheet gets the same question as an uploaded file.
Bring your own spreadsheet, keep your own names
Know what you need, before you need it.
The demo needs no signup and no card. It is the real product running on demo data.
Join the waitlist Open the order list