Connecting Sqquid to an existing ecommerce site

Use this guide when your ecommerce site already has products and you want Sqquid to keep them updated from your product and inventory source. It applies to BigCommerce, WooCommerce, Salesforce Commerce, and Delta5.

Start with product syncing turned off. Check that the products match, import your source data, and test a few products before syncing the rest.

Enabling the Connection can also start order and return imports. Read what to expect from orders and returns before you enable it, especially if your existing website orders already reach your POS or inventory system through another process.

1. Create and authorize the Connection

1. Open Connections in Sqquid.
2. Find your ecommerce platform and select Connect.
3. Complete authorization and enter any required credentials.
4. Open the new Connection’s settings. Leave the Connection disabled while you complete the checks below.

For platform-specific authorization steps, see Connect BigCommerce or Connect WooCommerce. If you need help with Salesforce Commerce or Delta5 credentials, contact help@sqquid.com.

2. Keep new products from syncing automatically

In the Connection’s product settings:

• Set the behavior for newly detected products to Do not sync. If your settings show Sync new products automatically, leave that switch off.
• Set the default sync mode to Full sync.
• Review which product fields Sqquid will update, then save your settings.

These controls do different things. Turning syncing off lets you review products before sending updates to the site. Full sync determines what Sqquid sends once you enable syncing for a product, subject to the Connection’s field settings.

Caution

Full sync can update existing product content and prices as well as inventory. Review the field settings before testing, especially if you maintain descriptions or images directly on your ecommerce site.

3. Match SKUs and product groups

Before enabling the Connection, compare the products in your product and inventory source with the products already on the ecommerce site.

Check both the identifiers and how variants are grouped:

• Each sellable variant has the same SKU in the source and on the site. Check capitalization, punctuation, and leading zeroes.
• SKUs are present and unique. A SKU must not identify different items in the two systems.
• Each source product corresponds to exactly one product on the site, and that site product corresponds only to that source product.
• The variants under each source product match the variants under its corresponding site product.

For example, one RunIt style must correspond to one ecommerce product. Every barcode under that style must correspond to a variant under that product. Do not split one style across several site products or combine several styles into one site product.

The same rule applies when Lightspeed or Shopify is the source. If a source product groups a shoe’s sizes together, the matching site product must group those same sizes together.

Note

RunIt uses barcodes to identify its sellable variants. Check how those identifiers become SKUs in your setup. A matching barcode field alone does not replace the SKU checks above.

Caution

Matching SKUs alone is not enough if the product groups differ. Mismatched SKUs or product groups can cause Sqquid to create duplicates or fail to link existing products. Correct these differences before enabling the Connection.

See Product matching for more examples. If you cannot establish a one-to-one match, contact help@sqquid.com before continuing.

4. Enable the Connection and import all source products

Caution

Keeping product syncing off does not pause order or return imports. Review the Connection’s order and return settings and the first-days monitoring steps before enabling it.

Once the matching checks are complete:

1. Complete the Connection’s required Setup settings and select Enable connection. Keep automatic syncing for new products off.
2. Return to Connections and find your product source Connection.
3. For supported POS sources, select Actions > Update catalog, choose All Products (!), then select Resync. This requests a full product import from the source.
4. Open Syncs to follow the import.
5. Open Products and select the ecommerce Connection you just enabled. Wait until all expected products and their variants are available there before continuing.

If this is your first import from RunIt or Lightspeed, import inventory before products. Check any source import filters so they include all the products you intend to sell. See Run your first imports.

If Shopify is your source

For Accounts with Shopify Channels Hub access, source imports run automatically while the source Connection is enabled. Follow the Shopify-source import steps and wait for all expected products to appear on the destination Connection. The POS import action above does not apply to this source.

Importing source products prepares their records in Sqquid. You will enable syncing to the site in the next step.

5. Test a few existing products

