Notifications

The bell in the top bar shows a count of unread notifications and opens a list grouped by kind. Clicking a notification marks it read and takes you to the page it is about (Filament, Products, Replenishment, Inventory, Maintenance, Orders, Invoices or Printers). A Bridge print notification opens the order's own fulfillment page when the lines on that printer belong to one order, otherwise the Fulfillment queue filtered to that printer; a printer error, or a print with no line on that printer, opens the printer itself on the Printers page. A paused store opens Settings → Integrations. Mark all read clears the badge. Notifications are worked out automatically from your data; nobody writes them by hand, and they refresh as you use the app.

• Low stock: filament: the spools of one brand, material and colour together fall to or below the low-stock threshold set on that type.
• Low stock: product: a variant's total stock across locations falls to its low-stock alert.
• Low stock: location: a store or channel row drops below its refill level; act on it from Replenishment.
• Low stock: inventory: an inventory item falls to or below its reorder point.
• Inventory expiry: an inventory item's expiry date is close or has passed.
• Maintenance due: a schedule's interval has elapsed since the last service. An archived printer raises none.
• Print finished, cancelled or failed: FoxTrack Bridge reports the end of a print. The title uses your name for the printer (Print failed: Workhorse), and a failed print names the order line that was on it (Blue Benchy on Workhorse, or Blue Benchy and 2 other lines). These are one-off events: once you have read one it leaves the list. To put the line back in the queue and take the lost grams off the spool, use Print failed on the line (Fulfillment topic, Recording a failed print).
• Printer error: a Bridge printer reports an error state. It clears by itself when the printer leaves that state. A printer error that comes within two minutes of a failed print on the same printer is not raised a second time.
• Store sync is paused (Shopify, Etsy, WooCommerce or CloudSlicer3D): the store is still connected, but the plan no longer includes its sync, so new orders are not imported. It says how many orders were skipped since when, and clears itself once the plan includes the sync again or the store is disconnected.
• Order due soon: an order's due date is within three days, or has passed (Order overdue). It counts orders not yet shipped or delivered, in a board column that is still active and counts as revenue. The dashboard's Upcoming deadlines and its overdue lane show the same orders.
• Invoice overdue: an outstanding invoice is past its due date.

Overdue orders, overdue invoices and expired stock are shown as urgent, the one place the app uses a red accent. When a notification you have already read turns urgent (an order due on Thursday is now overdue), it comes back as unread, and as undismissed, so the bell counts it again.

Low-stock conditions for filament, products and inventory also appear as a dismissible popup on the relevant page, with a breakdown (per spool for filament, per variant for products). Dismissing a popup is a stronger acknowledgement than reading: the row stays in the bell list but no longer counts as unread, and the popup does not come back until the condition clears and recurs.

There is no global switch. A notification goes away when its cause does: lower the low-stock threshold, restock, log the service, or pay the invoice. Clearing a threshold (leaving it blank) means that item never raises a low-stock notification.