Notifications and the bell

The bell in the top bar holds notifications addressed to you in the store you are working in. A red dot on the bell means something is unread. For about three seconds after you open Ordexs, and each time a new notification arrives, the dot shows the number of unread notifications, then turns back into the dot.

Your other stores. If you work in more than one store, a small red dot on the store button in the top bar means one of your other stores has unread notifications. Open the store list to see how many each store has, and switch to that store to read them. New notifications appear the moment they happen, without reloading the page, and play a sound that tells you what kind of news it is (see Sound below).

  • Pressing a notification opens what it is about (the order, or Inventory) and marks that one as read. Opening the bell on its own does not mark anything read.
  • Mark all read at the top clears every unread notification at once.
  • Older notifications load as you scroll down the list.
  • The sliders button next to it opens your notification settings.

What can notify you today, grouped by section:

  • Orders, coming in: a new order arrives on your store (every order gets its own notification, even when several arrive in a row). A new order that needs a look first arrives as a highlighted warning marked "Check first" instead: a possible duplicate (the same customer already has an open order, the same rule as the Duplicate badge; it opens the list searched by their phone so both orders show), or an order from a risky customer (on your blocklist, returned orders to you before, or returned orders at other stores when that check is on in the card-badge settings). Also: an order is assigned to you, to confirm or to follow on delivery; a teammate mentions you with @ in an order's notes; the automatic WhatsApp confirmation could not reach the customer.
  • Orders, waiting on you: once a day from 9:00, how many orders are still Pending after 24 hours, and how many in Attempt 1, 2 or 3 nobody called in the last 24 hours (a teammate who only works their own orders gets their own count); a Scheduled order's date has arrived; an exchange order still has not been sent to a courier 24 hours after it was created.
  • Delivery, a call can still save it (from the courier's updates): the customer is not answering the driver; the parcel is waiting at the stop desk for the customer to collect; the customer postponed delivery (off by default); the parcel started coming back to you; the delivery failed (the courier marked it failed, for example cancelled by the customer; cancelling a parcel yourself never sends this). Exchange pick-ups coming back are not reported as returns, since they are meant to come back. Also here: the customer sent a request from their tracking page (they are available, want a call at a better time, want the address fixed, or wrote a message).
  • Delivery, how it ended: the parcel was delivered (several in a row become one "12 orders delivered"); the courier collected the customer's item for an exchange and it is on its way back.
  • Delivery, parcels that need you: a return is ready for you at the courier or back with you and waiting to be validated in Returns (several become one "4 returns to validate"; pressing it opens Returns); an exchange return has waited at the courier for over 24 hours; once a day from 9:00, a parcel on its way with no new courier update for 4 days (once per stuck spell); the courier reports a parcel as lost.
  • Products & stock: a tracked product or variant runs out; one drops to your low-stock alert level; one that ran out is back in stock (not sent to the person who added the units); the date you set on incoming stock has arrived and it is not confirmed received (repeats every 3 days until it is); a teammate adds or removes stock by hand.
  • Products, what agents need to quote: a teammate changed a product's price (several changes on one product are grouped); an offer went live (a bundle, cross-sell or upsell, switched on or reaching its start date); an offer was paused or reached its end date; a product was taken off the store (back to draft, or archived). These go to everyone who handles orders, so agents always quote the current price and offers. The person who made the change is not notified.
  • Products, reviews from shoppers: a review is waiting for your approval (several become one "3 reviews to approve"; nothing is sent when reviews publish automatically); a shopper left 1 or 2 stars, shown as a warning instead of the normal review notification, even when it was published automatically. Reviews you add yourself never notify.
  • Customers: a teammate added a customer to the blocklist (Do not contact), so nobody confirms their orders. A normal new-order notification from a customer who already had orders delivered carries a Returning customer chip with how many.
  • Team: someone accepted your invite; an invite waited 3 days unanswered or expired; your own role or permissions changed; you were removed from another store or your access there was paused (shown in a store you still belong to); once a day, an agent with assigned orders to call has not been online for 24 hours (to the store owner); an order you were confirming or following on delivery was moved to someone else (several are grouped); a teammate left on their own (there is no Leave store button, so today that means they deleted their Ordexs account); every morning at 9:00, the owner gets yesterday's summary per agent: confirmed, cancelled, and orders still waiting.
  • Security: your account was signed in on a device (browser and system) it has not used before. It shows in every store you belong to. It never fires when the Ordexs team views your store to help you.
  • Billing (to the store owner only): 80% and 100% of this month's orders (on plans with a monthly order allowance), campaign messages, or storage; AI credits under 10% left, and out; the free trial ends in 3 days; the plan changed. Storefront visits are not counted yet, so there is no notification for them.
  • Developers (to the owner and admins): one of the store's webhook endpoints was turned off because every delivery to it failed for 3 days. The owner also gets an email. Fix the address it points to, then turn it back on.
  • Pre-orders on new orders: when a new order (or an order assigned to you) takes a product past zero, its notification carries a Pre-order chip and the date the stock is expected, or a No stock chip when nothing is on the way. You are never notified about your own changes. The same product only alerts once every 12 hours, so a busy item cannot flood the bell.

You only receive the notifications your permissions allow, and order notifications only for orders you can open. Someone who cannot see stock never gets stock alerts; an agent who sees only their assigned orders is only told about those (and about unassigned orders they are allowed to claim).

A notification about several orders opens the orders list already filtered to them, and those orders glow white for a moment. One about a single order opens the list searched for that order and opens the order itself, with a short white glow around it. A stock notification about one product opens Inventory searched for it, with that product's row glowing; a notification about a teammate opens Team with that person selected.

Choosing what reaches you. Open your account (your name in the top right), then Notifications. There is one card per section, with a switch for each kind of notification, grouped under small headings (for example Coming in and Waiting on you under Orders; A call can still save it, How it ended and Parcels that need you under Delivery), and a switch on the card to turn the whole section on or off. Everything starts switched on except "Customer postponed delivery". These choices are yours alone: each teammate picks their own, and they follow you to every store you work in. A change applies to new notifications; ones already in the bell stay.

Sound. At the top of the same page, the Sound card has a switch to play a sound when a new notification arrives, and a Play button to hear it. Each kind of news has its own sound: a new order plays a cash-register "cha-ching"; something going wrong (a customer not answering, a failed delivery, a return, a duplicate or risky order, a lost parcel, a bad review) plays a short falling "uh-oh"; good news (an order delivered, a product back in stock, a teammate joining) plays a quick rising chime; everything else plays the classic soft chime. Under the switch, one button per sound lets you hear each of them. It is on by default. This switch is for the device you are on only: you can keep sound on your computer and turn it off on your phone. The sound only plays for the store you are working in, plays once even when the dashboard is open in several tabs, and plays once for a burst of notifications that arrive together (the most urgent kind in the burst is the one you hear). Your browser only allows sound after you have clicked somewhere on the page, so right after opening the dashboard the first sound can be silent.

Team chat is not in the bell. Chat messages and @mentions in chat show as a badge on the chat icon next to the bell instead.

Analytics warnings (for example a drop in confirmations) are shown on the Statistics page, not in the bell.

More in Your account

Still need help?

Ask the assistant from the search box in your dashboard. It answers from these same guides, in English, French or Arabic, and can make changes for you. Or write to us and a person will reply.