Let logged-in WooCommerce customers track their orders

In WordPress, open Settings → Chatvox. Turn on Identify logged-in WordPress users to Chatvox. In your Chatvox Agent, open Settings → Security → User identification, generate a verification secret if needed, and copy it into the plugin’s Identity verification secret. Select Save widget settings.

The plugin sends the WordPress user ID unchanged, such as 31, together with the site address. Chatvox separates contacts by Agent, website, and user ID. See User identification.

Open WooCommerce → Settings → Advanced → REST API → Add key:

Select Generate API key. Copy the consumer key (ck_…) and consumer secret (cs_…) somewhere private. WooCommerce shows the secret only once. Keep this key Read only; the guide does not need write access.

Set these shell variables to your public store address and API credentials. Keep credentials out of chat and widget data.

STORE_URL='https://your-store.example'
WC_KEY='ck_paste-your-consumer-key'
WC_SECRET='cs_paste-your-consumer-secret'

Get up to five orders for the test customer:

curl -i -u "$WC_KEY:$WC_SECRET" \
  "$STORE_URL/wp-json/wc/v3/orders?customer=31&per_page=5"

Expect HTTP 200 and a JSON list. This real test response is trimmed to the newest order and the fields used here, with the image host replaced. Real responses contain more fields, including billing and shipping details.

[
  {
    "id": 217,
    "number": "217",
    "status": "processing",
    "currency_symbol": "$",
    "total": "80.00",
    "date_created": "2026-10-24T01:45:11",
    "line_items": [
      {
        "name": "Canvas tote",
        "quantity": 1,
        "total": "32.00",
        "image": {
          "src": "https://your-store.example/wp-content/uploads/2026/10/tote.jpg"
        }
      },
      {
        "name": "Linen shirt",
        "quantity": 1,
        "total": "48.00",
        "image": {
          "src": "https://your-store.example/wp-content/uploads/2026/10/shirt.jpg"
        }
      }
    ]
  }
]

Check a specific order and ownership:

# Owned order: 200, a list containing only order 217
curl -i -u "$WC_KEY:$WC_SECRET" \
  "$STORE_URL/wp-json/wc/v3/orders?customer=31&per_page=5&include=217"

# Another customer's order: 200, []
curl -i -u "$WC_KEY:$WC_SECRET" \
  "$STORE_URL/wp-json/wc/v3/orders?customer=31&per_page=5&include=218"

# No key: 401
curl -i "$STORE_URL/wp-json/wc/v3/orders?customer=31&per_page=5"

An empty customer= returns 400. An empty include= leaves the customer’s latest orders unfiltered. No matching orders returns 200 with [].

Chatvox calls your store from the internet. Use the exact public HTTPS address that returns JSON directly. Local development addresses, private networks, and redirects do not work.

In your Agent, open Build → API connections → Create connection:

Leave Headers empty and select Save changes. The connection keeps credentials on the server. Keep both credentials private, including the username.

Download the Order tracker widget file. Open Build → Widgets, select Import above the widget list, and choose the JSON file. The builder opens with the imported widget. Import creates a new widget; if its name is already in use, Chatvox adds a number.

The file includes the layout, example data, and five fields: number, status, total, currency, and items. It maps WooCommerce status slugs to readable labels and shows View order and Get help buttons. Completed means completed by the store; it does not prove carrier delivery.

Open Functions, expand viewOrder, and edit its Link. Replace your-store.example in https://your-store.example/my-account/view-order/{{number}}/ with your store address. Check the account page path too if your store uses a different one.

Item prices are line totals before tax. The total is the whole order total, which can include tax, shipping, fees, and discounts. currency holds the currency symbol, such as $.

Keep Enabled on and select Save changes. The Default example is sample preview data; mapped API fields replace it at runtime. When the action returns no matching fields, such as an empty list, Chatvox shows no card. If replacing an old widget, remove it once no action uses it so it cannot appear on its own.

Open Build → Actions → Create action and select Custom API. Enter:

Under What the agent sends, select Add field:

Who can use this action locks to Signed-in visitors only because the request uses {{contact.external_id}}. Chatvox fills that value from the verified sign-in; do not create a customer input field.

Under Response, use:

Clear all three path fields. WooCommerce returns a bare list, without a data wrapper or success flag. These settings use the HTTP status for success and the whole list as data. The card shows the first order; the Agent can use all returned orders in its answer.

In Test → Simulated signed-in user, select Test as contact and choose your test customer. They appear after chatting with this Agent while signed in. Check User ID is 31 and Website is your store’s host. You can also enter these values manually. Leave Order number empty and select Send test request. Expect a successful latest-orders list. This test sends a real GET request but does not render the card.

Under Map fields, open each Response value picker. Lists show their first item. Choose these fields from that first order, rather than Get all values:

Test again with an owned order number, then another customer’s order ID. The latter must return []. WooCommerce’s include parameter takes an order ID. In stock WooCommerce this equals the displayed order number. Stores using a sequential order numbers plugin need a different lookup that resolves the displayed number within the customer’s orders.

Select Save changes, confirm the action is Enabled, and keep Web widget on under Channels. Keep Run again → Every time so follow-up questions retrieve current orders. The action and its selected widget use one Actions & Widgets slot together.

Sign in to the store as your test customer and open a fresh chat:

Select View order and confirm it opens the correct order in the customer’s account. Get help sends a follow-up message in the same chat; it does not create a ticket or send email.

Try a fresh chat while signed out. The action is unavailable and the Agent asks the visitor to sign in. No order data should appear.