Admin
Two tools. One fixes a day your POS got wrong; the other loads recipes in bulk.
Sync Day
If a day was closed late on the POS, the archived data may be incomplete.
Your POS archives a day when it closes it. Close it late — or not at all — and what NexReps pulled is partial. The day looks light, and it is not the room's fault.
Pick the venue and the date, then Sync. NexReps goes back to your POS and pulls that day again.
Limited to the last 30 days.
When to use it
When a day looks wrong and you know why.
A manager forgot to close out. The POS was down at 4am. A day shows sales that stop at 11pm on a night you traded until 2. Sync it and the numbers come back.
Not for a day that is simply bad. If Tuesday was quiet, syncing it will return the same quiet Tuesday. This fixes missing data, not disappointing data.
What it touches
Everything downstream. Sales, product mix, checks, FOH, food cost for that day — all of it recomputes from the fresh pull.
The forecast learns from it too: a day corrected today improves the prediction for that weekday from then on.
Recipe / Preparation Import
Bulk import recipes and preparations from a CSV.
Fuzzy matching against the global ingredient catalog; manual review for unmatched items before commit.
Import from CSV walks you through it: upload, preview, review the matches, commit.
The review step is the point
NexReps matches your CSV rows to ingredients that already exist. Some match cleanly. Some do not.
The unmatched ones are yours to resolve — pick the right ingredient, or create it. Nothing is committed until you have been through them.
Skip the thinking here and you get recipes pointing at the wrong ingredient, which means a food cost that is wrong in a way nothing will ever flag. See Ingredients.
When to use it
Setting up. Moving a menu across from a spreadsheet, or from another system.
For one recipe, the Recipes page is faster. For a hundred and fifty, this is why it exists.
Next
Troubleshooting — when something is not right.