FarEye Delivery Scheduling Integration | Grasshopper Labs
Integration · FarEye

Real-Time Delivery Scheduling,Connected to FarEye.

Grasshopper plugs live truck capacity directly into FarEye, so brands can offer real delivery dates at checkout, and every appointment, milestone, and proof of delivery flows back automatically. One platform for scheduling and routing.

Appointment Confirmed sent to customer and FarEye
Booking ref RS-208413

70%Faster Scheduling
100%Live Delivery Tracking
22%Improved Truck Utilization
5Booking Channels, One Capacity Pool

Why this matters

Enterprise programs are won and lost on scheduling

Brands running FarEye expect their carriers to answer one question instantly: when can you actually deliver? If your answer is a spreadsheet, a phone call, or a static calendar, the program goes to someone else.

The old way

Static calendars overpromise

A published calendar has no idea how full Thursday's truck is. Customers book dates that don't exist, dispatch untangles it, and the scorecard takes the hit.

The cost

Rescheduling is a $200 problem

A rebooked appointment burns truck space, driver hours, warehouse touches, and customer patience. At scale, that math is what ends contracts.

The bar

Brands expect instant answers

Shoppers now pick a delivery date right next to the buy button, online and in stores. Carriers that feed that moment with live capacity are the ones programs keep.

The workflow

One connected flow, from checkout to proof of delivery

FarEye asks, Grasshopper answers. Here is the full round trip between the shopper, the brand's FarEye platform, and the carrier operation running scheduling and routing on Grasshopper.

Shoppercheckout, online or in store
FarEyebrand's delivery platform
Grasshopperlive capacity
TMS + WMS
Delivery Fleetrouted, verified, delivered

One connection, one event feed, no manual data entry.

1

FarEye asks for live availability

At checkout, FarEye sends the delivery ZIP and ready date to Grasshopper's availability API. Grasshopper answers with real slots from real trucks, checked at once against pieces, stops, and cubic volume.

ZIP-level lookupOrder-aware capacity checkService-level filtering
2

The shopper picks a date, FarEye reserves the slot

The customer chooses a window next to the buy button. FarEye reserves the slot through the API and receives a booking reference back in real time. No emails, no callbacks, no waiting on confirmation.

Reserve APIInstant booking reference
3

The order lands already scheduled

When FarEye creates the order with its reservation, Grasshopper books it straight onto the reserved route. Four gates check route, date, zone coverage, and status, and anything that fails goes to a person with a reason.

Auto-scheduledValidation gatesHuman fallback with context
4

Routing turns the date into a promise

Route optimization sequences the truck and produces each stop's arrival window. One broadcast sends that window by email, SMS, and automated call, and fires Appointment Confirmed to FarEye at the same moment.

Email + SMS + voiceAppointment Confirmed → FarEye
5

Every milestone flows back, ending with proof

Picked and verified, out for delivery, arrived on site, delivered. Exceptions carry item-level codes. The delivered event is held until proof-of-delivery photos attach, so FarEye gets one complete record.

Item-level statusesException codesePOD attached

Under the hood

Scheduling features built for big-and-bulky reality

The FarEye connection is powered by the same scheduling engine that runs every Grasshopper channel: web self-scheduling, shipper APIs, dispatch, automated outreach, and voice.

Order-aware availability

Every slot query re-checks live truck capacity against that order's piece count, stop load, and cube, so no one is offered a date the shipment cannot fit.

Capacity that manages itself

The moment a truck reaches any cap, the slot flips to full, drops out of customer-facing availability, and alerts dispatch. Free the space and it reopens.

Five channels, one capacity pool

Checkout through FarEye, customer self-scheduling, voice outreach, dispatcher tools, and auto-scheduling all draw on one live truck capacity pool.

Automated scheduling outreach

Unscheduled orders get chased by SMS, email, and voice whenever open capacity exists nearby, with business-hours limits, attempt caps, and contact rules.

Earlier-date optimization

Grasshopper scans under-filled trucks a week out, finds scheduled orders in the same zone that fit, and offers those customers an earlier date.

Nothing fails silently

