Choose the source around your update routine
A supplier CSV can be useful for adding products today and for maintaining their data later. Those are related jobs, but they need different source arrangements. The FeedPup video begins with that distinction: upload a file for a one-time snapshot, or connect a CSV link that can be checked again for supplier changes.
Before importing, decide which information the supplier should manage. You might want supplier stock updates while retaining your own product wording. Establishing that boundary helps you choose field mappings and update settings with a clear purpose. Keep the initial CSV so you can compare it with what arrives in WooCommerce.
Connect your store and add the CSV
Open FeedPup and connect the correct WooCommerce store. Follow the current setup instructions if this is your first connection. When the store is ready, either upload the supplier file from your computer or paste the stable web address where the supplier maintains its CSV.
An uploaded file contains the data available at that moment. It does not become a live feed simply because the supplier has newer information elsewhere. For recurring checks, use an accessible hosted link and the synchronization supported by your plan. Confirm that the address points to usable product data and remains available beyond the first download.
Read headers and sample rows together
Analyze the CSV and inspect the detected headers and sample records. Make sure the product names, item codes and numerical values look like the original file. A source with many similar price columns deserves extra attention: wholesale cost, suggested retail and sale price can look plausible while serving very different purposes.
If the detected records do not resemble the supplier file, stop before importing. Check that you selected the intended file or link and that the source really contains the catalog. Review the analysis information and any warnings rather than attempting to fix every suspicious value through unrelated field matches.
Map fields for consistent product identity
- Map the unique supplier item code to SKU.
- Match product name to the intended customer-facing title.
- Select the selling-price column and compare example amounts.
- Match the available stock value to inventory.
- Review image links and any supported option information.
A stable SKU is the link between your source review and your destination checks. Inspect codes that include leading zeros or letters, and check whether the same code already belongs to an unrelated product. Do not substitute a changing product title for a dependable identifier.
For quantities, distinguish a numerical amount from a general “available” message. For images, check whether the URL leads to the intended product picture. If the catalog contains variant rows, review how their relationships appear in the preview and which fields the current integration supports. The presence of similar names alone does not establish a correct variant grouping.
Review the preview before importing
Compare several preview products with the original CSV. Include a zero-stock item, an item with a missing optional value and any variant example you plan to import. Check that the correct price and stock remain attached to each SKU. Resolve mapping problems and review the current import allowance before starting the job.
Use the available test workflow or a small selection first. Wait for the import result, then open Products in WordPress and find the same SKUs. Compare product name, selling price, stock and images with your source. Check product status and visibility before deciding that the catalog is ready for customers.
Check recurring updates after the initial import
For a hosted feed, complete the initial import and choose which fields FeedPup may update. Later runs can check the link on the schedule supported by your plan, so supplier revisions may not appear immediately. Read sync history, identify an affected SKU and confirm its changed value in WooCommerce.
Keep this distinction in your operating routine: a file upload needs a newer file when you want a new snapshot, while an eligible hosted source can support repeat checks. In both cases, a clear source, stable identifiers and destination verification make the next update easier to understand.