# RetailCRM

Total RetailCRM orders by status and store right in chat

E-commerce CRM — заказы, клиенты, товары, справочники, задачи, аналитика

## How the agent works with RetailCRM

The agent calls the fifth version of the RetailCRM API at your workspace address — retailcrm.ru or retailcrm.pro — and reads orders, customers, products, reference books, tasks and analytics. On top of those it builds the order summary by status, source and store with revenue for the period, the segmentation of customers by purchase frequency and recency together with loyal buyers who have gone quiet, and the review of manager tasks with overdue items on orders in progress.

The agent starts from the status reference book, and that is not a formality: statuses in RetailCRM are configured per shop, everyone's names differ, and the meaning is carried by the group a status belongs to. Comparing orders by the label on a button is pointless — the agent sorts them into groups first and counts afterwards. It separates stores and sources the same way: a single account-wide figure that stacks several sales channels hides exactly what the report was asked for.

Cancelled and unredeemed orders are kept out of revenue and shown on a separate line, otherwise the summary looks livelier than the till. What the agent can do beyond reading is decided by the set of methods ticked for the key: if changing orders is not permitted, the agent stays a reader and says so rather than guessing. Before editing an order it re-reads the card — managers and the store exchange move it in parallel, and someone else's change must not be overwritten.

Access runs on an API key of the workspace: it travels with every request, is limited to a list of methods and a list of stores, and is revoked where it was created. A key narrowed down to one store reads to the agent as a data boundary rather than a breakage, and it explains the figure that way. It holds the request rate itself and fetches long periods page by page, and if a method is not ticked for the key or there were no orders in the period, it says so directly instead of showing an empty table.

## Integration scenarios

### Orders by status and store
The agent groups RetailCRM orders by status, source and store, spots the ones that have stalled and totals revenue for the period.

### Repeat purchase analysis
The agent segments customers by purchase frequency and recency, finds loyal buyers who have gone quiet and prepares a list for reactivation.

### Overdue task control
The agent reviews manager tasks, singles out the overdue ones on orders in progress and sends the list to whoever owns them.

### Cancellations and unredeemed orders
The agent takes cancelled and unredeemed orders for the period apart, keeps them off the revenue line and names the stores losing the most.

### What people actually buy
The agent matches order lines against the product reference book and shows what sells most often and what has sat in the catalogue without a single sale.

### Updating an order card
The agent re-reads the order card and sets a new status or a comment — if the key is allowed to change orders; otherwise it says plainly that it stays a reader.

## How to connect

**Before you connect**

- Administrator rights in the RetailCRM workspace.
- The shops whose orders the agent needs are connected in the workspace.

### Copy the subdomain from your account address
In “https://myshop.retailcrm.ru” the subdomain is myshop and “Account domain” is retailcrm.ru after the first dot. Some use retailcrm.pro.

### Open “Administration” → “Integration”
Open “Administration” → “Integration” and press “Add” in the API keys list. The token is generated automatically, at least 32 characters.

### Grant the key access to the right shops
In “Access type” pick “Access to all shops”, or tick the ones you need in the “Shops” field. Orders and customers of shops left out will not be returned.

### Tick the allowed methods and copy the key
In “Allowed API methods” enable orders, customers, products, reference books, tasks and users, then save and copy the key.

## FAQ

### What is needed to connect RetailCRM?
The account address — the subdomain and the domain your workspace opens on (retailcrm.ru or retailcrm.pro) — and an API key from Settings, Integration, API access keys. A key can be limited to only the methods and stores you need.

### What data does the agent read?
Orders, customers, products, reference books, tasks and analytics — for the stores the key has access to.

### Can access be limited to a single store?
Yes, it is set in RetailCRM itself at the API key level: the agent will see only the stores you pick.

### How does AI help an online store?
It counts orders by status, source and store with revenue for the period, keeps cancellations and non-redemptions out of the till figure, segments customers by purchase frequency and recency to surface lapsed regulars, and from the order contents shows what sells most and what sits in the catalogue without a single sale.

[Open RetailCRM](https://www.retailcrm.ru)