NetSuite Inbound Shipments.
Know what's coming.
Know what it costs.
Connect purchasing, incoming inventory and landed cost so your teams work from the same picture.
(724) 816-1000 • Work directly with Jack Ring.
NetSuite / Purchasing & Inventory
NetSuite Inbound Shipments: Where Is It, and What Does It Really Cost?
A purchase order tells you what you bought. An inbound shipment helps organize how it arrives. Landed cost helps establish what those units really cost.
By Jack Ring | October 2026
Your procurement team knows what it ordered. Your warehouse knows what it received. Your accounting team knows what it paid. But who knows what is currently floating somewhere in the Pacific Ocean?
For companies buying inventory internationally, that question is more than a curiosity. It affects customer commitments, replenishment planning, warehouse staffing, cash flow and the value ultimately assigned to inventory.
I recently worked through this challenge with a company already using NetSuite for purchasing and demand planning. The purchasing process itself was not the problem. The difficulty was coordinating everything that happened after a purchase order was issued and before its goods arrived.
Containers, vessels, freight brokers, estimated arrival dates, tariffs, duties and unexpected delays were being managed across people, emails and spreadsheets. Different departments needed the same information, but each saw a different piece of the journey.
One Purchase Order. Three Containers. Two Vessels.
Imagine a company orders 1,000 units from an overseas supplier. The manufacturer cannot ship everything at once. The order is split into three containers, with the last container leaving two weeks after the first two.
First departure
First departure
Two weeks later
Illustrative example: one purchase order, 1,000 units, three container allocations and two departure schedules.
On paper, it is still one purchase order for 1,000 units. Operationally, however, the company has separate movements with different expected arrival dates, freight documentation and potentially different costs.
NetSuite's Inbound Shipment feature provides a native record for organizing purchase order quantities into incoming shipments. A shipment can bring together eligible quantities from multiple purchase orders, and purchase order quantities can be split across different inbound shipment records as appropriate.
That is an important distinction. The purchase order represents the commercial commitment. The inbound shipment represents a particular movement of goods toward receipt.
When Spreadsheets Become the Logistics System
In many companies, the logistics picture exists, just not in the ERP. Purchasing maintains a workbook of expected deliveries. A freight forwarder sends updates by email. Someone in accounting tracks brokerage invoices. Operations asks when the next container will be unloaded.
None of those people is necessarily doing anything wrong. They are filling a gap in the process.
The trouble starts when a spreadsheet becomes the only place to find the latest estimated arrival date or when landed cost support is scattered across vendor invoices, customs paperwork and someone's desktop.
Then every update requires a conversation. And every conversation introduces another opportunity for the departments to work from different information.
Inbound Shipments: The Missing Transaction Layer
Inbound Shipments can help connect purchase orders to the physical receiving process. The record gives the organization a place to maintain shipment-level information and coordinate the quantities expected to arrive together.
Depending on the company's setup and the information it chooses to maintain, that process may include:
- Grouping purchase order lines and partial quantities into an incoming shipment.
- Maintaining expected shipment and arrival dates.
- Recording shipment identifiers and relevant logistics references.
- Coordinating which goods are expected in a particular delivery.
- Receiving goods against the appropriate inbound shipment quantities.
- Providing a shared operational view through searches, reports and dashboards.
There is a practical limit worth understanding: NetSuite is not automatically tracking a ship across the ocean. Accurate statuses and arrival information still depend on updates from employees, freight forwarders, brokers or an integration designed for that purpose.
And a container is not necessarily the same thing as an inbound shipment record. The right record granularity should reflect how the company plans, tracks, receives and costs its inventory. Some businesses will organize by vessel movement; others may need more detailed container-level tracking or custom references.
Landed Cost: What Did Those Units Really Cost?
Knowing when inventory will arrive is one part of the problem. Knowing what it actually costs is another.
A supplier's invoice price rarely tells the entire story for internationally sourced goods. Depending on the transaction and the company's accounting policies, inventory cost may also include qualifying freight, import duties, tariffs, brokerage, handling and other costs necessary to bring the goods to their intended location and condition.
Consider a simple illustration:
| Cost component | Per unit |
|---|---|
| Supplier purchase price | $100.00 |
| Ocean freight | $6.00 |
| Import duties | $4.00 |
| Tariffs | $5.00 |
| Brokerage and handling | $2.00 |
| Total illustrative landed cost | $117.00 |
That $17 difference matters. It can change gross margin analysis, pricing decisions and inventory valuation. And it becomes more complicated when the same purchase order arrives in multiple shipments, each with different freight and customs charges.
NetSuite supports landed cost functionality, including capabilities associated with inbound shipments where the appropriate features and configuration are enabled. The design question is not simply whether the system can hold a freight charge. It is which costs belong to which goods, how those costs should be allocated, and when the resulting inventory value is recognized.
Allocation may be driven by an appropriate basis such as quantity, value or weight, subject to the features and methods supported by the account. A heavy, low-value item and a lightweight, high-value item should not automatically receive identical freight or duty allocations without considering the nature of the charge.
Another practical consideration is timing. Freight invoices and customs bills do not always arrive when the inventory does. A sound process needs to address estimates, actual charges, variances and the reconciliation of those amounts without creating duplicate costs.
Accounting note: Not every incidental expense is necessarily capitalizable as inventory. The company's accounting policy, applicable standards and the nature of each charge govern the treatment. Inbound Shipment and landed cost features should be tested together in the specific NetSuite account before committing to a posting design.
When Does the Inventory Actually Belong to You?
Now we get to a question that should interest the controller and CFO as much as the purchasing manager.
One supplier's contract may transfer control or risk when goods are loaded onto a vessel. Another may retain responsibility until the goods reach a specified destination. Shipping terms such as FOB, CIF and DDP are relevant, but the actual contract and applicable accounting requirements determine the appropriate treatment.
Why does this matter? Because the company may need to recognize goods as inventory while they are still in transit, even though nothing has physically arrived at its warehouse. Or the opposite may be true: goods are on the way, but the company has not yet acquired the relevant ownership rights.
Tracking a shipment is not the same thing as accounting for ownership. An inbound shipment record can improve visibility into the movement of goods, but it does not, by itself, establish that the inventory has been properly recognized on the balance sheet.
NetSuite's related ownership and in-transit accounting capabilities, where available and enabled, need to be evaluated separately from the shipment-tracking process. Finance should define the ownership events, supporting documentation, journal implications and reconciliation controls before the workflow goes live.
Demand Planning Needs Better Information
Now consider the purchasing team already using NetSuite Demand Planning. It has a purchase order for 1,000 units. But 750 units are expected next week, and the remaining 250 may not arrive for another month.
Those differences matter when someone promises inventory to a customer, plans a replenishment order or schedules work at a distribution center.
Maintaining more accurate inbound shipment records can give procurement and operations a more reliable picture of expected receipts. Searches, reporting and dashboards can make those dates and quantities visible to the people who need them.
There is an important technical distinction, though. Do not assume that enabling Inbound Shipments automatically changes native Demand Planning calculations. The relationship between shipment dates, purchase order dates, supply planning and available-to-promise behavior must be verified against the specific planning features and configuration in use.
The objective is not to promise magic. It is to put better information into a controlled business process and determine where that information should influence planning.
Enabling the Feature Is Easy. Designing the Process Is the Work.
NetSuite provides the functionality. But enabling a feature is not the same thing as implementing a process.
Before rolling out Inbound Shipments, I would want the procurement, operations and finance teams in the same room to answer a few basic questions:
- Ownership: Who creates each inbound shipment and who is responsible for keeping it current?
- Structure: Does one record represent a vessel movement, a container or another practical shipment grouping?
- Updates: Who maintains expected arrival dates, delays and broker references?
- Receiving: How will the warehouse handle shortages, overages, partial receipts and discrepancies?
- Costing: Which landed cost categories are needed, who enters them and what allocation methods apply?
- Accounting: When does ownership transfer, and how will in-transit inventory and estimated costs be reconciled?
- Planning: Which dates and quantities should drive purchasing decisions, and which NetSuite reports or processes will use them?
I'd then test a small number of representative scenarios in Sandbox: a straightforward shipment, a purchase order split across vessels, multiple purchase orders consolidated into one shipment, late landed cost invoices and a shipment with a receiving discrepancy.
That testing often reveals the details that a feature demonstration misses. The warehouse has one interpretation of a shipment. Purchasing has another. Finance has a third. The implementation succeeds when those definitions become a shared, workable process.
Your Inventory Doesn't Disappear Between the Supplier and the Warehouse
Companies spend considerable time managing purchase orders and inventory receipts. Yet the days or weeks between those transactions may represent a significant amount of inventory moving through the supply chain.
Those goods do not stop being important simply because they have not reached the warehouse.
NetSuite Inbound Shipments can help close that visibility gap. Combined with a thoughtful landed cost process and properly designed accounting controls, it can help purchasing, operations and finance work from a clearer picture of incoming inventory.
And sometimes improving an ERP environment does not require another application. It requires understanding what the existing system can already do, and designing the business process around it.
A better way forward
Still tracking incoming containers in spreadsheets?
Call me. We can work through purchasing, receiving and landed cost together, and identify a practical next step for your NetSuite environment.
You don't need a finished project plan to start the conversation.
Call Jack: (724) 816-1000 Send a message