WooCommerce Dropshipping

What a dropshipping plugin does: it copies product data in, applies your pricing rules, and pushes orders out to a supplier, then pulls tracking numbers back. That is the whole job. Everything that actually decides whether a dropshipping store works — margin, supplier reliability, delivery time, returns handling, tax — is unaffected by which plugin you install.

Read this as a checklist of what you still own after the automation is in place.

The four jobs, and where each one leaks

The pattern is the same in each row: the plugin handles the happy path, and the exceptions are yours. Plan the exceptions first.

Product data is the part that decides your traffic

Imported product pages are the single biggest reason dropshipping stores get no organic traffic. Every store selling the same item imports the same title, the same description and the same photographs. Search engines pick one of them, and it is usually not the newest store.

What actually helps:

• Rewrite the title and description for the products you care about. Not all of them. Pick the twenty that could plausibly earn traffic and treat the rest as catalogue filler.
• Keep supplier SKUs in a field you control, so you can re-match products if you change suppliers.
• Check the images. Marketplace photography often carries watermarks or text in another language.
• Set canonical expectations honestly. If the description is the supplier's, the page is not going to rank on it. Category pages and buying guides are where a dropshipping store wins search, not product pages.

If you are importing in bulk without a supplier integration, the mechanics are the same as importing products to WooCommerce with CSV, including the variation columns that catch everyone out.

Stock you do not control

This is the structural risk. Your store's stock number is a copy of someone else's, refreshed periodically.

Three settings that reduce the damage:

1. Shorten the sync interval on fast movers and leave slow stock on a longer schedule. Every sync costs API calls and server time.
2. Decide your backorder policy per product, not globally. A three-week delay is fine for a niche part and fatal for a birthday gift.
3. Use held stock deliberately. Unpaid orders reserving stock prevents overselling during checkout, and the mechanics are in WooCommerce inventory management.

Accept that you will occasionally sell something unavailable. Write the apology email now, with a refund and an alternative, rather than improvising it at the time.

Shipping, tax and the paperwork

Dropshipping's real complexity is here, and no plugin resolves it for you.

• Shipping estimates. The supplier's dispatch time plus the carrier's transit time, stated as a range, before checkout. Hiding a twenty-day delivery until the confirmation email produces chargebacks. Rates and zones are set up as in WooCommerce shipping setup.
• Split shipments. Two items from two warehouses arrive separately, with two tracking numbers. Check that your plugin and your emails can express that, or customers will report half an order as missing.
• Import duty and VAT. Goods crossing a border may attract charges on delivery. A customer billed unexpectedly by a courier treats it as a scam. State who pays, on the product page.
• Customer-facing origin. Where the parcel ships from is material information for a buyer. Say it.

Order emails are the interface for all of this, so verify they actually send before launch, per WooCommerce emails not sending.

Returns are the honest test of a supplier

Ask, before signing up: where does a return go, who pays the return postage, and how long does a refund take? Many suppliers will not accept returns at all, which means either you accept them to your own address and absorb the loss, or you refund without a return. Both are legitimate business decisions. Discovering which one applies during your first return is not.

When a plugin earns its place

• Under a few orders a day, with under a hundred products. Manual routing is fine. Spend the money on product photography instead.
• Hundreds of products, one supplier with a real API. This is the sweet spot for a dedicated integration.
• Several suppliers. Check that the plugin routes per product rather than per order, and that an order containing items from two suppliers splits correctly. Many do not.
• A supplier with no API, only a spreadsheet. You want scheduled CSV import, not a marketplace integration. That is a different category of plugin.
• Custom or unusual arrangements. Building against the WooCommerce REST API is a real option, and it keeps the logic where you can read it.

Whichever route, install onto a store that already works. If products are not appearing correctly before automation, they will not start afterwards, and the causes are in WooCommerce products not showing.

Common mistakes

• Importing the entire catalogue. Thousands of thin pages with duplicate copy, all competing with each other and with every other store using the same feed.
• Setting one markup percentage and forgetting it. Supplier costs move. Review margins on a schedule.
• Trusting stock sync as if it were live. It is a snapshot with a delay.
• Hiding delivery times. The most reliable way to generate refund requests and card disputes.
• Ignoring the performance cost. Scheduled imports and price recalculations on a large catalogue are heavy background jobs. Watch admin and front-end response times, per how to speed up a WordPress site.
• Skipping a real test order. Placing one, paying for it, and following it through to delivery is the only way to see the whole chain.

Verify before launch

Place a genuine paid order for a genuine product. Confirm the supplier received it, the tracking number came back and reached the customer email, and the stock decremented on both sides. Then cancel a second order and confirm the reservation released. Finally, check what a customer sees when an item is out of stock, and make sure the checkout does not let them buy it anyway, per WooCommerce checkout not working.