# Check price and stock on WhatsApp

> Send Dri the code on WhatsApp and get the price with the customer's discount, ERP stock and arrivals. Several codes: one per line, with stock at the top.

Source: https://vendria.com/en/ajuda/preco-e-estoque-pelo-whatsapp

## Summary

Just type the product code in the conversation with Dri, for example
*"AB10371"*, and nothing else. She answers with the product card: price (already with the
discount of the conversation's customer, if any), packaging and the stock read from the ERP right then,
with pre-sale and expected arrival when there is one. You can also ask the
natural way, by name (*"do you have a thermos bottle?"*), or ask for a registration field
(*"what's the NCM of AB10371?"*).

To check several codes at once, send one per line and write
*stock* or *price* on the first or the last line. You get up to 30 cards.
Replying *in PDF* or *in Excel* right after the cards only becomes the list with
all the codes if there is no open quote in the conversation: with an open
quote, *in PDF* brings the quote's file. Codes alone, without any word,
Dri reads as an order and offers to build a quote.

## What it is

The one-off check on an item: how much it costs, whether it is in stock, where, when it
arrives. You ask Dri on WhatsApp and she answers with the product card,
with the current price and stock.

To send a selection of products to the customer, the path is different. See [Generate a product list on WhatsApp](/en/ajuda/gerar-lista-de-produtos-pelo-whatsapp). To see the whole catalog on screen, use
the **Catalog**.

## How to ask for price and stock

Send the code alone, or the question the natural way: *"how much is the
500 ml thermos bottle?"*, *"is AB10371 in stock?"*, *"what's the price of the
porcelain mug?"*.

For several codes at once, send one per line and write what you want
on the first or the last line: *stock*, *price*, *see stock*. For
example:

```
estoque
AB11659
AB11103
CD21608
```

Dri answers *one card per code*, up to 30. Beyond that, she answers
the first 30 and says which were left out (*"I answered the first 30. Left out:
…"*), so you can send them again or, with no open quote in the conversation, ask for the
list (see below).

The word has to be on the first or the last line. A word in the middle of the
column doesn't count, and neither does *photo* or *image*: with those the message is still
read as an order.

## Codes alone, without any word

A column of codes with no word next to it is how the customer's order
usually arrives, so Dri reads it as a possible quote. She answers in
one of these two ways:

- **📦 I read 3 codes in this message, but no quantity.**, asking whether
  she can assume *1 box of each* and build the quote. To just check, tap
  **No, I'll type it** and send again with *stock* on the first line;
- *"What you sent me: do you want me to look up these products, or to
  build a quote with them?"*, with the options **Look up the products** and
  **Build the quote**. To just check, answer *1* or *look up*. Answering
  with one of the codes doesn't work as a choice.

If you already turned on **Always do it this way** on the box question, the column without a
word becomes a quote right away, without asking. One more reason to put *stock*
on the first line when the idea is only to check. For Dri to ask
again, write *ask quantity*.

A code alone, in a message of its own, doesn't have this problem: it brings the
card.

## More than 30 codes: ask for the list

With no open quote in the conversation, reply *in PDF* or *in Excel* after the
cards, within 15 minutes, and Dri builds a product list with all the
codes you pasted, including the ones that didn't fit in the 30 cards. With an
open quote, *in PDF* brings the quote's file, not the list. The list says
how many codes were asked for, how many were found and which were missing. If
she asks first whether to build the list, confirm.

To get only the list, without the cards, write *build in PDF* on the first
line and the codes below. If instead of the list you get the box question,
tap **No, I'll type it**, check with *stock* on the first line and ask for the
file in the next message. How the list works inside (columns,
photos, filters) is in [Generate a product list on WhatsApp](/en/ajuda/gerar-lista-de-produtos-pelo-whatsapp).

## Examples that work

Most checks are just the code, and that is enough:

- *"AB10371"*: the whole card, with price, packaging and stock;
- *"10371"*: the code without the leading letters also works (see below);
- *"how much is CD21000?"* or *"AB10044 stock"*: the same card, the question only
  says what you want to read first;
- *"stock"* on the first line and the codes below, one per line: one card
  per code, up to 30;
- *"self-adhesive decorative paper 2 m x 45 cm"*: by description, when you don't
  have the code;
- *"AB11779 photo"* or *"I need the photo of CD20009"*: Dri answers about the
  photo, saying how many the catalog has, and sends the photo along;
- *"CD22496, I need the dimensions"*, *"what's the NCM of AB10371?"*, *"what's the weight
  of AB11370?"*: Dri answers the field you asked for, taken from the registration. If the
  registration doesn't have that field, she says it doesn't.

The codes above are examples: use your store's.

## How to write the code

Send the code as it is in the catalog, or just the numbers. The leading letters
are optional in two cases: when the store registered the prefix (for example,
you type *10070* and the store registers *AB10070*) or when the number is a piece
of a product's code. In both, Dri warns that she didn't find the exact code and
shows what she found.

Today it works best like this:

- write the code together, with no space between the letters and the numbers: *AB10070*,
  not *AB 10070*;
- don't put a word in front of the code, like *reference*, *ref* or *code*: the
  word goes into the search too and gets in the way;
- if you aren't sure of the letters, send just the numbers. Swapped letters
  (*DC21608* instead of *CD21608*, for example) are not corrected.

## Search a single store, and only what is in stock

Say the store's name at the start or the end of the sentence, or after *at* or *from*:
Dri searches only that store. If your store is called Casa Bela, for example,
*"candle Casa Bela"*, *"is there a lampshade at Casa Bela?"* and *"calendar from Casa
Bela"* all work. The answer says which store she searched.

In the middle of the sentence and without *at* or *from*, the store's name is read as part of the
product's name. And the store's name alone makes Dri ask what you are looking for:
*"What are you looking for at Casa Bela? Tell me the product's name or code."*

*"In stock"* doesn't always filter the short check: *"2027 planner in stock"*
may bring the count of all planners, in stock or not. To make sure you get only
what is in stock, ask for a list: *"list of 2027 planner in stock from Casa Bela"*. See
[Generate a product list on WhatsApp](/en/ajuda/gerar-lista-de-produtos-pelo-whatsapp).

## What comes back from the check

- *One product found* → the full card, with the photo when the product
  has one, and at the end **See product:** with the link to the product's page on the site.
- *Several products* → *"I found N products for '…'. Narrow it down or
  see them in the catalog:"*, with a link to the catalog already filtered. When you
  sell through more than one store, the count per store also comes (**📋 Stores:**).
  There is no list of products to pick from, not even when there are only two or three:
  refine by name or code, or open the link.
- *Code typed without the prefix* → when the store registers the code with
  letters in front and you typed only the numbers, she warns *"I didn't find the code
  '…' exactly. I found …, through the registered prefix …:"* and shows the product.
- *Incomplete code* → when the number you sent is a piece of a product's
  code, she warns *"I didn't find the code '…' exactly. This one contains
  that piece:"* and shows the card. With several products, the sentence is *"Codes that
  contain that piece:"*, followed by the link.
- *Only similar ones* → when the exact search finds nothing and the approximate one does,
  she says *"I didn't find '…' exactly, but the catalog has N similar ones."* and
  sends **See in the catalog:** with the link, without pointing at any as the answer.
- *None* → *"No product found for '…'."*, followed by **Search the
  catalog:** with a link that opens the catalog with the search done.

## What the product card shows

From top to bottom:

- the product's name, in bold, and on one line the store, the brand and the code;
- the price. With a discount, the **Table** line brings the table price struck through and,
  next to it, each discount with its name and percentage; below comes the **Price** in
  bold, which is the one that applies;
- the packaging, on the same line as the price, when the product sells by the box:
  *"Price: R$ 7,00/unit · box of 60 units: R$ 420,00"*;
- the taxes, when the store shows tax in the catalog (see the next
  section);
- the complementary description and some registered characteristics;
- the stock;
- each warehouse's balance on one line, when the ERP splits by location.

## The taxes on the WhatsApp card

When the store charges the tax on the order, each tax comes on a line with the
rate and the amount, and below, in bold, the price with the tax: **With** and the
tax's name when there is only one (**With IPI**, for example), **With taxes**
when there are two or more. That number is the
price of *one piece* with tax, not the total of an order.

Some stores show the rate in the catalog but don't charge it on the order. Then the
line says *"not included in the order"* and there is no **With IPI** line: the order goes out
at the price shown. That is why two stores of the same company can
answer differently. If you belong to a rep agency, its tax choice applies,
as on the product page.

The ICMS-ST the ERP calculates depends on the customer and doesn't show on the WhatsApp
card. See the question about ST in *Common questions*.

## The price is the active customer's

If a customer is picked in the conversation, the card already comes with their price: that
customer's table and negotiated discount, with the table price struck through
next to it. Without an active customer, the price is the table price.

To change the conversation's customer before checking, see [Choose the conversation's customer on WhatsApp](/en/ajuda/escolher-o-cliente-na-conversa).

## Stock is a live read from the ERP

The stock is read from the ERP at the moment of the question, and each sentence means something:

- *"📦 In stock: 40 units"*: the quantity available now;
- *"📦 Out of stock"*: the ERP answered that there is none;
- *"📦 Out of stock today"*, followed by **Pre-sale**: there is none on the shelf, but
  you can still sell from the goods that are about to arrive. With an open
  purchase, the date comes attached: *"Pre-sale: 120 units · arrives 15/10"*;
- **Expected arrival**: there is no pre-sale, but there is a purchase on the way, with the date;
- *"In inspection (customs)"*: goods that have already arrived and are under
  inspection. They are part of the pre-sale;
- *"⚠️ Pre-sale exceeded"*: more has already been sold for arrival than the
  open purchase covers;
- *"⚠️ Pre-sale without an open purchase order in the ERP"*: there is pre-sale, but the
  ERP doesn't show the purchase that backs it;
- the balance per warehouse, on a line right below, when the ERP splits it;
- *"📦 I couldn't check the stock right now"*: the ERP didn't answer. Dri
  never returns zero in place of a missing answer;
- *"📦 Not found in the ERP stock"*: the ERP answered and doesn't know
  that code.

## Specific questions shorten the answer

When the question is about a *field* of the card (weight, dimensions, material,
color, voltage, shelf life, NCM, barcode), she answers that field instead of
sending the whole card. The **See product** link is still at the end, so the
full card is one tap away.

Dimensions, size and measurements bring the registered height, width and length,
of the product and of the packaging when the registration has both. If
*"This product has no Dimensions in the catalog."* shows up, that product's
registration has none of those measurements: ask the store to complete the registration.

## Ask for the product photo

Send the code and the word photo (*"AB11779 photo"*, *"send the photo of
AB11779"*) and Dri answers with the registered photo and how many photos the product
has: *"📷 There are 3 photos registered in the catalog"*, followed by the store's name. With
more than one, she warns that the full gallery is at the product link.

- With no photo in the registration, she says plainly that the product has no photo
  registered.
- A real photo, of the product in hand, or more photos beyond the registered ones: the
  catalog doesn't have it, and Dri says that is requested from the store.
- If the same message asks for price or stock (*"price and photo of AB11779"*), the
  whole card comes, with the photo along.

Asking for photos of several codes at once, the photo doesn't come: with several cards in the
same answer, each product's photo is at the **See product** link. To
get the image in the conversation, send one code at a time. For several photos in
a single file, ask for the list in PDF with photos.

## Where it is: stock by branch

*"Which branch has AB10371?"* brings the stock split by location, read live from the
ERP: the answer starts with *"📍 Stock by location:"* and lists each
warehouse with the quantity.

If the store's ERP doesn't split the balance by location, she *says so*: *"This store's
ERP doesn't report the balance by branch: the number above is the store's total."* Silence
there would be read as "so it's all in one place". In that case the
split is checked in the store's system.

## When it arrives: the purchase forecast

*"What's the forecast for AB10919?"* or *"when is it back in stock?"* bring the arrival
date of the goods coming from the *supplier*: the open purchase. It isn't the
delivery time to your customer.

- With pre-sale and one open purchase, the date comes attached to the pre-sale:
  *"Pre-sale: 120 units · arrives 15/10"*.
- With pre-sale and two or more purchases, the **Arriving:** block comes, with up to
  four orders, each with its number, quantity and date (or *no date*).
  What goes beyond four becomes *"+2 order(s)"*, and a date already past shows
  marked as *late*.
- Without pre-sale, only the **Expected arrival:** line comes, with the nearest
  date, even if there is more than one open purchase.

Without a date, Dri tells the answers apart:

- *"There is an open purchase for this item, but the ERP didn't report its date."*:
  the purchase exists, with no forecast;
- *"No arrival forecast: there is no open purchase order for this
  item."*: the ERP was checked and there is no purchase;
- *"This store's ERP doesn't report arrival forecasts. Check with purchasing
  before promising a date."*: nobody measured, so she doesn't claim absence.

Questions with *delivery* or *to the customer* (*"what's the delivery forecast?"*,
*"when does it reach the customer?"*) are not read as purchase arrival and bring the
usual card: delivery time to the customer is agreed with the store.

## Common questions

**Why did the price come out different from what the customer pays?** Check whether the right
customer is active in the conversation; without a customer, the price is the table price.

**Why did she send a link instead of the card?** The search found more than one
product. Send the code or a more specific name, or open the catalog link.

**Why did Dri answer only 30 codes?** The limit is 30 per message, and
she says which were left out. Send the others next, or, with no open quote in the
conversation, reply *in PDF* to get all of them in a list.

**I sent the codes and she asked whether to look them up or build the quote.
What do I answer?** Answer *1* or *look up* to get the cards. Next
time, put *stock* or *price* on the first or the last line and the
cards come straight away.

**I sent the codes and she asked whether she can assume 1 box of each.
Why?** Codes alone, without any word, look like an order. Tap **No, I'll
type it** and send again with *stock* on the first line.

**I sent the code and she said she didn't find it. What now?** Check the leading
letters, write the code without a space and without a word before it, or send just the
numbers. The **Search the catalog** link in the answer itself opens the search on the
site.

**I asked for "in stock" and got the count of everything. Why?** The short check doesn't
always filter by stock. To see only what is in stock, ask for a list: *"list of
2027 planner in stock"*.

**I sent the product photo asking for the price and Dri built a quote.
Why?** A photo, for Dri, is an order: she reads the image and builds the quote. In
some accounts the caption decides: a question along with the photo (*"how much is
this one?"*, *"what size is it?"*) is answered about the codes the photo shows,
and **no** quote is created — Dri warns *"📸 I used only the codes in the photo to
answer"*. To just check in any account, send the product's code or name
as text.

**Does Dri send the product photo?** She does: ask for *"photo of"* and the code, one
code at a time. She says how many photos the catalog has, or that the product has no
registered photo.

**The customer wants a real photo or one with better quality. Can Dri get it?** No.
Dri only has the registered photos; a photo of the product in hand is requested from the store.

**I asked for the dimensions and she said there are none. Why?** That
product's registration has no height, width or length. Ask the store to complete the
registration.

**Does the product have ST?** The ICMS-ST that applies depends on the customer: when your
store calculates ST in the ERP, the amount comes per product and per customer, and the WhatsApp
card doesn't show that calculation. If the card brings an ST line, it is the
rate registered in the catalog. A card with no ST line doesn't mean
the product is exempt. To see a customer's ST, open the product page in the
**Catalog** and pick the customer in **See ICMS-ST for** (see [The product page for sellers: stock, price and adding to the quote](/en/ajuda/a-pagina-do-produto-para-quem-vende)). Or build the
quote for the customer: when the store charges ST on the order, the quote brings the
ST the ERP calculates for them. In the conversation, Dri doesn't calculate the ST of a
loose product, without a quote.

**Can I change a product's price on WhatsApp?** The catalog price,
no: it comes from the store's registration or from the ERP. On a quote, yes: write the price
next to the item (*"10 of 9003 at 12,50"*) and, if your company accepts prices
coming from the order, it becomes the line's price. See [Build a quote by text on WhatsApp](/en/ajuda/montar-cotacao-por-texto-no-whatsapp).

**I asked which branch has it and Dri said the ERP doesn't report by branch.
Why?** She says that when the store's ERP doesn't send the balance split by
warehouse. The number she shows is the store's total, and the split is checked
in the store's system.

**I asked for the delivery forecast and got the whole card. Why?** The delivery
forecast to the customer is agreed with the store. For the purchase arrival,
ask *"when does AB10919 arrive?"*.

**Why doesn't the card's stock match the store's system?** The read is
live; if the ERP didn't answer, she says she couldn't check instead of
showing an old number.