Set up shipping in five steps: decide which countries you can actually serve, group destinations that can share one price and one delivery promise, work out what each group costs you per order, enter those rules in your store’s shipping settings, and test real addresses through checkout. Launch with one region. A destination belongs in checkout once your product, carrier, costs, and packing routine are proven to work there. A carrier’s coverage map is not that proof.
Start with the parcel, not the map
Record the packed weight, outer dimensions, packaging cost, handling time, replacement value, and any restrictions for a typical order. A ceramic set, chilled food, perfume, a lithium battery, and a rolled print don’t share the same service options even when the delivery address is identical.
For each country you want to serve, confirm four things with the providers and records your business actually uses:
- the provider accepts the product and the packed parcel;
- the service covers the destination and the address type;
- your business can meet the tax, customs, product, and consumer obligations there;
- your team can pack, dispatch, communicate, and handle exceptions consistently.
Keep unsupported destinations out of checkout. “We’ll sort it out after the order arrives” hands your unsolved problem to the customer. If a launch depends on temperature control, dangerous-goods handling, remote-area surcharges, cross-border paperwork, or another specialist service, resolve it before you add the country.
Build a one-row parcel profile for the order you expect most often, then add rows for the realistic extremes: the smallest order, a mixed order, and the largest order you’re prepared to dispatch. Use packed measurements, not product measurements. If those parcels fall into different carrier price bands, one customer rate has to absorb the difference or be replaced.
In Setka, shipping rates can depend on order value, not yet on weight. A catalog with a wide weight spread therefore needs order-value bands in which the heaviest realistic parcel in each band still covers its cost. If your launch needs weight-based rates, tell us at contact@getsetka.com: requests go straight to the people building Setka.
Shipping is one dependency in the wider online-store build sequence. Product facts, payment configuration, delivery eligibility, and the order workflow need to agree before you publish.
Group destinations into zones
A shipping zone is a group of destinations that can honestly share the same method, customer price, and delivery wording. Plan the groups first, then enter them as shipping rules and check the result with real addresses.
Start small. One domestic group plus one nearby-country group is easier to price and test than a worldwide launch. Split a group when any of these differs materially:
- provider or service availability;
- expected parcel cost;
- tax treatment of the shipping charge;
- delivery wording or operating process;
- a surcharge or exception you can’t safely absorb.
A plan might look like this (every number is fictional):
DESTINATIONS YOU CAN SERVE
|
+--------------------+--------------------+
| |
Group A: Home country Group B: Nearby countries
PL DE, CZ, SK
| |
+--------+--------+ +---------+---------+
| | | |
Method A Method B Method C No second method
18.00 PLN 12.00 PLN 42.00 PLN unless verified
| | |
Home-country rule Home-country rule Nearby-country rule
One group can offer several choices, each with a clear eligibility rule. Don’t let rules overlap unless you want customers in the overlap to see more than one choice.
Work out the real cost before setting the customer rate
The carrier invoice is only part of the cost. Build an expected cost per dispatched order:
provider charge
+ packaging materials
+ pick-and-pack labor
+ expected surcharges
+ allowance for failed delivery, loss, or reshipment
= expected delivery cost
Compare that with what the customer pays, on the same tax basis. If your displayed rate includes tax, derive the net shipping revenue first, using the tax treatment confirmed for your store and jurisdiction, and only then compare it with net costs.
Example 1: domestic courier, fully charged
Fictional assumptions: the customer pays 18.00 PLN gross, the assumed tax rate on shipping is 23%, and the expected net delivery cost is 13.20 PLN.
Net shipping revenue = 18.00 / 1.23 = 14.63 PLN
Shipping contribution = 14.63 - 13.20 = 1.43 PLN
This rate leaves 1.43 PLN before the costs these assumptions leave out.
Example 2: pickup price subsidized by product margin
Fictional assumptions: the customer pays 10.00 PLN gross, the assumed tax rate on shipping is 23%, the expected net delivery cost is 11.60 PLN, and the product contribution before the shipping subsidy is 32.00 PLN.
Net shipping revenue = 10.00 / 1.23 = 8.13 PLN
Shipping contribution = 8.13 - 11.60 = -3.47 PLN
Contribution after subsidy = 32.00 - 3.47 = 28.53 PLN
You’re choosing to absorb 3.47 PLN per order. That’s fine if the order contribution can carry it. If a discount can apply to the same order, model the two together with the discount-and-margin guide instead of approving each incentive on its own.
Example 3: a group average hides a loss
Fictional assumptions, all net: customer shipping revenue is 34.00 PLN. Expected cost is 29.00 PLN to Country B, 33.00 PLN to Country C, and 43.00 PLN to Country D.
| Destination | Net revenue | Expected cost | Shipping contribution |
|---|---|---|---|
| Country B | 34.00 | 29.00 | +5.00 |
| Country C | 34.00 | 33.00 | +1.00 |
| Country D | 34.00 | 43.00 | -9.00 |
With orders spread evenly, the group loses 1.00 per shipment on average. Worse, every Country D order loses 9.00. Move Country D into its own group or set a rate the whole group can support. Don’t let an average hide a loss you can predict.
Before approving a rate, rerun each example with a higher provider charge, one extra unit of packaging, and a plausible failed-delivery allowance. You won’t predict every invoice. You’re looking for the assumption that turns a tolerable subsidy into a loss. Note the date and source of every supplier figure so you can review the rate when a quote changes.
Decide what shipping should cost the customer
A delivery rate can recover the full expected cost, part of it, or the cost plus a buffer for variability. A low displayed rate isn’t free: product margin or the rest of the business pays the difference.
A free-shipping threshold is the same decision with a boundary. With fictional numbers: your product contribution is 40% of the order value after product and payment costs, and delivery costs you 12. A 120 order that pays 12 for delivery contributes 48. A 180 order with free delivery contributes 72 − 12 = 60. The threshold pays for itself when it pulls a customer from 120 up to 180. It costs you 12 on every order that would have reached 180 anyway. Model that split for your own order values before you pick the number.
Because Setka sets shipping rates by order value, a threshold is one more rule rather than a workaround: a paid rate below the boundary and a free or discounted one at or above it. Setka promotions can also give free shipping, discounted shipping, or spend-and-save deals. Test baskets below, at, and above the boundary before you advertise it.
Enter the plan in Setka
In Setka, our e-commerce platform, each approved row becomes a shipping rule that you set up in the admin:
- Give it a customer-facing name, such as “Domestic courier” or “Local pickup.” Leave out a carrier name or delivery time you haven’t verified.
- Match it to the delivery service and destination group you priced.
- Enter the approved customer price in your store currency on one consistent tax basis. The tax treatment remains your responsibility.
- Test an eligible address, an ineligible address, and every price boundary in the published store.
- Check the method in the checkout a customer sees. A saved admin rule isn’t proof that checkout shows it correctly.
Shipping rules live in the same platform as the cart, checkout, payments, and orders. The rule you save is the one shoppers see at checkout, and the method they choose is recorded on the paid order. There’s no shipping app to install and no theme code to edit before a new rate appears. Local pickup is supported as a method like any other. See how shipping appears before payment in the shopping-cart UX guide and test it alongside the Stripe checkout flow.
Setka doesn’t create carrier labels yet, so you book shipments with your carrier. If your launch depends on label automation, tell us at contact@getsetka.com: requests go straight to the people building Setka.
Test addresses, totals, and wording
Make a small test matrix: at least one address in every allowed group, one country just outside it, and a boundary case that could trigger special handling. Use fictional customer data reserved for testing.
| Test | Expected result | Evidence to record |
|---|---|---|
| Eligible domestic address | Correct configured choices appear | Country, method names, prices, cart/checkout total |
| Eligible cross-border address | Only the approved cross-border method appears | Country, method, price, tax display, total |
| Unsupported country | No order can proceed on an unavailable promise | Address used and exact customer message |
| Address correction | Eligibility and totals update correctly | Before/after address and totals |
| Completed order | Chosen method and amount reach a paid Setka order | Order reference, method, currency, and totals |
Check the full amount after every address or method change: items, discount, shipping, tax, and final total. After payment succeeds, confirm that Setka created the paid order you expected. The first-order workflow starts from that order and covers fulfillment.
Promise only what you control. “Fixed courier delivery, 18 PLN” names a method and a price. “Arrives Tuesday” promises a timing that depends on cutoffs, carrier acceptance, destination, disruption, and a successful delivery. If you publish an estimate, write down its basis, scope, cutoff, and exception wording first. Your best case is not a guarantee.
For a country you don’t serve, show a useful stop: delivery isn’t available to that country, the shopper can choose an eligible address, and, if your team can genuinely handle exceptions, here’s how to ask. Never invite a customer to pay first and negotiate shipping later.
Launch with one region
Pick the group that carries most of your launch demand, usually your home country. Price your most common parcel and its extremes, configure that group and local pickup if you offer it, and run the five tests above. Add the next group once the first one has shipped real orders at the margin you planned. Then follow your first paid order from checkout to parcel.