# Dri learns how each customer orders > How Dri learns each customer's vocabulary from your corrections on the quote, and why a code alias only counts after it is approved. Source: https://vendria.com/en/ajuda/a-dri-aprende-o-jeito-do-seu-cliente ## Where to find it Learning has no screen for the seller: it happens behind the order readings Dri does, in the conversation and in on-screen import. You notice it in the quotes under **Quotes**: the same order from a frequent customer comes with fewer open questions over time. What feeds the learning is your work on the quote: every time you correct the product of a line. And whoever approves what becomes permanent memory is your company's administrator. ## What Dri keeps for each customer Each customer has their own vocabulary: they call the kraft box *"cx kraft 30"*, write the code without the prefix, use an abbreviation only their company uses. Dri keeps that way of ordering **per customer**: - **Code aliases**: *"cx kraft 30"* is such-and-such product. - **Abbreviations**: the short form and the full form. - **Likely codes**: what that customer orders often. - **Preferred unit** and **notes about the layout** of their order. ## The memory belongs to the customer, not the seller Two sellers who serve the same company read its orders with the same memory. And what one customer taught does not enter another's reading: the memory is looked up by the customer **of that quote**, and two memories never mix in the same reading. This depends on the customer being right. With the wrong customer chosen in the conversation, the reading comes out with the wrong customer's memory. See [Choose the conversation's customer on WhatsApp](/en/ajuda/escolher-o-cliente-na-conversa). On your side, what is kept and changes how the quote is built is the way you write quantities: the unit you declare in a message on its own (*I always order by the box*) and the **Always do this** choice for a message with only codes. This applies to what you type or say, with any customer, and does not go into the customer's memory or into the reading of a photo, PDF or spreadsheet. See [Build a quote by text on WhatsApp](/en/ajuda/montar-cotacao-por-texto-no-whatsapp). ## Where the learning comes from: your correction When you correct the product of a line (resolving an open question on the line or swapping the product on screen), the correction becomes learning **right away**, even if the quote is never confirmed. Three things happen: 1. **The store learns the reading mix-up.** "When this code is read, the right product is usually that one" is recorded for the store, and applies to the orders of all its customers. A single correction weighs little; several, in the same direction, weigh more. 2. **The customer's likely codes are updated**: the product you chose starts counting as an order from that customer. 3. **An alias is suggested**: "what this customer writes this way is this product" goes into a suggestion queue, and **does not count** until it is approved. The most valuable correction is on a line the reading had resolved **confidently and wrongly**: that is exactly the case nobody would suspect without you. When a quote is confirmed, the differences between what Dri read and what ended up in the order also become suggestions. ## No alias goes in on its own Code aliases are the part that changes the reading most strongly, and that is why **no alias enters the customer's memory without approval**. The suggestion sits in a queue, recorded with its origin, and your company's administrator approves or rejects it in **Order reading**, **Extraction memory** tab. See *Sugestões de Aprendizado: aprovar ou rejeitar o que a Dri propõe aprender*. If you corrected a line and the next reading for that customer still got the same spot wrong, the suggestion may be waiting for approval. ## There are two paths, and they carry different things This explains a behavior that looks inconsistent: - **The order reading** gets a limited slice of the memory: at most 40 aliases, 20 abbreviations and 20 likely codes. The reading is an artificial intelligence step: a long list **dilutes** attention instead of helping. - **Matching the code against the catalog** gets the **whole** memory, because there the comparison is exact and a large list does not get in the way. So a customer with a large memory may have an alias that did not influence the reading and, even so, matched correctly in the end. It is not luck: it is the two paths. ## When two people teach different things The same text can end up taught as pointing to two products: two people, two orders, disagreeing about what that code means. The way the memory works today in most accounts, **what was approved first wins**: the old alias keeps counting and the new one is discarded, without notice. Some accounts have an extra safeguard, which marks the alias as disputed and leaves it without effect until someone resolves it. It is not on in every account yet, so do not count on it: if you notice an alias leading the reading to the wrong product, tell the administrator to fix it. To change an alias's product for good, the administrator edits the customer's **Curated memory**: the edit replaces the old alias, in any account. See *Memória Curada: corrigir o que a Dri aprendeu de um cliente*. ## What this changes in your day to day - **Correct on the line, not only in the final file.** Swapping in the right product on the quote is what teaches; correcting only in the ERP afterwards teaches nothing. - **Check the customer before sending the order.** The memory used is the one of the quote's customer. - **A new customer reads with more doubt.** Their memory starts empty, and the first readings are naturally less certain. See [How Dri finds the product the customer asked for](/en/ajuda/como-a-dri-encontra-o-produto). ## Common questions **I corrected a line's product by hand. Does that change anything in this customer's next reading?** Yes. Their likely codes and the store's reading record change right away; the alias goes in once it is approved. **The alias we taught did not influence the reading, but the product came out right. How?** The reading uses only a slice of the memory; matching against the catalog uses the whole memory. **Does what one customer taught apply to another?** The alias and the likely codes do not: they are per customer. The record of reading mix-ups belongs to the store and helps the orders of all its customers. **Does Dri keep anything about me, or only about the customer?** About you, what changes how the quote is built is the way you write quantities: the unit you declared (*I always order by the box*) and the **Always do this** for a message with only codes. They apply to what you type or say, with any customer. The order vocabulary belongs to the customer.