How do I set dropshipping shipping and delivery times so Google Merchant Center does not suspend me?

Every claim on your store is a promise, but the delivery claim is the one promise whose breach is undeniable. A customer might argue about whether a product matched its photo; nobody argues about whether a parcel promised in 5 days arrived in 24. That is why deliverability sits at the centre of Google's Misrepresentation policy rather than at its edge.

Confirmed

Sticking to what Google's published Shopping policies actually say:

• Failure to deliver products in the promised timeframe falls under Misrepresentation. The policy explicitly covers not delivering in the advertised condition and timeframe, alongside unclear billing and promotions you cannot fulfil.
• Shipping costs and delivery times must be clear and accessible before purchase. This is a transparency requirement about your website, independent of what actually happens after an order.
• Shipping settings are a required part of Merchant Center configuration. Products targeted at a country with no configured shipping are disapproved for missing shipping information - this is enforced automatically and immediately, before any human review.
• Google may review your website alongside your account settings. Which means the delivery figures on your site and the delivery figures in your account are being read by the same evaluator, and a disagreement between them is visible without any order ever being placed.

Observed

What we find in practice, across suspended dropshipping stores: delivery-time contradictions are among the most common findings in our audits, and they are the finding we weight most heavily when predicting whether an appeal will succeed. A store with copied supplier images but perfectly aligned, honest delivery information has a real chance. A store with beautiful original photography and a "3-5 day delivery" badge over an unconfigured overseas supply chain does not. The enforcement asymmetry makes sense from Google's side: image originality requires judgment, but a delivery contradiction is a fact a reviewer can establish in under a minute with two browser tabs.

Here is the pattern we find over and over in suspended stores, in its purest form. One store, one product, three sources of delivery information:

Each source was written by a different author with a different motive: the banner by conversion optimism, the policy page by a template, the account settings by an integration default. No one ever read all three side by side - except that reading all three side by side is precisely what a policy review does. The contradiction does not need a test order, a complaint, or a tracking number to be found. It is sitting in plain text.

And note what the contradiction proves. If your own store cannot agree with itself about when a parcel arrives, then at least two of the three claims are false, and Google does not need to determine which. Under a policy that prohibits false statements about your service, an internal contradiction is self-authenticating evidence: no external checking required.

There is a fourth source people forget: the feed. If you submit delivery-time information at product level, or your platform integration does it for you, that figure joins the comparison too. Four authors, four numbers, one store.

To align your delivery claims you first need to understand how Merchant Center models them, because it does not store "delivery takes 10-15 days" as one number. It stores two components per shipping service:

Merchant Center takes the two ranges and computes the total delivery estimate shown to shoppers: minimum handling plus minimum transit through maximum handling plus maximum transit. Configure handling as 2-4 days and transit as 8-12 days and Google will present roughly 10-16 business days. That computed total is what gets compared against your website.

Why handling must match handling, not just the totals

A tempting shortcut: "my total is 15 days either way, so who cares how it splits". It matters, for three practical reasons.

• Your shipping policy page states the components separately. Nearly every policy template does: "processing 1-3 days, delivery 7-14 days". If your website says processing takes 1-3 days and Merchant Center says handling is 5-7 days, the totals can coincide while the components contradict - and the components are what is written down on both sides. A comparison of the two sources fails on the parts even when the sum survives.
• The components are checkable against different evidence. Handling time is corroborated by when tracking numbers go live; transit by carrier scans. A mis-split figure diverges from reality in a way a correctly split one does not, and every customer-facing tracking page documents the divergence.
• Cut-off logic depends on handling. Merchant Center's handling time interacts with your configured order cut-off time to decide which day counts as day zero. A fictional handling number makes every estimate downstream of it fictional too.

So the rule is stricter than "make the totals agree": the handling figure in Merchant Center must equal the processing figure on your website, and the transit figure must equal the delivery figure on your website. Same split, same numbers, both places.

Measure before you configure

For a dropshipper, the honest way to obtain these numbers is measurement, not hope. Place real orders with your supplier to your target countries - you need samples anyway for photography and quality control - and record two dates per order: order to carrier handoff (your true handling time) and handoff to delivery (your true transit time). Take the worst realistic case, not the best. If handling came out at 1, 2 and 4 days, configure 2-4, not 1-2. An estimate you beat is a pleasant surprise; an estimate you miss is a policy violation with a paper trail.

Shipping settings in Merchant Center are per country. There is no worldwide toggle: for every country your products target, there must be a shipping service covering that country with its own cost and its own delivery time. A product targeted at a country with no applicable shipping service is disapproved for missing shipping information - automatically, product by product, before any policy review happens.

This is where the dropshipping instinct to sell everywhere collides with mechanics. The supplier will nominally post to forty countries, so the store enables forty countries - and now owes Merchant Center forty accurate shipping configurations. In practice one of two things happens:

