When an inbound shipment arrives with fewer goods than expected, we should record the actual receipt first and close the inbound shipment only after deciding what happens to the remaining quantity. To close a partially received inbound shipment in NetSuite, open the inbound shipment record, verify the related item receipt reflects the quantities physically received, document the shortage or exception, and use the record’s close action or closed status to end the shipment. The remaining quantity should not be treated as received. If the missing units are still expected, create or retain a separate receiving plan, purchase order line, or replacement shipment rather than changing the receipt to match the original expectation.
This distinction matters because NetSuite tracks several related records at different stages. The inbound shipment represents goods moving toward your warehouse, the item receipt records what physically arrived, and the purchase order represents what your organization agreed to buy. Closing the inbound shipment ends the logistics event. It does not automatically receive missing inventory, erase the purchase order balance, or create a new shipment for the outstanding quantity.
Why close a partially received inbound shipment in NetSuite?
A partially received inbound shipment should be closed when the original shipment event is complete, even if the supplier did not send every expected unit. Leaving the record open indefinitely makes the shipment pipeline unreliable and creates confusion for purchasing, warehouse operations, and finance.
An open inbound shipment can continue to appear as an outstanding receipt even when the carrier has delivered the final available carton. That affects inbound visibility, receiving queues, expected delivery reporting, and exception management. It also makes it harder to distinguish a genuine late shipment from a shipment that arrived short.
Closing the record is appropriate when:
The carrier has delivered all cartons associated with the shipment.
The warehouse has completed its receiving count.
The unreceived quantity is confirmed as short, damaged, canceled, or otherwise excluded from this shipment.
A separate process exists for the remaining units, such as a backorder, replacement shipment, or purchase order follow-up.
Closing is not appropriate simply because a user wants the record removed from an open list. If inventory is still in transit or the warehouse has not completed its count, closing the inbound shipment hides an operational exception rather than resolving it.
For broader integration design, our NetSuite integration platform services cover the API, middleware, and workflow controls that keep inbound, fulfillment, and inventory records synchronized.
What is the difference between an inbound shipment and an item receipt?
The inbound shipment and item receipt serve different purposes, so closing one does not replace the other.
| NetSuite record | Primary purpose | Quantity it should represent | What closing or saving it does |
|---|---|---|---|
| Inbound Shipment | Tracks an expected shipment in transit | Planned shipment quantities and shipment-level logistics | Ends or completes the shipment tracking event |
| Item Receipt | Records goods physically received | Actual quantities accepted into inventory | Updates received inventory and purchase order receipt status |
| Purchase Order | Records the procurement commitment | Ordered quantities | Remains open for unreceived quantities unless separately closed or canceled |
The item receipt is the inventory record. If 80 units were expected and only 65 arrived, the item receipt should show 65 accepted units, subject to your receiving and inspection rules. The inbound shipment should retain enough information to show that 15 units were not received as part of that shipment.
This is the most important control in a partial receipt workflow: do not increase the item receipt quantity to make the inbound shipment appear complete. That creates inventory that does not exist and can produce incorrect available-to-promise quantities, valuation, replenishment decisions, and vendor balances.
The purchase order requires a separate decision. If the supplier will send the remaining 15 units later, the purchase order should remain open for that quantity, or the business should create the appropriate follow-up transaction. If the supplier confirms that the 15 units will never ship, purchasing may close or cancel the outstanding line based on internal policy.
How to close partially received inbound shipments in NetSuite
The exact buttons and field names depend on your NetSuite account configuration, permissions, workflows, and enabled features. The following process uses the standard record relationship and provides a safe control sequence.
1. Confirm the shipment’s expected quantity
Open the inbound shipment record and review the item sublist before changing its status. Compare the expected quantity with the quantity received, the quantity still outstanding, and any quantities already associated with item receipts.
Check the shipment number, purchase order, vendor, location, expected delivery date, and item lines. If the shipment includes multiple purchase orders or locations, review each line separately. A shipment can be partially received because one item was short, one carton was damaged, or one portion was routed to a different location.
Do not rely only on the shipment header status. A header such as “Partially Received” does not explain whether the difference is a supplier shortage, an unprocessed receipt, or a receiving error. The line-level quantities and related item receipts provide the useful evidence.
2. Post the actual item receipt
Create or open the related item receipt and enter only the quantity physically received and accepted. If your warehouse uses inspection or quarantine procedures, follow the account’s established treatment for damaged, rejected, or restricted goods.
For example, if the inbound shipment expected 120 units and the warehouse accepted 95, the item receipt should record 95. The remaining 25 should stay outside on-hand inventory unless they are later received through a valid transaction.
Validate the receiving location, bins, lot numbers, serial numbers, inventory status, and units of measure. Quantity accuracy alone is not enough. A receipt posted to the wrong location or inventory status can still make availability appear correct at the company level while making warehouse-level availability wrong.
If the item receipt already exists, review it before creating another one. Duplicate receipts are a common source of inflated inventory, particularly when a carrier integration, warehouse system, or manual receiving process sends the same event more than once.
3. Reconcile the remaining quantity
After saving the item receipt, calculate the difference between the expected quantity and the total quantity received across all item receipts tied to the shipment.
A simple reconciliation is:
Expected quantity minus total received quantity equals remaining quantity
The result should be classified before the inbound shipment is closed. The remaining units generally fall into one of these categories:
| Remaining quantity status | Appropriate treatment |
|---|---|
| Still in transit | Keep the shipment open or track the later movement separately |
| Supplier short shipment | Close the shipment with an exception note and follow up with purchasing |
| Damaged or rejected | Record the receiving disposition and handle replacement, credit, or return |
| Canceled before shipment | Update the purchasing process rather than receiving the units |
| Unclear discrepancy | Hold closure until warehouse and purchasing records agree |
The classification should be recorded in a memo, custom field, workflow action, or supporting document according to your governance standards. A closed record without an explanation forces the next person to reconstruct the reason from emails and carrier records.
4. Review related purchase order lines
A partially received inbound shipment does not necessarily mean the purchase order should be closed. Review the purchase order line to determine whether the outstanding quantity is still expected.
If the supplier will send the remaining quantity in a later shipment, keep the procurement commitment open and associate the later receipt with the correct transaction. If the remaining quantity is canceled or written off, use the approved purchasing process to reduce or close the balance.
This separation protects the three different facts in NetSuite:
What was ordered.
What was assigned to the original inbound shipment.
What was physically received.
Combining these facts into one quantity makes later reconciliation difficult. It also obscures whether a vendor owes goods, a warehouse missed a receipt, or a buyer approved a shortage.
5. Close the inbound shipment record
Once the physical receipt is reconciled and the remaining quantity has a documented disposition, edit the inbound shipment record and use the available close action or closed status.
Depending on the account, the close control may appear as a button, status selection, checkbox, workflow action, or custom form field. Some organizations also use approval workflows or scripts that prevent closure until required exception fields are completed.
Before saving, confirm that the record still identifies the correct shipment, vendor, location, and receipt history. Add a concise internal note that states the expected quantity, received quantity, remaining quantity, and reason for closure. Avoid writing only “closed short,” because that phrase does not identify whether the supplier, carrier, or warehouse caused the difference.
If the account does not expose a standard close action, do not force the status through an unsupported import or script. First confirm the enabled inbound shipment features and role permissions. A NetSuite administrator should inspect the form, workflow, and record permissions before introducing automation.
6. Verify downstream records and reports
After closing the inbound shipment, check the item receipt, purchase order, inventory balance, receiving queue, and any connected warehouse or ecommerce system. The objective is to confirm that closure changed the shipment tracking state without creating inventory for the missing quantity.
A practical verification checks:
The item receipt contains only accepted units.
The purchase order shows the correct open, received, canceled, or backordered quantity.
Inventory is available in the correct location and status.
The inbound shipment no longer appears as an unresolved receipt.
Exception notes or supporting documents are accessible to purchasing and finance.
Any integration did not create a second item receipt or overwrite the original quantity.
For automated environments, review the integration execution log and record audit trail. NetSuite integrations using SuiteTalk REST, SuiteTalk SOAP, middleware, or custom SuiteScript should use an external reference or idempotency control so a retry does not create a duplicate receipt.
What should happen to the unreceived quantity?
The missing quantity should follow the business outcome, not a generic “close” rule.
If the items are still traveling under a different tracking number, keep the original shipment open if it remains the correct operational record. If the shipment has been split into a later wave, create or maintain a separate inbound shipment structure that gives the later units their own expected date and tracking details.
If the supplier confirms a short shipment, close the original inbound shipment with the shortage documented. Purchasing can then request a credit, replacement, or revised delivery commitment. The item receipt should not be changed to show units that never arrived.
If goods were damaged, the receipt and inventory disposition should reflect your inspection policy. Some businesses reject damaged goods entirely, while others receive them into a restricted inventory status pending review. The correct treatment depends on the item type, accounting rules, and warehouse controls, but the record should make the physical outcome clear.
If the missing quantity was canceled, update the purchase order through the approved purchasing process. Closing the inbound shipment alone does not reliably communicate that the vendor obligation has ended.
Common mistakes when closing partial inbound receipts
The most damaging mistake is treating shipment closure as a substitute for receiving. Closure changes the lifecycle of the inbound shipment, while the item receipt changes inventory. They are related actions, not interchangeable ones.
Another mistake is closing at the header level without reviewing item lines. A shipment containing ten items might be complete for nine lines and short for one. A header-only review can hide the discrepancy and make later vendor reconciliation unnecessarily difficult.
Teams also create problems by reopening and editing a posted item receipt to make historical quantities match a packing slip. If the physical count was wrong, correct it through the appropriate NetSuite adjustment, reversal, or receiving procedure. Do not silently overwrite the audit trail.
Integration timing creates a separate risk. A warehouse or carrier system might send a receipt after a user has manually closed the inbound shipment. The integration should have a defined behavior for late events, such as rejecting them for review, applying them to a later shipment, or routing them into an exception queue. It should not blindly recreate the closed shipment or post an unapproved quantity.
Finally, avoid using custom statuses that look complete but do not drive a consistent workflow. A status named “Closed Short” is useful only if users know what it means, required fields capture the reason, and reports distinguish it from “Received Complete.”
How to prevent recurring partial receipt errors
Start with a receiving policy that defines when an inbound shipment remains open and when it can close short. The policy should address split shipments, supplier shortages, damaged goods, substitutions, canceled quantities, and late receipts.
Then configure NetSuite to make the policy visible at the point of action. Required exception reasons, role-based permissions, saved searches for open partial receipts, and workflow validation are more effective than relying on training alone. A saved search that compares expected and received quantities can identify records that have remained partially received beyond the expected delivery date.
For connected warehouse or ecommerce environments, establish ownership for each event. The warehouse system should report physical receipt facts, NetSuite should remain the system of record for inventory and accounting, and the integration should preserve transaction identifiers and processing outcomes. This division prevents two systems from independently creating competing receipts.
If your process includes multiple warehouses, third-party logistics providers, or several sales channels, document how location, inventory status, lot data, and shipment references move between systems. Our NetSuite integration guidance discusses the broader controls needed for split shipments, backorders, warehouse communication, and shipment documentation.
Is it safe to close an inbound shipment before all units arrive?
Yes, closing a partially received inbound shipment is safe when the original shipment is finished and the unreceived quantity has a documented disposition. It is not safe when units are still expected under the same shipment and no replacement tracking or follow-up process exists.
The decision should be based on physical logistics, not simply on whether the record is inconvenient to leave open. When in doubt, preserve the shipment as open until the receiving and purchasing teams agree on the outstanding quantity.
Conclusion
Closing a partially received inbound shipment in NetSuite is a reconciliation decision, not a shortcut for receiving inventory. Record the actual item receipt, preserve the correct open quantity on the purchase order, classify the shortage or exception, close the inbound shipment only when its logistics event is complete, and verify every downstream record.
This approach keeps inventory accurate while giving purchasing, receiving, finance, and customer service a reliable explanation for the difference. It also creates a stronger foundation for automation, because integrations can distinguish a legitimate short shipment from a missing receipt or duplicate transaction.
