Ecommerce shipping best practices, from someone who broke most of them first

Ecommerce shipping best practices are the operating habits that keep delivery fast, margins intact, and support queues quiet: computed delivery promises, right-sized packaging, multi-carrier routing, daily exception review. Plenty of pages will give you that list. What I can add, after years running the brands where these lessons got expensive, is which practices actually carry the weight, and the one practice underneath all of them. Every order is a promise. Keeyu keeps it, and every best practice on this page is in service of that single sentence. That is the lens of proactive e-commerce operations, the system of action for e-commerce: shipping is not a cost center to optimize, it is a promise-keeping machine to instrument.

Protect the margin before you optimize the speed

• Right-size packaging. Dimensional weight surcharges are the quietest margin leak in shipping. Audit your five most-shipped SKUs against the box they actually go in.
• Set free-shipping thresholds above AOV. Fifteen to twenty percent above, so the threshold pulls baskets up rather than subsidizing orders you already had. Recheck quarterly against real carrier cost.
• Price the promise, not just the parcel. Part of my strategy at SurfStitch was a monthly subscription that gave members access to priority shipping or discounts. It never eventuated, but the logic holds: delivery speed is a product you can sell, not only a cost you eat. Whatever you charge, the computed date at checkout, covered on the delivery promise page, is what converts.

Do the same for the reverse leg: reverse logistics software is the returns-side equivalent of everything in this section.

Carriers and 3PLs: trust, but instrument

Run more than one carrier once volume allows, route by lane performance, and measure each against your promise rather than their published SLA, using the metrics on the on-time delivery page. And instrument the connection itself, because the integration is a failure point of its own. At Papinelle, Tracy and I lived the nightmare version: a US 3PL integration that would break, so we would come in on a Monday pleased with a great weekend of US sales, then notice on Wednesday or Thursday that none of it was invoicing, and spend the week chasing our tail across a 24-hour time difference. The lesson was not "that 3PL was bad." The lesson was that no system in our stack owned noticing. The full stack view is on the order fulfillment system page.

Instrumenting means counting checkpoints, not carriers. We track roughly thirty to thirty-five checkpoints between the order being placed and the parcel arriving, a number I gave on The Ecommerce Edge. Counting that many is the point, because a late order is not just a carrier problem, as I said on The Breakout CEO. It is everything upstream: is Shopify syncing correctly, is inventory allocated correctly, are styles loaded correctly, is the payment system working, is the warehouse getting it out on time. Those system, process and people issues add up to more than a carrier losing or delaying a parcel.

Peak season: prepare the failure paths

Peak does not invent new failure modes, it multiplies your existing ones. Year after year, big brands end up in the news because they are not shipping orders, and it is a shame to watch, because they could have nailed it. The fix is decided before the sale: what order volume you expect, how long it takes to pick, pack and ship it, and how many people the warehouse needs to clear it inside your SLA. Getting that headcount right was one of the critical things I did at P.E. Nation and SurfStitch, so we never had to put up a banner saying everything would take a week longer. And plan for the 3PL stalling anyway: at peak a 3PL can stop shipping for days, and you will not see it unless something is watching. Decide the oversell playbook before November: detection threshold, bulk-communication templates from the shipping notifications playbook, refund authority. And be careful what you automate at the front door: one retailer had 60 percent of tickets flowing through helpdesk AI, and over peak it snowballed, because the AI only escalated angry customers while the polite ones churned silently. They pulled it back to 10 percent. Automation at the complaint end scales the apology. The automation that pays at peak sits at the detection end, before the complaint exists.

Watch what peak does to your headcount plan before it does it. A brand I spoke with runs twenty customer service people year round and scales to forty for the two months around peak, which I mentioned on eCommerce Australia. That second twenty is the price of a failure path nobody automated.

The practice under all the practices

Every habit above shares one dependency: knowing, order by order, whether the promise is still on track. Age your exceptions daily. Track promise-kept rate as a first-class metric alongside the measures on the customer satisfaction metrics page. And put something in the stack whose only job is watching every order against the date it was sold with, across storefront, warehouse, 3PL, and carriers, and acting when one drifts. Detect. Decide. Act. That is what Keeyu does, and it is the practice that turns the rest from folklore into a measured system. Keeyu gets shoppers what they want, on time, as promised. The wider discipline is on the post-purchase operations hub, and a demo will show you which best practices your orders are actually breaking. Every order is a promise. Keeyu keeps it. Best practice is just that sentence, operationalized.

Write the promise down as data before you optimize anything against it. Ours reads: order before twelve, pay for express, ships same day, arrives tomorrow, which is how I put it on Add To Cart. A practice you cannot express that precisely is a preference. The ones you can are the only ones an operation can be held to.

• Keeyu customer results: keeyu.com/customer-stories
• The Breakout CEO #86, The Pivot This Founder Made After an Investor Called It Impossible - one in five US shoppers not getting orders on time, and the ticket ratios behind it.
• Marketing for SMEs, Jevon Le Roux on the E-Commerce Mistake Costing Millions - the orchestration layer, and the 55% ticket cut at EHP Labs.