How to manage Amazon at $200M revenue: what changes at scale
The playbook that works at $1M a year breaks at $20M, and it breaks again at $200M. The channel itself doesn't change; Amazon is still Amazon. What changes is that the constraints around every decision get harder and less forgiving.
A client brand came in with roughly $200M in total annual revenue, a 20-person customer experience team, seven warehouses, and a $1M to $1.5M monthly target for the Amazon channel. Here's where the playbook changes at that scale.
Supply limits become the primary operational constraint
At $1M a year on Amazon, FBA supply limits are an occasional annoyance. You hit a limit, you file a case, the limit gets raised, you move on. At $200M in revenue with oversized items like the countertop oven and a multi-cooker, supply limits are the governing constraint for nearly every operational decision.
Amazon's supply limit algorithm penalizes long storage times and applies conservative limits to new FBA relationships. For oversized items, the calculation is in cubic footage, not units. A large countertop oven takes up more cubic space than several small products, so a 5,000-unit supply limit is a much tighter ceiling for a client brand than it would be for a brand selling small items.
During Prime Day preparation, the team had to track supply limits at the SKU level, estimate missed sales per SKU, and file cases to negotiate increases. The shipment strategy, sending 50% of needed inventory one week and the remaining 50% the following week, existed specifically to work around limits that couldn't be raised in time. When Prime Day paced at $2.3M in the first hour against a $1.2M full-day forecast, the supply limits were the ceiling on what the channel could sell. The inventory simply wasn't there.
Managing supply limits at this scale takes a dedicated operational layer. Someone has to own the tracker, file the cases, and watch for when limits reset. It does not fit as a side task on an existing operations role.
Warehouse routing is a strategic decision, not an afterthought
At $1M, warehouse routing is mostly a logistics cost optimization. At $200M with seven warehouses, it's a weekly strategic decision with real revenue implications.
Amazon's system recommendations frequently pointed to Texas, Pennsylvania, and Illinois when the California warehouses (CAO2 and CAO3) were better positioned for transit time and freight cost. The fix was a hard rule: always pull from California first for US FBA. Canada ran on its own routing logic. The UK needed a separate approach, limited to oversize items because standard-size storage there was tight.
Teams that follow Amazon's routing recommendations blindly incur higher freight costs and slower receiving times. Amazon's algorithm doesn't know your warehouse network. Your SOPs should override it.
Prime Day preparation starts weeks out
At smaller scale, Prime Day preparation happens in days. At a client brand's scale, it starts eight to ten weeks out.
The supply limit audit happens at the SKU level. Cases get filed on constrained items early enough to get increases approved before the shipment window. Inventory needs to be in FBA early enough to fully check in before the event. Amazon's receiving slowdowns during peak periods mean inventory sent one week before Prime Day may not be available to sell on the day. The team was also managing a 100 to 150 pallet maximum per single send from the warehouse side, which added its own scheduling constraint.
FBA receiving timelines have to be in the PO lead time
This is the simplest change and the one that gets missed most often when a brand scales into serious FBA volume.
At the point where inventory in transit represents weeks of sales coverage, FBA receiving timelines can't be treated as a logistics footnote. Amazon checks in shipments on its own schedule, and during peak periods that schedule slows significantly. A shipment that arrives at an Amazon FC takes days to weeks to become available as FBA inventory.
If your PO lead time is calculated as supplier production plus transit to your 3PL, you're understating the actual time from order placement to customer availability on Amazon. That understatement shows up as FBA stockouts even when your 3PL shows adequate on-hand inventory. The units are there. They just aren't available yet.
The PO lead time calculation has to include the 3PL-to-FBA transfer and the FBA receiving window. During peak, add buffer on top of the standard assumption. It reads as conservatism, but it is really just accuracy.
What to build before you hit these inflection points
Most brands don't build these things before they need them. They discover the gaps when scale breaks the existing approach.
The supply limit management layer, the warehouse routing SOPs, the Prime Day calendar with an eight-week lead time, the PO calculation that includes FBA receiving time: these all feel like overkill until they're not. A brand going from $5M to $20M will hit the supply limit problem before they've built tracking infrastructure for it. At $20M to $50M, the warehouse routing problem surfaces before the SOPs are written.
You don't need a client brand's full infrastructure at $5M. But supply limit management should be on your radar before it becomes the ceiling on what the channel can sell.
Want this run on your catalog?
This is the kind of problem we work every week inside live accounts. Bring your stock report to a 30-minute Fit Call, we’ll tell you which SKUs are at risk in the next 90 days. If we’re not the right fit, we’ll say so.