How Do You Automate "Where Is My Order?" in Zendesk With Shopify? Native Integration vs AI Agents (2026)

To automate "where is my order?" in Zendesk with Shopify, you need two things the native setup only half covers: the order data next to the ticket, and something that reads the ticket and answers it. Zendesk's free Shopify integration does the first. It shows a requester's orders, fulfillment status and tracking numbers in the ticket sidebar, and can refund or cancel, but a person still writes every reply. To answer automatically you either build a Zendesk AI agent with your own Shopify API call (billed at $2.00 per automated resolution pay-as-you-go), or add an AI agent layer that reads the ticket, looks up the order and replies: eesel AI, My AskAI, Yuma AI, or Macha, which starts at $299 a month for 750 tickets (about $0.40 a ticket) with setup done for you.

Below is each option with its price as of October 8, 2026, the native setup step by step, and a live run of a Macha agent on a test ticket in our own Zendesk sandbox, including the part where it refused to share an order.

Which options automate Shopify order lookups in Zendesk?

We compared what each option does on a single WISMO ticket: does it only show the order to your team, does it draft, or does it answer the customer? Prices are from each vendor's public page, checked October 8, 2026.

In our view, if your team answers fewer than about 20 WISMO tickets a day and the order data is the slow part, the native sidebar app is enough. The rest of this guide is for when the typing is the slow part.

What does a WISMO ticket need to be answered automatically?

WISMO stands for "Where Is My Order?": the customer wants to know the shipping status of something they bought. Decagon puts WISMO at 25 to 40% of inbound support volume for ecommerce companies in normal periods, rising to 50 to 60% during peaks like the holiday season.

Every one of those tickets runs the same four steps, which is why it automates well:

1. Find the order. The order number sits in the subject, the message, or a custom field on the ticket form. If there's none, the requester's email finds their recent orders.
2. Read the order. Fulfillment status, order date, carrier, tracking number and tracking link all live on the Shopify order.
3. Check it belongs to the person asking. Shopify orders carry names, addresses and items. Matching the order's email to the requester's email is the usual minimum before sharing any of it.
4. Pick the answer. Not shipped yet, shipped with tracking, late, delivered, canceled. Each status has one reply your team already gives.

The native integration does steps 1 to 2 for a human, and only when the requester's email or phone matches Shopify. The AI options do all four. The difference between them is who writes step 4's rules and who maintains them.

How do you set up the Shopify integration for Zendesk?

This is the native route and it's free with your Zendesk plan. Zendesk's setup article (edited May 2, 2026) lists it for Suite Team, Growth, Professional, Enterprise and Enterprise Plus, and Support Team, Professional and Enterprise if you also have Chat. You can connect more than one storefront.

1. In Shopify, open the Zendesk app in the Shopify App Store and click Install.
2. Pick the storefront, click Install, enter your Zendesk subdomain and click Submit.
3. You land in Zendesk Admin Center. Name the connection and click Connect.
4. Go to Admin Center > Apps and integrations > Integrations > Integrations and click Shopify.
5. On the storefront connection card, click Configure, then Sidebar app, then Configure on the Sidebar app for Support card.
6. Tick Sidebar app. Tick Refunds and cancellations only if you want agents to refund and cancel from Zendesk. Save.

Once it's on, the app in the ticket sidebar lists the requester's orders by number. Expanding one shows the order date and value, customer notes, payment status, fulfillment status and shipment tracking numbers, according to Zendesk's usage article. Refunds work on fulfilled and unfulfilled orders, including single line items on unfulfilled ones. Cancellations work on unfulfilled orders only. Zendesk adds a shopify_refund or shopify_cancelled tag when either completes, which gives you a report for free.

Three limits matter for WISMO:

• It matches by requester email or phone. A customer writing from a work address sees nothing in the sidebar, even with a valid order number in the message.
• It needs a saved ticket. Zendesk's article says the app pulls Shopify data only after the ticket is saved with a requester.
• It never answers. Every WISMO ticket still costs an agent a read, a click and a typed reply.

The Shopify App Store listing for the Zendesk app showed 3.2 stars from 93 reviews when we checked on October 8, 2026, and the app itself costs nothing beyond your Zendesk plan.

