Sales Order Field Guide

Plain-English guide to Sales Order fields for reports, dashboards, filtering, grouping, and totals

Sales Orders are one of the most important reporting objects in this Salesforce app. A Sales Order record combines customer, quote, payment, fulfillment, tracking, finance, commission, email, and external RMA correlation data.

That makes Sales Orders powerful, but it also means several fields look similar. Use this page before building Sales Order reports.

Field Families

Identity And Relationships

Field	Use in reports for	Notes
Sales Order Number	Human-readable order number, such as `SO-011436`.	Use this as the first detail column.
`Customer Purchase Order`	Customer-supplied PO reference.	Useful for customer service and invoice matching.
`Account`	Customer company.	Best grouping for customer-level order, AR, and volume reports.
`Contact`	Primary contact on the order.	Use for customer communication follow-up.
`Primary Sales Rep`	Rep credited or responsible for the order.	Use for sales performance and commission reports.
`Warehouse`	Internal/fulfillment warehouse route.	Use for operations reports.
`Quote`	Source quote.	Useful for quote-to-order conversion and approval analysis.
`Terms`	Customer/order payment terms.	Use when reporting terms or payment due expectations.
`Order Date`	Business date of the order.	Use this for sales-period reporting instead of Created Date.
`Ship Date`	Expected or recorded ship date.	Use for shipping schedules, not sales booking.

Status Fields

Field	Meaning	Best report use
`Status`	Broad operational order status. Source metadata describes it as derived from fulfillment lifecycle and business workflow state.	High-level order lists and simple status grouping.
`Stage`	Legacy/source stage copied from the old sales-order record.	Historical context only. Do not use as the main operational status when newer status fields exist.
`Order Type`	Order category.	Segment orders when the business process depends on type.
`Payment Status`	Canonical payment summary derived from payment orders and payment transactions.	Paid/unpaid/partial payment reporting.
`AR Status`	Formula receivables status: Paid when balance due is 0 or less; Overdue when due date is past; Due when payment orders exist; otherwise Open.	AR dashboards and collections queues.
`Fulfillment Status`	Operational fulfillment status.	Fulfillment summary reporting.
`Fulfillment Sync Status`	Canonical fulfillment lifecycle status: pending, dispatched, acknowledged, partial, fulfilled, failed, cancelled, or alt path.	Best field for fulfillment exception reports.
`3PL Runtime Sync Status`	Last Salesforce-native 3PL runtime sync result.	Runtime troubleshooting and provider health reports.
`3PL Order Sync Tag`	Formula tag summarizing queued/synced/waiting/partial/complete/review states.	Best grouping field for operational 3PL review.

Payment And AR Fields

Field	Meaning	Use when
`Final Total`	Final order total from the order.	You need the customer-facing final amount for the order.
`Total Collected Amount`	Total collected amount across payment orders tied to the order.	You need cash collected.
`Balance Due Amount`	Remaining balance due across payment activity tied to the order.	You need open AR or unpaid balance.
`Payment Due Date`	Date payment is due.	You need aging, collections, or terms compliance.
`Days Overdue`	Number of days past due.	You need collection priority.
`Collections Date`	Date sent to or handled by collections.	You need collections workflow reporting.
`Payment Order Count`	Count of active payment orders associated with the order.	You need to know whether payment workflow exists.
`Latest Payment Transaction At`	Most recent transaction timestamp.	You need recent payment activity.
`Invoice Count`	Number of invoices linked to the order.	You need invoice coverage.

Best practice: do not use Final Total to claim money was collected. Use Total Collected Amount, Payment Status, and Balance Due Amount.

Customer Email Fields

Field	Meaning	Use when
`Customer Email Status`	Last customer-facing email attempt: Not Sent, Sent, Failed, or Skipped.	You need an overall communication status.
`Customer Email Sent Count`	Count of customer-facing emails sent.	You need volume of communications.
`Invoice Email Sent`	At least one invoice email was sent.	You need invoice communication coverage.
`Payment Link Email Sent`	At least one payment-link email was sent.	You need payment-link follow-up.
`Payment Receipt Email Sent`	At least one payment receipt/update email was sent.	You need receipt communication coverage.
`Tracking Email Sent`	At least one tracking/fulfillment milestone email was sent.	You need post-fulfillment customer notification coverage.
`Last Customer Email Error`	Last email failure message.	You need an exception report.
`Last Customer Email Recipients`	Recipients from last customer email.	You need audit/detail, not grouping.

Best practice: use the specific sent checkbox when you care about a specific email type. Use Customer Email Status for broad exception lists.

Fulfillment, 3PL, And Tracking Fields

