Skip to main content
The catalog is the products or services your agent can recommend and quote. With it, your agent answers “do you have this?”, suggests options, and shares prices. You set it up in your agent’s Catalog tab.

What you will get

When a customer asks about a product, your agent will find it in your catalog and answer with its real information.

Choose how your products come in

The important difference between the two options is not how they load, but how they stay up to date afterwards.
A file catalog does not update itself. When your prices or your stock change, the file has to be uploaded again. If you need it to stay current without anyone touching it, the option is API.

Load your catalog

The first-time setup screen is one page.
1

Choose your source

In the Catalog tab, choose between API and Archivo (File). This first-time setup screen is shown in Spanish even with the interface in English.
Conectar productos screen with the API and Archivo options and the box for dropping the file.

The first step: API connects your system, Archivo (File) takes a CSV, JSON, or XLSX.

2

Paste the URL or drop the file

For API, paste the address of your product endpoint. For a file, drop a CSV, JSON, or XLSX of up to 50 MB. Eva reads it and shows how many products it detected, which field it will search by, and which fields it will show.
3

Save

Select Guardar y sincronizar (Save and sync).

Check how it was configured

Once loaded, the catalog card keeps its setup under Configuration. Open it to confirm where the catalog comes from and which field your agent searches by.
Catalog configuration panel with the source row reading Archivo and the search row reading Nombre.

Fuente (Source) says where the catalog comes from; Search by says which field your agent looks up.

Parts of this panel are still shown in Spanish even with the interface in English: Fuente (Source), Campos visibles (Visible fields), and the values Archivo (File) and Nombre (Name).

Tell Eva what each column means

Eva reads the price and the stock from the columns that carry that meaning, not from the header name. That way it quotes correctly even when your file uses headers like “X17”.
1

Open the column list

On the catalog card, under What Eva shares, next to Visible fields, select change. The list of columns Eva can read appears.
2

Choose what each column means

Next to each column, choose its meaning: for example Price, Units in stock or Payment term. If a column is none of these, leave it as No meaning.
3

Mark the price Eva quotes

On the price Eva should quote, turn on This is the price Eva quotes. If a column is a monthly payment, choose This is the primary installment and its Installment term right there.
4

Save

Select Save. Eva uses the changes from that moment on.
Changing the meaning or the name of a column does not process your products again. If you untick a column, Eva stops reading it, but the column keeps its meaning. To bring it back, tick it again. If your catalog reads live data, select change next to Visible prices. The same list opens with the columns of your live data, marked Live, and you choose the price there.

How to know it worked

The catalog card shows its state and the Last sync date. While it is working you see Syncing catalog.
Active file catalog: the card reads Syncs every 24 hours even though a file catalog does not update itself.

The active catalog card, with the product count and its last run.

What the screen says: on a file catalog, that same card reads Syncs every 24 hours, like the one in the picture. What actually happens: that cadence is the one for catalogs connected by API. A file catalog never reads anything again on its own. Its Last sync date stays on the day you uploaded the file, and only moves when you upload a new one. So a file catalog is kept current by you: every time your prices or your stock change, upload the file again. The real test is to ask it: open Test and ask your agent about a product you know exists.

Upload the file again when something changes

On the catalog card, select View products and then Update file. Drop the new file into the box: it replaces the previous one and syncs the catalog again.
Update catalog from file dialog with the box for dropping the updated file.

Update file is the only way a file catalog receives new data.

Review your products

Inside the catalog you can search by name and review each product with View products. View as agent shows you exactly the information your agent works with, which is the best way to spot an incomplete field before a customer sees it.
Catalog product list with the search box and the View as agent icon on every row.

The product list: the search box on top and the View as agent icon on each row.

In a catalog connected by API the products are read-only in Eva: they are edited in the source system and arrive on the next sync. The Edit button is disabled for those catalogs, with the note Products sync from the source.

If something goes wrong

Check the last sync date. If it is a file catalog and you changed prices or stock in your system, those changes did not reach Eva until you upload the file again. Use Edit to upload the new file.
The sync failed several times in a row and stopped so it would not keep retrying. Check that your system is still responding and save the catalog again. In the meantime Eva keeps using the last catalog that did sync — the card says Serving last successful catalog — so your customers are not left without answers.
It is a catalog synced from an external system. Its products are edited there, not in Eva.
Include useful detail on each product: description, variants, availability. The more complete the catalog, the better the recommendations your agent gives.

Next steps

Test your agent

Teach your agent about your business