SP-API Sales Endpoint Now Lets Sellers Track Amazon Haul Metrics Separately
Amazon added an optional `haul=true` query parameter to the SP‑API `getOrderMetrics` call, allowing sellers to pull metrics only for the Haul program. The filter works in the US, UK, Germany and Japan and can be combined with existing date ranges, granularity and ASIN filters, e.g., a request for 2024‑03‑01 to 2024‑03‑07 returns only Haul orders.
Overview
Amazon has upgraded the Selling Partner API (SP‑API) Sales endpoint to let developers pull metrics that belong only to the Amazon Haul program. The new optional filter, added to the getOrderMetrics call, isolates Haul orders from regular marketplace data, giving sellers a clean view of performance in the budget‑focused channel. Sellers who rely on data‑driven decisions can now track revenue, order count and other KPIs for Haul without rewriting existing integrations.
Key Points
- Haul‑only filter — Adding the
haul=truequery parameter togetOrderMetricsreturns metrics that exclude every non‑Haul transaction, e.g., a seller with 1,200 total orders sees only the 300 Haul orders in the response. - Zero‑impact upgrade — Because the parameter is optional, APIs that omit it continue to deliver the full data set exactly as before, so legacy dashboards remain functional.
- Four market support — The filter works for the United States, United Kingdom, Germany and Japan, allowing a single request to compare Haul performance across all active regions.
- Full compatibility with existing filters — Sellers can combine the Haul flag with date ranges, granularity (daily, weekly, monthly) and ASIN‑level breakdowns, e.g., a request for daily Haul metrics for ASIN B07XYZ on March 1‑7, 2024.
- Immediate analytics — No new authentication scopes or token changes are required; the same SP‑API credentials used for standard sales data grant access to the Haul‑specific view.
How the Sales Endpoint Works
-
Add the Haul flag — In the API request URL, append
haul=true.- Example:
GET https://sellingpartnerapi-na.amazon.com/sales/v1/orderMetrics?marketplaceIds=ATVPDKIKX0DER&haul=true&granularity=DAY&startDate=2024-03-01&endDate=2024-03-07. - The response now contains only orders that originated from the Haul shopping experience.
- Example:
-
— Keep any previously used parameters such as , , or .
Analysis & Recommendations
Why This Matters
Sellers can now isolate Haul performance—e.g., see 300 Haul orders out of 1,200 total or a 12 % contribution for a product—without manual post‑processing. The ability to compare across four regions and detect cannibalization helps optimize pricing and inventory for the low‑price channel.
Key Takeaways
- The `haul=true` flag isolates Haul orders; a seller with 1,200 total orders would receive only the 300 Haul orders in the response.
- No new authentication scopes are required; existing SP‑API credentials work unchanged.
- The filter is supported for United States, United Kingdom, Germany and Japan, enabling cross‑region analysis in a single request.
- It can be combined with other parameters like `asin=B07XYZ`, `granularity=DAY`, and date ranges such as 2024‑03‑01 to 2024‑03‑07.
Recommended Actions
- →Update your reporting scripts or API calls in Seller Central > Developer Central to append `&haul=true` to the `getOrderMetrics` URL.
- →Run a side‑by‑side query: first with `haul=true`, then without, using the same date and ASIN filters, to calculate Haul’s share of orders (e.g., 12...
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!