Don't Let Shipping and Tracking Break Your BFCM

Getting the order is the easy part.

You've spent months on the promotion, the site speed, the checkout flow, all of it aimed at one moment: the click that turns a visitor into a sale. Shopify's own 2025 BFCM data shows what that effort adds up to industry-wide: $14.6 billion in sales over the Black Friday-Cyber Monday weekend alone, up 27% year over year, with more than 81 million customers buying in five days. For the full breakdown of what BFCM volume actually looked like this year, see BFCM by the Numbers.

None of that is the hard part. The hard part starts the moment the order confirmation email sends, and it runs on two tracks at once: what happens while the package is in transit, and what happens if it comes back.

Some brands are calling that second track Q5, the six-to-eight-week wave that follows BFCM, and how it plays out is largely decided by what you set up during Peak, not what you scramble to fix once it arrives. Get either track wrong at BFCM volume, and it doesn't just cost you a support ticket or a shipping label. It costs you whether that customer buys from you again.

This is a checklist for both tracks, built from what actually breaks at peak volume and what fixes it before it does.

The volume problem is really a pressure problem

A normal order creates a normal amount of post-purchase activity: one delivery to track, one possible return to process. Everyone knows BFCM multiplies the number of orders. But it also multiplies the pressure on everything downstream of them, at the exact moment your team has the least slack to absorb it.

Two things happen in that window, and most brands only prepare for one of them:

