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

# NetSuite Integration

> Three things from your team. Owlery handles everything else.

Owlery connects to NetSuite through the SuiteTalk REST API and SuiteQL. We pull your orders and item data into Owlery automatically, then design and configure the write-back workflows that fit your business — so your team doesn't have to.

<Info>
  **No NetSuite admin on staff? No problem.** Most Owlery customers connect NetSuite without a dedicated NetSuite administrator or IT team. You provide credentials, we handle the rest.
</Info>

**Where to find it:** `Settings → Integrations`

## What Owlery handles

Everything else:

* **Discovering your configuration**: subsidiaries, custom fields, statuses, units of measure, item types, address formats, and operating workflows.
* **Designing the integration**: which records to sync, how to map fields, how to route subsidiaries, and which write-back events to enable.
* **Building and testing**: configuring mappings, filters, routing, and write-back strategies; testing normal, partial, and exception scenarios.
* **Rolling out and monitoring**: coordinating the go-live, backfilling historical data if needed, and monitoring synchronization going forward.
* **Adapting when things change**: when your NetSuite fields, roles, subsidiaries, or workflows evolve, Owlery updates the integration.

<Tip>
  Owlery adapts to *your* NetSuite — we don't ask you to change how your team uses it.
</Tip>

## Two parts of the integration

The NetSuite integration has two distinct parts, and they can be enabled independently:

<CardGroup cols={2}>
  <Card title="Reading data" icon="download" href="/shippers/netsuite/reading-data">
    Owlery pulls orders, items, and facilities from NetSuite automatically. This is hands-free after credentials are connected — no ongoing work from your team.
  </Card>

  <Card title="Writing back" icon="upload" href="/shippers/netsuite/writing-back">
    When you're ready, Owlery designs a best-practice system for creating fulfillments, receipts, and freight updates in NetSuite. We recommend what to enable based on your workflows.
  </Card>
</CardGroup>

Most teams start with read-only synchronization. Write-back strategies are introduced after your team validates the inbound data — there's no pressure to enable everything at once.

## Getting started

Owlery needs three things from you — credentials, a few sample transactions, and a short confirmation call. Everything else is on us.

<Steps>
  <Step title="Connect">
    You provide five token-based values — Account ID, Consumer Key, Consumer Secret, Access Token, and Token Secret. [Connecting NetSuite](/shippers/netsuite/connect) walks through generating them, and we're happy to do it with you on a screen share. Owlery verifies access and begins account discovery right away.
  </Step>

  <Step title="Design">
    Share two or three representative PO, SO, or TO numbers. Owlery reviews your transactions, custom fields, statuses, and workflows, then presents a recommended configuration — nothing is needed from your team during this stage.
  </Step>

  <Step title="Confirm">
    Your team reviews the recommendation in a short call and confirms it matches how you actually operate. We adjust anything that doesn't fit.
  </Step>

  <Step title="Go live">
    Owlery enables the configuration, validates representative records, monitors the first syncs, and adjusts as needed.
  </Step>
</Steps>

Straightforward accounts move through these stages quickly — often within the first week or two. Accounts with many subsidiaries, heavy customization, or complex lot requirements spend longer in the design stage. Owlery tells you what to expect once we've seen your account, and the waiting is on our side rather than yours.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Do we need a NetSuite admin or IT team?">
    No. You need someone who can generate API credentials — that's often an existing NetSuite user with an admin role, a bookkeeper, or even your NetSuite partner. Owlery handles everything after that.
  </Accordion>

  <Accordion title="Do we need to change how we use NetSuite?">
    Almost never. Owlery maps your existing records, fields, statuses, and workflows. If a small optional change would improve things, we explain the benefit and the minimal effort involved — but it's your call.
  </Accordion>

  <Accordion title="Can we start with just reading data?">
    Absolutely. Inbound synchronization works independently. Individual write-back strategies can be added later, one at a time, as your team gets comfortable.
  </Accordion>

  <Accordion title="What if we have multiple subsidiaries?">
    One connection can route orders from different NetSuite subsidiaries into the correct Owlery organizations. Separate connections are also supported when account boundaries require them.
  </Accordion>

  <Accordion title="Who maintains the integration after go-live?">
    Owlery does. We own the configuration and work with your designated contact when anything in NetSuite changes.
  </Accordion>

  <Accordion title="Can we backfill historical orders?">
    Yes. Owlery supports full re-syncs and exact-reference lookups for orders outside the normal selection window.
  </Accordion>
</AccordionGroup>

Need help planning your NetSuite connection? Email [support@owlery.ai](mailto:support@owlery.ai) and include a few representative transaction numbers.