Stock, purchasing and logistics with Oracle NetSuite

For most UK distributors, retailers and manufacturers, stock is the largest balance-sheet line that nobody can quite explain. Spreadsheets drift, the warehouse and the finance team count different things, and purchasing buys on gut feel. NetSuite inventory management is designed to close that gap: items, locations, receipts, shipments and supplier bills all post to the same system as the ledger.

This page explains how NetSuite handles stock, purchasing and logistics, what to decide before configuration starts, and where UK specifics such as VAT and cross-border movements come in.

How NetSuite organises stock, purchasing and fulfilment

NetSuite's documentation groups this under several areas. Items and Inventory covers stock setup, item records, shipping methods, barcodes and manufacturing. Customer Order Management covers order entry, fulfilment (picking and shipping) and invoicing. Purchasing and Receiving covers purchase orders, vendor records, bills and payments, purchase requisitions, approval routing and expense reports.

The practical point is that these are not separate products to stitch together. A purchase order, the goods receipt, the vendor bill and the stock valuation all refer to the same item record and the same location. The same is true on the sales side, from order to pick to invoice.

If you are still deciding whether NetSuite is the right fit, the overview of Oracle NetSuite modules shows how stock sits alongside finance, CRM and the rest.

Items, variants and item types

Everything starts with the item record. NetSuite distinguishes between item types, and the choice you make for each product drives how it is bought, stocked, sold and costed. A typical UK catalogue mixes:

• inventory items held in stock and valued;
• non-inventory items for things you resell without holding;
• assembly items built from components, which connect to manufacturing;
• service items for labour or delivery charges;
• kits or bundles sold together.

Variants such as size and colour are common for retail and ecommerce ranges. NetSuite handles these with matrix items, where a parent item carries the options and each combination becomes its own stockable child. If you sell clothing, footwear or similar lines, decide early how many attributes you really need, because every combination is something your team must count and reorder.

Clean item data is the single most valuable preparation for a stock project. Agree naming, units of measure (each, box, pallet), and whether you buy in one unit and sell in another. These choices are cheap to make before migration and painful afterwards; the NetSuite migration page covers how item data is loaded.

Warehouses, locations and bins

In NetSuite, stock is held at a location. A location can be a warehouse, a shop, a van or a third-party logistics site. Quantities, transfers and valuation are tracked per location, so a business with a depot in the Midlands and a retail outlet in Scotland sees stock by site rather than as one blurred total.

Inside a location, bins let you record where the stock physically sits, which supports directed put-away and picking. Not every business needs bins. A small trade counter often works well with locations alone; a busy distribution centre usually wants bins, and may want the separate WMS functionality described in NetSuite's guides.

For groups with entities in more than one country, NetSuite OneWorld gives each subsidiary its own legal identity, tax nexus and at least one location. That matters if, for example, a UK company and a Republic of Ireland company share a warehouse arrangement but must report separately. Read more on NetSuite in the UK.

Lots, serial numbers and traceability

Where a regulator, a customer or a recall could ask "which batch, and where did it go?", you need traceability. NetSuite supports lot-numbered items, which track batches and typically expiry, and serialised items, which track individual units.

Choose by risk and cost:

Traceability is only as good as the discipline at the dock door. If receiving staff skip the batch entry because the screen is slow, the report will be empty when you need it. This is why barcode capture, covered below, is so often paired with lot control. Sectors with strict traceability needs are discussed in the pages on food and beverage ERP and healthcare ERP.

Replenishment and demand planning

Replenishment answers two questions: when do we reorder, and how much? At the simple end, you set reorder points and preferred stock levels per item and location, then raise purchase orders from the shortage list. This is enough for many SMEs with a stable range.

For larger catalogues or seasonal demand, NetSuite Demand Planning goes further. It needs Advanced Inventory Management to be enabled, and it calculates demand plans using methods such as linear regression, moving average, seasonal average, sales forecast, or demand drawn from opportunities, quotes and orders. From that it builds supply plans that account for lead times and safety stock.

Two details are worth knowing. Demand Planning processes at most 10 000 items at a time, so very large ranges need to be segmented. And for assemblies, the supply plan reaches down through all components and raw materials across several manufacturing levels, which is where it overlaps with NetSuite manufacturing.

A sensible approach for most firms is to begin with reorder points, clean the data for a few trading cycles, and only then add forecasting once the history can be trusted.

Receiving, put-away and shipping