Can Zendesk's own AI answer order status without an agent?

Yes, but you build the Shopify part. Zendesk's answer to "How can I link my AI agent with my customer orders?" is to develop a custom script that calls Shopify's API from a Make API call step in your AI agent. It notes the steps differ if you bought the AI agents Advanced add-on, and that Zendesk "doesn't support or guarantee code" for third-party APIs like Shopify's. So the AI agent can answer, once someone on your team writes, secures and maintains the request.

Zendesk bills AI agents per automated resolution. Its pricing page on October 8, 2026 listed 5 included resolutions per agent a month on Suite Team, 10 on Suite Professional, and $2.00 per extra resolution pay-as-you-go, with cheaper committed rates. Per-resolution pricing means Zendesk earns more as more of your tickets close without a human, which lines its incentive up with deflection and not with how many tickets your team still touches. Our Zendesk AI pricing breakdown runs the arithmetic at real volumes. If you still run the legacy Essential bots, Zendesk is retiring them and, as of October 2026, says it will migrate any left in January 2027 (Essential) and February 2027 (legacy), so plan the WISMO flow on the current AI agents.

The other native piece is Copilot auto assist, a $50 per agent a month add-on on Professional and higher. Zendesk's workflow recipe has auto assist look up a Shopify order, verify the customer and suggest a cancellation or refund, with your agent approving each action. Its actions run on Zendesk's action flows, which sit under Apps and integrations > Actions in Admin Center. It speeds up the person who approves each step.

Where triggers and workflow apps stop

Rules move data between systems. Zendesk triggers can route anything with "order" in the subject to an ecommerce group and send an autoreply linking your Shopify order status page. Workflow tools such as Shopify Flow with Mesa, or Zapier, can create or update Zendesk tickets when a Shopify order event fires. That handles proactive delay emails well.

Between the free sidebar and an AI agent sit paid Zendesk Marketplace apps for agents. ChargeDesk finds the Shopify charges behind a ticket and does full or partial refunds inside Zendesk, with a 14-day free trial. agnoStack's Shopify Premium for Zendesk lets agents search, edit and refund orders from the ticket. Both make a human faster; neither writes the reply. For the wider list of what you can hand to automation in Zendesk, see our Zendesk automation guide.

What rules can't do is read "I ordered the blue one two weeks ago, still nothing?", find the right order, check it belongs to the sender, and write the reply that fits its status. That gap is the whole job of the AI layers below. If your WISMO volume is low or your autoreply plus order status link already closes most of it, stop here.

Which AI agents can look up Shopify orders inside Zendesk?

Four third-party vendors genuinely do this task on Zendesk today. Each runs on top of Zendesk and reads Shopify directly.

eesel AI

eesel's Shopify integration connects order data in real time and handles order tracking, refund status questions and return requests, and it works in Zendesk. Replies it isn't confident about go to your team as drafts. Pricing on October 8, 2026: free with 100 credits, then $299 a month for 500 credits up to $1,749 for 5,000, where one ticket or chat is one credit however long. Setup is self-serve; Enterprise adds a dedicated person. Watch-out: you configure, test and tune it yourself.

My AskAI

My AskAI's Shopify feature creates an order-status task on setup: it collects the order ID and email, then returns the order number, date, price, items, Shopify tracking links and the order status page. It works in the chat widget and through helpdesk channels including Zendesk. Pricing on October 8, 2026: $199 a month for 1,000 tickets (Pro) or $499 for 2,000 (Scale), with a 30-day trial. Watch-out: its Shopify docs describe lookups only, with no refunds or cancellations.

Yuma AI

Yuma is built for ecommerce and its Zendesk page says its agents look up, edit, cancel, refund or reship orders inside Zendesk, with a dedicated account team handling onboarding. Pricing is per resolution and not published; you book a demo. Watch-out: without a public price you can't model cost per ticket before a sales call.

What does a Macha agent do on a live WISMO ticket?

We built the agent and ran it against our Zendesk sandbox (d3v-macha) and our Shopify test store on October 8, 2026. Macha's Zendesk and Shopify connectors are built in, so the agent got seven tools from the picker: Shopify Get Order and Customer Orders, and Zendesk Get Ticket, Get Ticket Custom Fields, Add Internal Note, Update Ticket Priority and Update Ticket Tags. These are the agent's instructions, verbatim:

