> ## Documentation Index > Fetch the complete documentation index at: https://docs.chatnorris.ai/llms.txt > Use this file to discover all available pages before exploring further. # Laudus > How to connect your Laudus ERP to a ChatNorris agent to answer live price and stock, help your customers with their documents (balance, payments, shipping and detail), resend invoices and receipts to them, import the catalog into the Knowledge Base and create customers from your leads. # Laudus With the Laudus integration, your ChatNorris agent works with the real data in your ERP. Depending on what you turn on, the agent: * looks up products by name or SKU and answers the sales price and the stock in your warehouses at that moment; * helps your customers with their documents: outstanding balance, whether an invoice is paid, shipping and the detail of what they bought, always after verifying it is the customer; * resends an invoice or receipt to their documents email registered in Laudus; * uses your product catalog as a knowledge source; * creates in Laudus the customers who come in as leads through the chat. It works on the web widget, WhatsApp, Instagram, Messenger, Telegram, Email and the API. ## Requirements * A ChatNorris account on the **Premium** plan. Laudus, like the other ERPs (Odoo and Bsale), is exclusive to Premium. You can see the plans at [chatnorris.ai/pricing](https://chatnorris.ai/pricing). * At least one agent created in ChatNorris. If you don't have one yet, follow [Create an agent](https://docs.chatnorris.ai/en/guias/crear-agente-wizard.md). * A company in Laudus ERP (Chile) and a Laudus **API user**. * **Owner** or **Admin** role in your ChatNorris organization. > [!NOTE] > > Laudus shows up in the hub with the **Beta** label. If the card shows **Request access**, request it from there and we'll let you know when it's enabled for your organization (see [Integrations in beta](https://docs.chatnorris.ai/en/guias/integraciones.md#beta-integrations)). ## Connect Laudus Each agent connects to one Laudus company. **1. Create an API user in Laudus** We recommend a dedicated user (for example, "ChatNorris") with just the permissions it needs: read products, stock, prices, customers and sales documents. Add emailing documents and creating customers only if you're going to turn on those capabilities. **2. Open the agent's Integrations hub** In ChatNorris, go to `My agents → [your agent] → Integrations` and choose **Laudus**. **3. Enter the details and connect** Type the **Company RUT** (with hyphen and check digit), the **API user** and the **Password** of the API user, and click **Connect**. ChatNorris tests the details with Laudus before saving them: if they don't work, it tells you and saves nothing. The password is stored encrypted and is never shown in the dashboard. With **Test connection** you can verify it again whenever you want. If you change the user's password in Laudus, type the new one and save. ## Set up the Action Connecting Laudus doesn't turn anything on yet. To choose what the agent does: **1. Create the Laudus Action** Go to `My agents → [your agent] → Actions`, click **New action** and choose **Laudus**. **2. Choose the capabilities** Turn on the ones you want (see the table below). **3. Turn on the Action and save** From then on, the agent uses Laudus in all its conversations. | Capability | What it does | | - | - | | **Live stock and price** | Looks up products by name or SKU and answers the sales price calculated by Laudus (from the price list you choose, or the product's base price) and the stock in the warehouses you choose. | | **Outstanding debt** | Answers how much the customer owes based on their pending documents: overdue, not yet due and total. | | **Payment status** | Answers whether a document is paid, with the recorded receipts and the balance. | | **Shipping status** | Answers the shipping details of a document: date, carrier, district and dispatch guides. | | **Document detail** | Shows the products and quantities of a document, with its total. | | **Resend document** | Laudus resends the invoice or receipt to the customer's documents email, after an explicit "yes". | | **Create customers from leads** | When a lead confirms their email in the chat, links them to the Laudus customer with that email or creates one. It never modifies an existing customer. | ### Stock and price Choose the **Price list** the agent uses (if you don't choose one, it answers the product's base price in Laudus) and the **Warehouses for stock** whose stock it adds up (if you don't choose any, it reports total stock). Price and stock are checked in Laudus on every question: it never answers with old data. Taxes and discounts are calculated by Laudus. > [!NOTE] > > An agent answers prices and stock from a single integration. If another one already answers them (WooCommerce, Shopify, Jumpseller, Odoo or Bsale), turn it off before turning on this one. WooCommerce order lookup can stay on: prices and stock come from Laudus and orders from WooCommerce. ### Customer requests Before sharing any customer data, the agent verifies the customer once with their **RUT** and a **second detail** that you choose in **Verification**: * the number and total amount of one of their documents (default); * an email registered in Laudus (the contact email or the documents email); * either of the two. Once verified, for 30 minutes the customer can make all the enabled requests without giving their details again. To protect your customers: * if something doesn't match, the agent always answers the same thing, without saying which detail failed, so nobody can guess RUTs or document numbers; * after 5 failed attempts in the same conversation, requests are blocked; * only valid documents (never voided ones) are checked, of the types you choose in **Documents that can be queried** (invoices, receipts, credit notes and debit notes) and within the **Maximum age** you set. > [!WARNING] > > For these capabilities we recommend **Claude Sonnet or higher** as the agent's model (`Settings → AI`): they reveal your customers' data and resend real documents after a confirmation. ### Resend documents When the verified customer asks for an invoice or receipt, the agent shows them the documents email registered in Laudus, masked (for example, `f***@empresa.cl`), and asks whether to resend it there. Only after an explicit "yes" does Laudus send the document with its PDF. * The document always goes to the email registered in Laudus, never to another one. If the customer needs to change it, the agent offers them to talk to a person on the team. * In **Resend limits** you choose how many resends are allowed per conversation and per day across the whole agent. * In the Playground, resending is simulated: no email is sent. ### Create customers from leads With this capability, every lead who confirms their email in the chat (for example, in the Lead Form) becomes a customer in Laudus: if one with that email already exists, it's linked; if not, one is created with their name, email and phone. ChatNorris never modifies a customer that already exists. ## Import the catalog into the Knowledge Base With Laudus connected, you can add your catalog as a knowledge source so the agent finds the right product when the visitor describes it in their own words. **1. Add the source** Go to `My agents → [your agent] → Knowledge Base → Add source` and choose **Laudus**. **2. Import the catalog** Click **Import catalog**. Your company's current, sellable products are imported. * Each product becomes a document with its name, SKU, category and sales unit. * **Prices, stock and costs are not stored**: the agent checks them live with the Laudus Action. * The source resyncs on its own every day (Premium automatic sync). With **Import again** you can update it whenever you want. With the Action on, the source list also shows the **Live Laudus catalog** row. It's not a source: it shows that the agent checks price and stock directly in Laudus. ## Credits Connecting Laudus doesn't use credits. Each agent reply that checks live price and stock adds **0.5 AI credit** to the reply's normal cost. The imported catalog takes up characters of your Knowledge Base like any other source. ## Disconnect In `My agents → [your agent] → Integrations → Laudus`, click **Disconnect**. The Laudus Action turns off and keeps its configuration. If you're no longer going to use the API user, deactivate it in Laudus. ## Frequently asked questions > [accordion] The agent can't find a product that does exist > > The agent only sees **current, sellable** products in Laudus. Check that the product isn't discontinued or marked as not sellable. If you search by SKU, check that it's filled in on the product. > [accordion] The agent can't verify a customer > > Check that the customer's RUT is loaded in Laudus and that the second detail matches: the number and total amount of a valid document of an enabled type, or an email registered on their record. If the conversation piled up 5 failed attempts, it's blocked: the customer can write again in another conversation. > [accordion] The customer didn't receive the resent document > > Laudus sends it to the documents email registered on the customer's record. Ask them to check their spam folder and confirm in Laudus that the email is up to date. > [accordion] The integration shows as expired > > Laudus rejected the saved details, for example because the API user's password changed. Type the new password in the integration and save. > [accordion] Can I use Laudus and WooCommerce on the same agent? > > Yes, with one condition: prices and stock come from only one of the two. The usual setup is to leave stock and price in Laudus, and order lookup in WooCommerce. If you import both catalogs into the Knowledge Base, the agent sees the products twice: keep only one active. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.