Skip to content
NetSuite Reference

shipitem

master

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.

Grain note

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

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.

Structural facts — how the record is partitioned, not a trap by itself

Subsidiary-scoped
The record carries a subsidiary column 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 location column — an org segment in NetSuite before it is a warehouse — and the generated SQL anchors it the same way.

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field, and the T/F chip marks a check-box column Connect returns as a 'T'/'F' string.

Fields

19 fields · 1 key

19 fields.

Table fields: position, field name, description, data type, and flags. 19 fields.
#FieldDescriptionTypeFlags
1idInternal IDNUMBER
Primary-key field
2itemidShip name — the method as named on a documentVARCHAR
3displaynameDisplay name/codeVARCHAR
4descriptionDescriptionCLOB
5costbasisShipping rate basis (internal id) — decides WHICH rate column below is in forceNUMBER
6shippingflatrateamountFlat shipping rateNUMBER
7shippingperitemamountShipping rate charged per itemNUMBER
8shippingbyweightamountShipping rate charged by weightNUMBER
9shippingaspercentageoftotalShipping rate as a percentage of the order totalNUMBER
10minimumshippingcostMinimum shipping costNUMBER
11maximumshippingcostMaximum shipping costNUMBER
12handlingcostHandling rate basis (internal id) — the handling-side twin of costbasisNUMBER
13handlingflatrateamountFlat handling rateNUMBER
14ratingserviceselectCarrier service the rate is quoted against (internal id)NUMBER
15servicecodeShipper service code (internal id)NUMBER
16isonlineOffered in the web storeVARCHAR
17isinactiveInactiveVARCHAR
18subsidiarySubsidiaries — labeled in the plural, so no equality anchor is emittedNUMBER
19externalidExternal IDVARCHAR

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.

Query parameters

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.

Browse more Fulfillment & Logistics tables

More Fulfillment & Logistics tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle or NetSuite. NetSuite is a registered trademark of Oracle and/or its affiliates.