Start a NetSuite consignment design by establishing whose stock it is, where it is held, what event transfers ownership, and how the supplier or customer is settled. Then check whether the current native Consigned Inventory Management feature supports that exact flow and the other features in the account.
NetSuite now documents a dedicated vendor-consignment capability. Advice that every consignment process requires a virtual location or zero-cost workaround is therefore incomplete. The native feature also has important compatibility and transaction limitations, so availability alone does not establish fit.
Inbound vendor consignment means the business holds goods supplied under a vendor-owned arrangement until the agreed consumption or sale event. Outbound consignment means the business places its own goods with another party while retaining the relevant ownership interest under the arrangement.
Those are different system perspectives. A feature designed to track vendor-consigned purchases should not be assumed to manage every outbound consignment agreement. Describe the intended events and parties before deciding whether native functionality, another application, or a controlled custom process is appropriate.
Also distinguish consignment from vendor-managed replenishment. A supplier managing reorder quantities does not, by itself, determine ownership. Have the responsible accountant and legal adviser review the actual agreement, including damage, loss, return rights, pricing, and settlement obligations.
The current Consigned Inventory Management feature supports vendor-consigned inventory, including ordinary inventory and supported lot or serialized items. It separates consigned and non-consigned quantities using dedicated consigned statuses and item configuration.
Important current limitations can rule out the native design: it cannot coexist with the Warehouse Management feature or NetSuite WMS SuiteApp, and it is incompatible with Assembly Items. Manufacturing processes are not supported. Inbound shipments and several standalone or other transaction types are also outside the supported consigned flow.
Verify the current release, entitlement, prerequisites, localization requirements, and installed SuiteApps with the account team. Do this before a detailed configuration workshop. If the warehouse depends on an incompatible feature, the project needs an architecture decision rather than a late checkbox workaround.
List each event from receipt through sale, consumption, loss, return, and vendor settlement. For each, identify the physical quantity change, ownership conclusion, system transaction, value effect, and evidence.
A negative adjustment is particularly important in the native vendor-consigned flow: reduced consigned quantity is treated as consumed. Customer-returned goods are no longer vendor owned. These behaviors mean a routine shrinkage or customer-return procedure can affect settlement assumptions.
Do not use an inventory status change to turn consigned quantity into non-consigned quantity or the reverse. That conversion is not a supported shortcut. The process should use the appropriate ownership and transaction sequence, with finance reviewing the outcome.
A retailer receives 100 vendor-consigned units. During the month, it sells 30 units, records an approved negative adjustment for two damaged units, and receives three units back from customers who bought them earlier.
Under the documented native behavior, the two-unit negative adjustment is treated as consumption, and the three returned units do not simply restore vendor-owned consigned stock. The operational reconciliation therefore needs separate columns for vendor-owned quantity, sold or consumed quantity, and returned stock now held under its resulting ownership treatment.
The vendor agreement may address damage responsibility or credits differently from an ordinary sale. Finance and procurement must reconcile that agreement with the supported system transactions and any approved settlement corrections. They should not assume that 30 minus three equals the complete vendor liability calculation.
The test pack follows the actual records through receiving, sale, adjustment, return, consumption reporting, and billing. It verifies the financial entries and vendor statement under the approved policy rather than treating a stock count as the entire settlement answer.
Native vendor consignment uses dedicated tracking accounts and posting behavior for receiving, transfers, adjustments, consumption, and billing. Do not assume that vendor ownership means no NetSuite postings, or that receiving all stock at zero value is the correct design.
Have the accountant approve account mappings, financial-statement presentation, cost treatment, periods, and reconciliation. The system's account names do not decide the legal or financial reporting conclusion. Demonstrate actual GL impact for representative transactions before production use.
Keep consigned and owned quantities distinguishable in operational reports. A combined on-hand total can be useful for physical custody, while finance and procurement need the ownership split. Label reports clearly so a purchasing user does not interpret every stocked unit as already purchased.
Define the settlement frequency, cutoff, item identifiers, quantities, prices, returns, damage claims, and disputed lines. Name the owner who approves a consumption report before it is sent externally or used for billing.
The Consignment Purchases Workbook provides a reporting starting point for vendor-consigned purchase activity and consumption. Validate its filters and calculated fields for the intended reconciliation. Default displays can hide negative calculated quantities, so over-receipt or over-billing exceptions need deliberate review.
Match the vendor's identifiers and units with NetSuite's. A monthly file in cases and a vendor statement in individual units can disagree while describing the same goods. Retain the conversion and transaction references behind the settlement.
Moving goods between bins or locations does not necessarily mean ownership has changed. Use the supported consigned transfer process and verify the resulting quantities and accounts. Keep location custody separate from the vendor relationship.
Test vendor returns before consumption and customer returns after sale as distinct scenarios. They have different business meaning and supported transaction constraints. Do not use a standalone transaction merely because it resembles the desired result; confirm its eligibility for consigned items.
Include mixed owned and consigned stock for the same item, if the business uses it. The picker and finance reviewer must be able to identify which quantity was selected. A shared bin can be physically workable only if identity and status remain reliable in the approved process.
If WMS or manufacturing compatibility prevents the native feature from fitting, document the alternatives with their consequences. A third-party application, separate operating design, or custom solution may be considered, but each needs explicit ownership, transaction, and reconciliation tests.
A virtual location can help represent custody, but it does not independently solve ownership, valuation, or vendor settlement. A zero-cost receipt can simplify one report while weakening another. Evaluate the complete lifecycle rather than selecting the shortest setup path.
For outbound consignment, define stock at the consignee, consumption evidence, customer billing, returns, and count reconciliation from the business's perspective. Do not relabel the inbound vendor feature as an outbound solution without demonstrated support.
A pilot should include receipt, ordinary sale, partial consumption, damage, physical count difference, internal movement, vendor return, customer return, and settlement. Add the actual integrations and reporting recipients within the approved scope.
Require matched quantity, ownership, and financial outcomes. Include a duplicate consumption message or corrected vendor statement if external systems participate. Keep any unsupported step visible as a design gap rather than hiding it in an adjustment.
CuriousRubik's NetSuite support services can support a fit assessment using that lifecycle. The first decision is whether the account and contract match the supported vendor-consignment model, with responsible finance and legal review of the conclusions.
Current documentation describes Consigned Inventory Management for vendor-consigned inventory. Confirm release, entitlement, prerequisites, and compatibility in the target account. Older advice based solely on custom-location workarounds should be reassessed.
Current documented limitations say it cannot be used with Warehouse Management or the NetSuite WMS SuiteApp. Assembly Items and manufacturing are also incompatible. Treat these as early architecture gates and reverify them for the intended release.
Do not assume so. Its documented scope is vendor-consigned inventory. Outbound arrangements require a separate event and accounting design, with demonstrated support for stock held by the consignee and subsequent settlement.
That conversion is not supported as an ordinary status-change shortcut. Use the appropriate supported transaction and ownership process, and verify its financial consequences with the responsible accountant.
Native negative consigned adjustments are treated as consumption, while customer-returned goods are no longer vendor owned. Those behaviors can affect vendor settlement and ownership reporting, so a simple net-sales calculation may be insufficient.