Change the seller of a quote or a purchase

Where to find it

In the menu, under Quotes: open the quote (or the purchase) and use the Seller block in the header. For the administrator the seller's name is a button; clicking it opens the list of who can own the sale. With nobody set, the button says Set seller.

For a regular seller the same block is read-only. Changing the owner of a sale is an administrator's decision, and, inside a rep agency, also of whoever administers its team, only among the members of that team.

What the quote's seller decides

The document's seller is whose sale it is: who sees and works the quote, on whose behalf it goes out and whose numbers it counts toward. It belongs to the document. The customer's seller, on the customer profile, is something else: it is the portfolio.

How to change the seller of a quote

⚠️ Before you start: if the quote's customer has a seller in the portfolio, the list doesn't offer people. To hand the quote to someone else, first change the customer's seller, on their profile, and then the quote's (see the section on the portfolio, below).

1. Open the quote.
2. In the Seller block, click the name (or Set seller).
3. Type to search (the box accepts Name, legal name, CNPJ or code...) and choose the person or the rep agency company.
4. The change takes effect immediately: Seller updated.

It works in draft, awaiting, confirmed and exported. Once the order has entered the ERP, it doesn't: neither the person nor the rep agency can change there anymore, and the block becomes read-only.

Choosing a rep agency company (the Rep agency companies group), the order becomes the company's, with no person set, and its team sees it in the queue: Order assigned to <rep agency>.

To leave the document without an owner, open the list without typing anything and use Remove the seller, in the No owner group: Order without a seller. If the document belongs to a rep agency, it goes back to its team's queue.

Until when the change applies

Changing the seller is an administrative correction: it works in draft, awaiting, confirmed or exported, and doesn't touch the price: the document's amounts stay as they are.

Three exceptions:

• an order that is already in the ERP can no longer change seller — neither the person nor the rep agency. The seller code went with the submission, and changing it here would only make Vendria disagree with what the ERP recorded. The block becomes read-only and warns This order has already gone to the ERP: the seller and the rep agency can no longer change. This applies to an order that is in the ERP and to one on its way there (sending, awaiting import). In a purchase with several orders the lock covers the whole purchase: it is enough for one of the orders to be in the ERP;
• a rep agency order that has already left work (confirmed, cancelled…) doesn't go back to the team's queue: This order is no longer in work — it doesn't go back to the queue.;
• in a document that has died (cancelled, rejected, expired) the person can still be corrected, but the owning rep agency can no longer change. The block shows the same sentence as always, This order has already gone to the ERP — the rep agency can no longer change: it is generic on purpose, because the rep agency freeze has two causes (the order is in the ERP, or the document died) and the screen only receives the notice that it is frozen.

The ERP rejected the order: the change comes back

The lock asks "does the ERP have this order?". If the ERP declined it (customer not registered, writing turned off, order that didn't get in), the order isn't there, and the seller can be changed again — that is precisely the correction: change the seller and send it again. The rejection message itself records the way out, and also records its limit: the change applies again, but to the next submission.

⚠️ And it applies to the NEXT submission. The change doesn't reach the rejected submission: what stayed on the ERP side keeps the previous seller, and that submission is not resent — the path is to duplicate the order and confirm it again (see Quando o pedido confirmado não entra no ERP).

A cancelled order is another story: the PERSON can still be changed on it, because correcting ownership on a cancelled order that still needs an answer to the customer remains legitimate — even if that order reached the ERP before being cancelled.

In a purchase with several orders

When the quote is part of a purchase with several orders, the seller belongs to the whole purchase: the change is made on the purchase page and applies to all its orders. If the orders had different sellers, the page warns The orders in this purchase have N different sellers and reminds you that Setting a seller here applies to the whole purchase: orders with another seller become this one's.

In companies configured to treat each order in the purchase as independent, each order has its own seller and the change is made order by order.

⚠️ When the customer's portfolio already decides the seller

If the quote's customer has a seller in the portfolio, the list stops offering people, including the portfolio owner themselves. Below the name, the block shows Seller set by the customer's portfolio (or Portfolio of <rep agency>). When the portfolio owner is a person and the quote is with someone else, instead of that text the divergence warning appears with the Use portfolio owner button, explained in the next section.

What remains on the list:

• Remove the seller, when the quote has a seller;
• the rep agency companies that serve the order's stores, if your company works with rep agencies. The list warns that Choosing another company deselects this order's customer: choosing a rep agency that doesn't serve the customer, the order is left without a customer and you choose it again.

Vendria doesn't let the sale go to a person who doesn't serve the customer: trying responds Customer allocated to <name>'s portfolio — to change the document's seller, reallocate the customer in the portfolio.

The path is to first change the customer's seller (on their profile, or through bulk assignment under Customers) and then the document's. See The administrator's Customers list: columns, filters and bulk assignment.

Changing the customer's seller doesn't change the quotes'

Changing the seller on the customer profile changes the portfolio. Quotes that already exist stay in the name of whoever had them.

On such a quote, the Seller block warns Diverges from the portfolio — owner: <name> and offers Use portfolio owner: one click hands the quote to the customer's current seller (Seller corrected to the portfolio owner).

When a seller leaves and you reallocate their portfolio, also review their open quotes with the Seller filter on the Quotes list.

The Typist: who entered the order

In the quote header there is a second person field, the Typist, and it answers a different question. The Seller is whose sale it is. The Typist is who entered the order: the counter's shared account, someone who typed it for the seller, the order that came from a spreadsheet.

• Changing the Typist doesn't touch commission, visibility or the customer's portfolio. That is why it has no portfolio lock: the list shows the people linked to that document, including administrators who aren't sellers.
• To change it, use Set typist and choose the person. The screen confirms with Typist updated.
• Back to the original undoes the change, and the typist goes back to being whoever was signed in when the document was created.
• When the typist has been changed, the screen shows next to it "(recorded in the system: …)" with the name of whoever created the document. That record never changes.
• The typist is internal Vendria information: it doesn't go out in the order file or to the ERP.

Whoever can change the quote's seller is whoever can set the typist. Whoever can't sees the name as text.

When it goes wrong

• The seller's name isn't clickable: you don't have the authority to change this document's owner.
• "No seller available in this organization.": there is no active seller who can own a sale.
• "Error updating seller": the change didn't save; the next message says why when there is a reason.