When we were running 10,000+ deliveries a month as a final-mile operation, scheduling was the single biggest source of wasted hours and angry customers. So when we connected Grasshopper to FarEye for enterprise appliance and furniture programs, we built the flow we always wished existed.
This post walks through exactly how it works, and what it takes for a final-mile carrier to win this kind of business.
Why enterprise brands demand appointment-based delivery
Big-and-bulky purchases changed. A shopper buying a refrigerator or a sofa expects to pick a delivery date the same way they pick a color — right at checkout, online or in a store.
Platforms like FarEye exist to power that experience for the brand. But FarEye can only show a delivery date if someone on the carrier side can answer with real availability, instantly. That answer is the whole job of appointment-based delivery software.
The carriers who can plug in and answer live are the ones who get the volume. The ones who answer by phone the next morning become the backup plan.
The checkout is the new dispatch desk
Ten years ago, scheduling happened days after purchase. A rep called the customer, negotiated a date, and hoped the truck had room.
Today the scheduling moment has moved into the buy flow itself. The brand's system asks your system for dates while the shopper's card is still in their hand. If your delivery scheduling software can't answer in that moment, the experience breaks before you ever touch the freight.
What a static calendar really costs
Some carriers publish a fixed calendar and clean up the mess later. That mess is expensive.
What appointment-based delivery software actually does
Real appointment-based delivery software answers one question honestly: can this specific order go on a truck in this zone on this date?
Notice the words "this specific order." That's the difference between a calendar and a capacity engine, and it's where most delivery scheduling software stops short. A calendar knows Thursday exists. A capacity engine knows Thursday's truck in that zone has room for two more stops, nine more pieces, and 340 more cubic feet.
Grasshopper treats every truck, day, and zone as a live slot with three caps. Every availability answer is computed against those caps at the moment of the request.
Live capacity, not published calendars
When a slot request comes in, Grasshopper resolves the ZIP to a region and zone, then checks which trucks actually have room left. Slots that hit any cap flip to full automatically and disappear from availability.
Free up space, and the slot reopens on its own. No one maintains the calendar, because there is no calendar. There is only the truth about the trucks.
Three caps on every truck
Each slot enforces three limits at once, and every query checks the specific order against all of them.
A customer is never shown a date their order can't actually ride on. That single rule removes most reschedules before they're born.
Where scheduling meets the warehouse
Delivery scheduling software that can't see the warehouse ends up promising dates for freight that hasn't arrived yet. That's how carriers end up calling customers to walk back a confirmed appointment.
Because Grasshopper is one platform, scheduling reads the same data as receiving. Goods still in transit can be booked ahead against their expected arrival date, and lead times for consolidated freight are computed per lane from real transit days.
The result is simple: the dates offered at checkout already account for where the freight actually is.
Inside our FarEye integration
Here's the flow we run in production today for a global appliance leader and a premium furniture brand, both orchestrating deliveries through FarEye into Grasshopper carriers.
It's three API steps in, and one event stream out. No emails, no spreadsheets, no swivel-chair.
At checkout, FarEye sends the delivery ZIP and the date the goods are ready. Grasshopper responds with live slots in FarEye's own format, filtered to dates where that order genuinely fits.
The shopper sees real options next to the buy button. In stores, the sales associate sees the same live answer, so the promise made at the register matches the promise made online.
When the shopper picks a date, FarEye reserves the slot through the API and receives a booking reference instantly. Then the order comes in carrying that reservation.
Grasshopper books it straight onto the reserved route in the same call. The order arrives in your operation already scheduled, on a truck that has room for it, before anyone on your team has touched it.
Automation you can't trust is worse than no automation. So every auto-booking passes four validation gates first.
If any gate fails, the order routes to your team with a plain-English reason. A person finishes the job with full context. Nothing fails silently, and everything lands on the order's audit timeline.
Keeping the promise after the booking
Booking the date is half the job. Keeping the brand's control tower and the customer aligned until the proof of delivery lands is the other half.
This is where running scheduling inside an all-in-one platform pays off. Because Grasshopper is the TMS, the WMS, and the customer communication layer in one system, the confirmation, the warehouse verification, and the delivery events all come from the same source of truth. You can see how that platform fits together on our transportation management system page.
Routing builds the customer's window
The night before delivery, AI-powered route optimization sequences the truck and produces an expected arrival window for every stop.
That window becomes the customer's appointment. Routing and customer communication are one pipeline, so the window you promise is the window the route actually predicts.
One broadcast, three channels
One action sends the arrival window to every customer on the route by email, SMS, and automated voice call, honoring each customer's contact preferences and timezone.
The same broadcast fires the Appointment Confirmed event to FarEye at the same moment. The customer, your dispatcher, and the brand's control tower all learn the window together.
Proof-complete delivery events
As the day unfolds, FarEye receives the milestones that matter, without status noise.
The brand never has to chase a bare status.
Filling trucks while customers wait less
Appointment-based delivery isn't just a customer experience play. Done right, it's a utilization play, and utilization is where final-mile margin lives.
Those two numbers come from the same engine doing two jobs at once.
The earlier-date hunt
Grasshopper scans under-filled trucks up to a week out, finds orders already scheduled later in the same zone that would fit, and proactively offers those customers an earlier delivery.
Empty cube gets filled, customers get their furniture sooner, and your ops team gets a report of who was contacted. Nobody on your staff had to hunt for any of it.
Five booking channels, one pool
Checkout scheduling through FarEye is one door into your capacity. Grasshopper runs five, all drawing from the same live pool.
One pool means channels never double-book each other. Automated outreach runs with business-hours limits, attempt caps, and do-not-contact rules, so the automation stays polite.
How carriers win FarEye-connected programs
If you deliver appliances or furniture, enterprise programs orchestrated through FarEye are some of the best volume in the final mile. Winning them is less about price than about proving your operation can hold a promise at scale.
We wrote about choosing the right foundation in our big and bulky delivery software buyer's guide. The scheduling layer is where that foundation gets tested in public.
What the scorecard measures
Enterprise scorecards are blunt. They track the things customers feel.
Appointment-based delivery software moves all three at once, because dates are only offered where the order fits, confirmations fire themselves, and every delivered event arrives with proof attached.
Questions to ask before you connect
Whether you run Grasshopper or any other delivery scheduling software, pressure-test it with three questions before promising a brand you can plug into FarEye.
If any answer is shaky, the scorecard will find it. Fix it before the brand does.
Getting live in days, not quarters
The Grasshopper side of a FarEye connection is configuration, not a custom build. Endpoints, tokens, and shipper codes are account settings.
A standard program goes live in days: map the order flow, connect availability and orders, enable the event feed, run test orders with the brand, cut over. Your final mile operation keeps running the whole time.
Conclusion
Enterprise brands moved the scheduling moment to checkout, and platforms like FarEye are how they run it. Carriers now get sorted into two groups: the ones whose delivery scheduling software can answer live, and the ones being scheduled around.
Grasshopper was built by operators to put final-mile carriers in the first group. Live, order-aware slot availability. Reservations that book themselves onto real trucks. Appointment confirmations, milestones, and proof of delivery flowing back to the brand without a single manual touch.
That's what we built with FarEye for appliance and white glove furniture programs, and it's the same engine behind every scheduling channel in the platform — from white glove delivery software workflows to appliance delivery scheduling at retail scale.
The brands are asking one question: when can you actually deliver? Make sure your answer is instant.
Ready to schedule at checkout?
See Grasshopper in action.
Connect live capacity to FarEye, confirm appointments automatically, and stream proof of delivery back to the brand — without manual touches.
From the blog
Eyes on the road
Loading latest posts…