NetSuite Advanced Inventory Management: Complete Module Guide

NetSuite Advanced Inventory Management is a licensed module that extends the platform’s base inventory capabilities with four tightly integrated feature sets: lot and serial number traceability, bin-level location management, multi-location stock control, and landed cost allocation. For warehouse managers operating across multiple facilities, or operations directors who need a full cost trail from purchase order to COGS, these features close gaps that base NetSuite simply cannot address. This guide covers every major configuration area in netsuite advanced inventory management: what each feature does, how to turn it on, and where operators most commonly get it wrong. Whether you are evaluating the module for the first time or troubleshooting a live deployment, the sections below give you the technical detail needed to make it work reliably.

What Is the NetSuite Advanced Inventory Management Module?

NetSuite ships with a standard inventory engine that handles item records, stock-on-hand quantities, basic reorder points, and purchase-to-receipt workflows. The netsuite advanced inventory management module layers additional capability on top of that foundation without replacing it. It is a separately licensed add-on, meaning your account must have it provisioned before any of its features appear in the UI.

Base Inventory vs Advanced Inventory

The distinction matters for scoping both the license cost and the configuration effort. Base inventory handles items, quantities, and locations at the top level. Advanced Inventory Management adds the following on top:

Who Needs It

The module is most relevant for three operator profiles. First, manufacturers and distributors handling perishable or regulated goods where lot traceability is a legal or customer requirement. Second, warehouse operations with multiple physical zones or rack systems where item-level location is not precise enough for efficient picking. Third, importers and distributors who purchase goods on shipped terms and need actual landed cost, freight, duties, insurance, reflected in unit cost and COGS rather than estimated or written off as overhead. All three profiles run on NetSuite ERP as their core platform, with Advanced Inventory as the layer that brings warehouse-grade precision to the base system.

Licensing Notes

Advanced Inventory Management is included in some NetSuite editions and priced separately in others. As of 2025, it is bundled with NetSuite Manufacturing and available as a paid add-on for Distribution and mid-market editions. Confirm your current license by navigating to Setup > Company > Enable Features and looking for the Inventory section. If the Advanced Inventory tab is not visible, raise a case with your NetSuite account manager or reseller.

Enabling the Module: SuiteAdmin Steps and Prerequisites

Activating netsuite advanced inventory management requires SuiteAdmin access. The process takes under ten minutes, but several prerequisite settings must be in place before the primary switch is flipped.

Prerequisites

• Multi-Location Inventory must be enabled first (Setup > Company > Enable Features > Items and Inventory tab).
• At least one subsidiary (OneWorld accounts) or the parent company (non-OneWorld) must be set as an inventory-tracking entity.
• Item records must use inventory-tracked item types: Inventory Item, Lot Numbered Inventory Item, or Serialized Inventory Item.
• At least one Location record must exist and be marked as a Store Location or Warehouse for bin features to apply.

Activation Steps

1. Go to Setup > Company > Enable Features.
2. Click the Items and Inventory tab.
3. Check the box for Advanced Inventory Management. If this checkbox is greyed out, Multi-Location Inventory is not yet enabled. Enable it first and save before returning.
4. Optionally, enable Bins, Lot Tracking, Serialized Inventory, and Landed Cost individually on the same tab. Each can be toggled independently.
5. Click Save. NetSuite will run a brief background process to register the feature against your account.

After saving, new menu items appear under Inventory > Setup and new fields become visible on item records, location records, and transaction forms. No data is changed on existing records; the fields simply become available for population going forward.

Lot and Serial Number Tracking

Lot tracking and serial number tracking are related but distinct. Lots group multiple units under a single identifier (a production batch, a vendor lot code). Serial numbers identify individual units. NetSuite handles both through its netsuite lot tracking framework, which ties to item receipts, inventory adjustments, fulfillments, and returns.

Item Record Setup

To assign lot tracking to an item, the item type must be changed to Lot Numbered Inventory Item on the item record. This cannot be done on an existing Inventory Item type once transactions exist. A new item record must be created and inventory transferred over. Plan item types carefully before going live to avoid this migration step.

For serial number tracking, use the Serialized Inventory Item type. Each unit receives a unique serial number at the point of receipt or inventory adjustment, and that number travels with the unit through every subsequent transaction.

Lot Assignment at Receipt

When an item receipt is created against a purchase order for a lot-tracked item, NetSuite presents a Lot/Serial Number sublist on the receipt. The operator enters the lot number (typically from the vendor packing slip or Certificate of Analysis), the quantity for that lot, and optionally an expiration date. Multiple lots can be received on a single item receipt by adding rows to the sublist.

