Ecommerce AI Agents for UK Online Retailers
We build agents for your store, your marketplaces and the back office behind them. Your store sells on its own site, on Amazon.co.uk and eBay, and maybe to trade accounts. Orders pass through Linnworks, Brightpearl or Mintsoft, leave with Royal Mail, DPD or Evri, and end up in Xero or Sage. FactoryJet builds AI agents that work across that chain: answering order and returns questions, keeping listings right, drafting trade quotes and purchase orders. A person approves anything that moves money. You own what we build.
An ecommerce AI agent takes one repeated store job, such as a delivery question, a return, a listing update or a trade order, looks up the facts in your store, marketplaces and back-office systems, and prepares the reply or the change. Low-risk answers go straight out. Refunds, prices and supplier orders wait for a person. This is the kind of AI for ecommerce we build: one job at a time, inside the systems you already run, on any platform, and owned by the client.
An API is the official door a system offers other software, so an agent can read an order without anyone logging in. An API key is the pass for that door, and it decides what the agent may see and change. A digital link is HMRC’s name for data moving between software with nobody retyping or pasting it. An ERP is the back-office system that holds stock, buying and accounts in one place, such as NetSuite or Odoo. A SKU is the stock code you give each product and each size or colour of it.
Most of an ecommerce agent build is deciding which system owns each fact: stock in Shopify, Linnworks or Odoo, trade prices in the store or the ERP, and who approves a refund on a Klarna order. We settle that on paper before anything is built.
- 14 days
after delivery: how long UK customers can cancel most online orders
GOV.UK - Not a link
copy and paste between software, for Making Tax Digital for VAT
HMRC VAT Notice 700/22 - 4 safeguards
for significant decisions made solely by automation, under UK GDPR Article 22C
ICO draft guidance - 2 Aug 2026
when the EU AI Act’s rule on telling people they are talking to an AI applies
EU AI Act, Article 50
AI in ecommerce: nine store jobs we build agents for
Each agent does one job well before it gets a second. The jobs are listed roughly in the order we suggest building them, starting with the ones that only read data.
Delivery questions
The agent reads the order, the courier and the tracking number, checks the latest Royal Mail, DPD or Evri status and replies by email, chat or marketplace message. It confirms who is asking before sharing an address.
Returns and refunds
Each request is checked against your policy and dated from delivery, so the 14-day cancellation window is applied the same way every time. The agent prepares the refund and a person releases it.
Amazon.co.uk listings
Changes go through Amazon’s Selling Partner API on the UK marketplace (ID A1F83G8C2ARO7P). We use partial updates, because Amazon warns that attributes left out of a full update may be dropped.
eBay UK offers
On eBay’s Inventory API an item record with your SKU comes first, then an offer, and publishing the offer creates the live listing. The agent keeps the item data clean so offers publish without errors.
OnBuy, Etsy and other UK marketplaces
OnBuy’s API covers products, listings priced and stocked by SKU, and order export. Etsy’s Open API v3 covers inventory, sales orders and shop management. For any other marketplace we read the integration terms for your seller account before we quote, and the agent prepares the product data behind it.
Trade quotes and reorders
A buyer emails twenty codes and quantities. The agent matches each line, applies that account’s prices, checks stock and saves a draft for your sales team. See our B2B ecommerce work.
Stock and purchase orders
Stock and sales are read from Linnworks, Brightpearl, Mintsoft or your ERP and compared with your reorder points. The agent drafts the purchase order. Your buyer sends it.
Orders into the books
Sales, refunds and fees post to Xero, Sage or QuickBooks by API, on the accounts and tax codes your accountant chooses. Our Shopify Xero integration page covers the detail.
Customer service triage
Messages arriving in your helpdesk, such as Gorgias or Zendesk, are sorted by what they need: answered, drafted for a person, or escalated. Any message about a chargeback, a complaint or a product safety problem goes straight to a person. For a support desk built around agents, see AI customer service.
Sources, read on 29 October 2026 unless marked: Amazon Selling Partner API: marketplace IDs; Amazon Selling Partner API: Listings Items API; eBay Developers Program: Inventory API overview; OnBuy API documentation v2 (read 31 October 2026); Etsy Open API v3 documentation (read 31 October 2026); GOV.UK: Online and distance selling for businesses.
What the agent reads, what it drafts, and what stays with your team
The same rule runs through every system. The agent reads what it needs and writes drafts. Money and prices stay with a person until the logs show the agent follows your rules.
Swipe sideways to see every column.
| System | The agent reads | The agent drafts | A person approves |
|---|---|---|---|
| Store: Shopify, WooCommerce, Adobe Commerce, BigCommerce, Commerceflo | Orders, customers, products | Replies, return records | Refunds, discounts |
| Marketplaces: Amazon.co.uk, eBay UK | Orders, listing errors | Listing updates | Price changes |
| Channel and stock: Linnworks, Brightpearl, Mintsoft | Stock, despatch, tracking | Purchase orders | Supplier orders |
| Accounting: Xero, Sage 50, Sage 200, QuickBooks UK | Invoices, payment status | Sales, refund and fee entries | Account and tax code mapping |
| ERP: NetSuite, Business Central, Odoo, Sage Intacct | Customer prices, credit terms | Quotes, sales orders | Credit over limit |
| Payments: Stripe, GoCardless, Klarna, Clearpay | Payment and refund status | Refund requests | Every refund, at first |
Brightpearl’s API documentation covers sales orders, products and price lists, goods-in and goods-out notes, stock transfers and journals, which is why it is a common place for an agent to read from. Linnworks publishes an API for applications built on Linnworks data. Where neither is in place, we read from the store or the ERP directly.
Sources, read on 29 October 2026 unless marked: Brightpearl API documentation; Linnworks API reference: overview.
Next step
Send us twenty real customer emails. We show you what an agent would have done.
Pick one job: delivery questions, returns, listings or trade orders. On a short call with the founder we agree the systems it touches, then we run a first version on your own examples before you sign anything.
Four UK and EU rules an ecommerce agent has to respect
Cancellations and returns. GOV.UK says customers can cancel most online orders up to 14 days after delivery. If you never told them about that right, they can cancel at any time in the next 12 months. A returns agent has to know the delivery date and whether the right was explained, so it reads both from the order before it says yes or no.
Making Tax Digital for VAT. HMRC’s notice defines a digital link as data moved electronically with no manual step, says copy and paste does not count, and says that once data sits in your VAT records any further transfer must use digital links. An agent that posts orders and refunds to Xero or Sage by API keeps that chain intact. One that writes a spreadsheet for someone to paste does not.
UK GDPR after the Data (Use and Access) Act 2025. The Act received Royal Assent on 19 June 2025, and the ICO says its data protection changes are now in force. The ICO’s draft guidance on automated decisions lists four safeguards for significant decisions made solely by automation: information, the chance to make representations, human intervention and the right to contest. We design agents so that refusals go to a person.
The EU AI Act, if you sell into the EU. Article 2 reaches providers and deployers outside the EU when an AI system’s output is used in the EU. Article 50 says systems that talk directly with people must tell them they are dealing with an AI, unless that is obvious, and the Act’s timeline applies it from 2 August 2026. Our shopper-facing agents say so in their first message.
Sources, read on 29 October 2026 unless marked: GOV.UK: Online and distance selling for businesses; GOV.UK: VAT Notice 700/22, Making Tax Digital for VAT; ICO: The Data (Use and Access) Act 2025; ICO: What are the ADM safeguards? (draft guidance, updated 31 March 2026); EU AI Act, Article 2: scope; EU AI Act, Article 50: transparency obligations.
We are not lawyers or tax advisers. We map where an agent touches these rules, and you confirm the position with your accountant or solicitor.
Off-the-shelf AI app or a custom ecommerce agent
For plenty of jobs we suggest starting with an app. This is how we decide whether a job needs a custom agent or simpler ecommerce automation from a tool you can buy.
Swipe sideways to see every column.
| Question | Custom agent (FactoryJet) | Helpdesk AI app (Gorgias, Intercom Fin) |
|---|---|---|
| Job follows standard rules | Works, may be more than you need | Usually the right start |
| Job crosses two systems (store and Linnworks, store and ERP) | Built for it | Only if a connector exists |
| UK marketplaces beyond Amazon and eBay | Scoped per channel | Often not covered |
| Trade prices and credit terms | Read from your ERP | Limited |
| Who owns the code | You, from day one | The vendor |
| Time to first answer | Weeks, after a demo on your data | Days |
Gorgias sells an AI Agent built for ecommerce support that connects to Shopify and BigCommerce. Intercom sells Fin, a customer-facing AI agent that works in Intercom and also inside Zendesk, Salesforce and other helpdesks. Either is a sound first step for standard questions.
Sources, read on 29 October 2026 unless marked: Gorgias: AI Agent (read 31 October 2026); Fin by Intercom (read 31 October 2026).
Two UK trade sellers whose data an agent would work on
GPSUK supplies branded promotional products to UK businesses, a trade where buyers reorder the same lines and often need a quote first. FactoryJet built its trade storefront on Commerceflo, where business buyers log in, see their own account prices and move from quote to order without anyone retyping it. Read the GPSUK case study.
Sow Easy is a UK wholesale client with a WordPress WooCommerce trade store, where Odoo stays the master for stock, pricing and product codes. The build is in progress: the store and the Odoo link are being tested on staging, and launch is still ahead. Read the Sow Easy case study.
Neither is described here as an AI agent project. They show the part that decides whether an agent works: one owner for each fact, and clean links between the store and the system behind it.
- Demo before you sign. Working software on your own data before any contract.
- Fixed price per phase. Each phase is scoped, priced and signed on its own.
- You own it. The code and the repository are yours from day one.
- Your accounts, at cost. AI and hosting can run in your own accounts at cost, with no markup.
- Defect cover included. Defects are fixed inside the build price for a cover period agreed before work starts.
- Support is optional. Each change is quoted and approved, with no monthly minimum.
How we build an ecommerce AI agent, in seven steps
The steps are the same for a delivery-question agent and a trade-order agent. What changes is how many systems step three has to cover.
- 01
Pick one job and count it
We take a month of the messages, returns, listing errors or trade orders behind the job and sort them by type. That count becomes the brief and the test set.
- 02
Write down who owns each fact
Stock, prices, tracking, refunds and customer details each get one home: the store, Linnworks, the ERP or Xero. Where two systems disagree, the map says which wins.
- 03
Agree the keys and the approvals
Each system gets an API key made for the agent, with the least access it needs. We list every action that waits for a person, and you sign that list.
- 04
Show it on your own data
Before a contract, a first version runs on twenty or thirty of your real cases, with its drafts beside what your team sent. You decide from that.
- 05
Build and test on a copy
The agent is built against a staging store or sandbox accounts, which are test copies with no real customers or money. Awkward cases go through first: a part refund, a Klarna order, an EU customer, a missing SKU.
- 06
Run beside the team
For the first weeks the agent drafts and your team sends. We compare the two daily and adjust the rules where they differ.
- 07
Go live and stay on
Low-risk answers go out on their own. Money and prices stay with a person until you change that rule. The same team supports the agent, and you own the code.
What to put in a brief or RFP for an ecommerce agent
The best leads we get are a page or two naming the job and the systems. An RFP from your procurement team is welcome too. With either, we can reply with a fixed quote for the first phase.
FactoryJet quotes the build, and any support you choose, as fixed prices in writing after a short scoping call. If you want, we keep managing the servers, AI models, API connections and maintenance.
Related UK pages: AI agents, customer service, Xero and B2B stores
If the agent is part of a wider plan outside the store, our UK AI agents page covers sales, operations and finance work. If the store itself needs building or rebuilding first, see ecommerce development in the UK and WooCommerce development.
For US marketplaces, including Walmart, see the US ecommerce AI agents page.
Sources and the dates we read them
Every rule, platform fact and price range on this page was read on the pages below on 29 October 2026, or on the date shown beside the source. Laws change and vendors update their pages, so open the linked page before you act on a figure.
- GOV.UK: Online and distance selling for businesses
- GOV.UK: VAT Notice 700/22, Making Tax Digital for VAT
- ICO: The Data (Use and Access) Act 2025
- ICO: What are the ADM safeguards? (draft guidance, updated 31 March 2026)
- EU AI Act, Article 50: transparency obligations
- EU AI Act, Article 2: scope
- Amazon Selling Partner API: marketplace IDs
- Amazon Selling Partner API: Listings Items API
- eBay Developers Program: Inventory API overview
- Brightpearl API documentation
- Linnworks API reference: overview
- Softomate Solutions: AI chatbot development cost in the UK
- Cloudswitched: AI software development cost in the UK, 2026
- OnBuy API documentation v2 (read 31 October 2026)
- Etsy Open API v3 documentation (read 31 October 2026)
- Gorgias: AI Agent (read 31 October 2026)
- Fin by Intercom (read 31 October 2026)
Ecommerce AI agent questions from UK retailers and their finance teams
Ecommerce AI agents
What is an ecommerce AI agent?
It is software that does one store job from start to finish. It reads a customer email, a return request, a trade order or a stock report, looks the facts up in your own systems, and prepares the answer, refund, quote or purchase order. A person approves anything that moves money or changes a price. We build each one for your store, and you own it.
Is an ecommerce chatbot the same as an AI agent?
No. An ecommerce chatbot, including a plain ChatGPT chat, answers what you type. It holds none of your store’s API keys, returns rules or approval steps. An ecommerce agent is built around a model like it and given those: read access to your orders, a courier tracking lookup, a way to save a draft refund, and rules about when to stop and ask a person. Giving it those things is the build.
How is AI used in ecommerce by UK retailers?
We look at four places first. Customer service: questions about orders, deliveries and returns. Product data, where listings for Amazon.co.uk, eBay and your own store have to say the same thing. Trade sales, where buyers email orders that someone retypes. And the back office, where orders, stock and payouts have to reach Xero or Sage. We start with whichever costs your team the most hours.
Should we buy an AI app or have a custom agent built?
Buy the app if it already does the job. Helpdesk AI such as the Gorgias AI Agent or Intercom’s Fin, which also works inside Zendesk, handles plenty of standard questions. A custom agent makes sense when the job follows your own rules, crosses two systems such as Shopify and Linnworks, or covers a marketplace the apps ignore. Many stores run both: an app on chat and a built agent on returns or trade orders.
Store and marketplace jobs
Can an AI agent answer “where is my order?” messages?
Yes, and we usually suggest it as the first job. It works the same for Royal Mail, DPD and Evri parcels. The agent finds the order, reads the tracking number and courier from your store or your shipping software, checks the latest status and replies in the channel the customer used. It only reads data, so the risk is low. We still make it confirm who is asking before it shares an address or a delivery detail.
Can an agent handle returns and refunds under UK rules?
It can check each request against your returns policy and the UK cancellation window, then prepare the refund. GOV.UK says customers can cancel most online orders up to 14 days after delivery, and up to 12 months if you never told them about that right. The agent dates every request from the delivery date. A person approves the refund before money goes back through Stripe, Klarna or Clearpay.
Can an AI agent manage our Amazon.co.uk and eBay listings?
It can draft and send listing changes through each marketplace’s own API. Amazon’s documentation warns that attributes left out of a full listing update may be dropped, so our agent uses partial updates and previews errors first. On eBay, an inventory item with a SKU must exist before an offer, and the published offer is what becomes the live listing. Price changes stay with a person.
What about UK marketplaces other than Amazon and eBay?
Each marketplace has its own seller integration and its own product data rules. OnBuy publishes an API for products, listings by SKU and order export, and Etsy’s Open API v3 covers inventory, sales orders and shop management. Before we quote, we read the integration terms for your seller account and check whether your existing channel software, such as Linnworks or Brightpearl, already lists there. The agent then works on the product data and order flow behind those channels, whichever tool publishes the listing.
Can an agent handle trade quotes and repeat orders?
Trade buyers often email a list of codes and quantities. The agent matches each line to a product, applies that account’s price list, checks stock and saves a draft quote or order for your sales team to send. GPSUK, a UK promotional products supplier, runs its trade store on Commerceflo, where business buyers reorder at their own account prices. The agent work sits on the same kind of data.
Can an agent draft purchase orders when stock runs low?
It can. The agent reads stock on hand and recent sales from wherever stock lives, which for many UK sellers is Linnworks, Brightpearl, Mintsoft or an ERP, compares them with the reorder points you set, and drafts a purchase order for your buyer to approve. It never sends a supplier order on its own until you have seen enough correct drafts to change that rule.
Your systems and safety
Which ecommerce platforms do you build agents for?
Shopify and Shopify Plus, WooCommerce, Adobe Commerce (Magento), BigCommerce, Commerceflo and custom or headless stores. A back-office agent talks to the platform through its admin API, the back-office door to orders and products, so the platform matters less than you might expect. A customer-facing agent has to fit your theme or front end, which is where most of the platform-specific work sits.
Can the agent work with Linnworks, Brightpearl or Mintsoft?
Through their APIs. Brightpearl’s API documentation covers sales orders, products and price lists, goods-in and goods-out notes, stock transfers and journals. Linnworks publishes an API for building applications on Linnworks data. When one of these is already the record for stock and orders, the agent reads from it and writes drafts back to it, so your team keeps working in the screen they know.
Can the agent post orders into Xero, Sage or QuickBooks?
It can, and for VAT that link matters. HMRC’s Making Tax Digital notice says copy and paste is not a digital link, and that manually moving data between software is not acceptable once it is part of your VAT records. An agent that moves order, refund and fee data by API keeps that chain digital. Your accountant decides which accounts and tax codes each entry posts to.
We run NetSuite, Business Central or Odoo. Can an agent use it?
Yes. In many UK businesses the ERP (the back-office system for stock, buying and accounts) holds stock, customer prices and credit terms, and the store copies them. The agent reads those facts from NetSuite, Dynamics 365 Business Central, Odoo or Sage Intacct and writes draft quotes and sales orders back for your team to check. Credit over a customer’s limit always goes to a person.
Is it safe to give an AI agent access to our store and payments?
It is as safe as the key it is given. Each agent gets its own API key with the least access its job needs, starts read-only, and logs every action. Refunds, discounts, price changes and anything touching Stripe, GoCardless, Klarna or Clearpay wait for a person. If the agent misbehaves you can switch off one key without touching the rest of your setup.
UK and EU rules
Does UK GDPR let an AI agent make decisions about customers?
With safeguards, yes. The Data (Use and Access) Act 2025 received Royal Assent on 19 June 2025 and changed the UK GDPR rules on automated decisions. ICO draft guidance on Article 22C says that for significant decisions made solely by automation, you must give people information about the decision, let them make representations, offer human intervention and let them contest it. We keep a person on refusals, so the agent drafts and staff decide.
Do we have to tell customers they are talking to an AI?
For shoppers in the EU, plan on it. Article 50 of the EU AI Act says AI systems that talk directly with people must be designed so those people are told they are dealing with an AI, unless that is obvious from the context. The Act’s published timeline applies Article 50 from 2 August 2026. Our shopper-facing agents say they are an AI in their first message, for UK and EU customers alike.
Does the EU AI Act apply to a UK online store?
It can. Article 2 covers providers placing AI systems on the EU market wherever they are based, and providers and deployers (businesses using an AI system) outside the EU where the system’s output is used in the EU. A UK store whose chat agent answers shoppers in Ireland, France or Germany is in that picture. We are not lawyers, so we map where your agents touch EU customers and you confirm the position with your adviser.
Cost and working with us
How much does it cost to build an AI agent for a UK online store?
UK market ranges vary widely. Softomate Solutions, a London agency, lists £15,000 to £40,000 for an advanced build with deep CRM and ERP integration, and £40,000 or more for multiple agents, and its page notes that prices exclude VAT. Cloudswitched, a London IT services firm, lists £15,000 to £40,000 for a reactive agent and £35,000 to £80,000 for a task agent, without saying whether VAT is included. FactoryJet quotes a fixed price in writing after a short scoping call.
Can we see it working before we sign?
Before any contract we show working software on your own data. For a store agent that usually means twenty or thirty of your real customer emails, return requests or trade orders run through a first version, with its drafts set beside what your team actually sent. You judge it on your own cases.
What should we send you to get a quote?
A short written brief is best, and an RFP is welcome. Name the job you want the agent to do first, the systems it touches (store platform, marketplaces, channel or stock software, accounting or ERP, helpdesk), your rough monthly order and message volumes, and what a person must still approve. Attach a few anonymised examples. With that we can come back with a fixed quote for the first phase.
Who owns the agent, and what happens after launch?
You own the code and the repository from day one. Defects are fixed inside the build price for a cover period agreed before work starts. Support after that is optional, each change is quoted and approved, and there is no monthly minimum. If you want, we keep managing the servers, AI models, API connections and maintenance, and FactoryJet quotes that support as a fixed price in writing.
Have you worked with UK commerce businesses before?
Yes. GPSUK, a UK supplier of branded promotional products, runs its trade storefront on Commerceflo, built by FactoryJet, so business buyers reorder at their own account prices. FactoryJet has worked with more than 500 businesses since 2014.
Bhavesh replies within 24 hours.
See an agent work on your own orders before you sign
Send your name and work email, or a brief. Bhavesh replies within 24 hours to agree one job and the systems it touches, then we run a first version on your real examples. No obligation.