A shopper asks about stock after your team has logged off.
A purchase question often arrives while someone is comparing several stores. If the answer waits for the next shift, the shopper can make the decision somewhere else.
XML / YML product feed · scheduled refresh
UPLIFY Chat is an AI shopping assistant for ecommerce stores. It reads your current Merchant or YML XML feed, answers product questions, recommends available items, and sends the store manager a qualified lead with the shopper's request and contact details.
Where ecommerce conversations break
A purchase question often arrives while someone is comparing several stores. If the answer waits for the next shift, the shopper can make the decision somewhere else.
Generic bots can repeat product copy from an old document or invent a plausible answer. Product facts need a visible source and a known refresh time.
People describe a use case, a budget, and a few constraints. They rarely know the exact product title or attribute names used in your catalog.
When a shopper asks for a human, the manager should see the original request and the products already discussed. Otherwise the conversation starts again.
The goal is measurable: turn a product question into a relevant shortlist, a product click, or a lead with enough context for a manager to continue.
Test the flowThe answer shows its source
UPLIFY Chat fetches a public Merchant or YML feed, normalizes product names, prices, images, links, availability, and attributes, then searches the latest successful catalog version. If the source does not contain a fact, the assistant should ask or hand the question to a person.
<offer id="4956"available="true"> <name>Disco Wicca silver pendant</name> <price>7274</price> <currencyId>UAH</currencyId> </offer>
More than a generic support chatbot
| Criterion | Human live chat | Generic AI chatbot | UPLIFY Chat |
|---|---|---|---|
| Answer outside business hours | Waits for the next shift | May answer, but source is unclear | Answers from the latest connected catalog |
| Current price and availability | Checked manually | Often copied from pages or old files | Read from Merchant or YML XML |
| Products that do not exist | Not recommended | Possible without strict grounding | Only products present in the store catalog |
| Result of the conversation | Message thread | Generic answer | Qualified lead with request and products |
| Product payment in chat | Depends on the channel | Varies by vendor | Not taken; the store manager confirms payment |
When a person needs to step in
The lead keeps the shopper's original question and the products they considered. The manager can confirm the order, delivery, and payment without asking the shopper to repeat the entire conversation.
Olena+380 67 000 00 00
"A sterling silver pendant as a gift. Budget up to UAH 8,000."
4956 · Disco WiccaUAH 7,274
4963 · Bull & GirlUAH 5,555
Feed-based setup
UPLIFY Chat is a separate service. It connects through one public catalog URL and one JavaScript widget snippet, without replacing your storefront or checkout.
Use a public Google Merchant XML or YML XML link.
Review products, prices, availability, attributes, and feed warnings.
Place one JavaScript snippet on your ecommerce site.
Send the contact, request, and selected products to your team.
Pricing
Every plan uses your connected feed for product prices and availability. The widget does not take payment for store products.
0UAH / month
no card and no expiry390UAH / month
1,290UAH / month
3,490UAH / month
Catalog factsCome from the connected XML feed.
Qualified leadKeeps the contact, question, consent, and products.
Product paymentDoes not happen inside UPLIFY Chat.
Order confirmationRemains with the store manager.
Questions before setup
An AI shopping assistant for ecommerce is a conversational product discovery tool embedded in an online store. It understands natural-language requests, checks the store catalog, recommends relevant products, answers pre-purchase questions, and hands the conversation to a person when confirmation is needed.
UPLIFY Chat accepts a public Google Merchant XML or YML XML URL. In many cases, the store can reuse the feed it already sends to Merchant Center, an advertising platform, or a marketplace catalog.
No. The service fetches the feed from its URL on a schedule. If a new sync fails validation, the latest successful catalog remains available while the error is shown to the merchant.
The widget can run on Horoshop, OpenCart, WooCommerce, and other storefronts where the merchant can add a JavaScript snippet. The catalog connection is feed based, so it does not depend on the storefront theme.
No. The widget records an order request with explicit consent and the selected product. A store manager then confirms the order, delivery details, and payment method directly with the shopper.
The assistant should not invent a product fact. It can ask a clarifying question or send the unresolved request and conversation context to a store manager.
A standard setup can usually be completed within one business day: connect the feed URL, validate the catalog, configure the widget, and add its script to the storefront. Custom feeds and platform restrictions may take longer.
Start with your own catalog
Connect an XML or YML URL, inspect the imported catalog, and try product requests before adding the widget to live traffic. The free plan does not require a payment card.