How to Write a Shopify Shipping Policy That Stops Emails

Most shipping policies are written for the wrong reader. They get drafted once, by the founder, in the voice of a terms-and-conditions page, then linked in the footer and never opened again — least of all by the person who is about to email you.

That is a shame, because the shipping policy is the cheapest support asset a store owns. It costs an afternoon, it never sleeps, and it is the only page that can answer a question before it becomes a message in your inbox. A vague one does the opposite: it manufactures emails, because the customer reads it, does not find their answer, and now has a reason to write to you.

This is how to write one that actually does the job — and an honest account of the half it will never cover.

Two readers, two jobs

A shipping policy is read by two completely different people, and most policies are written for only the first.

Before the sale, someone is deciding whether to buy. Their real question is “will this get here in time, and what will it cost me?” They are comparing you against a competitor who might be clearer. Ambiguity here does not create an email — it creates an abandoned cart, which is worse because you never hear about it.

After the sale, someone is waiting. Their question is “is mine late?” They need one thing: a number to measure against. If your policy says “orders usually ship quickly”, they cannot tell whether day four is normal or a problem — so they ask you.

Write for both, and you remove work from both ends.

The five questions a shipping policy has to answer

Everything else is decoration. If your page answers these five clearly, it is a good policy.

1. When does the order leave you?

This is processing time, and it is the number most stores forget to publish. Customers merge it with delivery time and then start counting from the wrong day, which is the single most common cause of a premature “where is my order?” email.

Say it plainly, and say what a day means:

Orders are packed and handed to the carrier within 1–2 business days.·· Business days are Monday to Friday, excluding public holidays.·· Orders placed after 2 PM Friday are packed on Monday.

2. How long does it take from there?

Delivery time, separated from processing, and broken out by destination if it varies. A table beats a paragraph here, because people scan for their own country and nothing else.

Be specific about what the clock counts. “3–5 days” is not the same claim as “3–5 business days after dispatch”, and the second one is the only one you can defend in an email.

3. What does it cost, and when is it free?

If you have a free shipping threshold, state it in the currency the customer is being charged in, and state whether it is calculated before or after discount codes. That second detail is a real support driver — someone applies a 15% code, drops below the threshold, gets charged shipping, and writes to ask why.

4. What happens when it goes wrong?

This is the section most policies skip, and it is the one that saves the most time. Four cases are worth covering:

• The parcel is late — how long past the estimate before you will investigate
• Tracking has not updated in several days — what you do about it
• It is marked delivered but the customer does not have it — what you ask them to check first, and what you do next
• It is genuinely lost — who files the claim, how long it takes, and whether you replace or refund

You do not need generous policies for this to work. You need stated ones. “We open a carrier claim once a parcel is 7 days past its estimated delivery date” is not a promise to refund anybody — but it turns a worried, open-ended email into a customer who knows exactly when to come back.

5. Where do you not ship, and who pays customs?

The countries you exclude, and one sentence on duties and import taxes for the ones you serve:

International orders may be subject to import duties and taxes charged by your country. These are not included in the price you paid and are the responsibility of the recipient.

One line here prevents an entire category of angry post-delivery messages.

Publish the number you hit on a bad week

There is a strong pull toward writing the fastest number that is technically true — the day you dispatched an order in four hours, the week nothing went wrong. Resist it.

Publish the number you can hit when a supplier is late, someone is off sick, and it is the week before a holiday. Every day you beat a conservative estimate is quiet goodwill that nobody emails you about. Every day you miss an optimistic one is a message you have to answer, and the customer is already annoyed before they start typing.

The same logic applies to ranges. A 1–2 day processing window that you always meet is worth more than a “same day dispatch” claim you meet four times out of five, because the fifth customer does not experience it as a small miss. They experience it as a broken promise.

Write it in the buyer’s words, not the lawyer’s

Compare these two versions of the same fact:

Fulfilment of orders is subject to product availability and carrier capacity, and estimated timeframes are provided for informational purposes only and do not constitute a guarantee.

We pack orders within 1–2 business days. If something is out of stock and will take longer, we email you before we charge your card.

The first one is defensive writing — it protects you from a complaint you have not received yet, at the cost of being useless to everyone who reads it. The second one is a support asset. It answers the question, sets a boundary, and tells the customer what happens next.

A few habits that make the difference:

• Use “we” and “you”, never “the merchant” and “the customer”
• Give numbers, not adverbs. “Quickly”, “shortly” and “as soon as possible” are all the same word to someone who is waiting
• Answer the question in the first sentence of each section; put the caveat second
• Delete any sentence that exists only to protect you. Keep the ones that also inform

A policy nobody finds does nothing

You can write the clearest page on the internet and still get the emails, because the footer is not where questions form. Questions form at specific moments, and the answer has to be sitting at each one:

• On the product page, near the add-to-cart button — a short delivery estimate, not a link. This is where the buying decision happens
• In the cart and at checkout — cost and threshold, before the shipping charge surprises anyone
• In the order confirmation email — the processing time, restated. This is the highest-attention message you will ever send
• In the shipping confirmation email — the delivery window and the tracking link, so the customer has a date to measure against
• On the thank-you page — the same information again, because a good share of people never open the email
• In your FAQ, in the customer’s own words — a footer link titled “Shipping Policy” is found by people looking for a policy. A question titled “When will my order arrive?” is found by people with a question

The footer link stays. It is just the last line of defence, not the strategy.

The half a page can never fix

Here is the honest limit, and it is worth being clear about because no amount of good writing gets around it.

A shipping policy answers generic questions — how long, how much, what happens if. It cannot answer order-specific ones, and those are the messages that actually fill an inbox:

• “Where is order #1001?”
• “It says delivered and it is not here — what now?”
• “Can I still change the address on the one I placed this morning?”
• “I ordered two things, one arrived, where is the other?”

Every one of those needs a lookup against a specific order. The policy page has no idea who is reading it. So the realistic outcome of a good policy is not zero emails — it is a smaller, better inbox: fewer “how long does shipping take” messages, and a higher proportion of questions that genuinely need a person.

That is a real win. It is also the point where a page stops being enough. We have written separately about how to stop answering “where is my order?” emails and five templates for the ones you still have to answer — both start from that same split.

Where we come in, briefly. Order Genie is the AI Order Agent we build at ShopAppsLab. It sits on your storefront, looks the order up in your store, and answers “where is my order?” — plus the shipping, returns and FAQ questions that tend to follow it — 24/7, without you in the loop. When a message is a decision rather than a lookup — a refund, an address change, a parcel that is actually lost — the conversation is handed to you with the full transcript. It starts free with 50 chats a month, and paid plans begin at $9. If you would rather keep answering by hand, everything above still works on its own — that is the honest version.

Worth saying plainly: during setup it imports the shipping and refund policies you wrote on Shopify, shows you what it read, and answers from those. A vague page does not become a good answer because something automated is reading it out. The writing comes first either way.

If you only have ten minutes

Do these five things and stop:

1. Add a processing time, stated separately from delivery time, and define “business day”
2. Put a plain delivery estimate on the product page, next to the buy button
3. Restate the processing time in the order confirmation email
4. Write the four-line “what happens if it is late or lost” section
5. Retitle the footer link, or add an FAQ entry, in the words a customer would actually use

That is an afternoon of work against a question you will otherwise answer every week for as long as the store exists.