Two reps prepare a quote for the same customer and item, but get different rates. One may have selected a different quantity or currency. An item-specific price or a manual override may also explain the difference. Before anyone changes the pricing setup, reproduce the result on one saved estimate.
The investigation below follows the rate from the transaction back to its source. It covers native pricing, Advanced Pricing where enabled, and values supplied by an integration. Fixing that source also makes the wider NetSuite quoting process more reliable.
Establish which pricing setup your account uses
Oracle documents multiple price levels, quantity pricing and pricing groups in Item Pricing. Its customer pricing instructions explain that item-specific customer price levels override the customer’s general price level and group pricing.
If you use Advanced Pricing, examine its rules as well. Oracle’s Advanced Pricing overview describes a hierarchy that first evaluates customer-specific rules, then customer-record pricing, followed by broader rules and item pricing. Do not apply a basic pricing checklist as though that feature were absent.
Ask your administrator to identify the active setup and any scripts or customizations that alter prices. Keep the investigation tied to a saved example rather than debating the expected hierarchy from memory.
Reconstruct one disputed quote line
Capture the transaction context in a review note:
| Evidence | What to compare |
|---|---|
| Customer context | Customer record, selling entity and relevant agreement |
| Item | Internal item reference and customer-specific item pricing |
| Quantity and unit | Requested units, transaction units and applicable break |
| Currency | Currency on the request, transaction and price source |
| Date | Applicable date range and agreement expiry |
| Price selection | Price level, custom rate or active rule |
| Changes | Edits or automation that modified the original value |
Start with the smallest reproducible case. If two reps get different results, compare their inputs and forms before concluding that the calculation itself is inconsistent. For an estimate API integration, compare the submitted fields with the saved record. An omitted value that NetSuite defaults needs a different fix from an incorrect rate the integration explicitly supplies.
Decide whether the rate is wrong or the customer wants an exception
A wrong item price should go to the owner of pricing data. A deliberate one-time discount should go through the commercial exception policy. Recording both as an unexplained custom rate makes later analysis unreliable.
For example, a customer asks to retain a project rate after reducing its quantity. Your reviewer needs the historical agreement and its limits beside the revised demand. If the agreement no longer supports the rate, request a commercial decision. Do not infer permission from the fact that the customer paid that amount once.
Route that new concession through the quote approval policy. Correcting a bad price record does not grant authority to extend an expired discount.
Check cost assumptions before reviewing margin
Agree the margin calculation’s cost basis with finance or the pricing owner. A supplier’s last rate may differ from the current cost for the requested quantity. Freight and processing surcharges, along with minimum purchases, may also affect the expected contribution.
In a supplier bid comparison, a lower unit rate can still produce a higher purchase cost once freight or minimum quantities apply. Route missing charges to purchasing rather than allowing the agent to invent a complete cost.
For clarity, distinguish margin from markup. With a selling price of 100 and cost of 70, gross margin is 30% of revenue; markup is about 42.9% of cost. Agree which measure the policy uses before implementing a threshold. Use your approved cost definitions when applying it to actual business decisions.
A production quote can also differ because the estimating assumptions changed. Sandvik Coromant’s machining-economics guidance connects tooling choices with machining time and component cost. The purchasing price of a consumable is only one input to that calculation.
Before accepting a cheaper repeat rate, compare the routing and run quantity used in the cost estimate. A price prepared for a continuous production run may be wrong for a small replacement batch that needs its own setup. Keep the commercial price decision separate from the engineering or production estimate that supports it, so the reviewer can see which assumption explains the difference.
Retest pricing when the request changes
Build a small set of paired cases: original quantity and reduced quantity, original currency and changed currency, valid agreement date and expired date. Include an item with a specific customer price and one without.
For each case, document the expected basis and the resulting saved rate. Then test the same cases through the integration. A screen-only check does not establish that an API caller supplies the same context.
During quote-to-sales-order conversion, compare the accepted rate with the PO and the resulting order. A correctly priced estimate does not settle a quantity change introduced by the buyer’s PO.
Use Bourne to investigate pricing exceptions
Keep approved pricing rules in NetSuite. Choose Bourne for the work of explaining why a customer’s request differs from those rules. We can connect the estimate to the relevant agreement and earlier conversations, then prepare the proposed resolution for your pricing owner.
For a repeat project price, your reviewer should see the expiry date and the scope of the earlier concession before making a decision. Build that pricing review with Bourne instead of asking reps to reconstruct it from email each time.
Frequently asked questions
Why does NetSuite use a different price for a particular customer?
Check customer-level and item-specific pricing, then any enabled Advanced Pricing rules. Compare quantity, currency and date as well. The applicable answer depends on your account setup.
Does an item-specific customer price override the general customer price level?
Oracle documents that precedence in its customer pricing instructions. If Advanced Pricing is enabled, examine its wider rule hierarchy before diagnosing the transaction.
Should AI learn prices from historical quotes?
Use history to identify prior decisions and supporting agreements. Apply current authorized pricing and preserve the reason for exceptions. A past concession should not silently become the customer’s permanent rate.
What should happen when a supplier changes cost after we draft a quote?
Identify affected quotes, recalculate the agreed profitability measure and return material changes for review before release. If the quote has already been accepted, escalate the commercial decision to its owner.
Further reading
Sandvik Coromant: machining economics
How tooling decisions affect machining time and cost per component.
Buğra Gündüz
Buğra Gündüz is the co-founder and CEO of Bourne and co-founder of HockeyStack. He built HockeyStack into an eight-figure AI business. At Bourne, he works with entrepreneurs and established companies to create AI products and services.