Settings → Integrations. On the NetSuite card, click Settings.
You can change these in Settings. Changes save automatically and take effect on the next sync.
Import Rules
NetSuite connections have the shared Import Rules: pause sync, choose order types, and exclude orders by order number, status, customer, location, and more. NetSuite adds:
If your NetSuite account has the
custbody_owlery_sync checkbox field, only orders with the box checked sync. You control this in NetSuite, not in Owlery.
Fields & Values
If the pickup address you choose is incomplete, Owlery falls back through order, location, entity, and custom-location data, in that order.
Items
Routing & Mappings
Settings Owlery Manages
These settings depend on how your NetSuite account is built, so Owlery sets them up during onboarding.Status, Classification, and Department Rules
Owlery includes default status mappings for purchase, sales, and transfer orders. You can override any mapping when your NetSuite process interprets a standard status differently. Classification and department rules support NetSuite hierarchies. A rule can match a value directly or match one of its parent records — this lets you apply one rule to an entire branch of your NetSuite structure instead of configuring every child value individually. For example, one parent classification can identify parcel orders while all unmatched classifications remain freight orders.Subsidiaries and Multiple Organizations
A single NetSuite connection can route orders to different Owlery child organizations using the NetSuite subsidiary ID. Set this on the Routing & Mappings tab. Owlery validates that every configured destination belongs to the same organization family. Each sync checks every organization in the family, so no child organization’s orders are missed. You can also connect multiple NetSuite accounts when separate credentials or account boundaries are the better fit. If you send invoices through Ramp, map each organization to its Ramp entity as well. See subsidiary setup and verification for the steps across all three systems.Lots, Units, and Packaging
Owlery reads each line’s unit of measure from the item’s NetSuite Units Type. If NetSuite sends a unit Owlery doesn’t recognize, Owlery keeps the line, uses a safe default, and flags it for review. For lot-controlled inventory, Owlery can:- Read issue and receipt inventory numbers
- Preserve expiration dates
- Split one NetSuite line into multiple Owlery item lines when it contains multiple lots
- Recombine those item lines by original NetSuite line during write-back
- Match lots by item and location
- Send explicit inventory assignments only when the account requires them