A fast-growing soil brand began as a startup selling mushroom grow kits online. Over time, they grew into a nationally recognized gardening brand with a mission: make it easy for families to grow food at home.

As they expanded into soil and seeds - and began selling through big-box retailers like Home Depot, Target, and Lowe’s - the company hit a supply chain wall.

Soil posed a unique challenge. It’s heavy. It’s low-margin. And the cost to ship it to individual customers often exceeded the price of the product itself. Delivery times for ecommerce orders were often 7–10 days. For customers looking to plant by the weekend, that wasn’t good enough.

At the same time, the brand was thinking bigger. They didn’t just want to sell bags of soil — they wanted to compete with incumbents like Miracle-Gro and serve larger use cases: backyard renovations, community gardens, schools.

To do that, they needed a network that could:

That’s when they brought in WARP.

The soil brand didn’t tweak around the edges - they rebuilt their supply chain from scratch.

Here’s what they did:

First, they pulled 12–24 months of historical order data. Then, WARP overlaid it onto their network of 86 cross-docks across the US. Instead of guessing where inventory might need to be, they pinpointed the exact regions where customers were concentrated - and chose facilities to hit 1 - 2 day delivery windows with the fewest possible nodes.

The brand moved away from stockpiling 4–6 weeks of inventory at a few big warehouses. Instead, they placed just 1–2 weeks of inventory at 20+ regional cross-docks — right near customer demand.

Inventory restocking was dynamic, tied to actual order velocity and seasonality, not just static forecasts.

The leaner model meant faster replenishment, lower storage costs, and less risk of inventory getting stuck in the wrong place.

At the start, the brand handled their inbound truckloads manually. But gaps in timing and visibility slowed things down.

WARP stepped in to manage the full flow - from soil plants to cross-docks to customers.

By connecting inbound (FTL) and outbound (LTL) moves inside one platform, they tightened turnaround times, reduced stockouts, and created a cleaner flow of inventory across the system.

Traditional LTL wasn’t cutting it. It’s designed for warehouses, not for dropping pallets at farms, schools, or backyards.

Instead, WARP built a flexible delivery model:

This setup allowed the brand to offer 1–2 day delivery even for heavy, awkward shipments — without blowing up margins.

Instead of months of modeling and endless strategy decks, they started small: One location. One real-world test.

Once it worked, they quickly expanded to 20+ cross-docks — adjusting as they went.

Facilities that underperformed were pulled out. Inventory levels were tweaked weekly.

Speed, not perfection, was the priority — and it paid off.

Every node in the network - inbound shipments, cross-docks, drivers, final mile carriers — operated through WARP’s OS.

It wasn’t just data collection. Facilities and drivers worked inside the system for scanning, tracking, and updates.

That gave the brand real-time visibility without needing to stitch together WMS, TMS, and third-party freight portals.

One dashboard. One playbook. Full control.

The brand also uses the same system to manage broader operations beyond WARP-managed freight.

Plenty of brands duct-tape together a supply chain stack: one system for inventory, another for transportation, a separate WMS, and a tracking tool layered on top. That’s manageable when volumes are low and problems are predictable. But at scale, that fragmentation slows everything down — you can’t respond fast, and you lose visibility in the moments that matter.

What WARP provided wasn’t just software — it was a single layer of coordination across plants, cross-docks, and delivery. Every node, every handoff, every scan happened inside the same operating system. 

That allowed the brand to:

The signal here: Control beats integration. If you’re trying to scale complex logistics, don’t just connect the dots - own the whiteboard.

Before WARP, the brand mostly sold to hobbyists: people buying small bags of soil for balconies or windowsills. But with faster delivery — 1–2 days in most major markets — they unlocked a new kind of customer: one who orders entire pallets for bigger, planned projects.

That customer:

In other words: speed wasn’t just a performance win — it was a growth lever.

The companies that win in logistics-heavy categories aren’t always the cheapest. They’re the ones that change what’s possible for the customer and capture new use cases as a result.

