Troubleshoot products

Start with the affected Account and SKU. Identify whether the problem is between your source and Sqquid, or between Sqquid and an ecommerce Connection. A product can sync successfully to one Connection and fail on another.

A product is missing from Sqquid

1. Confirm the product exists in your source of truth and that you are searching for the correct SKU in the correct Account.
2. Check the source Connection’s import settings. For example, RunIt’s Sell on the Web filter can exclude products. Follow the source’s troubleshooting guide.
3. Find the product import in Syncs. If it failed, read the error and correct the source data or Connection setting it identifies. If it is running, check the result after it finishes.

After the import, find the SKU in Sqquid again. If no import appears, or an import after the product’s creation completed but the product is still absent, contact support with the SKU and sync details.

A product is missing from an ecommerce system

1. Confirm the product exists in Sqquid, then select the affected ecommerce Connection in Products.
2. Check the product and relevant variants have Sync on. Check the sync mode too. Inventory-only sync generally needs an existing listing; see the provider’s product settings before changing modes.
3. Check that SKUs match the intended listing and read any Error badge. If an error is present, recover the failed sync.
4. Check the product export for that Connection. If it is still running, check the listing after it finishes.

If there is no error or running export, follow Enabled products with no export. If the export completed but the product is still missing, check the provider’s listing visibility and eligibility requirements in its troubleshooting guide, then contact support if the result remains unclear.

Product information is incorrect

Compare the same SKU and field in the source, Sqquid, and the ecommerce system.

• If the source value is wrong, correct it there and check the next product import.
• If the source is correct but Sqquid is old, check the source import. Resync does not fetch fresh source data.
• If Sqquid is correct but the ecommerce value is wrong, check whether the Connection’s sync mode and product field settings allow that field to be updated. Read the product’s error and check the destination export.

After a correction reaches Sqquid, resync the product if another export is needed, then compare the field again in the destination. If a completed export still leaves an unexpected value, contact support with the field name and values from each system.

Inventory differs between the source and Sqquid

Compare the same SKU at the same physical Location in your source system and Sqquid.

1. Open Syncs and look for inventory syncs from the source Connection after the quantity changed.
2. Check whether any of those syncs have errors, or whether there are no inventory syncs from that Connection at all.
3. Read any errors and fix the reported issues in the source system. Check the next inventory sync to confirm the corrected quantity reaches Sqquid.

If a sync is running, check the quantity again after it finishes. If it completed but the quantity is still wrong, confirm the SKU and Location mappings and that the sync started after the source change. If there are no inventory syncs, or the difference is still unexplained, contact Sqquid support with the quantities in both systems.

Inventory differs between Sqquid and an ecommerce Connection

Compare the same SKU in Sqquid and the ecommerce system. For inventory tracked by Location, compare the same physical Location.

1. In Products, select the ecommerce Connection. Confirm the product and relevant variants have Sync on and check for sync errors. If there is an error, resolve it and resync the product.
2. Open Syncs and check whether product export syncs are running for that ecommerce Connection. If an export is still running, check the quantity again after it finishes. If no export appears after the change, follow Enabled products with no export.
3. Check whether any inventory buffers apply. Dynamic Buffers can intentionally reduce the quantity available online. Buffers that reduce the pooled total do not necessarily reduce each Location’s quantity.

If an export after the change completed, but the difference is not explained by buffers, check the Location mappings and the product’s latest error. If the difference remains unclear, contact Sqquid support with the quantities in both systems and any applicable buffer.

A product is enabled but no export appears

1. Confirm the Connection is enabled and the product and required variants have Sync on.
2. In Syncs, select All, then check for product exports after the change. The With errors filter can hide running or successful work.
3. Confirm Sqquid already has the corrected data. If an export is running, check its result before requesting another. Otherwise, select Resync for the affected product to queue Sqquid’s current record for that Connection.

Check for the new export and confirm the result in the ecommerce system. If no export appears or the result is still wrong, contact support with the SKU and the time you requested the resync.

Recover a failed sync

If the same product fails to sync product information or inventory three times in a row, Sqquid automatically deactivates its synchronization on the affected Connection and marks the error. This applies to inventory-only synchronization too.

The product’s Sync switch is now off. You must read the error, fix what caused it, and resync the product to resume updates. See How Sqquid handles sync failures for the shared retry rules.

Find the affected product

1. Open Products in the Sqquid app and select the affected Connection.
2. Open Filters and choose Last sync result → Errors. Add Sync enabled → Disabled to find products deactivated after repeated failures.
3. Select the product’s red Error badge and read Message from connection.

You can also follow the Dashboard’s Product errors detected alert. A product may succeed on one Connection and fail on another, so check the destination named in the error.

Resolve the cause

For rejected product information, check the field named in the message. Common causes include missing or duplicate SKUs, invalid prices, missing required fields, or a listing Sqquid cannot match.

Correct source-owned data in the source of truth and wait for the correction to reach Sqquid. Correct destination-specific settings on the affected Connection or in the destination system, as appropriate.

For inventory errors, check that the SKU matches the destination listing and that the relevant Locations are mapped. Confirm that the Connection’s inventory settings support the update you are trying to send.

For authorization or service errors, restore access or wait until the destination is available before resyncing. Use the provider’s troubleshooting guide for its requirements. If no useful message is shown, check the sync details or contact support.

Resync and check the result

1. Once the correction is in Sqquid, select Resync from the error dialog or the product’s ⋯ menu.
2. Confirm the required variants have Sync on. Resync enables the parent product but leaves individual variant switches unchanged.
3. Review the next export result and confirm the product information or inventory reached the destination. The error clears after a successful export.

Resync sends Sqquid’s current record to the selected Connection. It does not fetch fresh data from the source. To recover several products, follow Recover paused products.

If the error returns, read the new message before trying again. Use the support request template if you need help or a completed export still leaves the destination incorrect.