Reading the dashboard

Reading the dashboard

The app opens on the Dashboard: one card per instance with live metrics, day-on-day variances and every routine action one click away. This page explains each number, the variance arrows, the inactive states, and the Perform Operation popup used across the Operations pages.

The instance card

Header: instance name (click to open its configuration), provider, environment badge (blue Sandbox / green Live) and state badge (Draft/Connected/Active/Paused). A Draft card shows a single Finish Setup button instead of the stats.

The eight stat cards

Each is a mini-card with an icon, the count, and (where meaningful) a day-on-day variance in the top-right. Every stat card is a link - click it to open the exact filtered list behind the number.

Card Counts Variance means
To Send eligible confirmed orders not yet at the 3PL - including, in manual mode, orders waiting for a person new eligible orders today vs yesterday
At 3PL orders sent and in progress at the warehouse - (point-in-time)
Despatched orders the 3PL despatched today despatches today vs yesterday (green up = shipping more)
On Hold sent orders whose 3PL status maps to Hold - (point-in-time)
Products product bindings queued or failing to push bindings added today vs yesterday
Open ASNs announced/pending inbound notices not yet received ASNs raised today vs yesterday
Warnings operations that completed with warnings today (e.g. un-batched despatches) red up = more warnings than yesterday
Errors active (unacknowledged) errors in the Sync Log new errors today vs yesterday - down in green is a good morning

Variance arrows compare today's activity with yesterday's; a dash means no change (or a point-in-time metric where "since yesterday" has no meaning).

Inactive cards. A stat whose function is disabled on the instance - order sync off, product sync off, ASNs off, or a capability the provider lacks - greys out, loses its click, and shows an Inactive badge. The dashboard never shows a live-looking zero for something that cannot happen.

Below the stats: the last inventory sync (click for the sync reports) and the last status poll time.

Card actions

  • Perform Operation (Ops role and above) - dropdown of every operation the instance supports: Push Orders, Check Statuses, Inventory Sync, Poll Returns, Match Products. Entries appear only when the matching sync switch/capability is on.
  • Configure - opens the instance form (Read Only users can look; only Admins can change).

Reading the dashboard - a morning routine

Errors card red with 3? Click it - the filtered Sync Log opens; two are last night's timeout, one retry clears both; the third is an unmapped carrier - add the mapping, retry, acknowledge nothing. Warnings 1: an un-batched despatch - fine, the fallback did its job, the batch will reconcile at tonight's inventory sync. On Hold 2: click through, both "Error - No Stock", already on the replenishment list. To Send 4 with the up arrow: yesterday's evening orders - Perform Operation > Push Orders if you cannot wait for the next scheduled push. Total time: about two minutes, no menu-diving.

    • Related Articles

    • Dashboard

      The Dashboard is the first screen you land on when you open Amazon Seller Sync. It answers two questions quickly: how much of your catalogue is connected to Amazon, and when the app last spoke to Amazon on your behalf. At a glance The tiles across ...
    • Buy Box performance

      The Buy Box is the "Add to basket" position on an Amazon product page. When several sellers offer the same product, Amazon awards that button to one of them, and the overwhelming majority of sales on that listing go to whoever holds it. If you do not ...
    • Automation and schedule

      Most of what the app does happens without you. This page sets out precisely what runs on its own, what triggers it, and what each one needs in order to run at all. It is worth reading once, because "why has nothing happened yet?" is almost always ...
    • Install the app and assign roles

      Step 1 - Install Install LataSys: 3PL Connector from the Apps menu. The module depends on Sales, Inventory (with delivery), Purchase and Expiration Dates - Odoo installs these automatically if they are missing. After installation a new 3PL Connector ...
    • Status mappings

      Status mappings 3PLs report order progress in their own vocabulary (RDY2PK, PICKIP, COMPLT…). The status map translates each raw code into a human label and one of the connector's canonical statuses: Received > Processing > Picked > Packed > ...