Everyone repeats the same line about dropshipping clients: the website is the product, and the warehouse is somebody else’s problem. That’s half right. Customers don’t separate your build from the parcel. A China shipping forwarder can’t repair a confusing checkout page, and your theme can’t repair a crushed carton. Both end up in the same one-star review.
We’re taking apart five myths that agency owners and their store-owner clients keep repeating. They matter to your margin because they all end the same way: you scoped a website, the client blames the website for a problem that lives somewhere else, and your retainer quietly turns into an unpaid complaints desk.
Myth: Refunds and bad reviews are a customer service problem, not a website problem
Reality: Your site makes promises, and every promise the supply chain can’t keep comes back as a refund request with your client’s name on it.
The myth survives because the damage shows up in the wrong place. A damaged or missing parcel arrives at the customer’s door, but the complaint lands on the product page, the review widget and the contact form. You built those, so that’s where the client looks first.
A typical conversation goes like this. The owner says conversions are down and the site must be broken. You check, and the site is fine. The refund queue is full of messages about wrong items, missing parcels and photos that didn’t match what arrived. No plugin fixes that. A careless fulfillment partner is a business problem, and the website just puts it on display.
You still own part of it, because the delivery wording, the returns page and the order emails are your work. Scope them as promises, not decoration.
What to do instead
- List every claim the site makes about delivery, stock, returns and quality.
- Ask the owner who confirmed each claim with their fulfillment partner, and get the answer in writing.
- Cut or soften anything nobody can back up.
- Place a real test order before launch and read every email and tracking message the customer would receive.
No-bull verdict: If the site promises something the partner never agreed to, that promise is your problem, not the partner’s.
Myth: A catalog store is a brochure with a cart, so brochure hosting will do
Reality: A store that imports, updates and sells a large catalog is a working application, and hosting it like a five-page brochure site costs you support hours.
The myth lives on because every demo looks fast. Ten products, no visitors, and the owner is the only person clicking. Then the first ad campaign starts, a crowd arrives at once, and the checkout slows down at exactly the moment it needs to hold up.
Scheduled jobs make it worse. Stock and price updates run on a timer, and on WordPress that timer is triggered by page visits by default. A quiet store falls behind. A busy one piles background work on top of the shoppers. Ask your developer or host to run those jobs from a real server schedule instead (DISABLE_WP_CRON in wp-config.php is the usual starting point) and test that they fire.
Here is the gap between the pitch and the job:
| What you’re sold | What the store needs |
|---|---|
| “Unlimited products” | Enough memory and processing to import, update and search a big catalog without timing out |
| “Lightning fast” | A checkout that stays responsive while an ad campaign sends traffic |
| “Daily backups” | A restore you have actually tested, so a bad import doesn’t eat the order history |
Price the hosting conversation honestly. If the client insists on the cheapest plan, write down that you recommended otherwise, and bill the extra support at your normal rate.
No-bull verdict: Hosting a live store like a brochure site is a decision, and someone pays for it, usually you.
Myth: Supplier photos and descriptions are good enough to launch
Reality: Supplier content is raw material, and launching it unedited makes your client’s store look like every other store selling the same item.
It survives because it’s free and it’s already there. A catalog import fills hundreds of product pages in an afternoon, and everyone feels productive. The cost arrives later and in pieces.
The images are often heavy and inconsistent, so category pages crawl on a phone. The descriptions read like they passed through three translators, with measurements nobody checked. The same text sits on many other stores, which gives search engines little reason to prefer yours. Worst of all, a photo that doesn’t match the item in the box is the fastest route to a refund and a bad review.
Typical scope trouble: the quote covered the import, the client expected a finished store, and now the pages are slow and you’re being asked why. Import is cheap labor. The cleanup is where your margin goes.
Sell the content pass as its own line. Resize and compress the images, rewrite the best sellers first, and tell the owner to order samples of those items to compare against the photos before the pages go live.
No-bull verdict: Importing a catalog is the easy part of the job. Quote the rest, or you’ll do it for free.
Myth: Your agency should write the shipping and customs policy page
Reality: The policy has to describe what the owner’s business actually does, and import rules are not something an agency gets to guess at.
This one shows up as a favor. The owner says, “Just copy a policy from another store, it’s only a page.” It takes five minutes and feels harmless. It isn’t. That page makes statements about delivery, about who deals with import charges, about returns. If a statement is wrong, the customer finds out at their door, and your wording is the exhibit in the dispute.
Import rules differ by country and by product, and they change. We aren’t going to summarize them here, and neither should you on a client’s behalf. The owner should check their own situation with the official customs authority in the countries they sell to, or with a licensed customs broker. If a question is legal, it goes to a qualified professional, not to your support inbox.
What you can do well is everything around the words. Make the page easy to find from the footer, the cart and the order email. Give it a clear structure. Put the owner’s name on the sign-off, and keep that sign-off in your project records.
- The owner supplies the policy text and confirms it with their partners and advisers.
- You format it, link it, and flag anything that conflicts with other pages.
- Your contract says the content is client-supplied.
No-bull verdict: Build the page, not the promises on it. Policy text belongs to the owner, and so does the risk.
Myth: Once the store is live, it runs itself
Reality: A dropshipping store changes every week without anyone touching the site, so launching without a monthly check is a slow leak.
Agencies sell builds, and clients budget for builds. Then the project ends and everyone assumes the store sits there earning. Meanwhile products go out of stock, suppliers change what they list, links break, and plugin updates pile up. We’ve all seen retainers that retain nothing, and the clients who cancel them are not entirely wrong.
The fix is to make the monthly work visible. Not “maintenance” as a vague word, but a short list the owner can read and you can finish.
- Check for sold-out or removed items that still show as available.
- Place a test order and read the emails and tracking message.
- Read the support inbox and the recent reviews for repeating complaints.
- Apply updates on a staging copy first, then to the live store.
- Send the owner a note that says what you found and what you changed.
That note is what the client is really paying for. It proves the work happened, and it catches the next fulfillment problem before it becomes a pile of refunds.
No-bull verdict: A retainer is worth paying only when the client can read what it did each month.
Where we land
A dropshipping store is a website attached to a chain of people you don’t control, and your scope has to say so. The five myths share a root: treating the build as the whole job. This week, open your last dropshipping proposal and check whether it covers promises, content, policy sign-off and a monthly check. If it only lists a theme and an import, add the missing lines before the next quote goes out.
Sell the whole parcel journey, or expect to be billed for it in free support.