Limitations for Consigned Inventory Management in NetSuite 2026.1
Learn about limitations for Consigned Inventory Management in NetSuite 2026.1 and ensure compliance with transaction processing rules.
TL;DR Opening
Starting in NetSuite 2026.1, several limitations affect the Consigned Inventory Management feature. It’s crucial to understand these restrictions to ensure proper usage and avoid transaction errors while managing consigned stock effectively.
Overview of Limitations
When utilizing the Consigned Inventory Management feature in NetSuite, users should be aware of the following constraints:
Key Limitations
- Incompatibility with Assembly Items: The feature cannot be enabled if Assembly Items are in use. They cannot coexist in the same environment.
- Manufacturing Processes Exclusion: Consigned Inventory Management does not support manufacturing workflows or related processes.
- Warehouse Management Integration: This feature cannot operate in conjunction with the Warehouse Management feature or the NetSuite WMS SuiteApp.
- Transaction Restrictions: Vendor consigned items cannot be included in certain transactions such as:
- Inventory Transfer and Bin Transfer
- Inventory Worksheet
- Standalone Vendor Bill
- Standalone Vendor Return Authorization
- Cash Refund
- Credit Memo
- Blanket Purchase Order
- Inbound Shipment
- Status Transition Limitations: Changing an item's inventory status from consigned to non-consigned, and vice versa, is not supported.
Purchasing and Receiving Limitations
Further restrictions apply when purchasing or receiving consigned items:
- Limited Transaction Types: Certain transaction types, including Blanket Purchase Orders and Inbound Shipments, may not include consigned quantities.
- Landed Cost Management: Actual and estimated landed costs cannot be tracked or allocated for consigned items.
- Exclusions from Returns: Consigned items cannot be processed in standalone vendor return authorizations and similar transactions.
- Bill Preferences: The Bill in Advance of Receipt preference does not apply to consigned items, adding another layer of complexity.
Best Practices
- Verify Item Setup: Ensure vendor consigned items are properly set up to avoid issues during transactions. Reference the guidelines for [Setting Up Consigned Inventory per Item].
- Consult with Localization SuiteApp: If using the Brazil Localization SuiteApp, consult your account manager before enabling Consigned Inventory Management to confirm customization requirements.
Who This Affects
This information is particularly relevant for:
- Inventory Managers
- System Administrators
- Supply Chain Coordinators
- Accounts Payable Teams
Key Takeaways
- Understand the incompatibilities and limitations of the Consigned Inventory Management feature in NetSuite 2026.1.
- Ensure proper item setup and compliance with transaction rules to avoid processing errors.
- Review transaction types and restrictions to effectively manage consigned inventory processes.
Frequently Asked Questions (4)
Is Consigned Inventory Management feature compatible with Assembly Items in NetSuite 2026.1?
No, the Consigned Inventory Management feature cannot be enabled if Assembly Items are in use as they cannot coexist in the same environment.
Can I use the Consigned Inventory Management feature with Warehouse Management in NetSuite 2026.1?
No, the Consigned Inventory Management feature cannot operate with the Warehouse Management feature or the NetSuite WMS SuiteApp.
Are there any transaction types that cannot include vendor consigned items in NetSuite 2026.1?
Yes, vendor consigned items cannot be included in transactions such as Inventory Transfer, Bin Transfer, Inventory Worksheet, Standalone Vendor Bill, and others like Blanket Purchase Orders and Inbound Shipments.
Can landed costs be managed for consigned items in NetSuite 2026.1?
No, both actual and estimated landed costs cannot be tracked or allocated for consigned items.
Weekly Update History (1)
Source: Limitations for Consigned Inventory Management — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.
Was this article helpful?