Look at any Shopify store's support inbox and one question dominates, worded a dozen different ways: where is my order. Not a product question, not a sizing question — a status check the customer could answer themselves if they had the same information you do.
Why this one question costs so much
WISMO tickets ("where is my order") are usually the largest single category in a growing store's support queue, and the least interesting kind to answer. There's no judgment call — the answer is sitting in your Shopify order data. It just requires someone to look it up, copy it into a reply, and send it. Multiply that by every order placed during a sale weekend and it's most of a support team's week.
The pattern is predictable enough to set a clock by: a spike the day after a sale ends, another as tracking numbers go quiet in transit and customers start to worry, and a third right around the promised delivery date when a package is running a day late. None of those moments require judgment. They require an answer, immediately, from the same data your team would otherwise have to go look up by hand.
What AIVA does with your Shopify data
Connect AIVA to your Shopify store and it can answer directly, without a ticket ever being opened:
- Current order status and tracking, pulled from the real order — not "should be on its way"
- Delivery estimates based on the actual shipment, not a generic policy line
- Basic order checks a customer asks about, like confirming an address, what was ordered, or the amount due on a cash-on-delivery order
- Store policy questions — COD availability, return windows, shipping charges — answered from what you've told AIVA about the business, the same way the site's own FAQ page would if anyone actually read it
- A clear hand-off when it's not a status question anymore — wrong item, damage, a refund request — those go to your team, with the order context attached instead of a bare email
The distinction matters. AIVA isn't trying to resolve disputes. It's clearing out the large, repetitive, answerable-from-data share of order questions so your team's time goes to the ones that actually need a person.
A typical exchange looks like this: a customer opens the widget and types "hey, ordered a jacket last Tuesday, hasn't arrived yet." AIVA looks up the order tied to that customer, finds it's out for delivery with a courier, and replies with the actual status and expected date — no "let me check with the team," because there's no team to check with. The whole thing takes seconds, at any hour, on a Sunday as easily as a Tuesday afternoon.
A second, different kind of exchange: "the shirt I got is the wrong size, I need a large instead." That's not a status question, and AIVA doesn't pretend it is — it hands the conversation to your team with the order number, what was ordered, and what the customer is asking for already attached, so whoever picks it up isn't starting by asking the customer to repeat everything they just said.
Where customers ask it
Order questions come in wherever the customer already is — the chat widget on your store, a text back to the number that sent their shipping confirmation, or a phone call if that's a channel you run. Same order data, same answer, whichever way they reach out. That matters most around sales and launches, when order volume — and the number of "where is it" messages that come with it — spikes hardest and a delayed reply looks worst.
It also means a customer doesn't need to remember where they contacted you before. Someone who chatted on the site last week and texts this week gets the same order lookup either way — AIVA isn't tied to one channel's memory of the conversation.
What AIVA doesn't touch
Worth being specific about the boundary. AIVA reads order and fulfillment status from Shopify — it doesn't modify orders, issue refunds through Shopify itself, adjust inventory, or sit anywhere in your checkout flow. A refund request gets routed to your team as a hand-off, not processed automatically, because a refund on a physical order is a judgment call — condition of the return, restocking, which policy applies — not a lookup. That's a deliberate line: the integration is read access to the data a status question needs, not a general remote control for your store.
If your store also runs on Razorpay or Stripe
Order status and payment status are related questions but different systems. Some Shopify stores layer Razorpay or Stripe on top of Shopify's native checkout for additional payment methods, or to reconcile payments before fulfillment. If that's your setup, connecting Razorpay or Stripe separately lets AIVA answer payment-specific questions — did my payment go through, can I get a refund on the charge itself — the same way it answers order-status questions from Shopify. The integrations are independent; connect whichever ones actually match your payment setup.
Questions that come up before connecting
A few questions get asked often enough during setup to answer directly here. Does this work with subscription or recurring orders? Yes — a subscription order is still an order with a status, and AIVA reads it the same way it reads a one-off purchase. Does it handle split shipments, where part of an order ships separately from the rest? It reflects whatever Shopify's fulfillment data shows for that order, split shipments included, rather than collapsing everything into one all-or-nothing status. Does it slow down during a big sale? The lookup is a live read against your order data at the moment someone asks, not a cached snapshot from earlier in the day, so it holds up the same during a launch weekend as on a quiet Tuesday — which is exactly when question volume is highest and a slow answer matters most.
Setup
Connecting Shopify takes a few minutes from your AIVA dashboard — authorize the store, and AIVA has live, read-only access to order and fulfillment status. No theme edits beyond the usual widget embed, no separate order-lookup tool to maintain, and nothing to configure on the Shopify side beyond that initial authorization.
Who this is for
Stores past the point where one person can eyeball every order email — usually somewhere after the first big sale weekend, when order volume outpaces the team's ability to answer everyone same-day. If your support inbox is mostly WISMO with a few real issues mixed in, this is built for exactly that mix. It also fits stores that run WooCommerce for a second storefront or a legacy site — the pattern of "status question vs. real issue" is the same regardless of which platform the order actually lives on, and running both integrations side by side is normal for a business selling across two platforms.
Try it with your own store connected — start free, see how it fits alongside AIVA's web widget on your storefront, or check SMS if texting is where most of your order questions already land. Full setup steps are in the docs, and the complete list of what else AIVA connects to is on the integrations page.