Overview
Moby can answer questions about your retail-partner sales for any connected retailer. Daily net sales and units, broken out by ZIP code, sit right alongside your DTC data, giving you a fast, no-dashboard way to check how retail is trending, spot geographic patterns, and sanity-check retail performance without pulling a report from a retailer portal.
Today's data is partner-level (blended across all products sold through that retailer) and ZIP-level geography, refreshed daily on a rolling recent window. It does not yet include SKU-level, store-level, or inventory detail, so keep prompts at the partner and ZIP level rather than asking about individual products or stores. See the prompt reference table below for what to ask today, and the change log for what's coming.
Prompt reference
Prompt type | Example | Supported today |
Retailer sales trend |
| Yes |
Unit sales trend |
| Yes |
ZIP-level geography |
| Yes |
Period comparison |
| Yes |
ZIP-level anomalies |
| Yes |
Total revenue and units |
| Yes |
Product- or SKU-specific |
| Not yet |
Store- or door-specific |
| Not yet |
Inventory, sell-through, or stock level |
| Not yet |
Product-launch before/after comparison |
| Not yet |
Ad spend or media connected to retail sales |
| Not yet |
History beyond the rolling window |
| Not yet |
Swap in whichever retailer(s) you're connected to; the "Yes" rows work the same way across all 40+ supported retailers. For anything marked "Not yet," Moby will respond with "I can't answer this yet" rather than guess. That's a scope limit, not a bug.
Change log
Date | Update |
10-08-2026 | Initial release: partner-level, ZIP-level daily net sales and units for 40+ connected retailers. |
Planned | SKU-level and store-level detail, plus a longer historical window, across supported retailers. Once live, Moby will answer sell-through by SKU, geographic performance by product, stockout risk by store, and DTC-to-retail halo analysis around a launch. |
