WooCommerce Dropshipping: How To Use CSV Import

Running a WooCommerce dropshipping store becomes a data management job the moment you cross a few hundred SKUs. You stop worrying about adding products and start worrying about keeping them accurate: stock counts, prices, availability, variant updates. The question is how to automate CSV imports from your supplier feed so your catalog stays in sync, without a developer on call.

Here’s the part most guides skip. Dropshipping is not a one-shot import problem. It’s a recurring data sync problem. The moment your supplier updates their catalog, your store needs to keep up. A good CSV workflow solves four separate jobs at once: initial catalog load, stock refresh, price refresh, and SKU mapping so updates always land on the right product.

This guide walks through each of those jobs using Product Importer Deluxe. In this article, we’ll cover the four import jobs a WooCommerce dropshipping store runs, how to map SKUs so updates never drift, and how to keep stock and prices refreshing on their own. So, let’s get started!

Table of Contents

Why CSV Import Works For Dropshipping

CSV is the format you’ll spend the most time with as a dropshipper because it’s what suppliers publish and because it gives you full control over how data maps into your store. Before we get into the workflow, it helps to understand why a dedicated import tool pays for itself fast.

Supplier feeds are almost always CSV

Wholesale distributors, print-on-demand services, and aggregator marketplaces publish their catalogs as CSV feeds. You might see the occasional XML or JSON export, but CSV is the default because it’s the lowest common denominator across every store platform.

CSV gives you control over mapping

A supplier’s CSV almost never matches WooCommerce’s expected schema. Columns come labeled item_code instead of sku, qty instead of stock, retail_price instead of regular_price. With a CSV workflow you can rename, filter, and transform columns before they hit the database. You can add markup formulas, filter out discontinued ranges, or strip internal supplier codes that shouldn’t appear on your storefront.

A CSV workflow is supplier-neutral

If you change suppliers next year, the plumbing stays the same. Only the source file changes and the column mapping gets adjusted. That’s a real advantage over plugins tied to a single dropshipping service.

The WooCommerce Dropshipping Data Workflow

Think of a WooCommerce dropshipping workflow as four recurring jobs, not one import. Each one needs a different approach inside Product Importer Deluxe, and mixing them up is where most setups fall over.

• Initial product import. One-time push of the full catalog, usually hundreds to tens of thousands of SKUs. Run in new-products-only mode so you don’t touch anything that already exists.
• Stock updates. Daily or weekly refresh of quantities. Run in update-existing-only mode. This is the job you’ll run the most, and it’s where speed matters.
• Price updates. Supplier price changes flowing into your storefront, often with a markup formula applied. Weekly cadence is usually enough. Update-existing-only mode again.
• New and discontinued products. As your supplier’s catalog shifts, new SKUs appear and old ones drop off. This is the rarest job, usually run monthly in new-plus-update mode.

Product Importer Deluxe offers three import modes that map directly onto these jobs: new products only, update existing only, and new and update existing. Picking the wrong mode is the single most common reason dropshipping imports break.

This mistake shows up often: the initial import runs fine in new-only mode, but the first refresh afterward gets run in new-and-update mode instead of update-only, usually because of an SKU column mismatch between the two runs. The result is duplicate products across the catalog. The import mode is not a setting you set once and forget. It’s the heart of the workflow.

For a broader plugin overview, see the full import and export bundle page.

Step 1: Initial Product Import

The first import is the easiest to plan but the most important to get right, because everything downstream matches against the SKUs you push in this run.

Download and inspect the supplier CSV

Download your supplier’s latest product feed and open it in Excel, Numbers, or Google Sheets. Scan the columns for the usual fields: SKU, title, description, price, stock quantity, image URLs, and any variant columns. Note which ones you need, which can be skipped, and which are labeled differently from what WooCommerce expects.

Decide your markup logic before import

If your selling prices differ from supplier cost (they should), work out the markup before the first import. Add a retail_price column in Excel or Google Sheets, apply your markup formula (flat percentage, tiered by category, whatever fits), and upload the marked-up file. Stay consistent with the formula, because changing the logic later means re-running markup on every existing product.

Upload and map in Product Importer Deluxe

In WooCommerce, Product Importer, upload the CSV. The plugin’s intelligent column detection pre-fills mappings for common fields (SKU, title, price, stock), and you confirm or override anything it didn’t catch. Select the new products only import mode. Run a test with the first 10 rows before committing to the full catalog.

Where intelligent column detection saves time

Supplier columns are rarely named to WooCommerce standards. The plugin guesses sensibly on its own, so you mostly spend time on the edge cases: variant attribute columns, custom meta fields, and anything supplier-specific. Skip the ones you don’t need and map the rest manually.

Step 2: Configure SKU Mapping

SKU mapping is the single most important decision in the entire workflow. Every future update matches against SKU. Get this wrong and your daily refreshes either silently create duplicates or silently fail to update anything.

Use the supplier SKU as your WooCommerce SKU

Simplest setup. The supplier’s SKU becomes your WooCommerce SKU, updates match on that field directly, and nothing drifts. Recommended if your supplier’s SKU format is stable and you don’t have a reason to use your own internal format.

Decide on your SKU strategy before the initial import and stick with it. Changing it mid-workflow means re-matching every product by hand, which gets painful fast at any real catalog size.

Step 3: Set Up Scheduled Stock Updates

This is the step that turns a manual setup into a real dropshipping workflow. Running a stock update by hand every day isn’t sustainable past the first week. You want a process that pulls the latest CSV from your supplier and only touches the stock column, run on a recurring cadence you control.

Use FTP or URL import sources

Product Importer Deluxe supports four import sources: direct file upload, file path on the server, URL, and FTP. For recurring imports, FTP and URL are the two you care about. Most suppliers expose their feed at a stable URL or drop it onto an FTP server daily. Point the plugin at that source so every run pulls the latest version automatically.

