NetSuite 3PL Integration in Australia for Wholesalers

Written by Swara | Nov 7, 2026, 4:31:00 AM

For Australian wholesale and operations leads connecting a third party warehouse to NetSuite, with GST and stock ownership clear.

Last reviewed: 7 November 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.

A NetSuite 3PL integration in Australia connects NetSuite to a third party warehouse so orders, shipments and stock stay in step. NetSuite remains the system of record for inventory value and customer orders. The 3PL picks, packs and ships, then sends confirmations back. GST on fulfillment fees and a clear BAS owner sit beside the messages.

Key takeaways

Create one NetSuite Location for each 3PL site, and keep your own warehouse as a separate location when you still pick some orders yourself.
Agree which system creates the Item Fulfillment, and which message returns tracking and shipped quantity.
Post 3PL storage and fulfillment fees as supplier bills with the right GST tax code, not as a reduction of sales.
Reconcile on hand quantity at the 3PL location at least weekly, and again before each BAS period ends.

What is a NetSuite 3PL integration in Australia?

A 3PL integration is a standing data exchange between NetSuite and a warehouse you do not operate. Sales orders (or item fulfillments) leave NetSuite so the warehouse can pick them. Shipment confirmations, tracking numbers and quantity adjustments come back. Inventory on hand at that site updates in NetSuite without someone typing counts from a spreadsheet.

It is not the same as a storefront integration. A storefront such as the one described in our NetSuite ecommerce integration in Australia guide sends customer orders in. A 3PL integration sends warehouse work out and stock truth back.

Australian wholesalers use 3PLs when national reach, peak season capacity or specialised handling matters more than owning every square metre of warehouse space. NetSuite already supports multiple locations, so the platform is ready. The design work is about ownership, messages and tax.

Write the integration goal in one sentence before you buy a connector.

Example goal one: NetSuite sends every approved Sydney 3PL sales order within five minutes.

Example goal two: stock on that location matches the 3PL on hand report every morning.

Those sentences become the acceptance test.

How do NetSuite locations map to an Australian 3PL?

Start with locations, not with middleware.

Create a Location record for each physical 3PL site (for example "Sydney 3PL" and "Melbourne 3PL").
Keep your own facility as its own Location if you still fulfil some orders there.
Put available quantity on the correct location. Do not merge 3PL stock into a single national bucket if the warehouse cannot ship from every site.
If you use bins or inventory status, agree whether the 3PL sends bin level detail or only location totals.

NetSuite values stock through its costing method on the item. The 3PL should not invent a second cost. When stock moves from your warehouse to the 3PL, use an inventory transfer between locations so quantity and value stay tied together.

For OneWorld accounts, confirm which subsidiary owns the stock at the 3PL. Mixed ownership across subsidiaries needs an intercompany design before the first transfer.

Which messages move between NetSuite and the 3PL?

Exact formats vary by warehouse and connector, but the business messages are stable.

Outbound from NetSuite

A new fulfillment request when a sales order is approved and allocated to the 3PL location.
A cancellation or update when the customer changes the order before pick.
An advance ship notice style instruction when you send stock into the 3PL (purchase order receipt planned at that location, or a transfer).

Inbound to NetSuite

Shipment confirmation with quantity shipped, carrier and tracking number, which completes or updates the Item Fulfillment.
Inventory snapshot or adjustment advice for cycle counts, damage and found stock.
Receipt confirmation when inbound stock lands at the 3PL.

Our legacy guide to NetSuite 3PL integration that reconciles every quantity stays useful for the quantity match rules. This page adds the Australian tax and ownership layer around those rules.

How should fulfillment fees and GST be posted?

Australian 3PL invoices usually include storage, pick fees, packing materials, outbound freight and sometimes returns handling. GST is generally 10% on taxable supplies. Confirm the tax treatment of each fee line with your tax adviser, then reflect it in NetSuite.

A clean pattern looks like this:

Create the 3PL as a Vendor with the Australian Business Number and the default tax code for taxable domestic services.
Enter each fee invoice as a Vendor Bill (or import it) with expense or COGS accounts that match how you report fulfillment cost.
Do not net the fees against cash sale revenue. Gross sales stay on the invoice or cash sale. Fees stay on the bill.
When the 3PL passes through carrier freight that you recharge to the customer, decide if that recharge is a separate invoice line with GST. Keep the cost on the bill.
Accrue estimated 3PL fees at month end if the invoice arrives after you close, then reverse the accrual when the bill posts. That keeps margin reports steady.

