Work Trucks as Bins vs Child Locations in NetSuite

When field service trucks carry inventory that technicians consume on jobs or sell directly to customers, the location hierarchy decision directly controls how NetSuite calculates reorder points, drives demand planning, and surfaces available-to-promise quantities. Setting trucks up as bins under a single warehouse location looks simpler on the surface, but it collapses the supply-demand signals that separate mobile stock from the main depot, and it creates fulfillment conflicts when a truck is physically unavailable.

Why the Hierarchy Matters for Reorder Points

Reorder points in NetSuite are defined at the item-location level, on the item record itself (Purchasing/Inventory subtab > Locations subtab). If trucks are bins under a parent location, the system sees one aggregate on-hand quantity for that location. A reorder point set on the parent triggers when total stock across the warehouse plus all trucks drops below the threshold. You lose the ability to say "reorder when the main warehouse hits 50, but each truck only needs a top-up at 10."

With child locations, each truck gets its own row on that Locations subtab, with its own reorder point and preferred stock level. The demand plan engine (MRP/Supply Chain Management) treats each location as a distinct supply node. Purchase orders and transfer orders generate against the specific location that needs stock, not a blended pool.

Demand Planning and Supply Allocation

NetSuite's demand planning (Setup > Company > Enable Features > Items & Inventory > Demand Planning) calculates projected available balance per location. Child locations show up as separate supply nodes in supply plans and on the supply planning workbench. Bins do not.

Consider this scenario: the warehouse shelves hold 100 units of a part, and Truck T-101 carries 15 more. A sales order for 110 units comes in. If the truck is a bin, the location reports 115 available, so the order can commit all 110. The shortfall only surfaces at the pick, when 10 of those units turn out to be on a truck 50 miles away. With the truck as a child location, Main Warehouse reports 100 and the gap shows up at order entry. The truck's 15 stay on their own row until a transfer order moves them.

The quantity a sales rep sees on an order line is the location's available count. If truck stock sits inside that count, every order assumes the truck is parked at the dock.

Item Availability Display

The Item Availability subtab (on the item record) and the Available to Promise (ATP) inquiry show quantities by location, not by bin. Bin-level detail sits a layer below that. The Bin Putaway Worksheet (Transactions > Inventory > Bin Putaway Worksheet) is for assigning stock to bins, not for checking what can be sold. Sales reps and customer service looking at standard availability screens will see the parent location's aggregate number. They won't know 15 units are sitting on Truck T-102 unless they drill into bin details, which most don't.

The "Truck on a Job" Conflict

This is the operational showstopper. When a truck is out on a job, its inventory is physically out of reach for other orders. The documented control for this is on the location record, under what Oracle's help calls Non-Available Inventory Settings for Locations.

• Make Inventory Available checked: on-hand stock at the location counts toward availability and can be added to orders.
• Make Inventory Available cleared: the location still tracks its on-hand quantity, but that stock is excluded from the available count, so other orders can't commit against it.

For most fleets, the right default is to clear the box on every truck location. The warehouse stays the location that promises stock to customers, and truck quantities stay visible for replenishment. The trade-off is real: if technicians bill parts straight off the truck on orders that name the truck location, those orders can't commit truck stock either. Test that flow in a sandbox before you roll it out.

This setting lives on the location record, so a bin can't be switched off on its own. Getting the same effect with bins means a SuiteScript user event script on sales order save that checks a custom "Truck Status" field and blocks allocation, which is maintenance you don't need when the truck is a location.

WMS Module Implications

If you eventually enable the WMS module (Setup > Company > Enable Features > Items & Inventory > Warehouse Management System), the distinction sharpens. WMS uses locations as the primary fulfillment unit. Mobile devices, directed putaway/pick, and wave planning all operate at the location level. Bins inside a WMS-enabled location support directed tasks, but the truck-as-bin model forces all trucks into a single WMS location. You'd lose mobile-directed picking per truck, and wave templates would treat the entire fleet as one pick zone.

Child locations map 1:1 to WMS locations. Each truck becomes a mobile warehouse with its own pick/pack/ship workflow, which is closer to how a field service fleet actually runs.

Configuration Walkthrough: Converting Bin Thinking to Location Hierarchy

If you're setting up a new instance, build the hierarchy correctly from the start:

1. Create the parent warehouse location Setup > Company > Locations > New Name: "Main Warehouse" | Make Inventory Available: ✓

2. Create each truck as a child location Same path > New > Subsidiary: [select] | Parent Location: "Main Warehouse" Name: "Truck T-101" | Make Inventory Available: cleared (see the section above) If you use Supply Planning (MRP), check Include in Supply Planning so the truck is planned as its own location.

3. Set reorder points per truck Lists > Accounting > Items > Edit [part] > Purchasing/Inventory > Locations subtab Row "Truck T-101" | Reorder Point: 5 | Preferred Stock Level: 15

4. Restock trucks with transfer orders Transactions > Inventory > Replenish Location by Transfer Order generates the transfer orders from the warehouse to each truck. Create a saved search (Transaction > Transfer Order) filtering on From Location = "Main Warehouse" and To Location = any truck location to monitor restock flow.

5. Keep inactivation for retired trucks Setup > Company > Locations > Edit > Location is Inactive is meant for locations you no longer track, such as a truck that's been sold. It is not a dispatch switch. Inactivating a parent location also inactivates its children, so don't inactivate Main Warehouse unless you mean to retire every truck under it.

When Bins Are Appropriate

Use bins inside the main warehouse for aisle/rack/shelf granularity. Use bins inside a truck if you enable WMS and want directed putaway within the truck bed (e.g., "Front Compartment," "Rear Shelf"). But the truck itself must be a location.

Bottom Line

Trucks as child locations give you:

• Per-truck reorder points and demand plans
• Location-level ATP that sales and CS can trust
• A per-location Make Inventory Available setting that keeps truck stock out of other orders
• Clean WMS migration path

Trucks as bins give you a flatter location list, but they break planning, allocation, and future scalability. The hierarchy depth is worth the extra location records.