- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
Shipping loses the sale not because the amount is unreasonable but because it arrives late, wrong, or as a surprise.
Shipping rates in a client store: what breaks at checkout
Shipping is where a store’s checkout most often loses the sale, and rarely because the amount is unreasonable. It loses it because the amount appears late, appears wrong, or appears as a surprise after the buyer has already decided what they were going to pay.
Setting rates well is mostly a matter of choosing a model the business can actually honour and then making the result visible early. The arithmetic is the easy part.
The models, and what each one costs you
| Model | Suits | Where it goes wrong |
|---|---|---|
| Flat rate per order | A narrow product range of similar size and weight | Large or heavy items are sold at a loss |
| By weight | Products whose weight varies meaningfully | Product weights are missing or wrong, so the rate silently defaults |
| By zone or distance | Any business shipping beyond one region | Boundary cases — offshore addresses, remote postcodes — fall through |
| By order value | Encouraging larger baskets | Value has no relationship to what carriage actually costs |
| Free above a threshold | Raising average order size | The threshold is set without knowing the margin it consumes |
| Live carrier rates | Wide ranges and unpredictable destinations | A dependency on someone else’s service being available at checkout |
Most small stores are best served by zones with a small number of bands, plus a free threshold if the margin genuinely supports one. Live rates sound appealing and introduce a third party into the most important moment on the site; if you use them, decide what the checkout does when that service does not respond.
Show the cost before the checkout
Telling people what delivery costs before they have entered anything removes the surprise that abandons baskets. That can be a stated range, a threshold, or a simple table on the product page — the point is that the buyer is not surprised at the end.
The product page carries part of this: a delivery line answering “how much, how long” belongs alongside the specification, in the way product detail page structure describes. Where a store serves several regions, a clear statement of where it ships is worth more than a precise rate, because the most annoying discovery at checkout is not the price but that the order cannot be delivered at all.
The details that quietly break rates
- Missing product weights. Weight-based rates fall back to a default when a product has none, and the default is usually wrong in the expensive direction.
- A postcode field that accepts anything. Zone matching depends on the address being parseable, and a free-text field that permits typos routes orders into the wrong band. This is the sharp end of required-field validation.
- A country list that does not match where you ship. Offering every country in the dropdown and then refusing the order is avoidable; keep the list and the shipping configuration in step, with the discipline in writing a dropdown option list.
- Bundles and multiples. Two of an item may not cost twice as much to send. Check how the rules combine before assuming.
- Items added late. Anything appended at checkout changes the weight and sometimes the band, which makes where an order bump belongs and downsell branching worth testing against the shipping rules rather than in isolation.
- Discounts that reach shipping. A percentage code applied to the whole order can discount the carriage as well, which is usually not what was intended — one of the traps in coupon types, limits and traps.
Free shipping is a pricing decision
Offering free delivery does not remove the cost; it moves it into the product price or out of the margin. Both are legitimate, and the choice should be made deliberately rather than because a competitor does it.
A threshold is the middle position and the one most stores get approximately right by accident. Set it above the current average order value — high enough to change behaviour, close enough to be reachable — and check afterwards whether the extra revenue covers the carriage you gave away. That is a measurable question rather than a matter of instinct.
Where the store also sells subscriptions or repeat deliveries, decide how shipping behaves on the recurring charge specifically, because it is easy to set it correctly on the first order and not on subsequent ones — the wider mechanics of which are in recurring payments and failed cards.
Say what you are promising, and keep it separate from the price
A shipping rate is a price; a delivery time is a promise. Buyers conflate them, and the complaints that follow are almost always about the promise. State dispatch time and delivery window separately, and describe them as estimates where they are estimates rather than as commitments the carrier has not made.
Returns belong in the same conversation. Who pays return carriage, and under what circumstances, is one of the terms a buyer is agreeing to at checkout, and it needs to be visible and recorded — see what a consent record has to contain for what that record has to contain. A returns position that appears only in a policy page nobody opened is the origin of most post-purchase disputes.
Operational reality, then measurement
Rates that the business cannot actually fulfil are worse than rates that are slightly too high. Before publishing, confirm who packs, when the carrier collects, what happens on a day nobody is in, and what the cut-off actually is rather than what the page says it is. That belongs in the documented process described in structure, owners and exceptions, and the the thank-you step should repeat the same dispatch expectation the product page set.
Then watch the checkout as a step. Track how many buyers reach the shipping stage and how many continue past it; a large drop there points squarely at rates or at the surprise. Changes to the threshold or the band structure are a genuine experiment, and the way to run one without fooling yourself is in testing a funnel step — judged on completed orders and margin rather than on conversion alone, since a free-shipping threshold that raises orders and lowers profit is not an improvement.
Frequently Asked Questions
Which shipping rate model suits a small store?
Usually zones with a small number of bands, plus a free threshold if the margin genuinely supports one. Flat rates lose money on large items, order-value rates have no relationship to carriage cost, and live carrier rates introduce a third-party dependency at the most important moment on the site.
When should the delivery cost be shown?
Before the checkout. A stated range, a threshold or a small table on the product page prevents the surprise that abandons baskets. Where a store serves several regions, saying clearly where it ships matters more than the exact rate — the worst discovery at checkout is that the order cannot be delivered at all.
Why do weight-based rates sometimes charge the wrong amount?
Because a product with no weight recorded falls back to a default, and the default is usually wrong in the expensive direction. Address parsing is the other common cause: a postcode field that accepts anything routes orders into the wrong zone band.
Is free shipping worth offering?
It does not remove the cost, it moves it into the product price or out of the margin. Both are legitimate if chosen deliberately. A threshold set just above current average order value is the middle position, and whether the extra revenue covers the carriage given away is a measurable question.
How should a shipping rate and a delivery time be presented?
Separately. A rate is a price; a delivery time is a promise, and complaints are almost always about the promise. State dispatch time and delivery window distinctly, and describe estimates as estimates rather than as commitments the carrier has not made.
What should be checked before publishing new rates?
That the business can honour them: who packs, when the carrier collects, what happens on a day nobody is in, and what the real cut-off is rather than what the page claims. Rates that cannot be fulfilled cause more damage than rates that are slightly too high.
We build your GoHighLevel account for you
CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.
- Setup (one-time)$850
- Ongoing (per month)$38.80
No obligation quote · reply within 1 business day
This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.