Expiration dates feed into NetSuite’s FEFO (First Expiry, First Out) picking logic when bins are also enabled, which is covered in the next section.

Traceability Reports

Once lots are assigned, NetSuite provides several native reports for forward and backward traceability:

• Lot/Serial Number Transaction Report: Shows every transaction: receipts, transfers, fulfillments, adjustments, touching a specific lot number.
• Inventory Lot Report: Shows current on-hand quantities by lot across locations.
• Expiration Date Report: Flags lots approaching or past their expiration date, filterable by item or location.

These reports are accessible under Reports > Inventory and can be saved as custom searches for daily operational use. For FDA-regulated industries or ISO-certified operations, these reports are typically the primary documentation for product recall or audit events.

Bin and Location Management

The netsuite bin management feature subdivides a warehouse location into discrete storage zones: aisles, racks, shelves, or any physical unit the operation uses. Once bins are enabled, every put-away, pick, transfer, and adjustment can target a specific bin rather than just a location.

Enabling Bins

Bins is a sub-feature within Advanced Inventory. Enable it at Setup > Company > Enable Features > Items and Inventory > Bins. After enabling, each Location record gains a Bins subtab where individual bin records are created.

Bin Record Structure

Each bin belongs to one location. The bin record holds the bin name (typically an alphanumeric code matching physical signage, e.g., A-01-03 for Aisle A, Rack 01, Shelf 03), a memo field, and a Preferred Bin flag. The Preferred Bin designation tells NetSuite where to default putaway and picking for an item when no bin transfer or putaway rule specifies otherwise.

Putaway Rules

Putaway rules define where received inventory should be directed within a location. Rules are configured at Inventory > Bin Putaway Rules and can be filtered by item, item class, location, or a combination. The rule specifies a target bin and a priority. When multiple rules match, the highest-priority rule wins.

Common putaway rule patterns include directing hazardous items to a dedicated bin zone, routing fast-moving SKUs to forward pick bins near the dispatch area, and placing overstock in bulk storage bins until replenishment pulls move it forward.

Pick, Pack, and Bin Transfers

On item fulfillment records, the Pick subtab shows required bin picks line by line. NetSuite suggests the bin based on available quantity and the preferred bin setting, but operators can override per line. When Commitment is enabled, NetSuite locks inventory in a bin from the point of order creation, reducing the risk of the same unit being double-allocated.

Bin-to-bin transfers within a location are handled via Inventory > Bin Transfer. This is distinct from location-to-location transfers, which are inter-location transfers covered in the next section. A bin transfer does not change the location on the inventory record; only the bin assignment changes.

Multi-Location Inventory

NetSuite multi-location inventory allows a single item to hold independent quantity records, reorder points, preferred vendors, and costing data at each location. This is the foundation of netsuite multi location inventory management, and it operates whether or not bins are enabled.

Location Setup

Locations are created at Setup > Company > Locations. Each location record carries a type (Store, Warehouse, etc.), a subsidiary assignment (in OneWorld accounts), address details, and inventory-specific settings including Use Bins, Allow Store Pickup, and Include in Supply Planning.

For wholesale distribution workflows in NetSuite, multi-location setup typically mirrors the physical distribution network: a central distribution center as the primary location, regional warehouses as secondary locations, and possibly retail or 3PL locations where inventory is held on consignment or managed separately.

Location-Level Reorder Points

Once Multi-Location Inventory is enabled, the item record’s Purchasing/Inventory subtab displays a Location sublist. Each row holds that location’s reorder point, preferred stock level, and preferred vendor. A purchase order generated by NetSuite’s replenishment run will reference the location-specific reorder point rather than a global average, making replenishment accurate to each node in the network.

Inter-Location Transfers

Stock movement between locations is handled via Inventory Transfer records (Transactions > Inventory > Inventory Transfer). The transfer decrements the source location and increments the destination location. In transit quantities are optionally tracked using a dedicated In Transit location, which gives visibility into stock that has left the source but not yet arrived at the destination.

For inventory management best practices, configuring an In Transit location is strongly recommended for any inter-location move that takes more than a few hours, particularly for transfers between geographically separate warehouses or cross-border movements where customs clearance introduces delays.

Location-Level Reporting

NetSuite’s standard Inventory by Location report breaks down on-hand, committed, available, and on-order quantities per item per location. This report is a primary tool for identifying imbalances, locations holding excess stock while others are below reorder point, and initiating manual or rule-driven transfers to rebalance.

Landed Cost

Landed cost is the mechanism by which NetSuite allocates freight, customs duties, insurance, and other procurement expenses to the item cost of received goods rather than posting them as period expenses. Accurate landed cost is critical for gross margin reporting when purchase terms are FOB origin or CIF: any time the buyer bears freight and duty costs.

