You're at shift close, everything's filled in, you tap Close Shift — and instead of a happy confirmation, a red error dialog pops up saying "Internal Server Error" or "Failed to close shift". Before you panic, here's what to do.
Your data is safe
All sales for the day are already saved in the database. Closing the shift is just the final step — even if this step fails, you haven't lost any sales. The shift just stays open until the close succeeds.
Try this first
Check your internet connection
The most common cause is a weak Wi-Fi or mobile data connection. Close Shift requires a working connection to save inventory counts, print the report, and email the summary. If your connection is shaky, Amari may time out.
Open another tab and try loading any website. If that's slow or fails, fix your internet before retrying.
Wait 30 seconds and try again
Server hiccups sometimes resolve themselves. Wait a bit, then tap Close Shift again. The inventory counts you entered should still be in the form — you don't need to re-enter them.
Reload the page and re-enter
If retrying doesn't work, pull to refresh (or press F5 on desktop), navigate back to the Close Shift page, and enter the ending cash + inventory counts again.
Before reloading, if you've typed a lot of inventory counts, write them down on paper first. A reload clears the form. Losing 30 minutes of counting is worse than a 1-minute delay from writing them down.
Check if the shift actually closed
Sometimes the shift closes successfully but the response gets lost on its way back to your browser — so you see an error even though Amari already saved everything. Before retrying from scratch:
- Go to the POS page
- If it shows Open Shift again (with the starting cash field), the old shift actually closed. You're done.
- If it still shows your current shift as open, it didn't close. Retry.
Less common causes
Shift already closed
If another staff member already closed the shift from a different device, you'll see a specific error: "Shift is already closed". This isn't a bug — the shift ended successfully, you just missed the notification. Reload the POS page; it'll show Open Shift instead.
Too many inventory items counted
We've fixed this one before, but historically closing a shift with 30+ inventory items in one batch could exceed the server's timeout. If you're hitting a timeout consistently, email support and we'll investigate — there may be a new bottleneck.
Printer trying to print and failing
Closing a shift also prints the shift report. If the printer is offline or not paired, Amari asks you to connect it. If you decline or dismiss, the close still succeeds but no report prints — you can reprint later from the Inventory page.
What NOT to do
- Don't try to open a new shift without closing the old one. Amari only allows one open shift per branch at a time. You'll just get another error.
- Don't tap Close Shift repeatedly. If it failed once, hammering the button doesn't help. Wait and retry after 30 seconds.
- Don't log out and back in as a workaround. The shift is branch-scoped, not user-scoped. Logging out does nothing for the shift.
If nothing works
Email support@amaripos.com immediately with:
- The branch name
- The exact error message (screenshot is great)
- What time you tried to close
- Your device (iPad, Samsung Tab, etc.) and browser
We can usually close the shift manually from the admin console within a few minutes. Your data is safe in the meantime — just don't process more sales on the same shift while you wait (the numbers will be off).
Related articles
- Closing a shift
- Cash reconciliation — why numbers don't match