Sales Settings
Checking your sales connections
The first screen to open when sales are missing, and what each status means.
Last updated October 14, 2026
The Connection Status Report lists every tribe and the state of its sales integration. When figures look wrong, this is the first place to look — a silently broken connection is far more common than a broken report.
The columns
| Column | Tells you |
|---|---|
| Last sync | When Gorilla Dash last talked to the system. |
| Last transaction | When it last received anything. |
| Last sale | When the most recent sale arrived. |
| Last quote | When the most recent estimate arrived. |
The statuses
- Last sync successful — working.
- Last sync failed — open it and read the error log.
- Sync in progress — running now.
- Last sync timed out — usually the point of sale being slow or unreachable.
- No integration configured — nothing has been set up for this tribe.
- Never synced — configured but has never successfully run.
- No connection — no connection record at all.
Investigating one
Open a tribe for its connection status, its Error log and its credentials, where the API details can be revealed and copied. An integration whose keys Gorilla Dash keeps to itself, such as CoreBridge EVO, shows a dash instead of its API key, because the key is never sent to your browser. Clear Errors empties the log — do that after fixing something, so the next failure is obvious rather than buried.
When a tribe has more than one connection
A tribe can be connected to several platforms at once — a point of sale and an ordering platform, or an old system alongside its replacement. One of them is the tribe's default, and that is the connection its sales sync actually runs against.
This screen shows a selector on a tribe's row whenever there is a choice to make: either the tribe has more than one live connection, or it has one that is not yet its default. That second case is the row showing No connection, and the selector is how you fix it. Switching asks you to confirm first, because it changes where that tribe's figures come from from the next sync onwards.
You usually will not have to set this. Connecting a platform to a tribe that has no working default makes it the default automatically, so a newly connected tribe starts syncing that night rather than waiting for somebody to notice. A default that is already working is never replaced by a new connection.
Make it a routine
Scan this screen weekly and sort by last sync. A connection that broke a fortnight ago has already put a hole in the reports that everybody will argue about later — and re-syncing usually only reaches back so far, so the sooner it is caught the more of the data comes back.
If a sale is missing but the connection is healthy
Check that the order reached a status you have mapped as a sale. An unmapped status is not a failure — Gorilla Dash simply does not know it means sold.