Landed Cost Categories

Landed cost categories are configured at Setup > Accounting > Landed Cost Categories. Each category represents a type of charge: Freight, Duty, Insurance, Handling, etc. Each category is mapped to a GL account. When a landed cost is allocated, NetSuite debits the inventory asset account and credits the GL account specified on the category, reflecting the transfer of expense from the accrual account to the item’s cost.

Entering Landed Costs

Landed costs are entered on item receipts or via standalone Landed Cost records created after the receipt. On the item receipt, a Landed Cost subtab accepts one or more charge lines, each referencing a category, an amount, and an allocation method. Multiple charge types can be allocated in a single receipt: freight and duty in one step, for example.

Allocation Methods

NetSuite supports four native allocation methods for netsuite landed cost:

Choosing the wrong method creates cost distortions. Allocating freight by quantity when the shipment contains both small hardware components and heavy steel assemblies will over-cost the small items and under-cost the heavy ones. Weight-based allocation corrects this, but it requires accurate weight data on every item record before the first receipt is processed.

Impact on COGS

Once landed costs are allocated and the receipt saved, the additional cost is folded into the item’s average cost (for average cost items) or layer cost (for FIFO/LIFO items). When those units are subsequently fulfilled and invoiced, the COGS journal entry uses the fully landed unit cost, not just the purchase price. This means gross margin figures in P&L reports reflect true acquisition cost rather than an understated purchase price.

Demand-Based Replenishment

The Advanced Inventory module includes a replenishment engine based on min/max rules and reorder points. When NetSuite’s Supply Planning run executes, it compares available quantity at each location against the location-specific reorder point, calculates the shortfall, and generates either purchase orders or work orders to cover demand.

For operations that need forward-looking demand signals beyond simple reorder points, seasonal adjustments, sales velocity analysis, or supplier lead time modeling, the replenishment module connects to NetSuite’s broader inventory forecasting and replenishment capabilities. That guide covers how to configure planning horizons, demand sources, and safety stock calculations in detail.

Within Advanced Inventory specifically, the key replenishment configuration points are the per-location reorder point and preferred stock level fields on the item record, and the Supply Planning preference to include or exclude specific locations from automated planning runs.

Advanced Inventory vs NetSuite WMS: When to Upgrade

A question that comes up consistently in larger deployments is where the netsuite advanced inventory module ends and NetSuite WMS begins. They are not the same product, and the distinction has significant cost and configuration implications.

Advanced Inventory is appropriate for operations where warehouse staff work from desktop or tablet screens, pick volumes are manageable without wave optimization, and the primary requirement is accurate stock visibility with lot and bin resolution. For manufacturing operations specifically, Advanced Inventory typically covers the full production and warehouse traceability requirement unless the plant also runs a high-volume discrete pick operation. WMS becomes necessary when the operation processes hundreds of orders per shift, requires RF scanner guns on the floor, needs cartonization for multi-item shipments, or runs cycle counts as a continuous structured program rather than a periodic manual process.

The decision is not irreversible, but migrating from Advanced Inventory to WMS mid-operation requires careful data migration of bin records, open commitments, and lot assignments. Plan the transition during a low-volume period and run parallel processes for at least two weeks before fully cutting over.

Implementation Tips and Common Configuration Mistakes

After working through a range of Advanced Inventory deployments, the same configuration errors appear repeatedly. Avoiding them at the start saves weeks of cleanup.

Item Type Decisions Cannot Be Undone Mid-Stream

The most disruptive mistake is setting an item as a standard Inventory Item and then deciding mid-deployment that it needs lot tracking. NetSuite does not allow changing item type on a record that has existing transactions. The correct approach is to audit every item in scope before go-live, classify each as standard, lot-tracked, or serialized, and create records accordingly. If the business is not yet sure which items need lot tracking, err on the side of enabling it. It can be left unused with minimal overhead, but adding it retroactively requires creating a new item and transferring stock.

Preferred Bin Must Be Populated Before Receiving

If bins are enabled but no preferred bin is set on an item, NetSuite will accept the receipt but will not place the stock in a bin; it remains in a “no bin” state at the location level. This creates mismatches between location quantity and bin-level quantity that are difficult to reconcile after the fact. Run an inventory adjustment to move unassigned stock into the correct bin, and set up a preferred bin on every item record before enabling bins in a live environment.

Landed Cost Requires Weight Data Before Go-Live

