SPINS
Summary: SPINS provides syndicated retail POS and product intelligence, with strength in natural, organic, specialty, and conventional channels. Clients use it for velocity, distribution, category/competitive context, and narratives that need a market lens beyond first-party sell-in.
Typical Brainforge use: Land Sales API (GraphQL) extracts into object storage → Snowflake (or similar), govern grain in the warehouse, expose cuts in BI/Omni. Satori (portal) remains useful for exploration and spot validation.
Official documentation
| Resource | URL |
|---|---|
| POS / product story (marketing + channel overview) | spins.com/data/pos-data |
| Sales API (GraphQL, schema, measures/attributes, auth, FAQ, releases) | SPINS Sales API (Trainn) |
Replace or add links if SPINS publishes a canonical developer portal URL later.
Integration notes (cross-client)
- API vs portal: Sales API is aimed at automated, large pulls into a warehouse or lake; portal workflows do not replace a schedulable, auditable feed for OKRs and omnichannel reporting.
- Shape: GraphQL; outputs can include Parquet, JSON, CSV (per vendor docs). Requests are asynchronous at scale.
- Time: Vendor documents standard periods (e.g. multi-week rollups, YTD, YoY helpers, trended). Validate against each client’s finance/sales cadence.
- Aggregation: Confirm geography vs product vs time aggregation against contract and API behavior early—retailer/geo cuts are often solved in the warehouse from agreed base grain.
- Custom groups: Satori Custom Groups can carry into programmatic pulls where licensed (per vendor docs).
Operational themes we’ve seen
- Iteration phase — Align API output with business expectations (measures, windows, brand/competitive scope) before calling pipelines “done.”
- Backfill + multiple time windows — Plan for history and rolling windows up front; leadership usually wants both recent and trend context.
- Modeling — Prefer one base mart grain and roll-ups in BI so executive and operator views do not mix incompatible levels in a single export.
Related internal references
- LMNT — procurement / benefits framing:
knowledge/clients/lmnt/resources/spins-api-vs-ui-benefits-memo.md(API vs portal memo). - Magic Spoon — implementation and handoff context:
knowledge/clients/magicspoon/handoffs/andknowledge/clients/magicspoon/transcripts/(search “SPINS”). - General retail / SPINS threads:
knowledge/clients/unassigned/transcripts/(e.g. data standups, SPINS QA).