Shopify order tracking on WhatsApp: a workflow guide

Start with the question your support team receives: “Where is my order?” The useful response depends on whether the order is awaiting fulfilment, has tracking information or needs investigation. Payment, fulfilment and carrier delivery are different states.

Shopify exposes tracking details such as a carrier, tracking number and URL through its fulfilment tracking information. Not every record contains every detail. Your response needs a branch for an empty result.

List the fields your connected action actually returns. Do not write a message template around a promised delivery date unless your source supplies a reliable date and your team agrees how to describe it. The order-status reply guide covers the customer-facing wording.

An order number alone should not authorise disclosure. Someone may paste the wrong reference or message from a different number. Define a customer verification process that fits your store and the access controls in the selected action.

Use only the minimum information needed to establish the match. Avoid exposing addresses, email addresses or item details while asking someone to verify ownership. If your action cannot enforce the required customer match, keep the lookup staff-only until that gap is resolved.

Where several orders match, ask the customer to identify the relevant one without displaying other people's records. An empty or ambiguous match is a support case. It is not a reason to loosen access checks.

Example reply, using an illustrative order: “Your order has tracking information available. Use the tracking link for the carrier's latest update. If the link does not work, reply here and support will check it.” The production message should include only the verified link returned for that customer's order.

For an unfulfilled order, say that tracking is not yet available if that is what the record shows. Avoid “Your parcel is on its way” when the only confirmed event is payment.

If an order has several fulfilments, make the split clear. Where your selected action cannot explain the split reliably, hand the case to support. One tracking number should not be presented as covering all items by default.

Open the Shopify integration and follow the business app setup guide. Authorise the intended store. Confirm the order-read or tracking action exists in your workspace catalogue before designing the flow around it.

Use an inbound Logic Flow for a customer's question, with validated inputs and explicit success, no-match and failure branches. A connected store does not itself create a live customer reply flow.

Keep action permissions narrow. The reviewed Shopify connector supports order and tracking reads and optional order tagging. This workflow does not depend on issuing refunds, creating returns or receiving an abandoned-cart trigger. Those are separate capabilities and must not be assumed from the Shopify name.

Distinguish a missing order from a failed connection. “Order not found” is misleading when the store could not be reached. Tell the customer that support needs to check the status, preserve the reference and route the conversation to a named team.

A successful lookup also does not prove that WhatsApp delivered your reply. Review the message state separately if the customer reports no response.

For this read-only workflow, a retry may be reasonable under the action's documented rules. Do not generalize that approach to writes. An uncertain write must be reconciled before another attempt. The connected actions guide explains why a timeout can leave the result unknown.

Before publishing, test these cases with controlled store records:

• A verified customer with an unfulfilled order.
• An order with a valid tracking link and an order without one.
• Multiple fulfilments or multiple matching orders.
• A wrong reference and a failed customer match.
• A disconnected store or denied permission.
• A support handoff that preserves the reference without exposing unnecessary data.

Keep an owner for mapping changes when store data or action outputs change. Review confusing replies before adding outbound shipment notifications. Those require a verified event, eligible messaging and a separate delivery check.

For returns, use the return-request workflow. Tracking a parcel and deciding a return are different support jobs.