Why Inbound Shipments Matter

Many businesses that buy stock from overseas suppliers use inbound shipments in NetSuite. Rather than tracking each purchase order on its own, an inbound shipment groups the lines that are physically travelling together, such as a container or a consolidated delivery. That container might carry stock from several purchase orders, bound for more than one location.

It is a much better match for how goods actually arrive. When the container lands, the warehouse receives it as a single shipment, not as a pile of separate POs.

The Problem: The API Can't Receipt Them

This is where integrations run into trouble. When your warehouse or 3PL confirms what has arrived, the natural next step is to receipt that shipment in NetSuite automatically.

NetSuite's API does not support receipting inbound shipments. You can read them and you can update them, but you can't receive them.

You can't work around it by receipting the purchase orders either. Once a PO is linked to an inbound shipment, NetSuite won't let you receipt it through the API, because the shipment is expected to handle it. The receipt is blocked at both ends.

That leaves businesses with two unappealing options:

• Receipt manually. Someone re-keys the warehouse's confirmation into NetSuite by hand. It is slow, error-prone and does not scale with volume.
• Avoid inbound shipments altogether. Keeping POs off inbound shipments means they can be receipted over the API, but it gives up the visibility that made inbound shipments worth using in the first place.

None of these is a good outcome. The whole point of an integration is that the warehouse and the ERP agree without anyone stepping in.

Our Solution

CommerceStream has built a NetSuite extension that adds the missing piece: the ability to receipt inbound shipments over the API. It installs into your NetSuite account and gives your integration a simple endpoint to call whenever goods arrive.

It handles the situations that come up in real warehouses:

• Full and partial receipts. Receive everything that was expected, or only what turned up, and leave the rest open for a later delivery.
• Multiple purchase orders. One shipment containing lines from several POs is receipted in a single call.
• Multiple locations. Lines are received into the correct location without extra work in the flow.
• Repeated items. The same SKU appearing on several lines, or across several POs, is matched accurately line by line.
• Header fields. Standard receipt details can be set as part of the same request.

The result is a standard item receipt in NetSuite, linked to the inbound shipment, exactly as if a user had received it in the UI.

How It Fits Your Integration

The extension is designed to slot straight into an existing integration. If you are already using Patchworks to connect NetSuite with a warehouse management system or 3PL, the receipt step becomes another call in your process flow. The warehouse confirms a delivery, the flow passes the received quantities to NetSuite, and the inbound shipment is receipted, with no manual step in between.

Clear success and error responses mean failed receipts are surfaced in your flow logs, so they can be retried or investigated instead of being missed.

Get Inbound Shipments Receipting Automatically

If inbound shipments are holding back your NetSuite integration, or your team is still receipting containers by hand, CommerceStream can help. Get in touch and we'll talk through how the extension fits your warehouse process and get it running in your account.