The bell notifications: what reaches the seller

Where to find it

The bell sits at the top of the screen, in the top bar, on any page of your account. A number on it counts the notifications you have not read yet (above nine it shows "9+").

How to read and mark notifications

1. Click the bell. The Notifications list opens, newest to oldest. Unread notifications come with a dot and in bold.
2. Click a notification to open the full text. Opening it marks it as read.
3. In the notification window, Open takes you to the screen it is about; OK closes it.
4. When the notification summarizes several items, See details appears, listing them one by one (and Hide details collapses them).

View all, at the top of the list, opens the Notifications page. Load more, at the end, brings older notifications. Mark all as read, in the footer, clears the counter at once.

Notifications are kept for 90 days. After that they disappear from the list. What they announced stays on the source screens (the quote, latent demand).

The Notifications page

The page opens from the bell's View all and from your account menu, under Notifications. It shows everything that arrived in the last 90 days, split into Today, Yesterday, This week and Older.

• On the left are the filters: All, Unread, one filter per subject (My orders, Rep agency queue, ERP, Catalog, Stock, Team, Order notices) and Archived. The number next to each subject counts the unread ones.
• Click a notification to read it in full alongside. Opening it marks it as read.
• On the open notification, Mark as unread puts it back in the counter, and Archive takes it out of the inbox and the counter. The archived one stays in Archived, from where Back to the inbox brings it back.
• The queue notification shows how the order is now: No owner, or Taken by and the name of whoever took it.

Turn off the bell for a subject

In Notifications, the Preferences button lists the subjects, each with a switch. Turned off, notifications on that subject stop arriving, in the bell and on the page. Turning it back on resumes receiving from then on; what arrived while it was off does not appear.

• ERP has no switch and shows Always rings: an order rejected in the ERP, a delayed import, an expired connection and the other ERP notifications always arrive.
• Team has a switch, but it does not silence role and access notifications (role changed, access reset, Partner promoted automatically): those always arrive.
• Order notices (ERP stages and digest) have their own channels and schedules, in Notices.
• The choice applies to the organization you are in.

"COT-… changed after being sent" and "COT-… was changed"

It arrives when someone else changes a quote of yours after it has left the company (an administrator, a colleague who took over editing). Your own changes do not ring the bell.

• COT-… changed after being sent: the proposal had already gone to the customer. The copy they have in hand is out of date.
• COT-… was changed: the quote came from the buyer and was changed before they got an answer.

The notification text says what changed (lines added, removed, changed, with allocation changed, commercial conditions) and how the total ended up: "Total from R$ … to R$ …" or "The total did not change.". When you open the quote, the This quote was changed strip shows the detail item by item, who changed it and when.

What to do: check the change and, if the proposal was already with the customer, resend the new version. Nothing is sent to the customer's WhatsApp because of the change.

"COT-… was passed to you"

It arrives when someone else makes you the seller of an order: the rep agency's Partner or Administrative member distributing it, or a supplier administrator choosing the seller. The text says who passed it and which customer the order belongs to. Open takes you straight to it.

It does not arrive when you take an order from the queue yourself, or when the order was already yours. In a purchase with orders in several stores, only one notification arrives.

"New order for your rep agency"

It arrives for people at a rep agency company when an order lands in the team's queue, with no seller: "It arrived with no seller. Open the order to take it." Next to the notification its current state appears: when someone takes it, it starts showing who it was.

A variation is Confirmed order needs attention: the order was confirmed, did not get into the ERP and arrived with no seller: "Open, check and resend."

These notifications only reach whoever can see the queue and serves the order's store. With the queue restricted to Partner and Administrative members, the Seller does not get them. When someone takes the order, the notification stops counting as unread for the rest of the team. See The rep agency's order queue: take, pass on and return.

"New quote from <customer>"

It arrives when a customer in your portfolio builds a quote on their own on WhatsApp. The text has the COT number, the total and the number of items.

The Open on this notification takes you straight to the quote.

"COT-…: the invoiced order notice did not reach the customer"

It arrives for the order's seller when the stage notice that was going to the customer was rejected on every channel: the customer's WhatsApp or email did not accept the message. The text says which channel failed. What to do: check the customer's phone and email.

It arrives once per order and stage, even if the order has more than one buyer. It does not arrive when the sending was skipped on purpose (the customer stopped receiving, the team turned off the channel) or when the problem was on Vendria's side.

"Item that was missing is back in stock"

It arrives when an item that was missing on one of your orders again has enough stock in the ERP to cover what was missing. Stock that only partly came back does not trigger the notification: it waits until it covers the whole shortage.

• A single item: "<code> is back in stock — <customer>."
• Several: "N items that were missing are back in stock.", with See details.

The check is daily and only happens in a store that reads stock from the ERP. Open takes you to Latent demand, already filtered on the stock shortage lines that were notified. When the screen is not turned on for your company, the notification arrives without Open: the text and the item list already say what came back.

"Requested item is now in the catalog"

It arrives when a code the customer asked for that did not exist in the catalog comes to exist: it is the return of the item saved as Not in catalog.

• A single item: "<code> is now in the catalog — <customer>."
• Several: "N items <customer> asked for are now in the catalog." (or "that N customers asked for").

This notification depends on the store's catalog being updated automatically by the ERP; in a store that registers products only by hand, it may not arrive. Open takes you to Latent demand, filtered on the not-in-catalog lines that were notified (and, as with the notification above, it does not appear when the screen is not turned on).

What changes in Latent demand after the notification

After the stock or catalog notification, the line moves to the Customer notified status. ⚠️ Despite the name, the one who was notified is you: the customer did not receive anything. To talk to them, use Notify customer on the line itself, or Generate quote to build the proposal with what came back. See Latent demand: what the customer asked for and did not get.

Demand lines with no seller set do not generate notifications for anyone; they stay listed on the screen.

Common questions

• No stock notification arrived at all: the store needs to read stock from the ERP, and the quantity back needs to cover the whole shortage.
• The notification disappeared from the list: it passed 90 days. The quote or the demand line is still there.
• Does the customer get these notifications? No. The bell is yours. A buyer with access to the store is only notified when a proposal they already received is changed.