If weight-based allocation will be used, the weight field on every affected item record must be populated and accurate before the first landed cost entry. A common mistake is to activate landed cost and discover midway through configuration that item weights are blank, forcing either a manual weight-entry project or a switch to quantity-based allocation that distorts costs.

Reorder Points Must Be Set at Location Level, Not Global

When multi-location inventory is enabled, the global reorder point field on the item record is overridden by location-level values in the Location sublist. Teams that set a global reorder point expecting it to apply to all locations find that NetSuite’s replenishment run ignores it once location-level rows exist. Always configure reorder points in the Location sublist when operating multiple warehouse locations.

Inter-Location Transfers Need an In-Transit Location

Without an In-Transit location, stock disappears from the source the moment a transfer is initiated and appears at the destination when the receiving step is completed. During that window, the stock is invisible in all reports. For same-day short-haul transfers, this may be acceptable. For transfers that cross days or require customs clearance, the gap creates reconciliation problems and can trigger false replenishment orders at the destination. Set up an In-Transit location at go-live and train operators to use it consistently.

Test Lot Traceability Before Go-Live

Lot traceability reports are only as complete as the transaction history feeding them. If any receipts are entered without lot numbers (possible if the field is not made mandatory), those units exist in inventory but are invisible to lot-based reports. Make the lot number field mandatory on item receipts for lot-tracked items by using a custom form or a SuiteScript field validation, and test the Lot Transaction Report against a sample receipt before declaring the go-live complete.

Frequently Asked Questions

Can I enable netsuite advanced inventory management on an existing NetSuite account without disrupting live transactions?

Yes. Enabling the module at Setup > Company > Enable Features does not alter existing item records, open transactions, or quantity on hand. It makes new fields available and activates the additional transaction types. You then configure each feature, bins, lot tracking, landed cost, incrementally and apply them to items and locations as needed. The practical risk is not data loss but incomplete configuration: enabling bins without populating preferred bin fields, for example, leaves stock in an unassigned state on new receipts.

What is the difference between netsuite lot tracking and netsuite serial number tracking?

Lot tracking assigns a single identifier to a batch of units received together: typically a production lot, vendor lot code, or date-coded batch. One lot number covers multiple units. Serial number tracking assigns a unique identifier to each individual unit. Lot tracking is standard in food, pharma, and chemical industries where batch recall is the operative compliance requirement. Serial tracking is used for electronics, high-value capital goods, and warranty management where unit-level identification is required. NetSuite handles both through the same underlying framework but uses separate item types: Lot Numbered Inventory Item vs Serialized Inventory Item.

How does netsuite landed cost affect average cost calculations?

For items using average cost as the costing method, each landed cost allocation recalculates the weighted average unit cost by adding the allocated charge amount to the total inventory value and dividing by the quantity on hand at the time of allocation. If 100 units are in stock at $10.00 each and a $200 freight charge is allocated to a receipt of 50 of those units, the average cost rises to reflect the blended value across all 150 units. Subsequent sales draw COGS at the updated average, so cost accuracy improves progressively as more landed costs are captured rather than expensed as overhead.

Does netsuite bin management support FEFO picking automatically?

NetSuite supports First Expiry, First Out picking when both bins and lot tracking are enabled and expiration dates are recorded on lot records. On item fulfillment, NetSuite suggests pick bins in expiration date order for lot-tracked items. However, this is a suggestion rather than a hard enforcement: operators can override the recommended bin and lot on the pick sublist. If strict FEFO enforcement is required, either a workflow-based validation or a switch to NetSuite WMS (which supports directed picking with enforced rules) is needed.

When should a business upgrade from netsuite advanced inventory to NetSuite WMS?

The clearest indicators are: warehouse staff need to use RF scanner guns or mobile devices rather than desktop screens for put-away and picking; order volumes require wave or batch picking to meet throughput targets; cartonization (determining which box to use based on item dimensions and weights) needs to happen automatically; or cycle count programs need to be structured as continuous task-assigned workflows rather than periodic manual counts. If none of these apply and the primary needs are lot visibility, bin-level stock tracking, and landed cost accuracy, Advanced Inventory is sufficient and meaningfully less expensive to license and implement than WMS.

NetSuite advanced inventory management covers a wide surface area: lot traceability, bin-level putaway and pick, multi-location stock control, and landed cost allocation. Each feature is independently valuable, but they compound when deployed together. A warehouse using bins and lot tracking simultaneously gains FEFO picking. Landed cost combined with multi-location inventory gives an accurate margin picture at each node in the network. The configuration work is front-loaded and requires careful item type decisions and master data discipline before go-live. Done correctly, the module eliminates the spreadsheet workarounds most growing operations rely on and creates a single auditable record from purchase order receipt through customer delivery.