# Introduction to Subapps

A subapp is a connector that links a specific external platform — like Shopify, eBay, or Lightspeed — to your NetSuite account through IDC. Once you connect a subapp, IDC moves data between the two systems automatically on a schedule. You don't need to move data manually.

## What it is

Each subapp is dedicated to one platform. Setting it up is a one-time process. After that, IDC takes over — running syncs in the background so your data stays consistent between NetSuite and the platform.

## What moves between systems

The exact data depends on your integration, but most subapps move some combination of:

* **Orders** — new orders from the platform flow into NetSuite
* **Fulfillments** — when an order ships in NetSuite, the confirmation is sent back to the platform
* **Inventory** — stock levels in NetSuite are pushed to the platform so your listings stay accurate
* **Returns and refunds** — return requests and refund activity are kept in sync between both systems
* **Settlements and payouts** — financial summaries from the platform are brought into NetSuite for reconciliation

Your subapp's guide will show exactly which of these apply to your integration.

## How subapps are structured

Every subapp has the same three areas.

**Connection**\
Where you authorize IDC to access your platform account. You'll be guided through a setup process that ties your platform account to IDC. You do this once.

**Flows**\
The individual data syncs — one per data type. For example, "Orders to NetSuite" is one flow, "Inventory Sync" is another. Each flow runs on its own schedule. You can see the history of every run in [Logs](/idc/idc-core/logs.md).

**Settings**\
Configuration that controls how your platform's data maps to NetSuite — things like which subsidiary to post transactions to and how items are matched. Your integration admin sets these during onboarding.

## Key things to know

* A subapp must have an active license to run. If syncing stops unexpectedly, check [Licenses](/idc/idc-core/licenses.md) first.
* Every sync attempt is recorded in [Logs](/idc/idc-core/logs.md) — that's the first place to investigate if something isn't working.
* You can trigger a sync manually from the flow screen if you need to run it outside the regular schedule.
* Changes to settings take effect on the next sync run — there's no separate "publish" step.

## Your integration

* [Shopify](/idc/shopify/overview.md)
* [Lightspeed](/idc/lightspeed-x-series/overview.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.in8sync.com/idc/subapps/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.