Field	Meaning	Use when
`Sync to Fulfillment`	Whether the order should go to the fulfillment/3PL path.	Filter fulfillment reports.
`External Fulfillment ID`	Provider/external order reference, such as `Zenventory:1902282`.	Reconcile with provider systems.
`3PL Provider Display Number`	Human-facing provider order/reference.	Operations lookup.
`3PL Runtime Sync Status`	Last runtime sync result.	Runtime issue reports.
`3PL Order Sync Tag`	Summary formula for provider sync state.	Dashboard grouping.
`3PL Order Sync Issue`	Issue text from provider sync.	Exception detail.
`Fulfillment Sync Status`	Canonical fulfillment lifecycle state.	Primary operations status.
`Fulfillment Last Attempt`	Latest fulfillment sync attempt timestamp.	Stale queue or retry reports.
`Has Tracking`	True when at least one shipment/tracking record exists.	Tracking coverage.
`Tracking Count`	Number of tracking records.	Tracking volume/detail.
`Tracking Code`	Primary tracking code text.	Detail rows only; not a reliable grouping.
`Total Shipments`	Total shipment tracking records linked to the order.	Shipment coverage.
`Remaining Shipments`	Shipments without delivered date.	Delivery follow-up.
`First Tracking Received At`	First time tracking came back from fulfillment.	Time-to-tracking reports.
`First Delivered Shipment At`	First delivered shipment timestamp.	Delivery performance.
`All Items Delivered At`	Timestamp when all ordered quantities have tracking and every shipment is delivered.	Complete delivery reporting.
`AfterShip Last Refresh At`	Most recent AfterShip refresh across tracking records.	Staleness and tracking refresh reports.

Best practice: for missing tracking reports, filter on Sync to Fulfillment = true and Has Tracking = false, then include Fulfillment Sync Status, 3PL Order Sync Tag, 3PL Order Sync Issue, and First Tracking Received At.

Revenue And Totals

Field	Meaning	Use when
`Subtotal`	Order subtotal field.	Detail context when populated.
`Gross Amount`	Gross order amount.	High-level amount context.
`Gross Sales Amount`	Formula equal to `Total Order Revenue`.	Booked gross sales.
`Total Order Revenue`	Sum of booked revenue across custom sales-order lines.	Sales and margin reporting.
`Total Credits Amount`	Sum of credit-line revenue; usually negative.	Credit/adjustment reporting.
`Net Sales Amount`	Gross sales plus credits.	Net sales after credit lines.
`Final Total`	Final customer-facing order total.	Customer/order total reporting.
`Final Tax Total`	Final tax amount.	Tax reporting.
`Shipping Charged`	Shipping charged to the customer.	Shipping revenue analysis.
`Total Units`	Sum of order-line quantity in the current rollup model or legacy copied value depending on data path.	Average revenue/cost per unit and volume reports.

Example from a record: an order can show Total Order Revenue = $3,199.00, Total Credits Amount = -$566.50, and Final Total = $2,632.50. In that case, Total Order Revenue is the gross line revenue, while Final Total is the final customer-facing amount after credits.

Cost, Margin, And Commission Fields

Field	Meaning	Use when
`Total Order Cost`	Total estimated order cost across lines.	COGS/margin reporting.
`COGS (Sold Goods)`	Formula equal to `Total Order Cost`.	Readable COGS label in reports.
`Total COGS Variance`	Sum of COGS variance across lines.	Actual-vs-estimated cost review.
`COGS Variance %`	Cost variance percentage.	Cost performance.
`Cost Performance Rating`	Readable label for cost variance.	Dashboard grouping.
`Order Gross Margin`	`Total Order Revenue - Total Order Cost`.	Gross margin reporting.
`Order Gross Margin %`	Gross margin divided by revenue.	Margin trend and rep/order comparison.
`Total Line Net Margin`	Sum of line net margin.	Line-derived contribution margin.
`Total Commission Amount`	Sum of commission amount from lines.	Commission reports.
`Average Commission Rate`	Commission as percent of order revenue.	Commission rate trend.
`Net Margin After Commission`	Gross margin minus commission.	Profitability after rep cost.
`Net Margin % After Commission`	Net margin after commission divided by revenue.	Commission-adjusted margin.
`Commission to Margin Ratio`	Commission as percent of gross margin.	Payout risk.
`Commission to Revenue Ratio`	Commission as percent of revenue.	Commission burden.
`Profit At Risk`	Absolute value of negative net margin after commission.	Loss-risk reports.
`Order Profitability Tier`	Tiered label based on net margin after commission.	Executive grouping.
`Has Negative Margin`	True when the order is unprofitable after commission or has negative-margin lines.	Exception reports.
`Negative Margin Lines`	Count of lines with negative margin.	Margin investigation.

Best practice: use line-level reports when you need to know which item caused margin issues. Order-level margin fields are good for finding bad orders; line-level fields are better for fixing them.

BOM And Configuration Fields