• Most countries are left unconfigured, producing waves of missing-shipping-info disapprovals across the catalogue - which, beyond killing those listings, corroborates the account-level impression of a merchant promising markets it cannot serve.
• One configuration is copied to all countries, so Germany, Australia and Brazil all show "8-12 days" and identical shipping costs, which is certainly false for at least some of them: transit from one origin to different continents cannot be uniform, and any reviewer knows it.

Both outcomes are worse than the honest alternative: narrow your targeting to the countries you have actually measured, and configure each one properly. Three countries with real per-country transit times and costs beat forty countries of defaults. This is the same narrowing recommendation we make in the general dropshipping remediation sequence, but understand the delivery-specific reason for it: every additional country is an additional set of delivery promises you must be able to state accurately and keep. Countries are not free.

The basic mechanics of creating shipping services, choosing rate types and setting delivery ranges are covered in how to add tax and shipping information in Merchant Center; what this article adds is the requirement that what you enter there be measured, split correctly into handling and transit, and mirrored on the website.

Not every delivery statement carries the same risk. The distinction that matters is between claims whose truth you control and claims whose truth you do not.

Safe: dispatch commitments and honest ranges

• "Orders are dispatched within 2 business days." A handling commitment. You can verify it against your supplier's actual behaviour, and if the supplier degrades, you see it in your own order log before it becomes a pattern of broken promises.
• "Estimated delivery: 10-16 business days." A measured range, labelled as an estimate, matching your Merchant Center total. Unexciting and defensible.
• "Delivery times by country" tables with per-country ranges that match your per-country shipping services.

Unsafe: guarantees and borrowed adjectives

• "Guaranteed delivery in 5 days." A guarantee is a promise of the best case in a system where you do not control the worst case. One supplier stockout makes it false, and unlike an estimate, a guarantee has no honest miss.
• "Fast shipping" / "Express delivery" badges on a two-week supply chain. Vague enough to feel safe, but a reviewer reads "fast" next to a 14-day policy page as the banner contradiction from earlier, in adjective form.
• "Ships from the USA / UK / EU" when parcels originate from an overseas supplier. This is not a delivery-time claim at all - it is a false statement of fact about your operation, and customs paperwork and tracking origins disprove it trivially. If you genuinely use a local fulfilment warehouse, say so; if the supplier ships direct from abroad, the origin claim must reflect that.

Free-shipping thresholds

"Free shipping over 50 EUR" is fine - if it is replicated exactly in Merchant Center. Configure the same threshold with a price-based rate table in your shipping service: below the threshold the real cost, above it zero, in each country where the offer applies. The two failure modes we see: a sitewide free-shipping banner while Merchant Center charges shipping on every product (shoppers see a cost in the ad that vanishes at checkout, a price-accuracy mismatch), and the reverse, free shipping configured in the account while checkout quietly adds a carrier fee (the mismatch Google punishes hardest, because the ad understated the total). And if free shipping applies only to some countries, the banner needs to say so - an unqualified "Free worldwide shipping" claim recreates the multi-country problem in one sentence.

Returns have a delivery time too

Deliverability does not end at the doorstep. Your return policy makes time-and-logistics claims as well: how long the customer has, where the parcel must be sent, who pays, and how long the refund takes. For a dropshipper the trap is a template policy promising "free 30-day returns" while the practical reality is a return address at an overseas supplier with return postage costing more than the product. If returns go to the supplier's country, the policy must say so and state who pays; if you cannot support returns economically, offer what you can honestly support - a refund-without-return policy for low-value items is more compliant than a fictional free-returns promise no customer can actually use. The return terms stated on your site must also match what you declare in Merchant Center's returns settings, for the same reason as everything else here: two sources, one truth.

Everything above compresses into one procedure. It is the delivery-alignment step we run in every dropshipping remediation, expanded into its full form:

The acceptance test for the whole procedure is simple: open your product page, your shipping policy, your Merchant Center shipping settings and your returns settings side by side and check that a stranger reading all four would extract one consistent set of numbers. That side-by-side reading is not a metaphor - it is the review.

Not confirmed, and not needed

You will find claims that Google verifies delivery estimates at ZIP-code level against carrier APIs, or places test orders to time your fulfilment. Google has confirmed neither. More to the point, neither is needed to explain a single delivery-based suspension we have seen: the contradictions that sink dropshipping stores are written in plain text on the store and in the account, visible to any reader without a parcel ever moving. Build your compliance for the reader who compares your sources, not for an imagined carrier-API crawler, and you are covered either way.

The bottom line

Delivery compliance for a dropshipping store is not about being fast. It is about being consistent and honest about being slow, if slow is what you are. Measure the real handling and transit times per country, configure Merchant Center from those measurements with the components split correctly, put the identical figures in every place delivery is mentioned on your site, and only target countries where you have done all of that. A store that promises 16 days and delivers in 14 has no delivery problem in Google's eyes. A store that promises 5 and delivers in 14 has the exact problem the Misrepresentation policy was written for - and it advertised the evidence itself.