The Problem With "We'll Ship It All at Once"
So you've got 200 ZTE MC801A routers ready to deploy for a new 5G fixed wireless access rollout. Great. Then someone says: "Let's wait until the F660 ONTs arrive, batch everything, and ship it together. Save on freight costs."
Sound familiar? It's tempting to think that consolidating shipments is always the smarter, cheaper move. But here's the thing: that logic ignores a crucial variable—time. And in B2B telecom, time isn't just money; it's often the entire competitive advantage.
The Surface Problem: It's Just Logistics, Right?
The surface-level issue everyone acknowledges is inventory management. You want to minimize the number of shipments, reduce paperwork, and negotiate better freight rates. It's a neat, tidy calculation on a spreadsheet. But the spreadsheet doesn't show the downstream chaos.
I remember a project in March 2024. A client needed 500 ZTE 5G CPE MC801A routers for a regional network launch. We had the routers. But their order also included 500 ZTE F660 ONTs for fiber-to-the-home connections, and those were delayed by two weeks from the factory. The project manager, trying to be efficient, decided to hold the routers and ship everything together.
"It's tempting to think you can save money by batching. But identical specs from different vendors—or even different product lines from the same vendor—can result in wildly different lead times."
The Deeper Reason: It's Not About Freight Costs
Why does this matter? Because the real cost isn't the shipping. It's the lost revenue from delayed activation. When you batch orders for 5G CPEs and ONTs, you're tying up capital in finished goods that sit in a warehouse, generating zero return.
The question isn't "How much do we save on freight?" It's "How much revenue do we lose for every week of delay?" In a competitive market where operators are racing to sign up subscribers, a two-week delay can mean losing market share to a rival who deployed their Clear Phone or basic hotspot service first.
I said "We can ship the routers now." The client heard "They'll arrive next week with the ONTs." Result: the network launch was delayed by three weeks because the installation teams couldn't start without the CPEs. The saved $400 in freight costs was dwarfed by the estimated $12,000 in lost first-month subscriptions.
The Real Cost: What Happens When You Wait
Let's break this down, because the consequences go beyond just a late launch. Based on our internal data from 200+ rush jobs in the last two years, here's what batching actually costs:
- Delayed revenue: For a typical 1,000-subscriber rollout, each week of delay at $30/subscriber/month equals $30,000 in forgone revenue.
- Labor inefficiency: Installation teams get paid whether they're working or waiting. Idle teams cost about $150/hour for a crew of three.
- Testing bottlenecks: You can't do proper integration testing of the 5G CPE with the core network until you have the gear. Late hardware means compressed testing, which means bugs slip through.
- Customer churn: If you've already started marketing "5G is coming," delays erode trust. It's a lot harder to re-acquire a skeptical customer than a new one.
Look, I'm not saying batching is always wrong. I'm saying it's riskier than most people realize. The 'always wait for the full order' advice ignores the opportunity cost of delayed deployment and the value of getting the network live faster.
The Alternative: A Phased, Risk-Aware Approach
So what's the alternative? You don't need to ship everything overnight on a private jet. But you do need to prioritize. Here's a framework I've used after a painful lesson in 2023 when our company lost a $75,000 contract because we tried to save $1,200 on standard shipping instead of splitting the order.
- Identify the gating items. For a 5G FWA deployment, the CPE (like the MC801A) is the gating item. The ONT for the fiber backhaul can wait a week. Ship the CPEs first, even if it means paying for two smaller shipments.
- Set a cost threshold. We implemented a rule: if the extra shipping cost is less than 1% of the project's first-month revenue, we split the order. Period.
- Build buffer into the schedule. Instead of promising delivery on the day the last item arrives, promise delivery 48 hours after the first batch arrives. That's our policy now, born from a project in 2022 where all the phones arrived but the transceivers were a week late.
Switching to this phased approach cut our average deployment time from 5 days to 2 days for small-to-medium rollouts. The automated process of identifying gating items eliminated the communication errors we used to have. Now, when a client says "We need 200 routers and 200 ONTs for next week," we don't ask "When can you ship all of it?" We ask "What can you ship first?"
Bottom line: efficiency isn't about doing more with less. It's about doing the right things in the right order. And sometimes, the most efficient move is to pay a little extra for a split shipment.