WARP didn’t show up with a perfect solution. They started with a pilot in one market, saw what worked, and then expanded to 20+ cross-docks in a matter of weeks.

They made adjustments as they scaled:

And it worked because they moved before it was perfect.

The insight here? The cost of waiting is often higher than the cost of being slightly wrong. You don’t need 100% certainty - you need a feedback loop that lets you correct quickly.

If you’re facing slow, expensive fulfillment for pallets or heavy goods in “non-standard” locations, you typically have two paths:

Below, I’ve broken down both approaches.

For each step, I’ll note what you do yourself - and what’s handled for you if you work with a provider like WARP.

Why: You can’t optimize what you can’t see. Start with where your demand truly is.

DIY:

With WARP:

Why: Fewer, well-placed nodes beat a sprawling, underutilized network.

DIY:

With WARP:

Why: If you don’t sync these, you’ll end up with inventory in the wrong place at the wrong time.

DIY:

With WARP:

Why: If you can’t reliably serve homes, schools, or community sites, you lose trust.

DIY:

With WARP:

Why: You won’t get it perfect. Learn from live orders.

DIY:

With WARP:

Why: Disconnected systems kill speed and visibility.

DIY:

With WARP:

Why: A responsive team fixes problems before they escalate.

DIY:

With WARP:

Both paths can work.

If you want to go deeper on this project, here’s the full conversation I had with Daniel. We get into the weeds on everything from dynamic routing to what makes residential LTL actually work - plus lessons learned from scaling fast under real-world constraints.

Connect with WARP on LinkedIn and their website.

This conversation has been edited for length and clarity.

Before WARP, what did the brand’s supply chain look like? What were the biggest challenges?

Daniel: The soil brand started as an ecommerce company selling mushroom grow kits. That was the core of their business early on, and it worked well — it was lightweight, direct-to-consumer, and scalable online.

But as they expanded into organic soil and seeds, the game changed. Soil is bulky, heavy, and regulated. Each state has different permitting requirements for selling and moving soil, and getting that infrastructure set up is a heavy lift. It took them years to build relationships with production plants across the U.S. — they ended up with 22 different manufacturing facilities, each servicing different parts of the country.

They also got retail traction — Home Depot, Lowe’s, Target, etc. But ecommerce remained a huge piece of the business, and that’s where the pain started to show. You can’t ship a bag of soil cross-country in 7–10 days and expect to make a profit, especially if shipping costs more than the product. They needed a supply chain that could support fast, affordable home delivery — and that’s where they were stuck.

Did they have any forward-deployed inventory or cross-docks in place before you came in?

They were experimenting with it. They had started using a few cross-docks and worked with multiple partners, but the network wasn’t unified. Delivery was managed through freight brokers who passed off shipments to traditional LTL carriers. That works for warehouse-to-warehouse freight, but it breaks down when your customers are schools, farms, or suburban homes. These carriers just aren’t built for that kind of delivery experience.

So what made them reach out to you? Was there a specific turning point?

They had tested enough to see the potential — they knew that placing inventory closer to customers could work. But they didn’t know how to scale it. They came to us not just for transportation, but to help design and manage the whole system. They needed someone to take the proof of concept and operationalize it at scale.

What was your starting point once the brand came to WARP? What were the first problems you wanted to solve?

The first issue was cost per pallet. Soil is heavy — you can’t fit that many pallets on a truck, so if you’re shipping cross-country, your per-unit shipping cost goes way up. The second issue was delivery experience. Traditional LTL networks don’t work well for non-commercial destinations. And finally, they lacked visibility — they didn’t know what inventory was where, when it would arrive, or how fast it would turn.

Our goal was to fix all of that. We started by mapping their order and production data against our own facility network — which includes over 80 cross-docks across the U.S. We built out a scenario plan to forward-deploy inventory in 20+ markets, close to demand hubs, while minimizing shipping cost and reducing inventory holding times.

