Custom integration
AI chat for any e-commerce platform
Not on the list above? If your store can expose products and orders in any machine-readable way, AskSpot can read it — bespoke platforms, headless stacks and ERP-driven catalogs included.
What you get
- Works with bespoke, headless and in-house platforms
- Three ways in: API, product feed, or reading your site
- Orders from wherever they live — store, ERP or WMS
- No plugin to install and no platform to migrate to
- Available around the clock, in every language you sell in
- A solutions engineer scopes it with you before you commit
Requirements
If it can output data, we can read it
Platform
Any
Front-end
One script tag
Migration
None
Catalog size
No ceiling found
largest live store: 400,000 products
- Headless and PWA
- In-house platforms
- Sylius, Spree, Saleor
- ERP-driven catalogs
- B2B price lists
- Page caching and CDNs
How the connection is built
Three layers. Two are enough to go live.
The same three layers as every other platform. What changes is only how we reach your data — and there is more than one way in.
01
Your catalog, three ways in
Pick whichever you already have. An API — yours, your ERP’s, or your PIM’s. A product feed — the XML or CSV you already generate for Google Merchant Center or price comparison sites. Or your site itself — point us at a sitemap and we read the product pages directly, which is the route for stores with no feed and no API at all. Whichever it is, the source is re-read automatically every 24 hours — more often on higher plans.
Required
02
Front-end snippet
One asynchronous script tag, anywhere your stack renders HTML — server-rendered templates, a React or Vue app, or your tag manager. It loads off the critical path and needs no framework of its own.
Required
03
Orders, from wherever they live
Orders rarely sit where the storefront does. We read them from whichever system is authoritative for you — the store, an ERP, a WMS, an order-management layer — over its own API. Start read-only and extend the permissions when you’re ready for the assistant to act on orders.
Optional
No plugin to wait for and nothing to install. A solutions engineer walks your stack with you first, so you know what the connection looks like before you commit to anything.
Placement and control
You decide how it shows up
Three display modes, set per store from the dashboard. Switch between them at any time — no code change and no redeploy.
Live chat window
A pop-up in the corner of the page. The familiar option, and the least intrusive.
Slide-out window
Slides in from the side over your page. More room for product cards and longer answers.
Copilot mode
Shifts your page content aside instead of covering it, so the customer keeps browsing while they ask.
Appearance
- Your brand colour and logo
- Custom CSS on the widget
- Your own welcome and privacy text
- Six quick-action starter questions
Behaviour
- Desktop and mobile set separately
- A delay before the button appears
- Hidden on any page you choose
- Your own JavaScript on top
Tell us about your stack
A scoping call with a solutions engineer, not a sales pitch. We look at how your data is exposed and tell you plainly what the connection would take.
Security and control you can trust
AskSpot is designed to operate safely in demanding e-commerce — with data protection, reliable AI and full operational control.
Before you install
The questions your developer will ask
What a custom connection actually involves, before anyone books a call.
We have no product feed at all. Is that a blocker?
No. A sitemap is enough — we read your product pages directly and build the catalog from what is on them. A feed or an API is faster to set up and more precise, so we prefer them when they exist, but their absence does not stop the project.
Our orders live in an ERP, not the shop. Does that work?
Yes — that is the normal case for larger merchants. We connect to whichever system is authoritative for order state, over its own API. Permissions are yours to set: most teams start read-only, then extend to actions like cancellations or returns once they are comfortable.
How long does a custom connection take?
Up to two weeks, and often less. A clean feed or a documented API is close to a standard rollout; a bespoke source needs mapping work first, which is what the scoping call is for. If your case looks like an exception, we will tell you up front rather than after signing.
How large can the catalog be?
We have not found a ceiling yet. The largest store running on AskSpot today carries 400,000 products with variants and multi-currency pricing, and nothing in the architecture caps it there.
How fresh is the catalog data?
The feed is re-read automatically once every 24 hours. Our support team can trigger a re-sync on request when you’ve made a large change, and higher plans run the sync more frequently — each rebuild of the search index has a real cost, which is why it isn’t continuous by default.
Where does our data live?
Inside the EU, and never used to train external AI models. Deleted on request. More on security →
What if we want it gone?
Delete the script tag and revoke the key. Nothing is left behind in your theme, your database or your checkout.