The receiving flow starts with an approved purchase order. When goods arrive, the warehouse records an item receipt against the order, capturing quantity, location, bin and any lot or serial numbers. When the supplier bill arrives, it is matched against the order and receipt. If quantities or prices differ, the exception is visible before payment goes out.

On the outbound side, a sales order is released for fulfilment, picked, packed and shipped, and the shipment triggers the stock reduction and, depending on your set-up, the invoice. Shipping methods and carrier options are part of the item and inventory configuration, and integrations to carriers and couriers are usually handled through connectors; see NetSuite integrations for how those links are scoped.

For UK businesses, post-Brexit trade adds paperwork to cross-border movements. Customs declarations, commodity codes and import VAT treatment should be discussed explicitly with your integrator and your accountant, because they affect how receipts and landed costs are recorded. Do not assume this is covered by default settings.

Stock counts and valuation

NetSuite supports physical inventory counts and cycle counting, so you can count a zone or a product family without halting the whole operation. Adjustments post with a reason, and the difference flows through to the ledger. This gives your finance team an audit trail that explains movements rather than a lump-sum write-off at year end.

Valuation is where inventory meets accounting. NetSuite offers costing methods such as average cost, FIFO and standard cost, and the method is set by item. Which one suits you depends on your accountancy policy and sector, so agree it with your accountant before configuration. Changing the method after you have trading history is possible but disruptive.

Because stock valuation posts to the general ledger, it feeds directly into the figures behind your VAT returns and statutory accounts. If you file under Making Tax Digital, accurate stock and purchase data reduce the manual reconciling you do at period end; the guide to Making Tax Digital and ERP explains the wider picture, and the NetSuite accounting and finance page covers the ledger side.

Purchasing and supplier management

Purchasing in NetSuite starts with the vendor record: payment terms, currency, tax treatment and contacts. From there the flow runs from purchase requisition through approval to purchase order, then receipt, bill and payment.

Features that matter most in practice:

• Requisitions and approvals. Staff request, managers approve, and buyers convert approved requests into orders. Approval routing can follow value, department or budget holder.
• Multi-currency buying. Many UK firms buy in euros or US dollars. OneWorld subsidiaries each have a base currency and can transact in local and foreign currencies, with consolidated reporting converting between them.
• Drop shipping and special orders. Where goods go straight from supplier to customer, the purchase and sales orders are linked. Confirm how your integrator would configure the accounting for these.
• Expense reports. Part of the same Purchasing and Receiving area, which keeps small spend inside the same approval discipline.

NetSuite documentation refers to SuiteProcurement for the wider vendor, purchasing and receiving guide. Whether you need that depth or the core purchasing features is something to clarify during scoping, along with the cost implications of any additional modules.

Barcodes, mobile and handheld scanning

Warehouse errors usually come from typing. Barcode scanning replaces keyboards with scans at receiving, put-away, picking and counting, which improves accuracy and speed.

NetSuite's item and inventory documentation includes barcodes, and the wider guide catalogue includes a WMS guide and NetSuite for mobile. For production floors, the Advanced Manufacturing SuiteApp is documented alongside Manufacturing Mobile, which supports data capture with mobile scanners.

Ask your integrator to demonstrate the exact flows on a handheld you will really use. Check the following before sign-off:

1. Receiving against a purchase order, including a lot or serial entry.
2. Picking in sequence by bin.
3. A cycle count with an adjustment.
4. What happens when the Wi-Fi drops at the back of the warehouse.

Retail, ecommerce and point of sale

If stock also feeds a website or shops, NetSuite's Commerce documentation covers SuiteCommerce, SuiteCommerce Advanced and the older Site Builder, supporting both B2B and B2C with multiple brands, languages and currencies. For shops, NetSuite Point of Sale is documented for in-store tills. This means online and shop sales can draw on the same stock figures.

The detail depends heavily on your channel mix. A wholesaler selling on account behaves very differently from a retailer with a high street presence. The pages on wholesale and distribution ERP and ecommerce ERP go deeper on each model.

What to settle before the project starts

Most stock projects go wrong in preparation, not in software. Before you brief an integrator, work through these questions:

Bring answers to these to your first conversation and the scoping will be faster and more honest. The implementation guide shows how this fits within the wider project plan, and choosing a NetSuite partner helps you compare proposals.

Next step

If you want a NetSuite integrator who has handled stock-heavy projects in your sector, our free service can match you with a suitable one. We do not carry out the project ourselves and we are not affiliated with Oracle; the integrator you meet scopes and delivers the work. How the matching works explains what happens after you submit your request.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.