A wholesale NetSuite implementation should be designed around the complete movement of an order: customer demand, stock commitment, replenishment, warehouse execution, invoicing and collection. The useful starting point is a representative order with an exception, followed all the way into the accounts. A feature list alone will leave critical handoffs undecided.
For the COO and finance sponsor, the objective is to agree who owns each decision and how the business will prove that quantities, customer promises and financial results agree. Start with the highest-volume flow, then add the flows with the greatest operational or financial risk.
Draw a simple lifecycle during discovery:
Customer order → availability decision → purchase or stock allocation → receipt and putaway → pick and shipment → invoice → customer payment → return if required.
Under each stage, record the responsible team, originating system, required approval and evidence of completion. Separate the customer's requested date from the date the warehouse can ship. Identify which employee can approve a substitution, a partial shipment or a price exception. These decisions must survive a busy trading day, when the original salesperson is unavailable.
Stocked goods, drop shipments and special orders deserve separate scenarios. Do not assume the same receipt, costing and fulfillment events apply to all three. Ask procurement and finance to demonstrate how today's process handles goods purchased specifically for a customer and any supplier invoice that arrives before the physical shipment.
Create a representative item set containing a fast-moving stock item, a slow mover, a kit or assembly if applicable, and a tracked item where traceability matters. Decide whether customer and supplier item codes are aliases or genuinely different products. A duplicated item master can make the same stock appear unavailable to one sales channel and available to another.
NetSuite provides separate inventory, assembly, lot-numbered and serialized item types. Their feature prerequisites differ, so select the record design before loading opening stock.
For every physical site, ask who owns the goods and whether the location is a warehouse, returns area, supplier site or third-party facility. Do not create a new location for every shelf. Warehouse subdivisions and legal ownership answer different questions. Include goods in transit, rejected receipts and consignment arrangements in the design discussion, with accounting review where ownership is uncertain.
Define purchase, sales and stock units alongside conversion evidence. A supplier's carton might contain 24 pieces while a customer orders a pack of six. NetSuite's Multiple Units of Measure uses units types and base conversions; defaults can differ by transaction. Put the conversion on a signed mapping sheet and test both quantity and price interpretation.
Distribution pricing often includes negotiated customer rates, volume breaks, freight rules and promotional exceptions. Capture the source of each rule, effective dates and override authority. A sales order that imports successfully can still be commercially wrong.
Write down the evidence required before an order becomes releasable. Examples include credit clearance, customer purchase-order reference, acceptable margin and complete delivery instructions. Treat these as requirements to configure and test, rather than assuming a standard approval workflow will implement the policy automatically.
Define the return path at the same time. Decide who authorizes a return, where it is received, how condition is recorded and who approves customer credit. Otherwise, the implementation can speed up outbound shipments while leaving inventory and receivables corrections in spreadsheets.
List each connected warehouse, carrier, sales channel and trading partner. For every message, name the authoritative source for item identity, order quantity, shipment status and customer price. Decide whether the warehouse confirms a physical shipment or merely acknowledges receiving an order.
Agree how users identify an order that exists in one system but not the other. The support queue should show the business reference, affected line, last successful step and action owner. A replay must not create another fulfillment or customer invoice. Ask the integration team to demonstrate this failure path during acceptance testing.
The first integrations to design are usually those that determine whether the business can accept, ship and bill an order. Sequence secondary reporting feeds afterward unless a specific reporting obligation makes them critical to opening day.
Suppose a distributor sells 30 cartons, each containing 12 units. The main warehouse can supply 20 cartons immediately; another 10 will arrive from a supplier next week. The customer permits split deliveries but expects the negotiated carton price on both invoices.
The test should establish all of the following:
These numbers are illustrative. The pass condition is a documented match between the commercial agreement, physical quantities and accounting treatment, including taxes and freight as configured.
Before approving build, confirm the order types, item identities, units, location ownership, price rules, credit controls, partial-delivery policy, returns disposition and interface owners. Before approving cutover, add opening inventory reconciliation, open order status, supplier commitments and unresolved customer credits.
Assign a business owner to every unresolved decision. Record which decisions would block selling or shipping if left open. This gives the sponsor a more useful readiness view than a percentage-complete status covering unrelated configuration tasks.
Basic inventory processes may fit a small operation with straightforward locations, low process complexity and disciplined manual capture. Evaluate additional warehouse capabilities when directed execution, scanning, detailed task control or scale creates a demonstrated requirement. Test representative work under the intended role and device before selecting the final scope.
A successful distribution design produces an order journey that sales, purchasing, the warehouse and finance can all explain. Bring that journey and its exceptions to a CuriousRubik implementation discussion, so the scope can be assessed against the way your business actually trades.