Integrations
Connects to your ERP and WMS on day one
No data engineering team. No CSV uploads. Routeharvest reads directly from your transaction history via direct connectors to the ERP and WMS systems mid-market distributors actually use.
Supported systems
Full read access to purchase orders, sales orders, and inventory transactions. Syncs hourly on Growth and Scale plans.
Location-level inventory feeds including bin quantity, pick activity, and receiving dock status. Location granularity is critical for per-DC forecasting.
Historical demand data, open purchase orders, and supplier lead-time records. Cadence's data model maps cleanly to Routeharvest's SKU-location structure.
Designed for multi-location distributors. Vela's native location hierarchy feeds directly into Routeharvest's DC-level model partitioning.
Real-time pick and put-away data from the warehouse floor. Forklane's event stream lets Routeharvest detect demand spikes before the ERP reflects them.
Read existing demand plans from Axel and incorporate them as input signals to the Routeharvest model, preserving your team's manual adjustments.
ERP Integration
What Routeharvest reads from your ERP
Routeharvest does not need access to your entire ERP schema, only the tables that carry demand signal. The connector reads three data types:
Sales order history
Every line item, SKU, quantity, and order date going back 24 months minimum. This is the raw demand signal that trains the per-SKU model.
Open purchase orders
Inbound replenishment orders with expected receipt dates. Routeharvest subtracts inbound stock from the projected deficit to prevent duplicate reorder alerts.
Supplier lead times
Historical actual lead times per supplier, not the nominal lead time on the item master. Real variance is what determines how early a reorder alert needs to fire.
Read-only access
The integration uses read-only credentials. Routeharvest never writes back to your ERP. Your data model stays exactly as it is.
WMS Integration
Why location data changes the forecast
Aggregate demand forecasting (summing all SKU demand across all locations) masks the stockout risk at any single distribution center. A product can be overstocked at one DC and three days from zero at another. Without WMS location feeds, you can't see the DC-level risk.
Bin-level inventory
Actual quantity available by SKU and location, pulled from the WMS at each sync cycle. Not the ERP inventory record: the warehouse floor reality.
Pick rate signal
Daily pick velocity per SKU-location pair. A sudden pick rate increase at one DC can signal a demand event that the sales order history won't show for another week.
Custom API
Not on this list? Build a custom connector
The Routeharvest ingest API accepts any ERP or WMS that can push transaction records as JSON. Scale plan includes direct integration support.
POST /v1/ingest/transactions
Authorization: Bearer rhvt_ingest_xxxx...
Content-Type: application/json
{
"source": "custom-erp",
"transactions": [
{
"sku_id": "SKU-042",
"location_id": "cincinnati-dc",
"qty": 18,
"type": "sales_order",
"date": "2026-06-01"
}
]
}Connect your ERP today. First forecast in 48 hours.
Join the early-access cohort. Same-day integration setup, no data engineering team required.
Get Early Access