How did you decide how much inventory to place and where?

We looked at historical order volume, seasonality patterns, weather data (which affects soil demand), and population density. Our goal was to keep 1–2 weeks of inventory per region — enough to maintain high service levels, but lean enough to avoid excess storage fees. We also built in feedback loops: if demand surged, we could speed up replenishment from the plant. If demand dropped, we’d slow things down.

And on the inbound side — who handled the FTL shipments to the cross-docks?

Initially, the brand did. They worked with truckload brokers to move soil from the 22 plants to the forward facilities. But over time, we took over those linehauls to gain full control over timing and routing. Connecting both inbound and outbound gave us better planning capabilities and helped the entire network run smoother.

Outbound delivery is where most costs show up — especially with bulky residential orders. How did you design your LTL model to work for that use case?

Typical LTL carriers were built decades ago. Their networks are optimized for warehouse-to-warehouse moves. They own terminals, run fixed trailers, and don’t do well with one-off home deliveries — especially if it’s a pallet of soil going to a backyard or a school.

We took a different approach. Our network is built to be flexible. We don’t just use 53-foot trailers. We use everything from cargo vans to 16-foot, 26-foot, and even 30-foot box trucks — whatever is right for the job.

That flexibility lets us dynamically route based on the volume and destination type. It also lets us hit faster delivery times, because we’re not tied to fixed assets or fixed routing schedules. Most of the brand’s orders are delivered within 1–2 days now.

Is this something traditional brokers could replicate?

No — because they don’t control the delivery experience. A broker just passes your load to Carrier X or Y and hopes for the best. They can’t decide what equipment to use, how it’s routed, or what happens if a customer isn’t home. We operate as a virtual LTL carrier — we run our own network, our own tech, and our own routing logic. That’s how we control quality.

How did you ensure visibility across the supply chain — from the plant to the customer?

Everything runs on our operating system. The cross-docks, drivers, and even the customer-facing tracking — it’s all handled by our software. It’s not a patchwork of systems. That gives us real-time updates on where inventory is, what’s been picked, and when something’s out for delivery.

For the facilities, it’s like a lightweight hybrid of a WMS and IMS — focused on fast turn, not deep storage. And because we own the stack, we can customize it: require a photo for one type of delivery, a signature for another. That level of control lets us guarantee consistency across 20+ facilities.

Was this system used only for WARP shipments, or could the brand use it for other parts of their ops too?

They used it beyond just our shipments. Once it was in place, it helped them manage broader parts of their network. The tech and the supply chain model became part of their infrastructure.

We first connected around August or September. By October, we had a pilot running in one location. We didn’t put a formal timeline on the pilot — we just let both sides learn. Within 4–8 weeks, we expanded to 20+ cross-docks and took over linehaul as well. By spring, everything was fully operational.

What’s the biggest ROI? Cost savings? Speed? Something else?

All of the above — but really, the biggest ROI is enabling growth. Before, they were shipping bags of soil to casual gardeners. Now, people are buying pallets to redo entire backyards. They unlocked a new customer segment. Their margins are higher on these bulk orders, and the experience is better than anything their competitors offer.

Faster delivery = more trust = more repeat orders.

Any funny or surprising learnings?

One cross-dock received a shipment where every pallet had animal poop on it. The soil had been stored outdoors near a lot of wildlife. Needless to say, that facility refused to take any more unless the packaging changed.

But seriously — the biggest learning was adapting to different delivery environments. You need the right equipment, tires, and routing for a rural farm vs. a suburban home vs. a school.

And for brands thinking about working with WARP — when’s the right time to reach out?

When you’re scaling, launching a new product line, or your current network is breaking under complexity — that’s when it makes sense. We help teams go from patchwork logistics to a resilient, flexible network that supports growth.

And my advice: don’t overthink it. Plan well, but don’t get stuck in endless modeling. The only way to learn is to do.