This checklist applies to WooCommerce and Magento 2 stores. Use it after you change your store's domain, URL path, protocol (http or https) or port, or after a store upgrade or new caching setup.
1. Update the store connection in SKULabs
If your store address changed, SKULabs must use the new address. Open the store in SKULabs and update its connection fields to match your store:
Protocol: http or https.
Host: your domain, plus the port if you use a non-standard one.
Path: the folder your store runs in, if it is not at the root of the domain.
If you created new API credentials during the change, also update the Consumer Key and Consumer Secret (WooCommerce) or the Username and Password / API Key (Magento 2).
Watch out for caching. A cache or firewall rule that skips /admin may not skip a custom admin path or the store's API path. Cached API answers can make SKULabs see old orders or products. If something below fails only some of the time, check your cache settings first.
2. Test the connection
Orders: place a test order in your store and confirm it appears in SKULabs promptly. Then place a second test order and confirm it also comes in. The second order rules out caching problems.
Stock: confirm no stock sync errors appear in Sync Reports. To test, let stock sync run on its own, or re-push one SKU instead of the whole store. See Push inventory manually.
Listings: create a new product in your store and confirm the next listings sync imports it. Create a second product and check again, to rule out caching problems.
Check Sync Reports for order and listing sync errors.
If errors continue after the connection details are correct, contact our support team.