Amazon Services API Now Supports Estimated Technician Arrival Times Across All Marketplaces
Amazon's Services API now supports an `estimatedArrivalTime` object on the `serviceFulfillment` endpoint, allowing sellers to send a start‑time and end‑time window (e.g., 2026-02-14T10:00:00Z to 12:00:00Z). The feature is live across all marketplaces as of 2026‑02‑13 and aims to cut missed‑appointment rates by up to 15% and boost daily revenue 5‑10% for optimized fleets.
Overview
Amazon has rolled out an estimated technician arrival feature to its Services API, making it possible for home‑service sellers to transmit a realistic arrival window to customers at checkout. The capability is live across every Amazon marketplace and can be integrated immediately, giving providers a new lever to cut down on no‑shows and improve the overall buying experience.
Key Points
- New API field — The
serviceFulfillmentendpoint now accepts anestimatedArrivalTimeattribute that carries a start‑time and end‑time for the technician’s visit. - Window‑based estimates — Rather than a single timestamp, sellers can send a two‑hour (or any length) window, such as “10:00 am – 12:00 pm,” which reflects real‑world travel variability.
- Universal rollout — The feature works in all Amazon marketplaces without any region‑specific toggles, so a single integration serves North America, Europe, Japan, and other markets.
- Production‑ready today — The enhancement is already in the live environment, allowing developers to push code changes and start delivering windows to shoppers right now.
- Appointment‑reduction impact — Early tests show that providing a clear window can lower missed‑appointment rates by up to 15 % for providers that adopt the field.
- Operational efficiency boost — Accurate windows enable technicians to schedule more jobs per day, potentially increasing daily revenue by 5‑10 % for well‑optimized fleets.
How Estimated Arrival Times Work
- Add the window to the fulfillment request — When calling
serviceFulfillment, include anestimatedArrivalTimeobject containingstartTimeandendTimein ISO‑8601 format. Example:{ "estimatedArrivalTime": { "startTime": "2026-02-14T10:00:00Z", "endTime": "2026-02-14T12:00:00Z" } } - Calculate a realistic range — Pull data from dispatch software, current traffic APIs, and the technician’s existing schedule to generate a window that reflects travel time, expected job length, and buffer for unforeseen delays.
Analysis & Recommendations
Why This Matters
Providing a concrete two‑hour window lets customers plan around technician visits, which early tests show can lower missed‑appointment rates by 15% and increase provider revenue by 5‑10% per day. The universal rollout means a single code change serves every Amazon marketplace, simplifying multi‑region operations.
Key Takeaways
- New `estimatedArrivalTime` attribute (startTime, endTime) added to the `serviceFulfillment` request.
- Window‑based estimates replace single timestamps, supporting any length (e.g., 10:00 am–12:00 pm).
- Feature is production‑ready on 2026‑02‑13 and available in all Amazon marketplaces without region toggles.
- Early data shows up to 15% reduction in missed appointments and 5‑10% revenue uplift for optimized fleets.
Recommended Actions
- →Update your serviceFulfillment payloads in the SP‑API integration to include the `estimatedArrivalTime` object with ISO‑8601 startTime and endTime.
- →Integrate a real‑time traffic or mapping API in your dispatch system to calculate realistic windows, then test the new payload in the SP‑API sandbox.
- →Configure a webhook in Seller Central > Developer Settings > Webhooks to push updated `estimatedArrivalTime` values whenever a technician’s ETA cha...
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!