Webflow eCommerce Data Sync

This comprehensive guide walks you through the step-by-step configuration process for syncing Webflow eCommerce data using Byteline.

Supported Data Types

Byteline currently supports syncing the following Webflow eCommerce data objects:

• Products (including SKUs)
• Orders

Syncing Webflow CMS Data

If you're looking to sync data with Webflow CMS (such as blog posts, authors, or other CMS collections), the setup process is different from Webflow eCommerce.

➡️ Please follow the instructions in the Webflow CMS Data Sync for detailed steps.

This guide is specifically focused on syncing Webflow eCommerce data, such as Products and Orders.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers the usage of data sync features valid for all integrations.

Setting up Webflow eCommerce Data Sync with Byteline

Follow these steps to configure data sync for Webflow eCommerce Products using Byteline. You can follow a similar process to sync Webflow eCommerce Orders.

Step 1: Start the Sync Setup

1. Log in to your Byteline account and navigate to the My Syncs page.
2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select Webflow as Your First App

1. Choose Webflow as the first app to sync.
   Alternatively, you can select another app first and then pick Webflow as the second app.
2. Click on the "Sign In" button, if not already connected, under Webflow to connect it to Byteline.
3. Now select the eCommerce - Product for the data type to sync.
4. Select the site for which the data needs to be synced.

Step 3: Connect the Second App

1. Select the second app for syncing and log in to authorize the connection.
2. Once connected, click "Continue" to move to the table mapping screen.

Step 4: Map Tables Between Webflow eCommerce and the Other App

Note: In the instructions below, Webflow is configured as the right-side app in the sync setup.

This means you’ll be mapping fields from the other app (left side) to the corresponding fields in Webflow eCommerce (right side).

1. Select the tables you want to sync between the two apps.

   

Step 5: Choose Which Data to Sync

For each sync, you'll need to select whether to sync existing records, future changes, or both.

• Products:
  Choose "Existing Data and Future Changes" to sync all current product data to Webflow, along with any future updates.
  If products already exist in Webflow, Byteline will only sync the differences, avoiding duplicate entries.
• Orders:
  Typically, select "Future Changes Only" so that new orders are synced to your connected app as they are placed.

Step 6: Configure Field Mapping

1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.

   

2. To delete a mapping, click the X button next to the field.
3. Select the sync direction at the field level using the arrow buttons.
   One-Way Sync: Data flows from one app to the other.
   Two-Way Sync: Data flows bidirectionally between both apps.
4. Once your mappings are finalized, click "Continue.

Step 7: Sync Existing Data Configuration

Select the sync direction for your existing data.

Step 8: Review Sync Preview

1. Preview the sync setup to ensure everything is configured correctly.
2. If all looks good, click "Start Sync."
3. Byteline will sync your existing data and make the sync live.

   

Additional Configuration

Products That Do Not Require Shipping

When syncing products to Webflow eCommerce, you must configure the Requires Shipping field appropriately.

• If this field is not mapped, Webflow will assume the product requires shipping.
• To ensure that products like digital goods or services do not require shipping, you must explicitly map the Requires Shipping field and set its value to false.

This is important to avoid shipping-related issues for non-physical products.

Webflow’s 50-Variant Limit

Webflow enforces a strict limit of 50 variants per product. This is a platform-level restriction and cannot be overridden by Byteline.

A product’s total variants are calculated by multiplying all option values. For example:

• 3 sizes × 10 colors = 30 variants → Allowed
• 6 sizes × 10 colors = 60 variants → Rejected by Webflow

If a product exceeds 50 variants, Webflow will not allow it to be created or updated, and the sync will fail.

Recommendation: Before syncing multi-variant products to Webflow, ensure the total number of variants in the paired app, such as Printful, does not exceed 50. If necessary, reduce the number of sizes, colors, or other option values in your source product to comply with Webflow’s limitation.

Troubleshooting Webflow eCommerce Products

Product not found while adding variants

Error: Product not found. This can sometimes happen if the data sync ran into an issue while adding the product.

This error can occur while syncing product variants to Webflow when the parent product was not successfully created during an earlier sync.

Because variants are always linked to a product, Webflow cannot accept a variant unless its product already exists. If the product failed to sync, any attempt to add or update its variants will result in this error.

Why this happens

• The data sync encountered an error while creating the Webflow Product
• The product record is missing in Webflow
• Variants tried to sync before the product was successfully added - FIX

How to resolve the issue

Follow these steps to fix the problem in the correct order.

1. Find products that failed to sync

Use the Record Change History to identify product-level errors.

Apply the following filters:

• Destination Table: Webflow Product
• Status: Error

  

This will show all product records that failed to sync to Webflow.

2. Fix the product sync error

• Open each failed product record
• Review the error reason
• Fix the underlying issue (for example: missing required fields, invalid values, or configuration issues)
• Resync the product so it is successfully created in Webflow

⚠️ Variants cannot be added until the product exists in Webflow.

3. Resync the product variants

Once the product is successfully synced:

• Go back to the variant record(s)
• Run Resync on the variant

The variant sync should now succeed since the product is available.

Key takeaway

Always resolve product-level errors first. Variant errors like “Product not found” are usually a downstream effect of a failed product sync.

If you continue to see issues after resyncing the product, please reach out to Byteline support with the error details.