# Document price: the price the customer wrote next to the item

> For the administrator: decide whether the price the customer wrote next to the item goes into the quote on its own, as base price or fixed price.

Source: https://vendria.com/en/ajuda/preco-do-documento

## Where to find it

In your account menu, under **Prices**, **Discounts and limits** tab, in the
**Document price** section ("What to do with the price the customer wrote next
to the item, in any channel."). Until 18/10/2026 it was in **Commercial
Rules**. There are three controls: **Apply automatically**, **How to
apply** and **Per-store exception**.

## What the document price is

It's the price written next to an item in the incoming order: in a
photo, a PDF, a spreadsheet, a text or an audio message, or typed by the seller
on WhatsApp along with the code and quantity. Dri reads that number and keeps it
on the row as a note. This section decides whether it becomes the row's price and
how.

## Apply automatically: on or off

The **Apply automatically** switch belongs to the **whole organization** and comes
on out of the box.

- **On**: the price written on the customer's order goes in on its own in every
  new quote, whether it comes by text, photo, PDF, spreadsheet or audio.
- **Off**: the price is only noted, and the seller decides during review:
  the row shows the document price with the **Use** button.

"The store's concession limit still applies in both cases."

## When the document price doesn't go in on its own, even when on

- **The order was placed by the buyer.** A price the buyer writes is a
  discount request, not a closed agreement; it never goes in on its own.
- **The quote is no longer in Draft or Pending**: a sent proposal or a
  confirmed order doesn't have its price rewritten.
- **Someone has the quote open for editing**, except when it's the
  seller themselves importing the order there.
- **The row already has a price typed by hand** by the seller. That one is never replaced.
- **The price would break the store's discount cap.** The row is skipped and stays at the
  table price. See [Seller's maximum discount: the per-store concession cap](/en/ajuda/desconto-maximo-do-vendedor).
- **The row has no catalog product.** With no product found there's no table
  price to compare, and this applies in both **How to apply** modes.
- **The quote has the Values read as prices issue.** When Dri concludes
  that the numbers written in the quantity column were prices, no row
  of that order gets the written price on its own: they all stay at the table
  price.

## What the seller sees

On WhatsApp, Dri's reply that creates the quote says what happened to the
written price, when the option is on:

- **🏷️ Message price applied to 3 rows**, when the price went in;
- **⚠️ Message price NOT applied to 2 rows:** followed by the reason, such as
  *above the store's discount limit* or *I didn't find these products in the
  catalog*. Those rows stay at the table price.

With the option off, the reply that creates the quote doesn't mention the written
price: it stays noted on the row, and the seller sees it on screen.

On the quote screen, a row with a noted price that differs from the price in use
shows **Negotiated:** and the amount, with the **Use** button. On the computer, that
tag appears with **Show price and discounts** open; on mobile, it sits in
the row's drawer, as **Negotiated price**. One click on **Use** applies it the
way the store is configured in **How to apply**; the little arrow next to it,
when it appears, lets you choose **Negotiated as base** or **Negotiated as
final price** for that row only. The row that got the price then shows the badge
**✓ Negotiated**, with the **undo** option. Hover over the badge to see whether the
price went in as base or as final price; with **Show price and discounts**
open, the negotiated base appears in the **Table** column, and the final price in the
**Price** column.

## How to apply: Base price or Fixed price

**How to apply** belongs to the organization and decides what the written number means:

- **Base price** (the factory default): the number is the base and the order's
  discounts run on top of it. "An item written at R$ 10,00 in an order with 10%
  discount comes out at R$ 9,00."
- **Fixed price**: the number is the final price. "An item written at R$ 10,00 comes out
  at R$ 10,00, with or without a discount on the order."

Use **Base price** when the customer usually writes the table price they
know; use **Fixed price** when the written number is already the negotiated
price.

## Per-store exception

Below, **Per-store exception** lists each store. A store with no setting of its own
shows "follows the organization" and the step in use, with a button to diverge
(for example **Use Fixed price**). A store with an exception shows its own step and the
**Revert to default** button, which makes it follow the organization again.

The exception exists because stores of the same house write orders in
different ways. **Apply automatically** has no exception: accepting the
written price or not is a policy for the whole organization.

## When the section appears read-only

If the buttons appear disabled with the sentence "These two fields belong to the
organization. Whoever administers the organization can change them; here they appear
so you know what is in effect.", your access doesn't change the
organization's setting. Ask whoever administers the organization. If "couldn't
read" appears, the screen couldn't fetch the setting and doesn't state anything.

## What applies to quotes that already exist

The setting applies to **new** quotes and to whatever is applied from
now on. Rows that already got the document price stay as
they are. The seller can undo the application on the row itself, with **undo**,
and it goes back to the table price. If the price had gone in on its own and the seller
undid it, Dri doesn't apply it again on that row as long as it stays on the
same product; to use it again, it's the **Use** button.

## Common questions

**The customer sent a photo with a price and the quote came out with the table price. Why?**
Check whether **Apply automatically** is on, whether the order wasn't
sent by the buyer themselves, whether the product was found in the catalog and whether the
written price doesn't exceed the store's discount cap.

**The seller typed the price on WhatsApp and the quote came out with the table price, with no warning. Why?**
With **Apply automatically** off, the price is only noted on the row and
Dri's reply that creates the quote doesn't mention it. The seller applies it on the
quote screen, with the row's **Use** button. If you want the typed price to go in
on its own, turn on **Apply automatically**.

**With the option off, the seller added items with a price and got "NOT applied". Is that right?**
The price wasn't applied, yes. When adding items with a price to an already
open quote, the reply can bring **⚠️ Message price NOT applied** even with
the option off, sometimes with the reason *above the store's discount limit*.
In that case the real reason is the option being off, and the path is the same: **Use**
on screen.

**The written price went in, but the customer paid less than what was written. Why?**
The store is on **Base price**: the order's discounts ran on top of the
written number.

**How do I make the seller review before the price goes in?**
Turn off **Apply automatically**; the seller then applies it with **Use**,
row by row.

**Does this have to do with the seller typing a price in the table?**
No. The price the seller types in the table is a different setting. See [Can the seller set the price? Base price and fixed price](/en/ajuda/o-vendedor-pode-definir-o-preco).