Connect your WooCommerce Integration

We'll cover:

• Connecting Your WooCommerce Integration
• WooCommerce Requirements
• Sending a System Status Report
• FAQ

Connecting Your WooCommerce Integration

To connect your WooCommerce account with Craftybase:

1. Check that you have the correct WooCommerce configuration to connect.
2. Go to your Integrations page (How do I find my Integrations page?)

3. Enter your WooCommerce Shop URL in the textbox that appears.

   

It's best to copy this directly from your store URL to ensure that the correct address is used, as redirects can cause issues with the authentication process and subsequent imports, especially if your WooCommerce shop uses HTTPS.

4. Click the  Connect button. This will take you through the authentication process on the WooCommerce side. If you are not already logged into Woo on your browser, you'll be asked to enter your username/email and password.

Note: This is performed completely on the WooCommerce servers, so Craftybase cannot see or read your login details at any time.

6. Once logged in, you'll be presented with a page to confirm the connection between Woo and Craftybase. For your additional security, Craftybase requests only read access to your data - this will be shown on this page for you to review. To approve the connection, click the Approve button.

7. Once the connection has been made, you will be taken back to your Integration page, and your WooCommerce account name will appear along with your next scheduled import. 

WooCommerce Requirements

To use WooCommerce with Craftybase, you must be using the following:

• WooCommerce 2.6+
• WordPress 4.4+
• Enabled REST API. To enable the REST API within WooCommerce, visit the WooCommerce > Settings > Advanced > Legacy API tab link and tick the Enable REST API checkbox.
• Pretty Permalinks. To enable this, visit Settings > Permalinks so that the custom endpoints are supported. Default permalinks will not work.
• You can allow Craftybase access to your store with either HTTP or HTTPS, but HTTPS is recommended where possible.
• API User Role. A user that has the role of Shop Manager or Administrator

In order for Craftybase to access WooCommerce, you must have a user in your WooCommerce store who has the role of Shop Manager or Administrator, who assigns API keys to Craftybase to access your WooCommerce store. The account you sign in to your WooCommerce store will most likely have the role of Administrator. If you wish, you can set up a new user in your WooCommerce store for Craftybase, assign this user the role of Shop Manager, and then use this account when authorizing Craftybase access.

Sending a System Status Report

1. Go to WooCommerce > Status.
2. Troubleshoot using the info below before opening a ticket at Woo Support.

3. Click Get System Report and then Copy for support to copy/paste it into your Support Request. The information included will help our support team narrow down the issue much more quickly.

   

FAQ

When attempting to connect to WooCommerce, I receive the error message: "An error occurred in the request and at the time were unable to send the consumer data."

There are a few possible causes of this issue:

• The most common cause of this problem is that your store is using WooCommerce version 3.5 or earlier. Make sure you upgrade to the latest WooCommerce version before installing our plugin.
• Your store doesn’t have a valid HTTPS/SSL certificate. Make sure you install and activate one so our app can communicate with the WooCommerce API.
• For the plugin to work, WordPress needs to be installed at the domain or subdomain level, not at the page level. For example, say you’re developing a store for a client and you’re creating a mockup on www.example.com/devstore/ . Our server will try to connect to the WooCommerce API at subdomain level, on www.example.com  but the store is on www.example.com/devstore/ . As an alternative, you can install the development store on the devstore.example.com  subdomain, that will work.
• Your website is password protected, or you’re using a “coming soon” or “site under construction” plugin that’s disabling public access to your store. This also disables API access and our app needs it to work.
• You have a caching plugin on your store that strips the “Authorization” header. Try disabling your plugins one by one to find the one that’s causing the issue.

In some cases, doing the following might help (some may not apply to you):

• Review the configuration of your caching plugin and look for settings that pertain to caching or not caching headers
• Generate a new, valid LetsEncrypt certificate for your subdomain on the server level
• Remove the Cloudflare CDN Proxy from the Subdomain (i.e., having it point directly to the IP)
• Switch the WooCommerce Theme to “Storefront” just for the connection
• Adding the following to your .htaccess  file:

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

Sending a System Status Report

1. Go to WooCommerce > Status.
2. Troubleshoot using the info below before opening a ticket at Woo Support.

3. Click Get System Report and then Copy for support to copy/paste it into your Support Request. The information included will help our support team narrow down the issue much more quickly.