# AI Agents for Ecommerce: What They Can Do in Kentro

Source: https://kentro.ai/agents/capabilities/
Last updated: 2026-11-17

What AI agents for ecommerce can do in Kentro: every workflow by area, in the app, with Kentro AI, over MCP and over the API. Dated and kept current.

## Every workflow, and who can run it

Each row is a job in Kentro. Each column says whether a person in the app, Kentro AI, your agent over MCP or your agent over the API can do it, and how.

- Dated November 17, 2026
- Checked against the MCP tool registry
- Checked against the Channel API reference

- [Connect an agent](https://kentro.ai/agents/mcp/#connect)
- [Get started](https://kentro.ai/get-started/)

## What can AI agents do for an ecommerce business?

AI agents for ecommerce can answer questions from live order and stock data, investigate a late order, build reports and draft documents for a person to approve. In Kentro, agents read over MCP with a user's permissions and write orders, stock levels and invoices through the Channel API with a scoped key, as the matrix below shows.

## How to read the matrix

What each value in the capability matrix means

| Value | Meaning |
| --- | --- |
| Read | It can look the information up and report on it, with the permissions of the user or the key. |
| Write | It can create or change the record directly. |
| Write with approval | It prepares the change, and a person approves it before anything is saved or sent. |
| Not available | It does not do this job. Where another operator does, that column of the row says so. |

## The capability matrix

Filter by area. Every cell was checked on November 17, 2026.

Every cell checked on 2026-11-17. Access levels: Read, Write, Write with approval, Not available.

- In the app: People in the Kentro web apps and the Terminal handheld app.
- Kentro AI: The Kentro assistant, working with your permissions.
- Your agent over MCP: Claude, Codex or another MCP client, signed in as you.
- Your agent over API: Your code or agent with a scoped API key.

| Area | Workflow | In the app | Kentro AI | Your agent over MCP | Your agent over API | Notes |
| --- | --- | --- | --- | --- | --- | --- |
| Orders | Look up an order, its items, payment and tracking | Read | Read | Read | Read | Tools: `getOrderDetail`, `listOrders`. |
| Orders | Summarize orders and revenue for a period | Read | Read | Read | Read | Tools: `getOrdersSummary`, `runKiqReport`. |
| Orders | Create, import or update an order | Write | Not available | Not available | Write | Agents create and update orders through the Channel API. No MCP tool writes an order. |
| Orders | Cancel an order | Write | Not available | Not available | Write |  |
| Customers | Create or update a customer | Write | Not available | Not available | Write |  |
| Inventory | Check stock by product, warehouse and location | Read | Read | Read | Read | Tools: `getInventorySummary`, `getTopProducts`. |
| Inventory | Adjust stock or set on-hand quantities | Write | Not available | Not available | Write | The API sets on-hand quantities per warehouse, location and lot with a reason. No MCP tool changes stock. |
| Inventory | Transfer stock between warehouses | Write | Not available | Not available | Not available |  |
| Inventory | Create or update products, listings and price lists | Write | Not available | Not available | Write |  |
| Purchasing and planning | Create or update a purchase order to a vendor | Write | Not available | Not available | Not available | A person creates vendor purchase orders in the app. Agents read stock, sales and open purchase orders to prepare one. |
| Purchasing and planning | Record, accept or reject a retailer purchase order (EDI) | Write | Not available | Not available | Write | These endpoints are for purchase orders a retailer sends you. Accepting one creates the sales order. |
| Purchasing and planning | Find what will run out and what to reorder | Read | Read | Read | Not available | Demand planning and forecasts live in Kentro IQ. Tools: `getInventorySummary`, `runKiqReport`, `runSqlQuery`. |
| Purchasing and planning | Add a promotion or launch to the sales forecast | Write | Write with approval | Not available | Not available | Kentro AI drafts the demand event; it is saved only after the user approves it in the chat. Tools: `propose_demand_event`. |
| Fulfillment and shipping | See the fulfillment pipeline and what is stuck | Read | Read | Read | Read | Tools: `getFulfillmentPipeline`. |
| Fulfillment and shipping | Route, reroute, hold or cancel a fulfillment order | Write | Not available | Not available | Write |  |
| Fulfillment and shipping | Rate shop and buy a shipping label | Write | Not available | Not available | Not available | Labels are bought in the app from your prepaid postage balance. |
| Fulfillment and shipping | Record a shipment and its tracking from another system | Write | Not available | Not available | Write |  |
| Fulfillment and shipping | Quote, book and track LTL, FTL and intermodal freight | Write | Not available | Not available | Not available |  |
| Warehouse | Receive, put away, pick, pack and count on the handheld | Write | Not available | Not available | Not available | Scanning stays with people on Kentro Terminal. Agents have no warehouse write tools. |
| Warehouse | See what is left to pick before the cutoff | Read | Read | Read | Read | Tools: `getFulfillmentPipeline`, `listOrders`. |
| 3PL billing | Bill 3PL clients the fees you set for each one | Write | Not available | Not available | Not available | Fees are debited from each client’s prepaid balance in the provider portal. |
| Finance | Record invoices and payments, and apply a payment | Write | Not available | Not available | Write |  |
| Finance | List reconciliation exceptions and explain a variance | Read | Read | Read | Not available | 5-Way Reconciliation is in every Kentro OS plan and needs a connected QuickBooks. Tools: `list_recon_exceptions`, `get_recon_exception`, `explain_variance`, `suggest_matches`. |
| Finance | Fix a reconciliation exception in place | Write | Not available | Not available | Not available | Kentro AI suggests the fix; a person with invoice or payment permission applies it in the app. Tools: `get_recon_next_actions`. |
| Analytics | Run a report or ask a question of live data | Read | Read | Read | Not available | Data questions run on a read-only database connection. Tools: `listKiqReports`, `runKiqReport`, `listQueryableTables`, `runSqlQuery`. |
| Analytics | Build or edit a dashboard | Write | Write | Write | Not available | Over MCP, dashboards are created through askCopilot. Tools: `createDashboard`, `createDashboardPanel`, `updateDashboardLayout`, `listDashboards`. |
| Analytics | Review findings and mark them done or skipped | Write | Write | Write | Not available | Skipping a finding requires a reason. Tools: `getRecommendations`, `actOnFinding`. |
| Marketing | Draft and publish a social post, ad, landing page or email | Write | Write with approval | Not available | Not available | In Kentro GO every AI output is a draft. Nothing is published or sent until a person approves it. Kentro GO has no MCP tools. |
| Storefront | Place an order as a wholesale buyer at that buyer’s prices | Write | Not available | Not available | Write | The B2B portal, the storefront and the Store API are part of Kentro Storefront, in every Kentro OS plan. |
| Events and tracking | Get a webhook when an order or shipment changes | Not available | Not available | Not available | Not available | The Channel API has no outbound webhooks: integrations poll with updatedSince. |
| Events and tracking | Send browser and server events to Kentro Pixel | Not available | Not available | Not available | Write | Events come from your site or server code, not from people in the app. |

## Where agents stop

Some jobs stay with people in the app: warehouse scanning, buying shipping labels, charging a customer’s saved card, vendor purchase orders, stock transfers between warehouses, freight bookings, 3PL client billing, fixing reconciliation exceptions and account settings. Kentro GO has no MCP tools, so marketing work happens in the Kentro GO app, where a person approves every AI draft.

- [How agents connect over MCP](https://kentro.ai/agents/mcp/)

## How this page stays current

The MCP column follows the tool registry Kentro AI uses: the MCP server mirrors the assistant’s tools, except two that run inside the web app, so your client always lists the current set. The API column follows the Channel API reference on docs.kentro.ai. When a release changes what a person, Kentro AI or an agent can do, this page changes with it, and the date at the top moves.

- MCP: askCopilot, getSessionContext and every Kentro AI tool except two that run inside the web app
- Writes to operational records: the Channel API with a write-scoped key
- Approvals: Kentro GO drafts and Kentro AI demand events

- [Read the changelog](https://kentro.ai/changelog/)

## Related

- [Connect an agent over MCP](https://kentro.ai/agents/mcp/)
- [Channel API reference](https://docs.kentro.ai/reference/channel-api-getting-started)
- [Developers and API keys](https://kentro.ai/developers/)
- [Kentro AI, the assistant built into Kentro](https://kentro.ai/agents/kentro-ai/)
- [Changelog](https://kentro.ai/changelog/)
- [AI and agents in Kentro](https://kentro.ai/agents/)

## See it on your own data

Connect an agent to your workspace, or create a workspace to try it.

- [Connect an agent](https://kentro.ai/agents/mcp/#connect)
- [Get started](https://kentro.ai/get-started/)
