Item, Inventory, Purchasing Object Fields
Field guide for catalog, item setup, inventory, BOM, warehouse, and purchase order reporting
Use these objects for catalog readiness, stock visibility, purchasing, receiving, cost setup, BOM coverage, and warehouse routing.
Item
Items are the catalog backbone. They drive quoting, sales order lines, inventory, purchasing, BOM cost, fulfillment routing, GL defaults, payment gateway routing, and product reporting.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Identity | SKU, Item Code, Description, Item Group, Item Group Link, Product Type, Item Category, Item Type, variant family fields, image URL. | Use for catalog, product hierarchy, and SKU reporting. |
| Sell/quote/purchase eligibility | Can Quote, Can Sell, Can Purchase, Not Available for Quotes, Not Available For Sale, Not Available for Purchase, Line Add Setup Blocked, Standard Sales Visible, Visible to Standard Sales. | Use for product readiness and why items are hidden from selectors. |
| Item behavior flags | Is Credit, Is Shipping, Is Service Item, Is Non Physical, Exclude From Fulfillment, Not Count In Inventory. | Use to separate products, credits, shipping, services, and non-inventory lines. |
| Pricing and cost | Unit Price, Unit Cost, Effective Unit Cost, Gross Profit Per Unit, Gross Margin Percent, Markup Percent, Cost Basis, Cost Basis Source. | Use for catalog economics. |
| BOM and standard cost | Has BOM, Bill of Materials, Standard BOM Cost, BOM Component Count, BOM Depth Level, Has Nested BOMs, BOM Cost Variance, standard cost component fields. | Use for cost coverage and BOM setup reports. |
| Inventory position | Quantity On Hand, Available to Promise, Inventory Value On Hand, Potential Revenue On Hand, On Hand Profit Potential, Stock Status Rating, Stockout Risk Score, Days of Supply, Days Until Stockout. | Use for stock and replenishment dashboards. |
| Demand and replenishment | Average Daily Unit Demand, Sales Last 30 Days, Units Last 30 Days, Lead Time Days, Reorder Point, Safety Stock Quantity, Safety Stock Days, Reorder Gap Units, Reorder Gap Value, Excess Inventory Units, Excess Inventory Value. | Use for purchasing and inventory planning. |
| Routing | Default Warehouse, Warehouse, Warehouse Link, Default Vendor, Default Location, Default Unit Of Measure, package/dimension/weight fields. | Use for fulfillment and purchasing setup reports. |
| Payment and GL | Default Payment Gateway, Payment Gateway, Revenue GL Account, COGS GL Account, Inventory GL Account, Expense GL Account, Inventory Expense Account, PWO Material Variance Account. | Use for payment routing and finance readiness. |
| Migration lineage | External Source * fields. | Use only for import audit/reconciliation. |
Best practice: if an item cannot be quoted or sold, check eligibility flags, setup blockers, warehouse/gateway/GL defaults, and inventory behavior before assuming it is a data error.
Item Group
Item Groups organize related items for catalog search, reporting, commission grouping, and product-family analysis.
| Field family | Use |
|---|---|
| Group identity and hierarchy | Product family and category reporting. |
| Parent/child relationships | Rollup or nested group reporting. |
| Active/status fields | Hide inactive product families from active reports. |
Best practice: use Item Group for product-family reporting when users do not need exact SKU-level detail.
Warehouse
Warehouses represent internal warehouses and 3PL provider locations.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Identity | Warehouse Code, Normalized Code, address fields, primary contact fields, Account/Contact. | Use for warehouse lists and operational routing. |
| Active/config state | Is Active, Is 3PL Provider, Integration Type, Default Service Level, Order Cutoff Time. | Use for active warehouse and service-level reports. |
| 3PL runtime | Active 3PL Provider Config, ThreePL Runtime Connection, operating time/time zone fields. | Use for provider setup and runtime readiness. |
| Integration health | Integration Health Status, Last 3PL Activity, Last 3PL Success, Last 3PL Failure, Last 3PL Error, Last 3PL Status Code, Last 3PL Latency Ms, Last 3PL Endpoint, Last 3PL Product Fetch. | Use for warehouse/provider health dashboards. |
| Migration lineage | External Source * fields. | Use only for import audit/reconciliation. |
Best practice: do not report a warehouse as available just because the record exists. Use active/config/health fields together.
Inventory
Inventory records represent item quantity by warehouse/source.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Item and warehouse | Item, Item Link, Warehouse, Warehouse Link, Inventory Source. | Use for stock by SKU/location/source. |
| Quantities | Quantity On Hand, Quantity Allocated, Quantity Available, Provider Quantity On Hand. | Use for inventory availability and provider mirror comparisons. |
| Value/cost | Cost, Inventory Value, Last Cost Recalc. | Use for inventory valuation and cost recalc reports. |
| Movement/count | Last Count Date, Last Movement Date. | Use for stale inventory or cycle count reports. |
| Provider mirror | Provider Source System, Provider Snapshot At, Provider Mirror Status, Provider Mirror Message. | Use for external-provider inventory sync health. |
Best practice: use Inventory Transactions to explain why inventory changed. Inventory records show current state.
Inventory Transaction
Inventory Transactions are movement evidence.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Movement | Transaction Type, Transaction Date, Quantity, Quantity Before, Quantity After, Counted Quantity. | Use for inventory change history. |
| Adjustment context | Adjustment Mode, Adjustment Reason, Notes. | Use for adjustment audit reports. |
| Cost impact | Unit Cost Used, Average Cost Before, Average Cost After, Value Delta. | Use for inventory valuation change reports. |
| Reference | Reference Type, Reference Number, Reference Id, Inventory, Item, Warehouse. | Use to connect movement to order, PO, count, or adjustment source. |
Best practice: do not use direct quantity edits as reporting evidence. Inventory Transaction reports should explain stock movement.
Bill Of Materials
BOMs define how an item is costed or built from components.
| Object | Important fields | How to use in reports |
|---|---|---|
Bill_of_Materials__c | Item, Revision, Version Number, Effective Date, Expiration Date, Is Active. | Use for active BOM coverage and revision history. |
BOM_Component__c | Bill of Materials, Item, Quantity, Cost, Component Extended Cost, component/parent category and product type, Line Order. | Use for component cost, raw-material usage, and BOM cost breakdown. |
Best practice: use BOM Component reports when the question is "what drives this cost?" Use Item fields when the question is "does this item have BOM coverage?"
Purchase Order
Purchase Orders track supply pipeline, vendors, receiving, production, and 3PL PO sync.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Vendor and warehouse | Vendor, Contact, Warehouse, Warehouse Link, delivery address fields, Vendor Reference Number. | Use for vendor/warehouse purchasing reports. |
| Dates | Order Date, Issued Date, ETA, Due Date, Ship Date, Received Date, timeline start/end fields. | Use for open supply schedule and overdue PO reports. |
| Status and attention | Status, Pipeline Attention Status, Needs Attention, Has Blocker, Blocker Notes, Is Open Pipeline, Is Overdue Open, missing tracking/vendor acknowledgement fields. | Use for purchasing queues and exception dashboards. |
| Quantities and completion | Total Lines, Total Quantity Ordered, Total Quantity Received, Total Quantity Open, Completion Percent, Production Progress. | Use for receiving progress. |
| Amounts | Final Order Total, Net Order Total, Open Order Value, Freight Amount, Total Tax. | Use for supply value and open purchasing exposure. |
| Related records | Related Sales Order, Bill Of Materials, Item Group By, dependencies. | Use for demand-linked purchasing and production runs. |
| Notifications | Receipt notification status/count/error/recipients/sent date. | Use for receiving communication coverage. |
| 3PL sync | ThreePL Sync Status, ThreePL Runtime Sync Status, provider display number/mode/source/ref fields. | Use for PO sync health. |
| Migration lineage | External Source * fields. | Use only for import audit/reconciliation. |
Best practice: Purchase Order header fields are good for supply pipeline. Use Purchase Order Lines when the report needs exact items, quantities, and receiving detail.
Purchase Order Line
Purchase Order Lines are item-level supply detail.
| Field family | Use |
|---|---|
| Item, quantity, unit price, line totals | What is being purchased and for how much. |
| Received/open quantity fields | What has arrived and what remains open. |
| Warehouse/vendor relationships | Where supply is going and who provides it. |
| Related sales order/BOM context | Whether the PO exists to support demand or production. |
Best practice: for "what should be ordered or received next?", use line-level reports. For "which POs need attention?", use PO header reports.
Last updated on