For BAS, the GST on 3PL bills is an input tax credit when you are entitled to claim it. The sales GST sits on your invoices. Keep both visible. Clearing accounts help when the 3PL settles freight on your behalf and you reconcile to a bank line later.

A worked fee example helps the workshop. Suppose a week of pick fees is AUD 4,400 excluding GST. Storage is AUD 1,200 excluding GST. Passed through freight is AUD 2,000 excluding GST.

The vendor bill totals AUD 7,600 before GST and AUD 8,360 with 10% GST. NetSuite should show those three expense lines, GST of AUD 760 and a payable of AUD 8,360. None of that amount reduces the sales invoices for the same week.

Who owns inventory accuracy at month end?

Name three owners before the first live order.

Operations owns the daily exception queue: failed fulfillments, short picks and address rejects.
Inventory control owns the weekly quantity reconciliation between the 3PL on hand report and the NetSuite location quantity.
Finance owns the month end tie out of inventory value, unbilled 3PL fees and GST on those fees before BAS work starts.

A practical weekly check:

Export on hand by SKU from the 3PL portal for each location.
Run a NetSuite inventory balance search for the same locations.
Investigate any SKU variance above your agreed tolerance (many wholesalers start at one unit or AUD 50 of value).
Post inventory adjustments in NetSuite only after both sides agree the cause (damage, theft, count error or missed shipment message).

Do this again in the last week of each BAS quarter so stock adjustments do not surprise the return. After go live, fold the weekly stock check into your NetSuite hypercare in Australia rhythm.

What changes when you run mixed own warehouse and 3PL stock?

Many Australian wholesalers keep fast movers in house and send overflow or interstate demand to a 3PL. NetSuite can allocate a sales order line to one location. Prefer rules that are boring and written down:

Default allocation by customer state or by preferred location on the item.
A manual override role for customer service when a promise date needs the other site.
Transfer orders when you decide to reposition stock, with in transit quantity visible until the 3PL confirms receipt.
A daily open order search that shows lines still unallocated after the cut off time, so operations can move them before the 3PL wave closes.

Avoid silent "any location" availability on the storefront if only one site can ship a given SKU today. Overselling is usually a location design problem, not a gap in NetSuite itself.

When a sales order splits across two locations, invoice timing must stay clear. Some teams bill when the last line ships. Others bill per shipment. Pick one rule, put it in the customer terms if needed, and test GST on both a single shipment invoice and a split shipment case before go live.

How do returns and damaged stock come back?

Agree the path before peak season.

Customer returns to the 3PL: the 3PL receives the goods, inspects them and sends a receipt or adjustment message. NetSuite records an Item Receipt against a return authorization or posts an inventory adjustment, depending on your process.
Customer returns to your own warehouse: keep that flow on your location. Do not expect the 3PL integration to invent it.
Damaged stock found at the 3PL: require a reason code and a photo reference in the 3PL system. Post the NetSuite adjustment with the same reason in a memo field for audit.
Refused deliveries: the carrier returns the carton to the 3PL. Treat that as a reverse fulfillment with the original tracking linked in the memo so customer service can answer the buyer.

RMA timing matters for GST credit notes. Raise the credit in NetSuite when you accept the return, not when the 3PL happens to finish its count. If only part of a line is accepted, the credit memo quantity and GST must match the accepted quantity, and the 3PL on hand must rise by the same amount.

A short monthly meeting between operations and finance that reviews the top ten SKU variances and the open return authorizations older than fourteen days keeps both ledgers honest.

Which design fits your Australian operation?

Design	When it fits	Watch for
Own warehouse only	You pick every order today and have spare capacity	Revisit when interstate service levels slip
Single 3PL location	One national warehouse partner, no own pick	Location level available to promise, fee GST coding
Mixed own plus 3PL	Fast movers in house, overflow or remote states at the 3PL	Allocation rules, transfer orders, two reconciliation packs
Two or more 3PLs	Separate partners by state or product family	Duplicate SKU mapping, separate vendors and fee bills

Use the table in a one hour design workshop. Write the chosen row into the statement of work so build and test follow the same picture. Include three test orders in the acceptance pack: a full shipment, a short pick and a return. The broader options for warehouse interfaces are sketched in our NetSuite warehouse and 3PL integration design guide.

At CuriousRubik, we design fulfillment integrations so NetSuite stays the system of record for stock and margin. Our fulfillment integration team can map your locations, message set and GST posting, then test short picks and returns before go live. See how we support NetSuite customers in Australia.