Failed auto-bookings, webhook sends, and customer broadcasts land on the order timeline and route to the right team with a reason and a link.

Built for enterprise program requirements

Dedicated capacity per brand. Reserve entire trucks for one shipper in chosen regions, visible only to that one brand.
Per-shipper visibility controls. Grant each brand none, read-only, or full scheduling access to live truck capacity.
Reschedule governance. Standardized reason codes and tiered fee policies, carried in every event.
Cross-network scheduling. Serve extra zones through partner carriers with one merged availability search.
Config-driven onboarding. Endpoints, tokens, and shipper codes are account settings, so new programs go live in days.
Full audit trail. Every scheduling action, broadcast, and webhook lands on the order timeline with exact timestamps.

For brands and shippers

Already on FarEye? Your carrier network can plug right in.

For a delivery experience running on FarEye, every carrier on Grasshopper becomes a turnkey node in the network: live slot availability at checkout, automatic appointment confirmations, item-level exception visibility, and delivered events that arrive with proof attached. Same API, every market.

Talk to an Expert
Live in production

A global appliance leader offers real delivery dates in e-commerce checkout and in retail stores through FarEye, answered live from Grasshopper carrier capacity.

Running at scale

A premium furniture brand routes white glove orders through FarEye into Grasshopper carriers across several U.S. markets, with milestone events streaming back live.

The event feed

What FarEye hears back from Grasshopper

Every status change is pushed as a token-authenticated webhook, in order, with the detail FarEye needs to update the brand and the customer without chasing anything down.

order lifecycle · FarEye endpoint LIVE
  • ScheduledDelivery date locked against a real truck
  • Appointment ConfirmedArrival window attached after route optimization
  • Picked & VerifiedWarehouse scan complete, item level
  • Out for DeliveryTruck departed, live tracking active
  • Arrived on SiteDriver on location at the delivery address
  • DeliveredHeld until proof-of-delivery photos are attachedePOD attached
Fires on change

Re-Scheduled

Detected automatically by comparing the booked date to the original request, then sent with the new date and the reason code selected by dispatch.

Sent on exception

Exceptions

Item-level reason codes travel with the event, so a partial refusal or a damaged piece is never flattened into a single order-level status.

Always on

Secure and complete

Webhooks are token authenticated, and Delivered is withheld until proof is attached, so downstream systems never reconcile a bare status.

FAQ

Common questions

Do we need developers to connect to FarEye?
No. The integration is configuration, not a custom build. Endpoints, auth tokens, shipper and carrier codes are account-level settings inside Grasshopper. Standard programs onboard in days, and the Grasshopper team handles certification with the brand and FarEye alongside you.
Does the brand see all of our truck capacity?
Only what you allow. Availability answers are scoped per shipper, and you control visibility per account: none, read-only, or scheduling-enabled. You can also dedicate entire trucks to one brand in specific regions so their bookings never compete with the rest of your business.
What happens when an automatic booking can't be completed?
Grasshopper validates the route, date, zone coverage, and route status before booking. If any check fails, the order is flagged to your team with a plain-English reason, for example that the requested route doesn't cover the delivery address, so a person finishes the job with full context. Nothing is dropped and nothing fails silently.
Can customers still schedule directly with us?
Yes. Checkout scheduling through FarEye, the customer self-scheduling portal, automated SMS, email, and voice outreach, dispatcher booking, and unattended auto-scheduling all run on the same live capacity pool. Every channel sees the same truth, so channels never double-book each other.
How do reschedules flow back to FarEye?
Automatically. When a booked date changes, Grasshopper compares it to the originally requested date and emits a Re-Scheduled event on its own, including the new date and the reason code your team selected. Reschedule fee policies, tiered by how close to delivery the change happens, are configurable per account.
We already deliver for a FarEye-connected brand. How do we start?
Book a demo and mention the program you're running. We'll map your current order flow, connect the availability and order APIs, enable the event feed, and run test orders with the brand before cutover. Your operation keeps running the whole time.

See Grasshopper scheduling in action

Watch a live slot query hit a real truck, an order auto-book itself, and the Appointment Confirmed event land, all in one demo.