Every time MenuDock talks to your till system, whether pulling your catalogue in or pushing an order out, it records the result in a log. The log is how you check that syncing is working and find out what went wrong when it isn't. This article explains where the log lives, how to read it, and what to do about an error.
Where the log lives
Each POS integration has its own logs page at /admin/settings/integrations/[name]/logs, where [name] is the system, for example square. The page lists the most recent events first, with a filter to show all events, only successes, or only errors.
Reading a row
Each row is one attempt. It records:
- Status — success or error.
- Action — what was being done, such as a catalogue sync or an order push.
- Message — a short note. On a success that's usually a count, like "Synced 12 products". On an error it's the reason the attempt failed.
- Time — when it happened.
The newest events sit at the top, so after running a sync you can refresh the page and read the result straight away.
When the log is empty
An empty log is normal and isn't a fault. It just means nothing has run yet for that integration: no sync has been triggered and no order has been pushed. Once you connect a POS and run your first sync, or take your first online order while connected, rows start appearing. If you expected activity and see none, check that the POS is actually connected on the Integrations page and that you're looking at the right branch.
What to do about an error
An error row means one attempt didn't complete. The first thing to do is read its message, which usually names the cause. Common patterns:
- "not connected" or a credentials error. The link to your till has dropped or was never finished. Reconnect from the Integrations page.
- A message pointing at a specific item. A single product failed to import while the rest went through. Check that item in your till for an odd name, price or missing variation, then re-sync.
- A timeout or network message. A temporary blip at the POS end. Re-run the sync; if it keeps failing, the POS service may be down.
A failed order push is worth knowing about but not urgent: the customer's order was never at risk, it still landed in your Orders and on the mobile app. The push to your till simply didn't happen, so that one order won't appear on the Square side until you handle it manually.
Errors come to you by email too
You don't have to watch this page. When a POS attempt errors, MenuDock emails the store admin so you find out without checking. To avoid flooding your inbox, repeated errors of the same kind are held back to roughly one email an hour.
Related articles
Need a hand?
If an error message isn't clear and re-syncing doesn't fix it, email support@menudock.co.uk with your store name, the integration name, and the exact message from the failed row. That's the fastest way for us to pin it down.