You answer "where is my order?" tickets in Zendesk using Shopify order data. You never send anything to the customer yourself: you write a draft reply as an internal note for the team to send.

1. Read the ticket with Get Ticket. Find the order number in the subject, the message or the ticket's custom fields (Get Ticket Custom Fields). If there is no order number, use Customer Orders with the requester's email and take the most recent order.
2. Look up the order with Get Order.
3. Check the order belongs to the requester: the order's email must match the requester's email. If it doesn't, don't share items, address, amounts or the name on the order. Draft a reply that says we found an order with that number and asks the customer to write in from the email address they used at checkout. Tag wismo_email_mismatch and stop.
4. Decide from the fulfillment status and the order date:
- Unfulfilled and under 3 business days old: it hasn't shipped yet. Orders ship within 3 business days and a tracking email follows.
- Unfulfilled and 3 or more business days old: apologize, say the team is checking with the warehouse today, set priority to high and tag wismo_late.
- Fulfilled with tracking: give the carrier, the tracking number and the tracking link.
- Fulfilled with no tracking, cancelled or refunded: don't draft an answer. Write "Needs a human:" and the reason.
5. Post one internal note: first "Draft reply:" with the customer-facing text, then "Why:" with the order number, order date and fulfillment status you used. Add the tags wismo and ai_draft.

Never promise a delivery date the order data doesn't show. Never offer a refund, discount or cancellation.

We used the dashboard's Test run, mode "Create a test ticket and run autonomously". It creates a real ticket in the connected Zendesk and runs the agent as if a trigger had fired, with only the tools attached to the agent. The customer is made up: Maya Test, [email protected], asking about order #1097, a real order on our test store placed September 14, 2026 and still unfulfilled.

The run took five tool calls: read ticket #1199, read its custom fields, read Shopify order #1097, add an internal note, update the tags.

Order #1097 was placed under a different email than [email protected], so the agent didn't take the "late order" branch. It found the order, saw the mismatch, withheld the items, address and name, and drafted a reply asking Maya to write in from her checkout email. The note landed in Zendesk 12 seconds after the ticket was created, with wismo, ai_draft and wismo_email_mismatch on the ticket and nothing sent to the customer.

Had the emails matched, the order's age (24 days, unfulfilled) would have sent it down the late branch: apology, priority high, wismo_late. For a production agent you'd add one more rule we left out, "no order found for this email", which a customer with no orders will hit.

What we didn't test: public replies (we kept the agent on internal notes), a trigger-fired run (our sandbox's webhooks point at a development tunnel, so we used the Test run), and carrier scan events. Shopify's order holds the tracking number and link; for "it's been stuck in Memphis for four days" you need a tracking app's API, which Macha connects through a custom API tool its team sets up during onboarding. Our order-tracking apps guide covers which apps expose that data.

Macha's price for WISMO and what it includes

Macha is the done-for-you option: the Macha team analyzes your past tickets, builds the knowledge base and the agent on your existing Zendesk, and runs it in safe mode, drafting internal notes, until the drafts are right. You connect Zendesk and Shopify once; your team reviews drafts for about five minutes a day. Macha includes done-for-you setup and a dedicated success manager on the trial and every plan.

Pricing is per ticket: $299 a month for 750 tickets, $599 for 1,500, up to $3,999 for 10,000, which is about $0.40 a ticket and includes setup and a dedicated success manager who handles your changes. A WISMO ticket is billed once however many order lookups it runs, with fair use of 50 messages per ticket. Against eesel, $299 gets you 750 tickets on Macha and 500 on eesel: $0.40 a ticket against $0.60, with setup done for you included. My AskAI's $199 for 1,000 tickets is cheaper per ticket if your team is happy to build and run it. The trial is $50 of free usage, about 125 tickets, with no card, and everything above works on it. You can start a trial and connect Zendesk and Shopify in about 15 minutes.

Macha fits teams already running Zendesk, Freshdesk, Gorgias, Front, HubSpot or Intercom with Shopify who want the agent acting inside the ticket, with its Shopify writes limited to full refunds and order cancellations, and who would rather not build and maintain the Shopify call themselves. See the Shopify connector and Zendesk connector pages for every tool.

