The things that actually go wrong, and what they usually are.
The app is empty
You signed in fine, and there is nothing there.
No venues assigned. Your account works; it just reaches nothing. An admin ticks your venues in Settings → Team and it fills. See Venue access.
This is the most common first-day problem, and it looks like a broken app rather than a missing setting.
The numbers do not match my POS
Almost always the business day.
Your POS report cuts at midnight. NexReps cuts at 5am for a restaurant, 7am for a club. A Saturday that trades until 2am puts those sales in Saturday; your POS puts them in Sunday.
Neither is broken. NexReps matches how the room actually works. See Key concepts.
A day looks light
Check whether it was closed properly on the POS. A day closed late archives incomplete, and NexReps pulled what was there.
Fix it: Settings → Data → Sync Day. Pick the venue and date, sync. Last 30 days only. See Data.
A venue shows as "down"
The connection to that POS dropped. It does not mean the venue is closed — it means NexReps cannot see it.
You cannot fix this from your settings; POS connections are managed by NexReps. Check status.nexreps.com first — if several venues are down at once, it is not your venues.
My food cost looks too good
It is not good news. It is missing data.
Check Linked on the Food Cost page. If it says 1 of 243 items, your food cost percentage is computed from one dish. Unlinked items contribute revenue and no cost, so the more that are missing, the better the number looks.
Link them on the Menu page.
A recipe costs less than it should
Look for the Incomplete badge under the cost on the recipe list. It means at least one line has no resolvable price, and lines with no price count as zero — so the total is short.
Open the recipe, find the line at $0.00, and price the product — usually by validating an invoice that carries it — or give it the unit weight it needs.
The badge is recursive: a dish is flagged when the hole is inside one of its sub-recipes. See Recipes.
A recipe cost is wildly wrong
Two usual suspects.
Yield. A recipe yielding 4 L divides its cost by four litres. Get the yield wrong and everything using that recipe is wrong by the same factor.
An inverted conversion. 1 L = ? asks how many recipe units are in one purchase unit. Backwards, and the cost is off by a factor of a thousand. If the number is wrong by a suspiciously round multiple, that is why. See Units and conversions.
The same supplier appears twice
MOSTO FOODS and MOSTO FOODS INC. are two suppliers to NexReps and one company to you.
It happens when a supplier prints their name differently on one invoice. Their catalogues split, and Price History shows two short lines instead of one long one.
Catch it in the supplier dropdown when reviewing an invoice — before it exists. See Suppliers.
The same product appears twice in recipes
Two canonical products for one thing — Rice - Basmati and White Basmati Rice — split your recipes and your costs in half.
It happens when a product is created with None of these: create a new canonical instead of picking the one that exists. When you create a product, type the start of its name in Canonical product and pick. NexReps also checks the catalogue every night. See Canonical products.
An invoice failed to scan
Bad photo, usually. Flat, in light, whole invoice in frame. Try again.
An invoice scanned but the lines are wrong
Read the line statuses. Red holds the invoice, orange is worth a look, blue is information, green has nothing to say.
A quantity or a price that looks absurd is usually a pack read wrong. Open the line, Edit the line, and write how the item really arrives — NexReps remembers it for next time. See Reception format.
An invoice will not validate
A red line remains — open it; the reason is written on it. See Reviewing a line.
The total does not reconcile — a delivery fee or a discount on the paper is missing on the screen. Add it with Add charge or Add discount. See Discounts and charges.
I validated an invoice by mistake
The circular arrow reverts it: stock movement undone, status back to Pending review.
The price is not reverted. That is deliberate — you paid it, so it stays as the latest known price. See Invoices.
Push notifications do not arrive
On iPhone: is NexReps on your home screen? Apple does not allow push to a browser tab. Add it via Safari → Share → Add to Home Screen. See Install the app.
Is push enabled on this device? "Enable on this device" is per device, not per account. Your phone and your laptop each need it.
Too many notifications
Everything is on by default, which is wrong for most people.
Daily Report by email and by push are the same content twice. End of Service on twenty venues is twenty buzzes a night.
Turn off what you do not read. A phone that buzzes forty times a day is a phone nobody reads. See Configuration.
Alerts fire every single day
Then the threshold is wrong, not the venue.
A takeout counter and a tasting room do not have the same normal discount rate. Override the threshold on that venue. An alert that always fires is wallpaper.
Everyone sees a different comparison
They should not. The comparison basis is one setting for the whole organization.
Except Weekly and Monthly, which have their own pickers, per user. That is deliberate — those pages are where "against last year" means something. See Configuration.
A new venue has no comparison
It has no last year to compare to. The field is empty rather than invented.
That is correct. An empty comparison is honest; a fabricated one is not.
I lost my 2FA device
Only an admin can reset it. There is no self-service path, on purpose — a self-service path is one an attacker can walk too.
If you are the only admin, contact info@nexreps.com. Expect to prove who you are.
Still stuck
info@nexreps.com. Tell us the venue, the date, and what you expected to see.
Next
Glossary — the words we use.