quantitypricingschedule
masterVolume-break pricing schedules: one row per schedule, naming the base discount, the unit the breaks are counted in, and whether the discount applies marginally or to the whole order.
this record exposes no lastmodifieddate — there is no watermark column here, so incremental extraction must full-refresh the schedules. The BREAKS are not here: this record is the schedule's settings, and the per-level quantity and discount rows live on satellite records this catalog does not carry.
Browser page name is quantityPricingSchedule. Feature-gated on Quantity Pricing: an account with the feature off has the record and no rows. overallquantitypricingtype is the switch between counting the break on the line, on the whole item across the order, and on the parent item — and no public source enumerates its values, so it lands as an id; see quirks #display-values. usemarginalrates decides whether the discount applies only to the units above a break or to all of them, which is the difference between two very different price answers from the same schedule. No 2025.2 script page exists for this record (the URL is a 405), so its continued existence is corroborated against the Help Center's Quantity Pricing Schedules topic instead.
What the badges mean
- master
- Data class: what the record holds — master data, transaction documents, control/configuration, or a documented convenience record. NetSuite has no product-family or schema axis, so this is the whole classification.
- Subsidiary-scoped
- The record carries a
subsidiarycolumn that partitions its rows, so the generated SQL anchors it. On a few records the column is a multiselect rather than a scalar foreign key — the table notes say which (see the quirks guide). - Location-scoped
- The record carries a
locationcolumn — an org segment in NetSuite before it is a warehouse — and the generated SQL anchors it the same way. - View
- A documented convenience record rather than a stored one. Land the records it stands in for instead of assuming it extracts as-is — the table notes say where the rows actually live.
Structural facts — how the record is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
'T'/'F' string.Fields
10 fields · 1 key
10 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | name | Schedule name | VARCHAR | |
| 3 | basediscount | Discount percentage applied before the breaks | NUMBER | |
| 4 | overallquantitypricingtype | What the break quantity is counted over — the line, the item across the order, or the parent item (internal id, no public value list) | NUMBER | |
| 5 | usemarginalrates | Discount applies only to the units above each break | VARCHAR | |
| 6 | unit | Unit the break quantities are stated in (internal id) — resolves to unitstypeuom.internalid | NUMBER | |
| 7 | unitstype | Unit-of-measure family (internal id) | NUMBER | |
| 8 | vendor | Vendor the schedule applies to (internal id) | NUMBER | |
| 9 | isinactive | Inactive | VARCHAR | |
| 10 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of quantitypricingschedule on Databricks — dates are real DATE/TIMESTAMP columns and need no conversion, and the partition anchors are already in place. This record carries no modification stamp, and the snippet says so where the watermark would otherwise go. Set your Unity Catalog location, schema, and filter values below; they’re substituted into the SQL and the copy button.
3 parameters not filled: <catalog>, <schema>, <id>
-- ============================================================
-- Table : quantitypricingschedule — Volume-break pricing schedules: one row per schedule, naming the base discount, the unit the breaks are counted in, and whether the discount applies marginally or to the whole order.
-- Purpose: Column-selected read of quantitypricingschedule — auto-generated from field metadata
-- Grain : One row per id
-- Caution: this record exposes no lastmodifieddate — there is no watermark column here, so incremental extraction must full-refresh the schedules. The BREAKS are not here: this record is the schedule's settings, and the per-level quantity and discount rows live on satellite records this catalog does not carry.
-- Notes : Auto-generated skeleton for NetSuite data landed in your lakehouse from a SuiteAnalytics Connect (or SuiteQL) extract — it never addresses live NetSuite. Identifiers are lowercase as NetSuite2.com renders them. Select-type columns hold numeric internal ids: BUILTIN.DF() display resolution exists only at extraction time, so decode ids by joining the landed list records; see quirks #display-values. Check-box columns arrive as 'T'/'F' strings; see quirks #tf-booleans.
-- ============================================================
SELECT
t.id AS "Internal ID",
t.name AS "Schedule name",
t.basediscount AS "Discount percentage applied before the breaks",
t.overallquantitypricingtype AS "What the break quantity is counted over — the line, the item across the order, or the parent item (internal id, no public value list)",
t.usemarginalrates AS "Discount applies only to the units above each break", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.unit AS "Unit the break quantities are stated in (internal id) — resolves to unitstypeuom.internalid",
t.unitstype AS "Unit-of-measure family (internal id)",
t.vendor AS "Vendor the schedule applies to (internal id)",
t.isinactive AS "Inactive", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.externalid AS "External ID"
FROM <catalog>.<schema>.quantitypricingschedule t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.id = <id>
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
ORDER BY t.id;Verified August 2026 · Analytics Browser 2021.1 · corroborated 2025.2
Select columns hold internal ids, not display text — see decoding display values.
Relationships
Diagram of 1-hop neighbors — join details below. Document-link edges are highlighted; they chain one document to the next and are the joins newcomers most often get wrong.
Join details
ON quantitypricingschedule.unit = unitstypeuom.internalidON quantitypricingschedule.unitstype = unitstype.idON quantitypricingschedule.vendor = vendor.id
More Pricing tables
- termThe payment-terms master: one row per terms code with the whole date-driven rule set behind it — days till net due, discount percentage and expiry, day-of-month due, and the installment schedule columns.
- pricelevelThe price-level list: one row per level (base price, online price, a customer tier), each with the markup or discount percentage that defines it.
- pricingThe item price matrix: one row per item, price level, currency, quantity break and sale unit, carrying the unit price. This is where a price actually lives.
- pricinggroupThe pricing-group list: four columns naming the groups items are bucketed into for group-level price rules.