Extraction Memory: what Dri learned about each customer

Where to find it

In your account menu, under Order reading, Extraction memory tab. Until 18/10/2026 it had its own menu entry; today it is a tab of the Order reading screen, next to Reading rules.

The tab opens with two cards that have no per-customer scope: Memory health (for the whole organization) and Learned confusions by store. Below them comes the Customer selector: the Learning suggestions (pending) queue and the Curated memory only appear after you choose one. With no customer chosen, the tab says "Select a customer to see the data."

Don't confuse it with Dri's knowledge: that is what Dri knows about your company (payment terms, policies, technical sheets) to answer questions; this is what she learned about each customer's way of ordering, to read their orders.

What Extraction Memory is for

Extraction Memory is where the administrator sees and corrects what Dri learned from each customer: the nicknames they give products, the internal code they write in place of your SKU, their company's abbreviations. It is this learning that makes that customer's next photo, spreadsheet or message get read right without anyone needing to correct it again.

The two memories: customer and store

The customer memory belongs to the buying company. It keeps code aliases, abbreviations, frequent products, preferred unit and notes. Aliases only come in with approval; frequent products come in on their own with each confirmed order. It applies in all the organization's stores, only for that customer.

The store memory keeps the reading confusions the team corrected ("read X → real SKU Y"). It applies to all customers of that store, and doesn't go through approval, but it only serves to raise a review alert, never changes the product on its own.

Where Dri learns from

Every time someone on the team corrects the reading of a line:

1. changes the product by hand in a quote, or
2. resolves an open question on the line by choosing the right product, or
3. confirms a quote in which the customer's code differs from the SKU,

Dri proposes an alias for that customer (it goes to the suggestion queue), and, in the first two cases, the store records the confusion right away. Correcting a line carefully is therefore the most direct way to teach Dri.

The four parts of the screen

• Memory health: whether the memory is being used and whether it helps. See Memory health and confusions per store: how to read the numbers.
• Learned confusions by store: what each store learned on its own, with weight and state active/inactive. Read-only.
• Learning suggestions (pending): the queue of proposed aliases, with Approve and Reject. See Learning Suggestions: approve or reject what Dri proposes to learn.
• Curated memory: the customer's approved content, editable, with Save. See Curated Memory: correct what Dri learned about a customer.

How the memory changes the reading of an order

• Code alias: when the code written by the customer doesn't match any product directly, Dri tries the alias's SKU. The code that matches directly always wins.
• Abbreviations, preferred unit and notes: they come in as guidance for reading that customer's order.
• Frequent products and store confusions: when the code read has a twin in the catalog (differing by one digit, for example) and the history points to the twin, the line gets the alert "Similar code in the catalog — confirm which one".

The memory applies to new readings. Quotes already built aren't reread when you approve a suggestion or edit the memory.

When it goes wrong

Dri keeps getting the same code wrong after I approved. The memory is per customer: approving on customer A teaches nothing to customer B, even if it's the same code and the same product. Also check that the quote has the right customer set: with no customer, their memory isn't used.

Dri started matching a code to the wrong product. Probably a wrong alias was approved. Open the customer's Curated memory and correct or remove the alias.

A similar-code alert appears on an order that is correct. It may be an active confusion in the store or the customer's history. Confirm the product read; the store confusion fades on its own over time if it isn't corrected again.

The Customer selector doesn't show the company. It lists the buying companies registered in your organization, under Customers. Register the company there.