IKAS Commerce
Connects your ikas online store to a Botonom agent that tracks orders, revenue, stock and customers, and (when you allow it) updates products, runs campaigns and manages fulfillment.
This guide begins with What IKAS Commerce does, continues through What your agent can do, Install and use it, Connect your ikas store, and finishes with Good to know.
What IKAS Commerce does
IKAS Commerce connects your ikas online store (ikas.com) to a Botonom agent, so one of your AI teammates can answer questions about the store and, when you allow it, take action on it in plain language.
Once connected, your agent works with your live store data. It can look up products and stock, track orders, revenue, transactions and abandoned checkouts, review customers, and read the store settings it needs to give accurate answers (sales channels, shipping and tax setup). With the right permissions, the same agent can also create orders, update products and prices, manage fulfillment and refunds, and run campaigns.
What it touches, in plain terms:
- Your products, brands and inventory
- Your orders, payments and revenue
- Your customers and abandoned checkouts
- Your campaigns and coupons
- Store configuration it reads for context (merchant profile, sales channels, shipping, taxes, address data)
Your store data is not copied out anywhere. The agent reads and writes directly through ikas's own admin connection, using a token you provide, and every action is scoped to what you have allowed.
What your agent can do
The skill turns your ikas store into things you can simply ask for. Reading your store is available right away. Actions that change your store are separate permissions you switch on per teammate (see Good to know).
Look up and report (available by default)
- List your products, brands and attributes, including stock levels, with search and filtering
- Track orders by date, status and payment state, and organize them with tags
- See the money side of orders: transactions, pending payments and revenue totals
- Understand where orders came from: traffic source, referrer and UTM tags (order sessions)
- Review customers and their profile fields, and spot abandoned checkouts to win back sales
- Read store setup for accurate answers: merchant profile, sales channels, shipping and tax settings, plus country, state, city and district address data
Change your store (role-gated, off by default)
- Orders: create an order with payment, fulfill line items, cancel or refund specific lines, update package status, approve pending payments, and add, remove or download order invoices (PDF)
- Products and stock: create and update products, add or remove variants, update variant prices, and update stock levels by location
- Campaigns: create and update campaigns, attach coupon codes, and remove campaigns
- Customers: update customer details and add timeline notes
Install and use it
- Open the Skill Marketplace in your Botonom dashboard and install IKAS Commerce.
- Assign the skill to an agent (for example your Sales Assistant or Operations Helper).
- Add your store connection once (see Connect your ikas store below).
- Chat with the agent in normal language.
Realistic examples once it is connected:
User: How many orders came in yesterday, and what did they add up to?
Agent: Yesterday you had 42 orders totaling 68,540 TL.
3 of them are still awaiting payment. Want me to list those 3?
User: Which products are down to fewer than 5 in stock?
Agent: 7 products are below 5 units. The lowest are
"Linen Shirt / M" (1 left) and "Canvas Tote" (2 left).
I can show the full list or filter to one brand.
User: Show me abandoned checkouts from the last 7 days.
Agent: There are 18 abandoned checkouts in the last 7 days,
worth about 24,300 TL, most dropping off at the payment step.
Want the customer contacts so you can follow up?
If the agent's role has the matching write permission turned on, you can also ask it to act, for example "Mark order #10432 as fulfilled" or "Set the price of the Canvas Tote to 349 TL". Without that permission, the agent will tell you it is not allowed to make the change.
Connect your ikas store
IKAS Commerce connects with a token you paste in once, not a click-through login. Setup takes about three minutes.
- In your ikas admin panel, create a Private App and set its app type to MCP-Client.
- Copy the token it generates (it starts with
mcp_). - In Botonom, open the skill's configuration and paste it into the IKAS API Token field. Leave the optional endpoint field blank unless ikas gives you a custom one.
- Save. Your agent is now linked to that store.
Because the token comes from your own ikas store, the agent can only reach what your ikas app is allowed to reach. To disconnect, remove or replace the token in the skill configuration.
Good to know
Read first, write when you decide. Looking up your store is available immediately. Every action that changes your store is a separate permission that is off by default for everyone except your full-access owner role. You turn each one on per teammate in Roles & Access, so a support agent can read orders while only an operations lead can issue refunds.
It stays inside ikas. The skill can only see and act on your ikas store. It does not reach into other tools, and it does not process payments itself: it records and approves transactions that already exist in ikas.
Public chat widget is catalog-only. When anonymous visitors talk to your agent through a public widget, the skill lets it read only your product catalog (products, brands and attributes). It can never see orders, customers or settings through that surface, and it can never make changes.
Storefront script editing is locked. Adding custom JavaScript to your storefront is disabled at the platform level for safety and stays off unless your operator deliberately enables it, even if a role has the permission.
On the roadmap. Read reporting is the fully proven core today, and write actions are being rolled out under tight role control. Proactive automation, for example the agent reacting on its own when a new order arrives, is planned but not live yet.