1. Every customer who ordered is now watching for their package, and a share of them will contact you before it arrives if you don't tell them first.
2. A meaningful share of what you sold is coming back, and how much that costs you depends on decisions you made (or didn't make) before the volume hit.

Fixing the first without the second just means your support team stays quiet while your shipping costs quietly climb. Fixing both is what actually protects the season.

Track: stop the questions before they're asked

At Casely, before they fixed this, roughly half of all support tickets were some version of "where is my order." That's a design problem, not a support capacity one: customers were asking because nobody had told them yet.

WISMO tickets (where is my order) cluster around uncertainty, and BFCM manufactures uncertainty on purpose. Bigger order volumes, tighter carrier capacity, and gift-timing pressure turn "when will this arrive" into "will this arrive in time." A customer who'd shrug off a slow update in March will file a ticket in November because a holiday deadline is riding on it.

Customers are always going to check. Send them to a generic carrier tracking page, and where they check becomes the whole problem: you hand off the moment entirely, along with any chance to reassure them, sell them something else, or even know the conversation happened. You just find out later, as a ticket.

The fix is two things working together: a tracking page customers actually stay on, in your brand, instead of a carrier's site, and proactive updates sent automatically when something real happens (shipped, out for delivery, delayed) so the update reaches the customer before the anxiety does.

What that's worth in practice: David Donahue, a premium menswear brand, used to send every tracking click straight to a carrier's page. High WISMO volume, and worse, zero visibility into what should have been some of their most engaged traffic all year.

As Nick Ledwitz, who runs the brand, put it: "Customers checking on their orders represent some of the most captive, purchase-ready traffic you'll ever have."

After moving to a branded tracking page built on Track by Loop, WISMO tickets dropped to near zero, and the tracking page itself generated $64,000 in revenue from 189 orders in a single year, at a $336 average order value. That's a 28x return, with transactional emails tied to the experience hitting a 76% open rate.

The pattern holds at different scales. CurrentBody, shipping across 30 carriers and 22 storefronts globally, cut WISMO from 29% of all support inquiries down to 5%. Casely cut tickets 76% and eliminated roughly 2,000 of them in the first month, freeing their CS team of more than 10 hours a week each. Different brands, same shape: the ticket volume didn't get handled faster. It stopped arriving.

The look doesn't have to be minimal to work. The Body Shop's tracking page leans fully into their own brand identity, bold color, bold type, full shipment timeline, and still does the same job: the shopper never leaves to check a carrier site.

Ship: decide the cost before the volume decides it for you

The other half of BFCM's post-purchase pressure shows up a few weeks later, when Q5's returns start.

Retailers expect to process $849.9 billion in returns in 2025, according to the National Retail Federation, or 15.8% of all retail sales. During the holiday season specifically, that rate climbs to 17%, and online orders run even higher, at 19.3%. Now compress a meaningful share of your annual return volume into about six weeks, and the question isn't whether returns are coming. It's whether you decided how to handle them before they did.

The real driver of return shipping cost, for most brands, is a default: one carrier, one label type, one process, applied to every return regardless of what it is or where it's going. That works fine at low volume. At BFCM volume, it means paying the same undifferentiated rate on thousands of returns that could have routed more efficiently, simply because nobody set up the rules to do otherwise.

Three levers control that cost, and all three need to be decided in advance, not mid-November:

1. Rate shopping

Not every carrier is cheapest for every parcel; a shipment crossing the country behaves differently than one staying local, and the carrier that wins on price changes accordingly. Comparing rates across carriers per shipment, rather than defaulting to one negotiated rate for everything, is the single highest-impact lever available.

2. Convenience that doesn't cost you the customer

A return that requires a printer is a return that gets delayed, sometimes indefinitely, by a shopper who doesn't own one. QR-code-based labels and flexible drop-off options remove that friction, and it matters more than it sounds: a customer who has a painful return experience, especially one where the shipping cost feels disproportionate to what they're sending back, tends to remember it a lot longer than a customer who has an easy one.

3. Routing by what's actually being returned.

A couch and a keychain should not travel the same path home. Rules based on product attributes (type, vendor, weight, destination) let different categories route automatically, instead of a person deciding each one manually. Ship by Loop applies these rules the moment a return is created and rate-shops across every carrier you have enabled, rather than defaulting to a single option.

International returns need their own version of this, not an exception process improvised on the fly. Customs documentation, HS codes, and carrier coverage all change once a package crosses a border. Shaping New Tomorrow, a Scandinavian apparel brand shipping across Denmark, Sweden, Germany, and the broader EU, built this in advance: seven workflows for their main markets and five more specifically for Norway and other non-EU destinations, on top of fraud detection that's already caught $0.87 of every $1 in confirmed fraud. (More on fraud at BFCM scale in our upcoming BFCM P&L piece.)

What matters here is the shape of the fix, not a specific savings percentage: international returns get their own set of rules, built once, instead of a manual exception handled every time one shows up.

The checklist: do this before BFCM starts

For the full season checklist across Prep, Peak, and Q5, see The Q5 Returns Playbook.

Tracking

• Brand the tracking experience. If clicking "track my order" sends customers off your site, that's the first thing to change.
• Turn on proactive notifications for the moments that matter (shipped, delayed, out for delivery), not every possible status update.
• Connect tracking events to the tools you already use, like Klaviyo, so customer communication doesn't depend on someone remembering to send it.
• Test it yourself. Place an order and follow the whole notification sequence before your customers do.

Shipping and returns

• Confirm your rates, whether negotiated or your own carrier accounts, will hold up at BFCM volume before the first spike, not after.
• Add a backup payment method for label generation, so one declined card can't stop labels from printing during your busiest week.
• Review routing rules for the exceptions, not just the common case: international, oversized, high-value. These are the returns that cost the most when handled manually.
• Audit your alert settings so a delayed or stuck shipment surfaces to your team before a customer has to ask about it.

That's what a controlled Peak and Q5 actually look like on both tracks: not a surprise ticket, not a surprise shipping bill, but decisions your team already made.

FAQ

Does fixing WISMO tickets cost more than it saves? Based on the David Donahue result, no. The tracking page didn't just reduce support cost, it generated $64,000 in direct revenue against a fraction of that in setup effort, for a 28x return.

We already have negotiated carrier rates. Is rate shopping still worth setting up? Usually yes. A negotiated rate is typically your best price with one carrier, not necessarily the best price for every parcel. Rate shopping compares your options per shipment instead of committing every return to the same carrier regardless of distance or size.

What should be locked in before BFCM versus handled as it comes up? Branded tracking, proactive notification triggers, rate access, backup payment methods, and routing rules for known exceptions should all be decided in advance. What's left to handle in the moment should be genuinely novel cases, not the categories you could have already planned for.

Whichever track is the bigger pressure point for your team this year, both are worth fixing before Peak arrives, not during Q5.

Covered through Q5?

Peak earns the revenue. Q5 decides how much of it you keep.

See how it works