You don’t configure these yourself. Owlery sets up and maintains all configuration. This page is a reference so you can see what’s available and have informed conversations with our team.
Configuration options
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. Owlery validates that every configured destination belongs to the same organization family. Incremental synchronization checks the complete organization family so child-organization activity is never missed. You can also connect multiple NetSuite accounts when separate credentials or account boundaries are the better fit.Lots, units, and packaging
Owlery resolves the transaction unit against the item’s NetSuite Units Type record. When NetSuite returns an unavailable or unsupported unit, Owlery preserves the line using a safe default and reports the condition 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