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.

These are the things that put an entry in the bell. Most entries clear themselves once the cause is gone.

• Low filament: <name>: the spools of one brand, material and color 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 at <store>: (or Low in the default pool:): a store or channel row, or your own shelf stock, drops below its refill level; act on it from Replenishment.
• Low inventory: <name>: an inventory item falls to or below its reorder point.
• Expiring soon: <name> and Expired: <name>: an inventory item's expiry date is close or has passed.
• Expired product: <name>: an active product's expiry date has passed. The product form has no expiry date, so only a product that already has one raises it. Archive the product to clear it.
• Maintenance due: <schedule>: a schedule's interval has elapsed since the last service. An archived printer raises none.
• Print finished, canceled or failed: FoxTrack Bridge reports the end of a print. The title uses your name for the printer (Print failed: Workhorse). 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, so 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.
• Print paused: a Bridge print stops in the middle, for example on a filament runout. It clears when the print goes on.
• Printer went quiet: a printer that was printing has not reported to Bridge for five minutes. It clears when the printer reports again.
• Reorder <color>: a color will run out before a new delivery could arrive, going by its real use over the last weeks (Pro and Farm; see Runs out and reordering under Filament).
• <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: ORD-0001 and Order overdue: ORD-0001: an order's due date is within three days, or has passed. 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.
• Run due: a dated restock run is close to its date or past it. The title reads Run due: RPL-0003, then Run overdue: RPL-0003, and the row opens the run. Shipped and Completed runs do not count. The dashboard lists them with the orders.
• <Store> sync has a problem and Webhook deliveries are failing (owners and admins): a connected store, or your webhook endpoints, keep failing. It opens Settings → Integrations or Settings → Developer. The Shopify, WooCommerce and CloudSlicer3D cards there also show Delivery refused when a webhook was dropped, for example because of a wrong secret or shop.
• Invoice overdue: INV-0001: 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 show on the relevant page as a warning button (a triangle with a count) by the page's buttons. Press it for the list, with a breakdown (per spool for filament, in a side panel; per variant for products). Dismissing an entry there is a stronger acknowledgement than reading: the row stays in the bell list but no longer counts as unread, and it does not come back until the condition clears and recurs.

Phone alerts send a message to your phone. You pick which ones:

• New order: an order comes in from Shopify, Etsy, WooCommerce, CloudSlicer3D or the API. The message names the store, the order number, the customer, how many items, the total and the due date. Orders you add in FoxTrack, and Etsy file imports, do not send one.
• Morning summary: one message at about 8 AM in your shop's time zone (Settings, General; the alert card shows which one, like Morning summary (about 8 AM, Europe/Paris time)) listing what is open in your bell, like orders due or overdue, low stock, a printer still in error or a store sync with a problem. Nothing is sent on a morning when the bell is empty. A shop with no time zone set uses UTC, and the card says so; when an owner or admin links a phone or turns the summary on, FoxTrack saves the browser's time zone for a shop that has none.
• Print alerts: a print finishes, fails, is canceled or pauses, a printer reports an error, or a printer stops reporting in the middle of a print. These come from FoxTrack Bridge, so Bridge has to be running in your shop.

Phone alerts are on the Pro and Farm plans. A phone gets at most 30 routine alerts and 30 urgent alerts (a print failing or pausing, a printer error or a printer gone quiet) an hour, counted apart, so a burst of orders or finished prints cannot use up the room for a real failure.

Set them up under Settings → Account → Phone alerts. Each person in the workspace links their own phone and ticks the alerts they want. For Telegram, press Link Telegram, then open the link and press Start in Telegram, or send the 6-character code to the FoxTrack bot. Remove a phone there at any time. The bell keeps showing the same events whether or not a phone is linked.

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.