Signal
Delivery ETA is computable per destination
Concrete handling time, transit time, order cutoff and per-destination shipping data let an agent answer 'when will it arrive?' and 'can it arrive by [date]?' rather than defer to a competitor that can.
Per-platform status
Where a platform documents relevant behavior, its status and source are shown. Undocumented platforms show "unknown" - honest unknowns, never invented.
| Platform | Status | Notes | Source |
|---|---|---|---|
| ChatGPT | Partial | Checkout fulfillment_options carry delivery windows in RFC 3339. Handling time and order cutoff are not documented fields. | Source (opens in new tab) · verified 2026-09-18 |
| Gemini / Google AI Mode | Supported | shippingDetails documents handling time, transit time, destination region and rate as recommended merchant-listing properties. | Source (opens in new tab) · verified 2026-09-18 |
| Perplexity | Unknown | Not documented by this platform. | - |
| Copilot | Partial | ProductShipping carries per-location price and a service field for delivery speed. There is no handling-time, transit-time or cutoff field. | Source (opens in new tab) · verified 2026-01-02 |
| Claude | Partial | The reference agent retrieves fulfillment data through get_fulfillment_options. No ETA field schema or ETA-based ranking is documented. | Source (opens in new tab) · verified 2026-09-02 |
Evidence and sources
This signal is typed hypothesis (Low confidence).
How to act on this
Set handlingTime, transitTime and cutoffTime as ranges (siblings, not nested) with per-destination transit, and echo the estimate in PDP text so a distinct ETA resolves for two distant ZIPs.
Related checklist items
Handbook chapters