Google displays this screen because you created the Google Cloud app yourself. There is nothing wrong — you are the developer of this app. Google only flags self-created apps until they go through a formal verification process, which is not required for personal or internal use.

To continue: click Advanced → Go to [your app name] (unsafe). This is completely safe.

This means the redirect URI registered in your Google Cloud Console does not match the one your WordPress site is sending.

Fix:

1. In WordPress, go to WP Sync Sheets → General Settings → Google Sheets API Settings and copy the redirect URI shown there exactly.
2. In Google Cloud Console → APIs & Services → Credentials → click your OAuth 2.0 Client ID.
3. Under Authorised redirect URIs, paste the URI you copied. Click Save.
4. Return to WordPress and generate the token again.

Common triggers: switching from HTTP to HTTPS, adding or removing www., or migrating to a new domain without updating the Cloud Console.

Full walkthrough: https://docs.wpsyncsheets.com/how-to-resolve-google-oauth-2-authorization-error-redirect_uri_mismatch/

Work through these steps in order:

1. Do a clean reinstall. Deactivate and fully delete the plugin via Plugins → Installed Plugins, then download the latest version from your account at wpsyncsheets.com and upload it fresh.
2. Clear all caches — your caching plugin’s “Clear All”, server-side opcode cache, and browser cache.
3. Check your PHP version. Go to Tools → Site Health → Info → Server. The plugin requires PHP 7.4 or higher. If you are on an older version, upgrade via your hosting control panel.
4. Increase PHP memory. Add this to wp-config.php above the /* That's all, stop editing! */ line:

php

   define('WP_MEMORY_LIMIT', '256M');

5. Check for a plugin conflict. Deactivate all plugins except WooCommerce and WP Sync Sheets, then reactivate them one by one. If the error clears when a specific plugin is deactivated, that is the conflict — see Q7 below if GuzzleHttp is mentioned in the error.
6. If the error persists, open a support ticket and include: your PHP version, the exact error from your server’s error log, and a list of your active plugins.

Actual quota exceeded (rare). If your store processes a very high order volume, reduce sync frequency to every 30–60 minutes, or use the Cron URL from General Settings with a server-side scheduler instead of WP-Cron.

1. Make sure you have allowed all the checkboxes when generating the authentication code.
2. Make sure you publish the app.

WPSyncSheets bundles the GuzzleHttp library. Some third-party plugins — particularly CRM and email marketing tools — also bundle GuzzleHttp in the same global namespace, causing a conflict.

Fix:

1. Confirm the conflict by deactivating the suspected plugin. If the error disappears, that plugin is the source.
2. Update both WP Sync Sheets and the conflicting plugin to their latest versions. Many GuzzleHttp conflicts are resolved in recent releases.
3. If the conflict persists after both updates, open a support ticket with the name and version of the conflicting plugin. The team will issue a patched build.

Plugins most commonly reported as conflicting: ActiveCampaign for WooCommerce, Mailjet for WooCommerce, Booster Plus for WooCommerce.

This is a WordPress-level PHP fatal error triggered by the plugin. Work through these steps:

1. Revoke and regenerate the token. Go to WPSyncSheets → General Settings → Google API Settings, click Revoke Token, then generate a fresh one.
2. Confirm both APIs are enabled in Google Cloud Console — Google Sheets API and Google Drive API must both appear under APIs & Services → Enabled APIs.
3. Update the plugin to the latest version (delete first, then reinstall fresh).
4. Clear all caches — caching plugin, server opcode cache, and browser cache
5. Increase PHP memory — add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php.

This error appears during product or order import when column A of your spreadsheet contains values in the ID field.

Fix:

1. Open your import spreadsheet.
2. Find the Product Id column (or Order Id for order imports) — it must be in column A.
3. Clear all data values below the header row in that column. Do not delete the header itself — just remove the cell values.

For importing new products or orders, the ID column must always be blank. WooCommerce generates the ID automatically during import. If you are updating existing products, fill in the WooCommerce product ID values — but make sure the header row cell in that column contains no numeric artefacts.

Work through the following checks:

“No new orders to export” message: All orders are already marked as synced. Click “Clear Spreadsheet” in Order Settings, then click “Sync” to rebuild.

A column was added or removed but existing rows are not updated: Changing Sheet Headers only affects new syncs. To apply the new layout to existing rows: click “Clear Spreadsheet”, then “Sync”.

Orders with multiple products are missing shared data (status, totals) on some rows: Enable “Allow to Copy Same Columns” in plugin settings. This copies shared order-level fields into every product row for multi-item orders. See: https://docs.wpsyncsheets.com/wpssw-plugin-settings/

Two common causes:

A. “Click to Sync” was run multiple times without clearing first. Each sync appends rows. Click “Clear Spreadsheet” before running a full sync.

B. “Allow to Copy Same Columns” combined with repeated syncing. This option copies shared order data across product rows — if synced repeatedly without clearing, rows can accumulate. Go to WPSyncSheets → Order Settings, review whether you need this option enabled, then clear the sheet and sync once.

To fix existing duplicates: click “Clear Spreadsheet”, then click “Sync” once.

