When an entry seems to have vanished, it's almost always somewhere it wasn't supposed to be. The three-location check below resolves nearly every "missing entry" report.
01 Which three places should I look first?
- Wrong location. Click the location picker top-right. Switch locations and check Revenue for the date in question.
- Wrong date. Was the entry logged for today when you meant yesterday? Click the calendar on Revenue and walk the dates either side.
- Wrong tab. Was it logged as a product sale when you're looking at the manual entries list? Check both tabs on Revenue.
02 What if the entry is genuinely gone?
If you've checked all three locations and date positions and the entry genuinely isn't there, it was almost certainly never saved in the first place. The usual causes are a browser closed mid-save before you clicked Save, a rare network blip that failed the save silently, or simply confusing it with a different account or staff member's log. Each is detailed below — in most cases the fix is just to re-log the entry.
- Browser closed mid-save. If you typed an entry and closed the tab before clicking Save, it never persisted.
- Network blip during save. Rare but possible — the save failed silently. Re-log the entry.
- You're thinking of a different account / staff member's log. Two-person teams sometimes have this happen.
03 How do I ask you to investigate?
If you're sure the entry was saved and is now missing, email support@nouz.co with the date, approximate amount, and location. We can check server logs for delete or save events around that time and confirm what happened.
04 How do I prevent future losses?
A few small habits prevent almost every "missing entry" report. Wait for the green toast after every save, since it confirms the entry persisted server-side. Glance at the day's total on Revenue afterwards — if it doesn't move, the save failed. And check the location picker before logging multi-location days, especially first thing in the morning. The full list is below.
- Wait for the green toast after every save. The toast confirms the entry persisted server-side.
- Glance at the day's total on Revenue after saving. If it doesn't move, the save failed.
- Check the location picker before logging multi-location days. Especially first thing in the morning.
Was this article helpful?
Your vote helps us decide what to write next.