Critical: set import mode to update existing only

This is the rule that saves the most dropshippers from pain. A recurring stock run must be set to update existing only. Any other mode either duplicates products that already exist or re-imports the whole catalog every time, which is slow and churns the database unnecessarily.

Only map the columns that change

For a stock refresh, you only need SKU and stock quantity. Map those two columns and skip everything else. Title, description, category, and image columns shouldn’t be touched during a stock refresh because they haven’t changed. Mapping only what moves makes the import faster, since it skips every field that hasn’t changed.

Monitoring

Check the import log regularly. Supplier feed format changes are the number one silent failure in dropshipping workflows, and the only way you catch them is by monitoring rather than assuming a run went fine because the last one did. If something looks off, work through our troubleshooting guide for import failures.

Streamline your supplier stock refresh with Product Importer Deluxe

Step 4: Handle Price Changes

Price updates are structurally the same as stock updates: update-existing-only mode, recurring run, minimal column mapping. The differences are cadence and markup logic.

Markup logic on import

Most dropshipping setups apply a markup before the price hits WooCommerce. Transform the supplier file in Excel, Google Sheets, or a simple script so the uploaded feed already has marked-up prices before you import it. Run the pre-processing step on a consistent cadence too, so the markup formula and the price refresh stay in sync.

How often to refresh prices

Weekly is usually enough unless your supplier changes prices daily (rare). Keep the price refresh schedule separate from the stock refresh schedule. You don’t want to re-run markup logic more than necessary, and prices changing slower than stock means you can run the heavier price job on a lighter cadence.

Keep stock and price refreshes separate

If stock and price come from different source files, run them as two distinct recurring jobs. Don’t try to chain them into a single import. Separate jobs means separate logs, separate failure checks, and you can change one cadence without touching the other.

Common Dropshipping CSV Challenges

What We’ve Seen: Three problems show up in almost every WooCommerce dropshipping CSV workflow that breaks. First, SKU drift. The supplier silently changes an SKU prefix or format, the update-only import can’t find matches, and either nothing updates or (worse) new duplicates get created. Second, supplier format changes. A column gets renamed, a delimiter changes from comma to semicolon, a date field gets reformatted, and the whole import starts failing silently with nobody watching. Third, out-of-stock handling that goes unmanaged. The supplier drops a product, your store keeps showing it as in stock, customers order it, and now you’re refunding orders. The fix for all three is the same. Treat your import as a monitored production system, not a one-time setup. Review the import log regularly. Watch for failures. And decide how you’ll handle discontinued or out-of-stock products before you run your first refresh.

A few other gotchas worth flagging:

• UTF-8 encoding with smart quotes and special characters. Supplier feeds from non-English platforms, especially European and Asian suppliers, often use character encodings that scramble when WooCommerce reads them as ASCII. Save the source file as UTF-8 before upload. If you see question marks or mojibake in product names after import, this is almost always the cause.
• Variable products with attribute mismatches. Supplier variant structures don’t always match WooCommerce’s expected format. A supplier might list each size as a separate row with no parent; WooCommerce needs a parent product plus variation rows. Pre-process the CSV to add parent rows and set the right product types if your supplier exports variants flat.

Frequently Asked Questions

Do I need a developer to import CSVs from my supplier?

No. Product Importer Deluxe supports FTP and URL as import sources, so you can point it at your supplier’s feed without writing any code. Configuration happens inside the WordPress admin, the same place you’d manage any other WooCommerce setting.

What if my supplier only sends XML or JSON, not CSV?

Convert to CSV as a pre-processing step, either manually or via a simple script that runs before the import. Most dropshipping suppliers publish CSV by default, but if yours doesn’t, the cleanest path is to transform XML or JSON into CSV once and keep the rest of the workflow standard.

How do I prevent duplicates on repeat imports?

Always use update-existing-only mode for recurring refreshes, and make sure your SKU mapping is consistent between the initial import and every update after it. The most common cause of duplicate products in a WooCommerce dropshipping setup is an import mode mismatch: a refresh left in new-and-update mode quietly creates new entries every time it runs.

Will recurring imports slow down my site?

Not if they’re configured well. Run heavier imports during low-traffic windows, use update-existing-only mode, and map only the columns that change. Limiting the mapped columns to just SKU and stock keeps the database load light, even on catalogs with thousands of products.

What happens if an import fails?

The plugin logs the failure so you can see what went wrong. Common causes are supplier feed format changes (a column was renamed), authentication failures on FTP, or network timeouts. Check the log, fix the source, and re-run the import to catch up.

Build Your Dropshipping CSV Import Workflow

A WooCommerce dropshipping store is a recurring CSV sync problem, not a one-shot import. The workflow needs four pieces working together: an initial catalog load, a stable SKU mapping strategy, a recurring stock refresh, and a recurring price refresh. Product Importer Deluxe handles all four because it was built around exactly those capabilities. Three import modes for the different jobs. Four import sources, including FTP and URL, for pulling feeds straight from your supplier. Intelligent column detection for feeds that never match WooCommerce’s expected schema.

Here’s a quick recap of what we covered:

• Run the initial catalog load in new-products-only mode
• Lock in your SKU mapping before the first import
• Set the stock refresh to update-existing-only on a recurring cadence
• Keep the price refresh as a separate job with its own markup logic
• Monitor the import log so supplier feed changes don’t break things silently

Get the mapping and mode right for each job, check the logs regularly, and the catalog stays in sync while you focus on growing the store. If you’re ready to put your WooCommerce dropshipping catalog on autopilot, explore Product Importer Deluxe at $79/yr for the full bundle.