Skip to main content
Once your NetSuite credentials are connected, Owlery begins pulling data automatically. There is no manual mapping, no CSV uploads, and no recurring work from your team. Owlery discovers your account configuration, converts NetSuite records into Owlery shipments and items, and keeps everything in sync on an ongoing basis.
Reading data from NetSuite is the simplest part of the integration. Owlery handles it almost entirely hands-free — your team just provides credentials and confirms the initial setup.

​
How It Works

1

Owlery connects securely

Owlery connects with the tokens you created during setup and never stores them in plain text.
2

Owlery discovers your account

We read your classifications, departments, locations, cost categories, units of measure, and item records to understand how your NetSuite is configured.
3

Records sync automatically

Each sync pulls only what’s new or changed since the last one. Owlery doesn’t repeatedly import your full account.
4

Data is converted and validated

Each NetSuite record is transformed into the facilities, stops, dates, items, references, and statuses your Owlery workflows need. Invalid data is flagged for review, not silently accepted.

​
Orders

Owlery supports three NetSuite transaction types: Each order type can be enabled or disabled independently. Owlery recommends which ones to turn on based on the transactions it finds in your account. From each order, Owlery can synchronize:
  • Internal ID, transaction number, external ID, and reference numbers
  • Statuses (mapped to Owlery equivalents based on your workflows)
  • Created and last-modified timestamps
  • Creator, employee, or sales representative email
  • Customer, vendor, subsidiary, classification, department, and sales channel
  • Pickup and delivery facilities, addresses, and dates
  • Header notes and line-level handling notes
  • Line items with SKU, quantity, fulfilled/received quantity, unit, rate, and amount
  • Lot or inventory assignments and expiration dates
  • Ship method and other configured custom fields

​
Item Master

Owlery synchronizes your item catalog alongside orders. The default configuration recognizes more than 15 item types — inventory, assembly, kit, non-inventory, service, shipping, and other charge items — and the included types can be customized for your account. Item data can include:
  • SKU, name, description, and NetSuite record type
  • Base and transaction units of measure
  • Weight and weight unit
  • Case, carton, each, and pallet packaging relationships
  • Cases per pallet (including TI × HI calculations)
  • Temperature ranges for refrigerated products
  • Lot numbers and expiration dates
The packaging relationships and cases per pallet become each SKU’s packaging hierarchy, which drives pallet counts.

​
Addresses and Facilities

Addresses are often the most account-specific part of a NetSuite setup. Owlery resolves facilities from whichever source your account uses:
  • The shipping address on the order itself
  • A NetSuite Location record
  • A vendor or customer address-book entry
  • A custom body field
  • A <br>-delimited address in a custom field
  • A linked custom location record
Different sources can apply to sales, purchase, and transfer orders. If the preferred source is missing, Owlery falls back through configured alternatives while preserving facility identity. Invalid addresses are flagged for review.

​
Selection and Filtering

Not every NetSuite record needs to come into Owlery. You choose which orders come in on the Import Rules tab: order types, ship methods, and rules on order number, status, customer, location, and more. See Import Rules and the Configuration Reference.

​
Reliability

Owlery paces its requests to stay within NetSuite’s limits, waits and retries when NetSuite is busy, and keeps split orders linked across syncs. If you need a transaction your filters skip, an authorized user can import it by its number.
Owlery monitors sync health continuously. If something breaks — a permission change, a NetSuite update, an API hiccup — we catch it and resolve it before your team needs to get involved.