> ## 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. # Configuration Reference > The full set of configuration options Owlery supports for NetSuite — order scope, field mapping, routing, filtering, and more. This page documents every configuration option available for the NetSuite integration. You don't need to read this to get started — Owlery reviews your account and recommends the right settings. This reference exists for teams that want to understand the full range of what's possible. **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 | Area | Available controls | | ------------------------- | ----------------------------------------------------------------------------------------------------------- | | Order scope | Enable or disable purchase, sales, and transfer-order synchronization independently | | Sync selection | Use an optional NetSuite sync flag; filter by ship method or transaction-number patterns | | Ship methods | Configure include or exclude lists; apply each rule to selected order types | | Transaction numbers | Exclude orders using starts-with, ends-with, contains, or does-not-contain rules | | Status mapping | Keep Owlery defaults or override individual NetSuite statuses by transaction type | | Pickup and delivery dates | Select standard or custom fields separately for each order type, or disable a date when it doesn't apply | | Pickup addresses | Read a standard address, custom HTML address, NetSuite Location, or vendor/customer address-book entry | | Address fallback | Fall back through order, location, entity, and custom-location data when the preferred source is incomplete | | Classification routing | Map a classification or any parent classification to parcel or freight mode | | Department routing | Map a department hierarchy to parcel or freight mode, optionally by order type | | Subsidiary routing | Route records from one connection into the correct child organization using the order subsidiary | | Sales channel mapping | Read a sales channel from the order or linked customer and map it to GL codes | | SKU mapping | Use the NetSuite item SKU or override it with a configured transaction-line field | | Notes | Choose the body and line fields used for operational and BOL instructions | | Item types | Use Owlery's default item set or choose the exact NetSuite record types to include | | Facility identity | Control whether the NetSuite Location ID is used as the stable facility source ID | | Weight and packaging | Read weight from item records; build configurable packaging relationships | | PO splitting | Split one PO into stable child shipments using configured quantity fields on each line | | Landed cost | Select the NetSuite cost category; allocate freight by weight, quantity, or line value | | Write-back strategy | Enable individual fulfillment, receipt, load ID, delivery date, and freight-booked actions | | Write-back triggers | Trigger by load event, order event, order type, or order tag | | Lot behavior | Use source lot assignments, warehouse lot data, NetSuite auto-assignment, or explicit inventory detail | ## 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 This distinction matters because accounts with Inventory Status enabled can require different fulfillment behavior from accounts using lot tracking without Inventory Status. ## Authentication and permissions Owlery authenticates with NetSuite token-based OAuth 1.0 using the five values you generate during setup. [Connecting NetSuite](/shippers/netsuite/connect) covers the credentials, the recommended integration role, and how permissions are scoped to the record types and write-back actions you enable.