Sales Data: Daily Sales Guide & Improved Docs

The Sales Data API now has a dedicated guide for daily sales endpoints, with clearer descriptions, response semantics, and worked examples.

What's New

New guide page: Managing Daily Sales — a single place that documents both the GET aggregation and PUT projection endpoints, with end-to-end examples and use cases.
Improved endpoint descriptions for GET /sales/v1/daily-sales and PUT /sales/v1/locations/{locationId}/daily-sales in the API Reference.
Refreshed the Sales Data overview to include daily-sales endpoints, scopes, and the new guide.

totalSales vs projectedSales: totalSales is computed automatically from the Transactions API and cannot be set directly. projectedSales is your forecast and is set via the PUT endpoint — the two values are independent.
Sparse GET results: days with no aggregation data are omitted from the response (not returned as zero). Treat missing days as 'no data yet'.
PUT semantics: each date in updates may appear at most once and replaces only the projected value — totalSales is never modified.
Date format: all daily-sales dates are ISO 8601 YYYY-MM-DD.
Error cases: documented 400 responses for invalid ranges, unknown locations, and duplicate dates.

sales_data.read — required for GET /sales/v1/daily-sales
sales_data.write — required for PUT /sales/v1/locations/{locationId}/daily-sales

For full details, see the Daily Sales Guide and the API Reference.