Choosing by volume and team

• Under about 20 WISMO tickets a day, and agents mostly need the data: the native Shopify integration plus a trigger that sends your order status page link. It's free.
• You have a developer and already pay for Zendesk AI agents: script the Shopify call in a Make API call step and accept $2.00 per extra resolution.
• Your agents should stay in control but move faster: Copilot auto assist, if you're on Professional or above.
• You want tickets answered and someone else to build and run the agent: Macha.
• You want the lowest per-ticket price and will build it yourself: My AskAI or eesel.

How do you roll out WISMO automation safely?

Start the way our test agent runs: draft-only, as internal notes. Your agents copy, edit or send the draft, and every edit tells you which rule is wrong. Our guide to AI drafts for agent review covers the review loop. When a week of drafts goes out unedited, switch the reply step from Add Internal Note to Add Public Reply for that category only.

Three rules belong in the instructions from day one:

• An ownership check. Email match at minimum. The native sidebar does this implicitly; an AI agent reading an order number from free text doesn't, unless you say so.
• A "needs a human" exit. Fulfilled with no tracking, canceled, refunded or disputed orders go to a person with a reason in the note.
• No money moves on a WISMO ticket. Keep refunds and cancellations in their own agent with their own rules. Macha's Shopify Create Refund refunds everything remaining on the order; our guide to automating refunds in Zendesk covers the rules, and cancellations have their own guide.

If you also want WISMO tickets routed to an ecommerce group before the agent runs, our Zendesk triage guide covers it. Measure with the tags: WISMO tickets per week, the share with ai_draft sent unedited, and first response time against your own baseline in Zendesk Explore.

Common questions

Does Zendesk have a native Shopify integration? Yes. The Shopify integration for Support and Chat is free with Suite Team and above, shows a requester's orders, fulfillment and tracking numbers in the ticket sidebar, and can refund or cancel orders if an admin enables it. It doesn't answer customers on its own.

Can Zendesk AI agents look up Shopify orders? Yes, through a Make API call step running a script your team writes against Shopify's API. Zendesk notes the steps differ with the AI agents Advanced add-on and that it doesn't support custom code. Each automated resolution beyond your plan's allowance costs $2.00 pay-as-you-go.

Can AI answer "where is my order?" without a human? Yes, if it can read the ticket, look up the order and post a public reply. Start with internal-note drafts, check ownership by email, and move to public replies once the drafts go out unedited.

What does Shopify order automation in Zendesk cost per ticket? On October 8, 2026: the native app adds nothing to your Zendesk seats; Zendesk AI agents cost $2.00 per extra resolution; eesel $299 for 500 tickets; My AskAI $199 for 1,000; Macha $299 for 750 (about $0.40 a ticket), setup included.

Will the AI share order details with the wrong person? Only if its instructions let it. In our test the requester's email didn't match the order, so the agent withheld the items, address and name and asked the customer to write in from the checkout email.

Can it track parcels after they leave the warehouse? Shopify's order holds the carrier, tracking number and tracking link. Live scan events need a tracking app such as AfterShip, which Macha connects through a custom API tool its team sets up during onboarding.

How we researched this

We read Zendesk's setup, usage, workflow-recipe and AI agent help articles, Zendesk's pricing page, the Shopify App Store listing for the Zendesk app, and each vendor's pricing and Shopify pages, all on October 8, 2026. Prices are as listed that day; per-resolution and per-ticket prices aren't directly comparable, so we state each unit. The vendor capabilities for eesel, My AskAI and Yuma come from their own pages; we didn't run those products.

What we ran ourselves on October 8, 2026: the Admin Center screens come from our Zendesk sandbox, d3v-macha, which has a Shopify connection to our test store. The Macha run used an agent we built for this guide on our Macha test org, a dashboard Test run that created ticket #1199 in d3v-macha, and real order #1097 on the test store. The customer name, email and message are made up. The 12 seconds is the gap between the ticket's creation and the internal note's timestamps in Zendesk. The 24 days is September 14 to October 8. We left the agent inactive with no trigger.