Skip to content
ajan.io

From stock to customer, run every retail moment smarter.

Run store, e-commerce, stock, order, and customer data with AI agents. Build operations that understand demand, use product knowledge, check systems, and start the actions that matter.

  • Stock
  • Store
  • Orders
  • Campaigns
  • Returns
  • E-commerce
  • Customers
Sample scenario
ajanWhatsApp

Customer: When will the navy wool coat be back in size M?

Size M is out of stock online right now, but our Kadıköy store has 2. I can hold one for you, or the store can ship it to your address.

Hold in storeShip to me

The agent, behind the scenes

  • Product catalogWool coat · navy · M
  • StockOnline 0 · Kadıköy 2 · Bornova 0
  • Ship-from-store ruleIn-stock items ship within 2 business days

Next step

48-hour hold at the Kadıköy storeAutomatic

The store team is notified.

The customer says what they want. Your agent knows the rest.

Even one question can require many systems evaluated together.

In retail, a single customer question can require stock, product, order, campaign, delivery, and return data to be evaluated together. ajan.io agents don’t just “talk about products”; they can find the right knowledge, check system data, and start the next piece of work.

ajanOne question

  • Knows the product

    Product descriptions, attributes, and company policies.

  • Checks stock

    Pulls current status from connected systems.

  • Understands the order

    Evaluates customer and order context together.

  • Runs the process

    Starts request, return, or operations flows.

From customer question to operational outcome — one agent experience.

From “When does this product arrive?” to a delivery action

  1. 01

    What the customer sees

    Customer request arrives

    From web, WhatsApp, or your existing app.

  2. 02

    What happens in the back office

    Product knowledge is found

    Product and company sources are checked.

  3. 03

    What happens in the back office

    Stock is queried

    Store or warehouse stock is pulled from the connected system.

  4. 04

    What happens in the back office

    Order status is evaluated

    Delivery or supply options are determined.

  5. 05

    What the customer sees

    Best option is offered

    Available alternatives are explained to the customer.

  6. 06

    What happens in the back office

    Action is taken

    A reservation, request, or operations record can be created.

  7. 07

    What happens in the back office

    Approval is requested if needed

    Discounts, exceptions, or special handling go to an authorized user.

  8. 08

    What the customer sees

    Customer is informed

Wherever the customer asks

One agent works across channels with the same product and stock information. Each channel needs its own setup and authorization.

  • Website

    A chat window on your site answers the question right on the product page.

  • WhatsApp

    Order and return questions in the channel customers already use.

  • Store teams

    Stock, campaign, and procedure questions through Teams or Slack.

Example scenarios

  • Product advisor

    Offers the right options based on product knowledge and customer need.

  • Stock lookup

    Returns current stock by channel and location.

  • Order status

    Explains the current stage and starts the needed operation.

  • Returns & exchanges

    Checks company policy and runs the right process.

  • Store operations

    Summarizes daily exceptions, critical stock, and pending work.

  • Campaign info

    Explains campaign terms from corporate sources and checks eligibility.

  • Sales analysis

    Summarizes data by product, category, or channel.

  • Post-purchase actions

    Classifies requests and issues and starts the related flow.

From store to head office: who hands off what?

In retail the same question lands on four different teams. The agent takes the repeated part off each one.

  • Customer service

    First answers and ticket records for order, shipping, and return questions.

  • Store teams

    Stock in other stores, campaign terms, procedure questions.

  • E-commerce team

    Consistent product information, stock alerts, campaign questions.

  • Regional and category managers

    Sales and stock summaries, stores that need attention.

Where the agent looks

Behind every customer answer sit several systems. The agent reads them at once and starts the permitted action in the right one.

  • Product catalogSpecs, size charts, care information
  • Stock and storesStock by channel and store
  • Order systemOrder, payment, and return status
  • Carrier trackingShipment status, delivery requests
  • Campaign rulesActive campaigns and their terms
  • PoliciesReturn, exchange, and delivery rules

Connections are set up through ready integrations, MCP servers, or your own API. If your e-commerce platform has no ready connection, it can be defined as a custom integration.

Happy customer, rule intact

The agent immediately does what the policy allows and leaves anything involving amounts, exceptions, or goodwill to the team. You set the split.

The agent does right away

  • Answers stock and order status
  • Creates a code for returns within the policy window
  • Opens an in-store hold request
  • Explains campaign terms with the source

The team decides

  • Late returns or exception requests
  • Refunds and goodwill discounts
  • The outcome of a damaged-item complaint
  • Price requests outside a campaign

Example prompts

Ask the agent…Sample scenario

  • Which stores have the product this customer is looking for?
  • Why hasn’t this order shipped yet?
  • Does this product meet our return conditions?
  • Show products whose stock risk rose in the last 7 days.

Not one AI feature — a working system

Work in your industry runs on the same ajan.io architecture.

  • Your company knowledge

    Lets the agent know your company and your rules.

    Product information, return policy, campaign terms

  • AI agents

    Evaluate information and decide what work to do next.

    Product advisor, order and return agent

  • Integrations

    Pull data from existing systems and take permitted actions.

    Catalog, stock, order, and carrier connections

  • Workflows

    Manage multiple steps, conditions, and waits in one process.

    Return and exchange from question to delivery

  • Human approval

    Keeps critical decisions with the right person.

    Approval for exception returns and refunds

  • Governance

    Keeps access, usage, and AI costs under control.

    Usage by channel and store

Knowledge + decision + action + process. One platform.

Not just AI chat — a layer that runs work

AI chat onlyajan.io
Answers a questionFinds knowledge, evaluates, and advances the work
Works from user-provided contextUses company knowledge and system context
Generates textCan act in systems
Ends in one interactionCan start multi-step workflows
The user tracks progressCan keep process state
Fully manual or fully automaticCan require human approval at critical points
Model-centricWork-process-centric

Faster customer experience, fewer operational handoffs.

Instead of jumping between product screens, stock systems, and order panels to answer one question, unite knowledge and action in a single agent experience.

First agent: "Where is my order?"

The most common customer service question is one of the easiest to hand off. Start here; add return and stock questions later.

  1. 1

    Upload the policies

    Add your delivery and return policies as knowledge sources.

  2. 2

    Connect orders and carrier

    Connections that can read order status and tracking are enough.

  3. 3

    Open one channel

    Publish on your website or WhatsApp first and watch the answers.

Questions retail teams ask

What people ask most before publishing a customer-facing agent.

All FAQs

No. It answers only from the campaign rules you connect. Out-of-rule requests go to the team; you decide which actions need approval.

Turn your customer and operations data into working AI.

Start free · No credit card required