shipitem
masterThe shipping-item record — which in NetSuite is also the shipping METHOD: one row per method a document can be shipped on, carrying its carrier service codes and the whole rate-and-handling rule set behind the quoted freight.
sixty-six columns, most of them PRICING RULES rather than facts — flat rate, per-item, per-weight, percent-of-total and table-driven variants all coexist, and only the one costbasis names is in force. Read the basis column before reading any rate column.
Browser page name is ShipItem (label "Shipping Item"). The catalog draws no edge from the transaction spine to this record: the spine's shipment satellite carries ship-via as TEXT, not as a shipping-item id, so no attested id join exists. The rate tables and translations the page joins to are not cataloged, which is why this record ships with no edges at all. hasSubsidiary is false by design: the `subsidiary` column is authored below, but the page labels it in the plural while typing it as a single select, so whether one shipping item can serve several subsidiaries is not settled by any public source — and an equality filter against a column that might hold several ids would silently drop every shared row. Confirm the shape in your own account before filtering on it.
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
19 fields · 1 key
19 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | itemid | Ship name — the method as named on a document | VARCHAR | |
| 3 | displayname | Display name/code | VARCHAR | |
| 4 | description | Description | CLOB | |
| 5 | costbasis | Shipping rate basis (internal id) — decides WHICH rate column below is in force | NUMBER | |
| 6 | shippingflatrateamount | Flat shipping rate | NUMBER | |
| 7 | shippingperitemamount | Shipping rate charged per item | NUMBER | |
| 8 | shippingbyweightamount | Shipping rate charged by weight | NUMBER | |
| 9 | shippingaspercentageoftotal | Shipping rate as a percentage of the order total | NUMBER | |
| 10 | minimumshippingcost | Minimum shipping cost | NUMBER | |
| 11 | maximumshippingcost | Maximum shipping cost | NUMBER | |
| 12 | handlingcost | Handling rate basis (internal id) — the handling-side twin of costbasis | NUMBER | |
| 13 | handlingflatrateamount | Flat handling rate | NUMBER | |
| 14 | ratingserviceselect | Carrier service the rate is quoted against (internal id) | NUMBER | |
| 15 | servicecode | Shipper service code (internal id) | NUMBER | |
| 16 | isonline | Offered in the web store | VARCHAR | |
| 17 | isinactive | Inactive | VARCHAR | |
| 18 | subsidiary | Subsidiaries — labeled in the plural, so no equality anchor is emitted | NUMBER | |
| 19 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of shipitem 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 : shipitem — The shipping-item record — which in NetSuite is also the shipping METHOD: one row per method a document can be shipped on, carrying its carrier service codes and the whole rate-and-handling rule set behind the quoted freight.
-- Purpose: Column-selected read of shipitem — auto-generated from field metadata
-- Grain : One row per id
-- Caution: sixty-six columns, most of them PRICING RULES rather than facts — flat rate, per-item, per-weight, percent-of-total and table-driven variants all coexist, and only the one costbasis names is in force. Read the basis column before reading any rate column.
-- 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.itemid AS "Ship name — the method as named on a document",
t.displayname AS "Display name/code",
t.description AS "Description",
t.costbasis AS "Shipping rate basis (internal id) — decides WHICH rate column below is in force",
t.shippingflatrateamount AS "Flat shipping rate",
t.shippingperitemamount AS "Shipping rate charged per item",
t.shippingbyweightamount AS "Shipping rate charged by weight",
t.shippingaspercentageoftotal AS "Shipping rate as a percentage of the order total",
t.minimumshippingcost AS "Minimum shipping cost",
t.maximumshippingcost AS "Maximum shipping cost",
t.handlingcost AS "Handling rate basis (internal id) — the handling-side twin of costbasis",
t.handlingflatrateamount AS "Flat handling rate",
t.ratingserviceselect AS "Carrier service the rate is quoted against (internal id)",
t.servicecode AS "Shipper service code (internal id)",
t.isonline AS "Offered in the web store", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.isinactive AS "Inactive", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.subsidiary AS "Subsidiaries — labeled in the plural, so no equality anchor is emitted",
t.externalid AS "External ID"
FROM <catalog>.<schema>.shipitem 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.
More Fulfillment & Logistics tables
- zoneThe warehouse zone list: one row per pick zone at a location, with its name and description.
- fulfillmentrequestThe fulfillment-request document: a store or site being asked to fulfill part of an order, with its own number, date, status, fulfillment type, assignee and pickup-hold state.
- picktaskThe warehouse pick task: one row per item, lot/serial and recommended bin a picker is asked to pull, with the picked and remaining quantities and the wave it belongs to.