When rows are inserted via the Google Sheets API they can inherit formatting from the row above. To disable this, add the following to your theme’s functions.php:

php

// Disable style inheritance when rows are inserted into Google Sheets
add_filter( 'wpssw_insert_dimension_inherit_from_before', '__return_false' );

After adding this, new rows will no longer pick up header styles. Rows already affected will need to be manually reformatted or cleared and re-synced.

This is caused by the Row Input Format being set to RAW. In RAW mode, Google Sheets stores the value as literal text and does not evaluate formulas.

Fix:

1. Go to WPSyncSheets → General Settings → Row Input Format.
2. Switch from RAW to USER_ENTERED.
3. Save, then clear and re-sync.

Check 1 — WordPress cron is firing. WPSyncSheets relies on WP-Cron. Some managed hosting providers disable WP-Cron. Install WP Crontrol to verify your scheduled tasks are running.

Check 2 — Use the external Cron URL (recommended for production). In General Settings, copy the Generate Cron URL value and set up a server cron job or a free service like cron-job.org to call it at your preferred interval. This is more reliable than WP-Cron and is the recommended method for all production sites.

Do not rearrange or rename columns directly inside Google Sheets. The plugin maps data to columns by position, so manual edits to the sheet structure will cause data to land in the wrong columns.

To control which columns appear and in what order:

1. Go to WPSyncSheets → Order Settings (or Product Settings) → Sheet Headers.
2. Enable or disable columns using the toggles, and drag to reorder them.
3. Click Save, then “Clear Spreadsheet” and “Sync” to rebuild the sheet with the new layout.

There are two separate settings depending on what you want to change:

Change the date format the plugin exports (WordPress level): Go to WordPress Admin → Settings → General → Date Format. WP Sync Sheets reads this when writing dates to the sheet.

Change how dates are displayed inside Google Sheets:

1. Select the date column(s) in the sheet.
2. Click Format → Number → Custom date and time.
3. Choose or define your preferred display format (e.g., DD/MM/YYYY).

This only changes how Google Sheets renders the value — it does not change what the plugin writes.

Go to WPSyncSheets → General Settings → Row Input Format and choose the appropriate option:

• RAW — Values are stored exactly as sent, with no formula evaluation. Use this if you need precise numeric values without any locale-based reformatting. Note: formulas and hyperlinks will not render in this mode.
• USER_ENTERED — Values are processed as if typed directly into the cell. Formulas evaluate, numbers are formatted to your sheet’s locale. This is the recommended setting for most stores.

Tip: If hyperlink columns show a leading apostrophe ('=HYPERLINK(...)), switch to USER_ENTERED.

Full reference: https://developers.google.com/sheets/api/reference/rest/v4/ValueInputOption

Your Google Sheet has run out of rows. Fix:

1. Open the Google Sheet.
2. Scroll to the very bottom.
3. In the footer bar, type 2000 in the “Add rows” input and click Add.

To prevent this recurring, note that Google Sheets has a hard limit of 10 million cells per spreadsheet. For high-volume stores, consider archiving older data to a separate sheet periodically or splitting exports by date range (month or quarter).

For standard post meta (hand-coded fields):

1. Go to WPSyncSheets → Order/Product Settings → Sheet Headers.
2. In the “Add Custom Headers from Metadata” dropdown, select your meta key by its exact name (no prefix needed).
3. Toggle it on in the headers list.

For ACF (Advanced Custom Fields): ACF-compatible fields are automatically inserted into the Sheet Headers section — they do not appear in the dropdown. Look for them directly in the headers list and toggle them on. Supported ACF field types: https://docs.wpsyncsheets.com/custom-fields-type-lists/#acf-field-type-lists

For MetaBox fields: Update the plugin to the latest version. Supported MetaBox field types: https://docs.wpsyncsheets.com/metabox-field-type-lists/

For Secure Custom Fields (SCF): Contact support — SCF coupon and order fields require a one-time compatibility update for your site, after which they appear in Sheet Headers normally.

For complex or array-indexed meta (e.g., variation-level data): Use the wpssw_custom_headers_for_product and wpssw_custom_values_for_product filters in your functions.php. Example:

php

// Register the custom header in the plugin UI
add_filter( 'wpssw_custom_headers_for_product', function( $headers ) {
    $headers[] = 'My Custom Field';
    return $headers;
} );

// Supply the value during sync
add_filter( 'wpssw_custom_values_for_product', function( $value, $product_id, $header_name ) {
    if ( 'My Custom Field' !== $header_name ) {
        return $value;
    }
    return get_post_meta( $product_id, '_my_meta_key', true );
}, 10, 3 );

Full filter reference: https://docs.wpsyncsheets.com/filters-hooks-snippets/

This happens when the import sheet is not structured correctly for variable products.

Key rules:

• The parent product row must have Type = variable.
• Each variation row must have Type = variation.
• Variation rows must reference the parent via the Product Id column.
• Do not leave the Product Id blank for variation rows when updating existing products.

For variation images: populate the Product Variation Image column with comma-separated URLs — one per variation, in the same order as the variation rows.

Full guide including the “create variable product and variations simultaneously” section: https://docs.wpsyncsheets.com/how-to-import-products/#product-variation-import