1. In Products, keep the new ecommerce Connection selected.
2. Choose a few products that already exist on your site. Include a product with multiple variants.
3. Turn on Sync for those products and the variants you want to test. Confirm their mode is Full sync, then save.
4. Wait for their syncs to finish and check for sync errors.
5. Open the existing products on your ecommerce platform and verify the results.

Check that Sqquid updated the existing listings without creating duplicates. Confirm that each variant still belongs to the correct product, its SKU matches, and the fields you chose to sync have the expected values. Check inventory too, allowing for any configured dynamic buffers.

If a product fails to match or updates incorrectly, keep the remaining products unsynced. Correct the cause and repeat the test before continuing.

6. Enable syncing for the remaining products

After the test succeeds, use bulk editing on the same ecommerce Connection:

1. Select the remaining products on the current page.
2. Select Edit Selected.
3. Choose Sync > Enable Sync, review the preview, and apply the change.
4. Select Save.
5. Repeat for the remaining pages until you have enabled all intended products.

Bulk editing works on the current page. Select all matching products does not support bulk editing across pages. See Bulk changes for selection details.

Leave automatic syncing for newly detected products off if you want to review future additions before they sync. You can enable it later in the Connection’s product settings once you are ready for new products to sync automatically.

Allow time for the first sync

The first sync may take a few seconds for a small product set or several hours for a very large one. The destination platform and its plan also affect how quickly it accepts updates. These are estimates, not completion deadlines.

Check Syncs for progress and errors. Wait for the current work to finish before requesting the same full import or resync again. Once processing finishes, spot-check products on the site to confirm the updates arrived.

What to expect from orders and returns

When you enable an existing site’s Connection, Sqquid can pick up recent orders and returns, including activity from before you enabled it. Order and return imports depend on what the Connection supports and which features you have enabled.

How orders arrive in Sqquid

For Connections that support order import, Sqquid checks for orders every 10 minutes. It typically fetches orders updated in the last 6 hours. An older order can fall within that window if someone recently changed it on the ecommerce site.

Sqquid imports eligible orders that do not already exist in Sqquid. If processing into your POS or inventory management system is enabled, Sqquid then attempts to send those orders there. Each platform’s import rules still apply, including required order statuses. See BigCommerce orders or WooCommerce order import for those details.

Supported systems, such as Shopify, can also send orders through webhooks. These are automatic notifications from the ecommerce platform, so an order can arrive without waiting for the next scheduled check.

Monitor orders during the first few days

An order that is new to Sqquid may already exist in your POS because your team entered it manually or another integration sent it there. Sqquid may create another POS order when it imports and processes that website order.

For example, your team might have entered yesterday’s website order into the POS before connecting Sqquid. If someone updates that order on the website today, it can enter the six-hour lookback window. Sqquid can then import it and send it to the POS again.

During the first few days:

1. Monitor incoming orders in Orders and compare them with your POS or inventory system.
2. If an order appears twice in the POS, check the website order number and order details to confirm that both records represent the same sale.
3. Void the duplicate order in the POS, keeping the original valid order. Once voided, leave the duplicate alone and continue handling the sale through the original order.

Do not fulfill the duplicate as another sale. The six-hour window is based on recent updates, so an order’s original creation date alone does not tell you whether Sqquid will import it.

How returns arrive in Sqquid

For Connections that support return import, with that feature enabled, Sqquid typically checks every 10 minutes for returns created in the last 6 hours. Supported systems can also send return updates through webhooks.

Sqquid attempts to process imported returns into the configured POS or inventory system. This depends on Sqquid having successfully processed the original order into that system. An order merely appearing in Sqquid is not enough.

If Sqquid did not process the original order, it cannot process the return into that system, and the return will eventually be marked Skipped. This can happen with returns for sales your team handled before connecting Sqquid, even if the original sale already exists in the POS.

Monitor incoming returns alongside orders during the first few days. For a skipped return, check how the original order was processed before taking action. If your team handled the sale outside Sqquid, use your existing return process and check whether the return has already been recorded before entering it again. For an order Sqquid was supposed to process, follow Troubleshoot returns to investigate the failure.