NetSuite Sales Order: setup, key fields & best practice

Setup

• Enable the relevant features (Setup > Company > Enable Features): standard Sales Orders need the transaction enabled; Advanced Shipping and Pick/Pack/Ship affect the fulfilment flow.
• Confirm the order-to-cash form, statuses and approval routing match the client's process before loading any orders.

Key fields

• Customer (Entity). The buyer. Drives default currency, terms, pricing and which subsidiary the order belongs to in OneWorld.
• Subsidiary. In OneWorld, sets the legal entity, base currency and tax treatment. Must match the customer's subsidiary and be correct before lines are entered.
• Items sublist. The lines being sold — item, quantity, rate, and tax/nexus-driven tax code. Pricing pulls from the item and the customer's price level.
• Status. Tracks the order through Pending Approval, Pending Fulfilment, Partially Fulfilled, Billed and Closed — the backbone of the order-to-cash flow.
• Location. Drives inventory commitment and fulfilment, and is required when Multi-Location Inventory is on.

Best practice

• Lock down the subsidiary and currency on the form so users cannot create cross-subsidiary orders by accident.
• Use approval routing for orders above a threshold rather than manual checking, and keep the status workflow standard so reporting stays clean.

Common errors

• SSS_MISSING_REQD_ARGUMENT when scripting against sales orders
• INSUFFICIENT_PERMISSION creating orders under a restricted role

Frequently asked questions

Can a sales order span two subsidiaries?

No. A sales order belongs to one subsidiary. Cross-entity sales are handled with intercompany orders, not a single multi-subsidiary order.