If your installation is not properly creating API Keys, or you are having trouble syncing products or receiving orders, there is likely a problem getting your WooCommerce installation communicating to the Apliiq platform.  Due to the nature of WooCommerce, there are a number of different configuration settings that could create challenges in communicating to 3rd party platforms like Apliiq.  The following list we've identified as causes and solutions to ensure your WooCommerce store can communicate with Apliiq.  Please note, in some cases you may need to work with your hosting provider to change the configuration of your store.

1. Please ensure, your store is utilizing WooCommerce version 3.5 or prior. Ensure you move up to the most recent WooCommerce version prior to connecting your shop.
2. Your store doesn't have a valid HTTPS/SSL certificate. Ensure you install and activate one so our app can communicated with the WooCommerce API.
   
3. For the module to work WordPress should be installed at domain or subdomain level, not at page level. For instance, say you're building up a store for a customer and you're making a mockup on www.example.com/userstore/. Our server will attempt to associate with the WooCommerce API at subdomain level, on www.example.com however the store is setup on www.example.com/userstore/. As another option, you can stall the development store on the userstore.example.com subdomain, that it will work.
   
4. Your site is password protected, or is still "coming soon" or you're using a "site under development" module that is blocking the connection to your store. This likewise disables the API access and our application cannot connect to your shop.
   
5. You have a caching plugin or similar plugins on your store that strips the "authorization" header. Try disabling any such plugins individually one by one to locate the one that is causing the issue.

Important: As this relates to your webserver as well as other WordPress plugins, Apliiq can't offer help in these cases, but's it's likely that your hosting provider can. You can attempt the solutions underneath at your own risk. If you need technical support, we recommend connecting with a developer to address this issue.

You can try adding the following to your .htaccess file as it might resolve the issue:

SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1

If that does not help, please review the configuration of your caching plugins and look for settings that pertain to caching or not caching headers.

If that does not work, contact your hosting provider.