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.
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.
Two parts of the integration
The NetSuite integration has two distinct parts, and they can be enabled independently: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.
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.
Getting started
Owlery needs three things from you — credentials, a few sample transactions, and a short confirmation call. Everything else is on us.1
Connect
You provide five token-based values — Account ID, Consumer Key, Consumer Secret, Access Token, and Token Secret. Connecting NetSuite 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.
2
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.
3
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.
4
Go live
Owlery enables the configuration, validates representative records, monitors the first syncs, and adjusts as needed.
Frequently asked questions
Do we need a NetSuite admin or IT team?
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.
Do we need to change how we use NetSuite?
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.
Can we start with just reading data?
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.
What if we have multiple subsidiaries?
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.
Who maintains the integration after go-live?
Who maintains the integration after go-live?
Owlery does. We own the configuration and work with your designated contact when anything in NetSuite changes.
Can we backfill historical orders?
Can we backfill historical orders?
Yes. Owlery supports full re-syncs and exact-reference lookups for orders outside the normal selection window.