Effect of Inactivating Price Level and Defaulting to Base Price on Customer Master

Scope:

  • Inactivating Price Level: Analyze the process of inactivating a price level and its effects on historical transactions, customer pricing, and future quotes or orders.
  • Defaulting to Base Price: Evaluate how customers are impacted when the base price is applied as the default, especially in cases where a custom price level is in use.
  • Review how it affects the previous reports 

Solution Guidance:

Customer Record Considerations

  • Even if a price level is inactivated, it will not be automatically removed from customer records.
  • Customer records will still show the inactive price level until it is manually or mass-updated.
  • If a custom price level is inactive, NetSuite may default to the Base Price or another predefined active price level on transactions.

Impact on Historical Transactions

Closed Transactions:

  • No impact on historical closed transactions (e.g., invoices, closed sales orders, or completed quotes).
  • These records retain the originally assigned price level.

Open Transactions:

  • Open transactions (Sales Orders, Estimates, Invoices, Quotes, etc.) will not be updated automatically.
  • If an existing transaction references the inactive price level, it will remain unchanged.
  • Copying an existing transaction:
  • If you copy a transaction that used the inactive price level, the copied record will retain the same price level.
  • Creating a next related transaction (e.g., Sales Order > Invoice):
  • If an invoice is created from an open Sales Order that used the inactive price level, the system will retain the inactive price level on the new invoice.
  • Price Level Dropdown Behavior:
  • The price level dropdown will no longer show the inactive price level as a selectable option in new transactions.

Outcome:

  • Open transactions will still function, but users need to be aware that inactive price levels cannot be selected in new transactions.

Impact on Future Transactions

  • Users will no longer be able to select the inactive price level when creating new transactions.
  • If a customer had a default price level that was inactivated, NetSuite will default to the base price level unless manually updated.

Impact on Reports

  • Reports that include historical transactions (e.g., past sales orders, invoices, or quotes) will continue to show the inactive price level where it was originally applied.
  • The reports will show the results based on the date that we have tracked in the records.
  • If the inactive price level was set as a static value in any report, saved search, workflow, or script, it must be manually updated to an active price level to ensure continued functionality.

Steps to Inactivate a Price Level in NetSuite

  1. Navigate to Setup > Accounting > Accounting Lists > Type = Price Level
  2. Set Show Inactives = True
  3. Check the Inactive box for price level need to make inactive

Outcome:

  • The inactive price level will no longer be available for selection in new transactions.
  • However, existing transactions and customer records that reference this price level will not be automatically updated.

Steps to Update Customer Price Level to Base Price

Option 1: Manual Update (For a Small Number of Customers)

  1. Navigate to Lists > Relationships > Customers > Edit Customer.
  2. Change the Price Level:
  • Under the Financial subtab, locate the Price Level field.
  • Select Base Price or any other active price level.
  1. Save the Changes:
  • Click Save to update the record.

Option 2: Mass Update (For Bulk Changes)

  1. Navigate to Lists > Mass Update > Customers.
  2. In the mass update field, choose the new price level (e.g., Base Price).
  3. Click Update to apply the changes.

Note: CSV import is also an option to update the Customer’s Price level

Outcome:

  • All selected customer records will now reference the new price level.
  • Future transactions will use the new price level instead of the inactive one.

Leave a comment

Your email address will not be published. Required fields are marked *