Shopify WISMO in Chat: Order Lookup

What WISMO means here

WISMO is the post-purchase question every Shopify brand knows by heart. The shipping email is buried. The shopper is anxious. Someone on your team opens Admin, finds the order, pastes status and a tracking URL back into the thread.

A WISMO chatbot for Shopify is supposed to short-circuit that loop. The shopper self-serves in chat. You keep the exception cases—wrong email, not connected, needs a human—for handoff.

I care that the lookup stays honest. Competitors invent ETAs, last-scan timelines, and deflection percentages. Rinhelp’s path is narrower on purpose: prove the match, show the closed status set, give tracking you can open, and stop cleanly when the store cannot confirm the order.

The job to be done is simple enough to say out loud. Let the shopper type order number + email in chat and see fulfillment status + tracking without your team copy-pasting from Shopify.

Exact lookup flow

Here is the hero how-it-works. Invent nothing beyond it.

1. The visitor asks where their order is—any natural phrasing.
2. The widget collects order number and email.
3. Lookup runs against connected Shopify, not against indexed help pages.
4. Found: order name + fulfillment status label + tracking lines.
5. Miss: refuse + handoff offer—when the shop is not connected, or when order + email are not found.

Page citations and Shopify lookup are separate paths. A shipping policy question still comes from your indexed pages. An order status question comes from Shopify when connected.

If you only remember one line from this guide, make it that split. Crawl answers what you published. Shopify answers what the store knows about one order. Mixing those sources is how bots start guessing.

What the shopper sees on a match

Closed vocabulary. Do not expect fields we do not return.

Order name

The shop’s order name for that match—so the shopper knows which order you found.

Fulfillment status label (closed set only)

Only these labels:

• Canceled
• Fulfilled
• In progress
• On hold
• Partially fulfilled
• Pending
• Processing
• Restocked
• Scheduled

No custom status theater. No invented stages.

Tracking lines

Each tracking line can include:

• company (optional)
• number
• url

If company is absent, the line still works from number and url. Partial fulfillments can surface more than one tracking line; each line is still only those fields.

No ETA field

There is no ETA on this lookup. No carrier SLA math. No invented delivery window. Status + tracking is the promise. ETA is not.

That constraint is a feature for trust. A confident “arrives Thursday” that the carrier never promised is worse than a clear Fulfilled + tracking URL the shopper can open themselves.

Connect Shopify (custom OAuth)

Merchants connect Shopify through custom OAuth. That is enough to claim the capability.

A public Shopify App Store install is not required. Do not wait on an App Store listing to evaluate the lookup. Connect the shop, keep the widget install as one script tag, and the WISMO path can run in the same panel.

Same afternoon shape as the rest of Rinhelp: connect what you need, style the chat, paste the snippet, ask a real question in preview. WISMO is the Shopify-connected path inside that widget—not a second product you migrate into.

Operator path: MCP shopify.lookup_order

Operators can run the same lookup through MCP tool shopify.lookup_order.

Same inputs in spirit: find the order against the connected shop. Same honesty on the result shape. No invented second MCP tool for “ETA” or “carrier timeline.” When you are working a thread and need the store truth, that is the tool name.

I like that the visitor path and the operator path agree. If chat shows Fulfilled + a tracking URL, the operator lookup should not invent a richer story with line items and last-scan theater. Closed fields keep everyone looking at the same truth.

What stays page-grounded

WISMO does not replace cite-and-refuse. It sits beside it.

Sizing charts, shipping policy, returns policy, docs FAQs—those still answer from indexed pages, with citations, or refuse when the pages cannot support the question. See AI support with citations that refuses when it can’t and the AI agent surface.

Here is the kicker for Shopify operators: one widget, two honest paths. Published-page questions stay grounded in what you wrote. Order status questions hit Shopify when connected. Collapsing them into “the bot will figure it out” is how you get invented policies and fake tracking stories.

Misses from either path still matter in the shared inbox—page gaps as writing backlog, order misses as refuse + handoff.

What this page is not

Phrase-split and product edges, stated plainly.

• Not refund / returns processing. Looking up where an order is is not approving a refund or processing a return. That is a separate surface; this guide stays on WISMO.
• Not a helpdesk replacement. Widget + inbox. Not a mailbox, not SLA software, not a leave-your-stack pitch.
• Not ETA prediction. Status label + tracking lines only.
• Not crawl-as-order-source. Order lookup is Shopify data.
• Not App Store theater. Custom OAuth connects the shop; App Store is not required to claim lookup.
• Not invented returned fields. No line items, ship-to address, payment status, photos, or last-scan location on this lookup—only order name, status label, and tracking company/number/url.

FAQ

Can an AI chat widget look up Shopify order status?

Yes—when Shopify is connected. In Rinhelp, the visitor submits order number + email; the lookup runs against Shopify, not crawled pages.

What is a WISMO chatbot for Shopify?

A chat experience that answers “where is my order?” with a live store lookup so the shopper does not dig through email and support does not copy-paste from Admin. Rinhelp’s version is constrained: status label + tracking lines, refuse + handoff on miss.

How does order lookup work in a Shopify support widget?

Order number + email → connected Shopify → on match, order name, fulfillment status, tracking company (optional) / number / url. On miss, refuse and offer handoff.

What does the customer need to check where their order is?

Order number and email. That is the claimable input pair.

What fulfillment statuses can a Shopify order lookup return?

Canceled, Fulfilled, In progress, On hold, Partially fulfilled, Pending, Processing, Restocked, Scheduled. Only that set.

What happens if the order number and email don’t match?

Rinhelp refuses and offers handoff. Same pattern if the shop is not connected.

Do I need a Shopify App Store app for AI order lookup?

No. Connect Shopify via custom OAuth. App Store is not required to claim this capability.

Does AI order tracking include an ETA?

No. There is no ETA field on Rinhelp’s WISMO lookup. You get status and tracking lines—not delivery-window invent.

Can operators look up an order too?

Yes. MCP shopify.lookup_order runs the same lookup for operators.

Does this replace my helpdesk?

No. Rinhelp is the widget and the inbox agents can run—not a ticket queue you migrate into.

Is WISMO the same as answering from my FAQ pages?

No. FAQ and policy questions still use page-grounded cite-and-refuse. WISMO looks up the order in connected Shopify. Keep the paths separate so neither one pretends to be the other.

Closing

Order number + email. Shopify when connected. Order name, closed status set, tracking lines. No ETA. Refuse + handoff on miss. Operators: shopify.lookup_order.

I would rather ship that narrow loop than pretend the widget knows a delivery day the carrier never promised. Shoppers get something they can verify. You get fewer Admin tab hops for the same question.

Page-grounded cite/refuse still covers the questions your published pages already answer. Install stays one script on live chat. Pricing stays the plan on pricing—$29/mo for 300 resolutions, then $0.10; unresolved free; 14-day trial, no card.

If you run Shopify and WISMO still eats your afternoon, start here:

• Start the trial
• Features · Live chat · AI agent · Shared inbox
• Sibling guides: one script tag install · cite + refuse · miss pile inbox