Articles on: Frequently Asked Questions (FAQ)

What should I do if my feed is not updating correctly?

If your feed is not updating correctly, check the following common causes:


• Clear any active filters in Step 3 of the feed settings. Incorrect filters can prevent products or quantities from updating.


• Ensure your Product Identifier is mapped correctly. If the SKU or barcode is missing in your store or feed, switch to another identifier, such as Product Title and map it accordingly.


• If the feed returns 0 matches, verify that the fields you mapped in Step 2 actually exist in the feed file. Re-map the correct column and test again.


• If your feed shows 0 updated items even though mappings are correct, check whether your SKU values contain hidden characters or prefixes (such as an apostrophe). Use SKU Smart Settings to remove or normalize prefixes so they match the identifiers in your store.


• If the Before Qty and After Qty fields are empty in the Change Log, verify the Inventory Location in Smart Settings. An incorrect location can stop stock updates.


• If you duplicated another feed and the new one does not work, ensure all Smart Settings (such as prefix/postfix and inventory location) match your data.


• If you recently edited products in Shopify and updates do not appear, confirm the feed is using the correct Product Identifier (e.g., switch from SKU to Barcode).


• Run a full sync after making changes to apply updates across all products.


• If the feed URL is accessible only from certain regions or requires IP whitelisting, request your supplier to whitelist Stock Sync’s IP. Restricted access can prevent the system from loading the source.


• If the feed source cannot be retrieved (for example, FTP/SFTP connection fails or credentials/host/port are incorrect), the feed will not update any products. Verify the login details with your supplier and ensure the file is accessible outside Stock Sync (e.g., via FileZilla).


• If auto‑detect fails to identify the file format, manually set the correct format (e.g., XML or HTML Table) in the feed settings.


• If the feed file contains hidden BOM characters in the header, column names may not match (for example, the system may read SKU instead of SKU). In this case, map using the column index number instead of the column name.


• If the schedule stops running after repeated failures, the auto‑disable safety may have been triggered. Contact support if you need this disabled for your account.


• If a feed suddenly sets a large percentage of products to zero (for example, over your configured Halt Threshold), Stock Sync will automatically pause the update to prevent accidental mass zeroing. Review the Halt slider in the feed settings and ensure the feed file contains the expected products before resuming.


• If your Shopify store displays negative inventory while the Change Log shows correct values, run the update manually and review the product’s Adjustment History in Shopify. If discrepancies persist, escalate to support for technical review.


• If a feed suddenly stops processing (email or URL feeds), try a manual force start to re-trigger the update and verify whether the latest file is being picked up correctly.


• If only some variants update, check for mismatched option values (such as colour codes vs full names). The values in the feed must match those in Shopify.


• If quantities appear incorrect due to thousand separators (e.g., 1.700 interpreted as 1), adjust the quantity delimiter settings to match your supplier’s format.


• If a file such as Google Sheets is renamed, updates will stop until the sheet name is corrected in the feed settings.


• If your Shopify store displays negative inventory while the Change Log shows correct values, run the update manually and review the product’s Adjustment History in Shopify. If discrepancies persist, escalate to support for technical review.


• If a feed suddenly stops processing (email or URL feeds), try a manual force start to re-trigger the update and verify whether the latest file is being picked up correctly.


• Only one feed can process at a time. If other feeds are still in queuing or processing state, wait until they finish before running your feed to avoid 0 updates.


• If your update feed shows 0 items added but the file contains products, ensure the products already exist in your store. New products must be added first using an Add Feed before an Update Feed can modify them.


• If an Add Feed shows no new products added even though they appear in the file, the items may already exist in your store. Add Feeds only import products that are not yet in the store. To test without consuming credits, enable "Only process 3 products".


• If some products do not import, check whether "Skip product(s) with zero quantity" is enabled, as this will exclude out-of-stock items.


• If updates stop working after modifying your source file (for example, Google Sheets), ensure the sheet name has not changed. A renamed sheet prevents the feed from reading data.


• In rare cases, feeds may not update due to temporary backend incidents (such as global service outages or high queue volume). During these periods, feeds may stay in queuing or process more slowly. Once the incident is resolved, updates resume normally. If you suspect a system‑wide issue, try running the feed again after a few minutes or contact support.


• If a feed is disabled or fails suddenly without errors, this can be due to an internal system interruption. Retry the update after a short delay, and contact support if the issue continues.


• If the interface shows an error or warning (e.g., orange status) but no errors appear in the list, this may be a temporary display glitch. Re-run the feed or wait for the system to auto-correct.


• If an Update Feed shows "No matches found" even though the file contains products, ensure that the products already exist in your store — Update Feeds cannot add new products. Use an Add Feed first if your store has no matching items.


• If you cannot load the mapping page or receive "There was a problem loading this website," the issue may be related to file structure or format detection. Support may need to adjust file-reading settings before mapping becomes accessible.


• If the feed file contains values with extra text (e.g., “More than 10”), adjust your mapping or use Smart Settings to clean the value so the system can read the quantity correctly.


If issues persist, provide support with your feed name and a sample SKU so they can test the update.


Updated on: 24/06/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!