Troubleshooting & FAQ
Start here when something is not working
Use a safe first-response checklist before changing data, retrying payments, or rebuilding configuration.
Overview
- Most MiniTill problems fall into one of five groups: wrong Business/Store scope, permission/plan restriction, stale/offline client state, an external provider failure, or data/configuration that is valid but incomplete.
- Start with the smallest reversible checks first. Confirm scope, status, connectivity, and the existing record before creating duplicates or deleting anything.
- For payments, orders, stock, loyalty, and accounting syncs, MiniTill often has recovery/retry workflows specifically designed to preserve audit history.
- A visible error message, status badge, retry reason, order/payment ID, or device status is usually more useful than reloading repeatedly.
When to use this
- Use this guide whenever the symptom is unclear or you are deciding whether to retry, recreate, delete, or contact support.
Step-by-step
- Confirm the selected Business and Store.
- Confirm your role and whether the feature is included in the Business plan.
- Read the exact status/error shown on screen.
- Check whether the problem affects one device/user or every device/user.
- For local hardware, check power/network/pairing before changing server data.
- For payments or external integrations, use the existing recovery/retry path before creating another transaction.
- If still unresolved, collect the identifiers and context listed in the Support guide.
Common mistakes
- Do not create a second order, payment, customer, stock record, or supplier document simply because the first one looks stuck.
- Do not delete historical records to make an error disappear.
- Do not force-refresh external-provider actions repeatedly when the result of the first attempt is uncertain.
Troubleshooting
- If you are unsure whether an action is safe to repeat, stop and inspect the existing record/status first.
- If the same problem affects several Stores/devices at once, treat it as a broader service/provider issue rather than reconfiguring each device independently.