Items, products and services

Is an item optional, required, or a subsystem? Xero treats items as a convenience most invoices ignore. QuickBooks makes them the required mechanism for sales lines. NetSuite makes them a costing subsystem with a dozen record types.

Concepts: 7
Divergences: 2
Structural: 0

Endpoints

Xero

GET /Items

One object, a flag for inventory

QBO

SELECT * FROM Item

Type discriminates

NetSuite

inventoryitem, serviceitem, …

A record type per item kind

The same concept in three vocabularies

Read across a row. Where a cell is absent, the concept has nowhere to live in that system — which is a design constraint, not a gap to paper over.

Native: — A field or object exists for it
Partial: — Exists with a caveat that changes what you can build
Derived: — Not stored — you compute it
Absent: — Nothing in the API

Items, products and services fields compared across Xero, QuickBooks Online and NetSuite
Concept	Xero	QBO	NetSuite
Type model	One object IsTrackedAsInventory flag	Type Inventory, NonInventory, Service, Group (a bundle in the UI), Category	Many record types inventoryitem, noninventoryitem, serviceitem, assemblyitem, kititem, itemgroup…
Code	Code Unique, user-facing	Name / Sku	itemid
Sales posting	SalesDetails.{UnitPrice, AccountCode, TaxType}	IncomeAccountRef, UnitPrice	incomeaccount + pricing sublists
Purchase posting	PurchaseDetails.{UnitPrice, COGSAccountCode}	ExpenseAccountRef, PurchaseCost	expenseaccount / cogsaccount
Inventory	InventoryAssetAccountCode, QuantityOnHand Average cost only	AssetAccountRef, QtyOnHand, InvStartDate FIFO	Locations, bins, lots, serials, costing methods
Hierarchy	—	Category items + ParentRef	parent, matrix items
Required on a sales line	No	Effectively yes	Yes

What actually differs, and what you do about it

A difference stated without a response is trivia. Each of these carries the handling.

Sharp edge

Writing an invoice to QuickBooks may mean creating items

QBO

If your source model carries accounts and not items, every QBO invoice write needs an item that points at the intended income account. Created on the fly, one per account, those items accumulate in the customer's product list and appear in their own reports.

Do — Provision a small, clearly named set of integration items up front, map account to item explicitly, and show the mapping in the connection settings rather than hiding it in the adapter.

Sharp edge

Inventory valuation is not comparable across the three

Xero · QBO · NetSuite

Xero is average cost, QBO is FIFO, NetSuite is configurable per item and per location. The quantity on hand is comparable; the value is not, and neither is the cost of goods sold that flows from it.

Do — Never present an inventory value as a cross-source aggregate without stating the costing method per source. Quantities may be summed; values may not.

The type the components consume

items.ts

type Item = {
  id: string;
  code?: string;
  name: string;
  kind: "service" | "inventory" | "non_inventory" | "bundle" | "category";
  sales?: { unitPrice?: Money; accountId?: string; taxCode?: string };
  purchase?: { unitCost?: Money; accountId?: string };
  inventory?: { assetAccountId?: string; quantityOnHand?: string; costingMethod?: string };
  active: boolean;
  source: SourceRef;
};

What this changes in the interface

The payoff. Every difference above that reaches the surface, and what the component does about it.

Item requiredness varies by source: InvoiceForm reads capabilities.lineTarget. On 'account' it shows an account picker; on 'item' an item picker; on 'both' it shows both with one primary.
Costing methods differ: Any inventory value shown across sources is labelled per source. A single consolidated inventory value is not offered, because it would not mean anything.

Where the accounting is explained

DocProcure to pay

What consumes this payload

The normalised object above is what the components read. These are the surfaces it feeds, the words for the concepts in it, and the document that explains the accounting.

Compared acrossXero docs QuickBooks Online docs NetSuite docs