Connects to your planning stack in under a day.

No IT project. No custom development. Ready-made connectors for the tools supply chain teams actually use — ERP, demand planning, data warehouses, and direct CSV.

Request a pilot See methodology
12 connectors

Ready-made for the tools you're already running.

Your data team installs the connector — no custom development, no IT ticket queue. Each connector is preconfigured for the data schema and authentication method of its target system.

SAP IBP

Integrated Business Planning. Pulls historical sell-in/sell-out data and demand signal baseline. Supports IBP for Demand and Supply modules.

ERP OAuth2 < 1 day

Oracle Demantra

Demand management and trade planning integration. Extracts baseline demand history and seasonal indices per SKU and channel.

Planning API key < 1 day

Blue Yonder Luminate

Demand planning and replenishment module. Pulls SKU-level forecast history and actuals for baseline calibration.

Planning OAuth2 < 1 day

Kinaxis RapidResponse

Supply chain planning platform. Reads demand plan actuals and supply constraints for baseline and output integration.

Planning API key < 1 day

o9 Solutions

Integrated business planning platform. Pulls demand signals, actuals, and SKU performance data through the o9 REST API.

Planning REST API < 1 day

Infor M3

ERP for process manufacturers. Integrates with Infor M3's demand planning and inventory management modules for CPG-specific data structures.

ERP API key < 4 hours

Snowflake

Data warehouse connector for teams that have already centralized their POS and ERP data in Snowflake. Direct SQL query integration against your demand tables.

Data Warehouse SQL / OAuth < 4 hours

Microsoft Dynamics 365

Dynamics 365 Supply Chain Management. Connects to demand forecasting and inventory management modules via Microsoft Graph API.

ERP OAuth2 < 1 day

NetSuite

Oracle NetSuite ERP. Pulls transaction-level demand history, purchase orders, and inventory data for smaller to mid-market CPG brands on NetSuite.

ERP API key < 4 hours

CSV / Excel Direct

No ERP required. Upload your POS scan data and sales history directly as CSV or Excel. Fastest path to first forecast — working within hours of file upload.

Direct CSV / XLSX < 4 hours

REST API (Custom)

Build your own integration using the Heatvelo REST API. POST your POS data, receive enriched forecast JSON back. Full documentation available after pilot sign-up.

API REST / JSON Custom

Retail Data APIs

Direct integration with retailer-provided scan data APIs (Walmart Retail Link, Kroger Partner API, Target Partners). Pulls sell-through at retail without ERP intermediary.

Retail API key < 1 day
REST API

Build your own integration in a day.

For technical teams who prefer direct API integration. POST your POS data, receive enriched forecast JSON back. Authentication via API key — no OAuth dance required for pilot tier.

POST https://api.heatvelo.com/v1/forecast 
// Request — send your POS baseline
{
  "api_key": "htvo_live_xxxxxxxxxxxx",
  "forecast_horizon_weeks": 12,
  "region": "US-MIDWEST",
  "skus": [
    {
      "sku_id": "SKU-B12",
      "category": "cold-brew",
      "pos_history_weeks": 104,
      "units_by_week": [2100, 2240, 2380, "..."]
    }
  ]
}

// Response — enriched 12-week forecast
{
  "forecast_id": "fc_20260627_B12",
  "generated_at": "2026-06-27T06:14:22Z",
  "skus": [
    {
      "sku_id": "SKU-B12",
      "weeks": [
        {
          "week": 1,
          "forecast_units": 2840,
          "confidence_low": 2721,
          "confidence_high": 2959,
          "signal_flags": []
        },
        {
          "week": 3,
          "forecast_units": 3520,
          "confidence_low": 3372,
          "confidence_high": 3668,
          "signal_flags": [
            {
              "type": "weather",
              "description": "+8°F temperature deviation above seasonal baseline",
              "demand_impact_pct": +23.9
            }
          ]
        }
      ]
    }
  ]
}
Pilot 500 SKUs / 10 API calls per day. Sufficient for most pilot evaluations. No credit card required during 2-week pilot period.
Growth+ 2,500–10,000 SKUs / 100+ API calls per day. SLA on response time. Dedicated endpoint with your API key tied to your forecast model.
Data security

How your POS data is handled.

In transit: All data transmitted from your systems to Heatvelo uses TLS 1.3 encryption. No unencrypted channel is supported. API keys rotate on 90-day cycles with configurable shorter rotation for security-sensitive environments.
Processing window: Your POS scan data is ingested, normalized, and used to calibrate your SKU baseline model. Raw scan data is not retained beyond the 48-hour processing window. What's retained is the normalized demand pattern (seasonal curve, baseline units per SKU per week) — not the underlying transaction data.
Data isolation: Your POS data is processed in an isolated pipeline and is not shared with or used to calibrate models for other customers. Each customer's baseline model is tenant-isolated in Heatvelo's infrastructure.
No long-term retention by default: Heatvelo does not store your historical POS export beyond what's required to maintain your rolling 24-month baseline. You can request deletion of your baseline data at any time by contacting [email protected]. This terminates your forecast service — it cannot continue without a baseline.

Note: Heatvelo is a bootstrapped early-stage company. We have not yet pursued SOC 2 Type II certification. These data handling practices are contractually binding in our service agreement, but third-party audited certification is on our roadmap for 2027. If your procurement process requires SOC 2 today, this is something to discuss with Tobias directly before starting a pilot.

Don't see your planning tool?

Tell us what you're running. If it exposes a data API or exports CSVs, we can almost certainly build a connector. Describe your stack and we'll tell you the setup timeline.

Request a connector See pricing

Or reach Tobias directly: [email protected]