Why do my DSers-synced products keep showing the wrong shipping origin?

When DSers assigns inventory to a location that doesn't match your real shipping origin, checkout rates and fulfillment can quietly go wrong. Here's how to find the mismatch and fix it for good.

inventoryshippingDSersmulti-locationdropshipping

What's going on

Shopify tracks inventory per location (Settings > Locations), and shipping rates are calculated using the ship-from address of whichever shipping profile a product belongs to (Settings > Shipping and delivery). Those two things are supposed to agree: the location holding the stock should be the same location your shipping profile treats as the origin for rate and zone calculations.

DSers breaks that assumption in a specific way. Because it exists to sync inventory and orders between Shopify and dropshipping suppliers, it writes stock quantities to a Shopify location on its own schedule, and that location isn't always the one your shipping profiles were built around. The result: a product's on-hand count updates fine, but the shipping rates or delivery estimates shown at checkout are calculated as though the item ships from somewhere else entirely, or the product ends up bucketed into the wrong shipping profile. Merchants running multiple suppliers, or who added DSers after their shipping profiles were already set up, run into this most often.

It's a genuinely confusing problem to diagnose because nothing throws an error. The store just quietly shows shipping rates or delivery windows that don't match how the order is actually going to be fulfilled, and the mismatch usually isn't discovered until a customer complains or an order fulfills strangely.

Why it happens

Shopify was built around a straightforward model: pick a location, that location has an address, shipping profiles calculate rates from that address. DSers layers a second, independent process on top — it needs to keep stock counts current from suppliers who aren't in your Locations list at all, so it has to write those counts to some Shopify location, and it doesn't necessarily know (or ask) which location your shipping profiles consider the ship-from origin.

This gets worse with multiple suppliers or a store that grew organically: a merchant might set up one shipping profile assuming everything ships from a single warehouse, then add DSers later without revisiting that profile, or add a second supplier that DSers maps to a different location than the first. Nobody actively misconfigures anything — the two systems (Shopify's shipping engine and DSers' inventory sync) just were never explicitly told to agree with each other.

5 ways to fix it

1

Pick one location as the real ship-from address for each supplier relationship

Open Settings > Locations in Shopify admin and list every location that currently holds inventory, including any that DSers or another sync app created automatically. For each supplier/product group, decide which single location is the actual ship-from origin for rate and zone purposes, and make sure that location's address is accurate. Where DSers is only tracking stock counts rather than physically holding goods, it's still fine to let it write quantities to that location, but shipping rates should be calculated from the location that matches how the order will really move to the customer.

2

Check Settings > Shipping and delivery and re-map profiles to the correct origin

In Shopify, each shipping profile (Settings > Shipping and delivery) has its own product list and its own ship-from location, and rates in that profile are calculated from that location's address to the customer. If DSers-managed products are sitting in the General profile tied to your primary location, but DSers has actually assigned their stock to a different location, split those products into their own custom shipping profile pointed at the correct origin so zone/rate calculations match reality.

3

Turn off inventory tracking or fulfillment on locations you don't actually use

If DSers (or a past inventory app) created a location you no longer need, go to that location's settings and disable 'Fulfill online orders' for it, or deactivate the location entirely once its inventory is moved. A stray active location with fulfillment enabled is the most common way a stock count silently outranks your intended shipping origin at checkout.

4

Rebuild the DSers <-> Shopify location mapping and document it

Inside DSers, review how supplier/product mappings are tied to a Shopify location (this is typically set per product or per store connection). Write down, in a simple internal doc, which Shopify location each supplier's products should map to and which shipping profile that location feeds. This turns a one-time fix into something a teammate can follow instead of re-discovering the conflict every time a new product is added.

5

Ask Shopify or DSers support to confirm which location is authoritative

If quantities and shipping origin still disagree after re-mapping, contact Shopify support to confirm which location the shipping profile is actually reading from for the affected products, and separately ask DSers support to confirm where their sync writes inventory. Multi-location shipping calculations can be non-obvious when more than one app touches inventory, so getting both sides to state their source of truth in writing avoids repeating this debugging cycle.

Bottom line

This is almost always a configuration and documentation problem, not something that needs a paid app to solve — Shopify's own Locations and Shipping and delivery settings can fully resolve a location/shipping-origin mismatch once you decide which location is authoritative for each supplier. If your catalog spans many suppliers or locations and this keeps recurring, a general inventory/multi-location audit (from your dev agency or a careful manual pass) is more useful than any single-purpose app.

Still Stuck?

Browse the rest of the problem library, run a free storefront scan to catch issues like this automatically, or email us and we'll work out a custom solution for it.