The bell at the bottom of the sidebar opens the notifications panel. It is the one place in Fiftify that comes to you rather than waiting to be opened.
What arrives here
Section titled “What arrives here”New orders. When a connected channel sends an order, a notification names it and its value — New Order #1002 · USD 84.00 via Shopify — and links straight to the order.
Sync results. When a channel finishes a sync, a notification reports what happened — Sync Complete: Listings · fiftify-demo-store: 24 succeeded, 2 failed.
Each notification is marked read once you have opened it, and mark all as read clears the backlog.
The one that needs acting on
Section titled “The one that needs acting on”A sync notification with a non-zero failure count is the only entry here that is not just information.
Failures are usually one of three things: a listing the channel rejected, a location that is not mapped to a warehouse, or a connection that has expired. The first is per-listing and often self-corrects on the next sync; the other two do not fix themselves.
Start with the channel’s own settings page — if a location is unmapped, Fiftify says so in a banner there. See channel settings and locations.
Notifications are company-wide
Section titled “Notifications are company-wide”The panel shows what happened in the company, not what happened to you personally. Two people looking at it see the same list.
That has a practical consequence worth agreeing on in advance: if everybody assumes somebody else is watching the failed syncs, nobody is. Make it one person’s job.
What does not arrive here
Section titled “What does not arrive here”Warehouse work does not. A pick task appearing in a queue, a task going on hold, a short pick reported — none of that raises a notification, because the queues and the outbound board are where that work is visible, and a bell that rings for every task is a bell nobody reads.
The mobile app does push one thing to a device: a new order arriving. Everything else a worker needs is in their task queue.