Test and troubleshoot a store connection
Interpret test results and fix URL, token, permissions or network without recreating the connection unnecessarily.
Updated 7 August 2026Test creates verification state independent from activation
A newly saved connection is inactive and unverified. Test calls a representative endpoint and stores success or failure, HTTP status, message and time. Activation selects the exclusive connection used by the assistant.
An account can have only one active store among WooCommerce, PrestaShop, Shopify and Wix. Keeping several configurations is possible, but activating one disables another to protect recommendations and orders.
Recommended order
Save, Test, fix until successful, Activate, then run product and protected order tests.
Know what each test checks
Success proves basic authentication, not every business datum.
WooCommerce
Call to /wp-json/wc/v3/system_status with URL, Consumer Key and Consumer Secret.
PrestaShop
Call to /api/ with Webservice key as authentication identifier.
Shopify
GraphQL shop-name query on myshopify domain with Admin API token managed by Wavize.
Wix
Key and Site ID check followed by v1 or v3 catalogue-version detection.
Read HTTP status before changing credentials
Network errors, permissions and wrong secrets require different fixes.
401 Unauthorized
Secret is incorrect, revoked, truncated or used with the wrong account. Recopy from official source or create a new key.
403 Forbidden
Credential is recognized but permission, scope, site association or firewall denies action. Add only required read permission.
404 Not Found
Base URL, endpoint, permalinks or resource identifier is wrong. Do not randomly append /api or /wp-json in Wavize.
429 or 5xx
Provider rate limit or temporary outage. Record time, wait, then retry once before changing configuration.
Test both uses after activation
Technical test does not necessarily verify permissions for every resource.
Product recommendation
Ask for a published product with a precise criterion. Check title, price, image, link and variants against source store.
Test order
Use an authorized reference and exact email. A wrong email must receive the same neutral result as an unknown order.
Store isolation
After changing active connection, confirm assistant no longer recommends old catalogue or searches orders in old provider.
Prepare an actionable ticket
Never attach the secret. Support needs diagnosis, not keys.
Useful information
Provider, public URL, time, HTTP status, exact message, App Store or manual source and latest successful action.
Redacted screenshot
Hide token, key, customer email and order reference. Keep Verified/Active state and message.
Careful external test
Do not publish URLs containing credentials. If using an API tool, clear history and do not store the secret in a shared collection.
Production-ready connection
All four checks must be true at the same time.
- Recently verified — Last test succeeded after latest key rotation.
- Active and exclusive — No other account store is active.
- Accurate product — Data matches published catalogue.
- Protected order — Both reference and email are verified.
Still need help?
Our team can help from your client area.