Field	Meaning	Use when
`BOM Cost Coverage %`	Percent of order lines costed from active BOMs.	Confidence in cost/margin reporting.
`BOM Lines Count`	Number of lines whose cost basis is BOM-backed.	Cost coverage reports.
`BOM Covered Line Count`	Count of lines with BOM-backed costing.	Setup completeness.
`Lines With No Config Count`	Count of lines without commission/cost configuration.	Setup exception reporting.
`Items With Opportunity`	Count of lines with a commission-tier opportunity/nudge.	Rep optimization reports.
`Items At Max Tier`	Count of lines already at maximum commission tier.	Commission opportunity reports.
`Order Complexity Score`	Order complexity metric.	Operations/complexity review when populated.

Best practice: when BOM Cost Coverage % is low, margin reports are less trustworthy. Fix item/BOM setup before treating margin numbers as final.

RMA Correlation Fields

Field	Meaning	Use when
`External RMA Count`	Count of external RMA evidence linked to the order.	Customer return visibility.
`External RMA IDs`	Serialized external RMA identifiers.	Detail/audit.
`Primary External RMA ID`	Primary return identifier from the external RMA app.	Linking out to the external workflow.
`External RMA URLs`	External URLs for related RMA records.	Detail/audit.
`Primary External RMA URL`	Main external RMA link.	Service follow-up.
`External RMA Summary`	Summary of external RMA state.	Detail rows.
`Latest External RMA Status`	Most recent RMA status from the external app.	RMA exception reporting.
`Latest External RMA Synced At`	Last sync timestamp from the external app.	Staleness reporting.

Best practice: Salesforce is the correlation surface for external RMAs. Do not treat these fields as proof that Salesforce owns the full RMA workflow.

Address Fields

Field family	Meaning	Best report use
Delivery company/street/city/state/postal/country	Ship-to snapshot on the order.	Historical shipped-to reporting.
Billing company/street/city/state/postal/country	Bill-to snapshot on the order.	Invoice/payment address reporting.
`Shipping Address Tracker`	Reusable address record linked as ship-to.	Grouping by reusable ship-to address and address DLRS reports.
`Address Tracker`	Reusable address record linked as bill-to.	Bill-to address reporting and address rollups.
`Shipping Instructions`	Human instructions for shipping.	Detail only, not grouping.

Best practice: snapshot address fields are historical. If an Account or Address Tracker changes later, old order snapshot fields should still describe what happened on that order.

Rollup And System Fields

Field	Meaning	Use when
`Line Item Count`	Count of all sales-order lines.	Order complexity and sanity checks.
`Payment Activity Count`	Count of payment activity records.	Payment workflow coverage.
`Payment Transaction Count`	Count of transactions.	Payment activity volume.
`Invoice Count`	Count of invoices.	Invoice coverage.
`Tracking Count` / `Total Shipments`	Count of tracking/shipment records.	Fulfillment coverage.
`Metrics Last Calculated At`	Last time persisted sales-order metrics were recalculated.	Staleness/debugging only.
`Metrics Version`	Version token for recalculated metrics.	Debugging only.

Best practice: fields ending in Count, Amount, Total, Percent, Rating, Tier, or Last/Latest are often formulas, rollups, or service-maintained values. Use them in reports, but do not manually edit them.

What To Use For Common Reports

Report	Filters	Columns
Paid orders by rep	`Payment Status = Paid`, date by `Order Date`.	Sales Order Number, Account, Primary Sales Rep, Order Date, Final Total, Total Collected Amount, Total Commission Amount.
Open AR	`Balance Due Amount > 0`.	Sales Order Number, Account, Primary Sales Rep, AR Status, Payment Due Date, Days Overdue, Balance Due Amount, Total Collected Amount.
Missing tracking	`Sync to Fulfillment = true`, `Has Tracking = false`.	Sales Order Number, Account, Warehouse, Fulfillment Sync Status, 3PL Order Sync Tag, 3PL Order Sync Issue, First Tracking Received At.
Margin exceptions	`Has Negative Margin = true` or `Profit At Risk > 0`.	Sales Order Number, Account, Total Order Revenue, Total Order Cost, Order Gross Margin %, Net Margin After Commission, Negative Margin Lines.
Email follow-up	`Customer Email Status = Failed` or specific sent checkbox is false.	Sales Order Number, Account, Customer Email Status, Last Customer Email Type, Last Customer Email Error, Last Customer Email Sent On.
RMA watchlist	`External RMA Count > 0` or latest status in review states.	Sales Order Number, Account, Latest External RMA Status, Primary External RMA URL, Latest External RMA Synced At.

Fields To Avoid As Primary Filters

Field	Why
`Stage`	Legacy/source stage; newer status fields are more meaningful.
`Tracking Code`	Detail text; not stable for grouping or coverage. Use `Has Tracking` and `Tracking Count`.
`Comments` / `Internal Notes`	Useful for reading a record, weak for reliable reports.
`External RMA Metadata JSON`	Machine payload; use status/count/url fields for reports.
`External Source *` fields	Migration/integration lineage; not business state.
`Metrics Version`	Debug token, not a business metric.

On this page