> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spherecast.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> See the data feeds between Spherecast and your ERP, confirm data is flowing, and trigger a manual pull on NetSuite.

## What this page is for

This page shows the connected data feeds between Spherecast and your ERP (Enterprise Resource Planning system — your company's system of record). Each feed is a **sync record**: a stream of one kind of data, like warehouses or purchase orders, flowing in from the source system.

In plain terms, this is where you confirm your data is actually flowing. Every plan you make rests on this data being current, so when something looks stale or wrong downstream, this is the first place to check. Spherecast is **NetSuite-first**: the richest features here — manual pulls and timing metrics — are available on NetSuite connections. Other ERPs may appear as source-system labels, but they don't all offer the same manual-sync and metrics options.

## What each sync record shows

| Element                         | What it means                                                                                                                                             |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**                        | The record's name in Spherecast, alongside its name in the source system — for example "Product (item)".                                                  |
| **Last synced**                 | When data last came in, or **Never synced** if it hasn't yet.                                                                                             |
| **Source-system badge**         | Which system the feed comes from — for example **NetSuite**.                                                                                              |
| **Cadence / health indicator**  | How often the feed runs and whether it looks healthy.                                                                                                     |
| **Synced fields**               | An expandable list of exactly which fields flow in, shown as *field ← source field*, with a **Custom** badge on fields mapped from a custom source field. |
| **Manual Sync** *(NetSuite)*    | A button to pull that record right now instead of waiting for the next scheduled run.                                                                     |
| **Timing metrics** *(NetSuite)* | Performance figures such as average sync time and runs today.                                                                                             |

## What gets synced

These record types flow into Spherecast:

* Warehouse
* Inventory
* Purchase Order
* Transfer Order
* Bill of Materials
* Work Order
* Product
* Supplier

On **NetSuite**, several of these can also be pulled on demand with **Manual Sync**: Product, Supplier, Bill of Materials, Purchase Order, Transfer Order, and Work Order.

Demo companies also see a **Gmail connect** card for connecting an email account.

## How it affects planning

Your forecasts, coverage signals, and recommended orders are only as fresh as these feeds. If **Last synced** is old, or a record reads **Never synced**, the plan may be working from stale data — that's your cue to investigate or, on NetSuite, to run a manual pull. The **synced fields** list also tells you exactly which attributes Spherecast receives, so you can confirm a field you rely on is actually coming across.

## Step by step: pull fresh data on NetSuite

1. Find the sync record you want to refresh — for example **Product** or **Purchase Order**.
2. Check its **Last synced** time to see how current it is.
3. Expand **synced fields** if you want to confirm which fields flow in.
4. Click **Manual Sync** to pull that record now.
5. Watch **Last synced** update, and glance at the timing metrics to confirm the run completed.

## Example

Before a planning session, you notice the **Purchase Order** record shows **Last synced** several hours ago, but you know new POs were placed in NetSuite this morning. You click **Manual Sync** on that record, wait for **Last synced** to refresh to "just now," and then plan against the up-to-date orders.

> **Note:** Manual pulls and timing metrics are NetSuite features; other source systems appear here but may not offer them. Once your data is confirmed flowing, see [Writing to your ERP](/guide/supply-planning/writing-to-erp) for sending plans back out, and [Data alerts view](/guide/home/data-alerts) for data problems the feeds surface.