The sales order detail view

TL;DR

One order in full: its header, its acquisition, every transaction that followed it, and its lines, discounts and taxes. It is the fastest way to see an order's whole chain in one place.

/transactions/salesorderdetail/<id> shows a single sales order. It is reached from the sales orders table and has no navigation entry of its own, which is the documented exception for a detail sub-view. An id that resolves to nothing renders the page empty rather than erroring.

What is on it

The order. Its CCC id and NetSuite id, its status, the transaction date, the creation moment, the amount in VAT, the cost of goods estimate, the currency and the Paazl shipping option and delivery type. When the order is not in euros it also shows the foreign amount and the exchange rate it was converted at, so the conversion is visible rather than implied.

Its acquisition. Sales channel, country, and the source and medium both as resolved and as it arrived raw. Seeing both is the point: a resolved value that looks wrong is checked against the raw one here. See source and medium.

Its related records. Every prepayment, item fulfillment, invoice, return authorization, item receipt and credit memo whose classification points at this order, each with its NetSuite number linked straight into NetSuite. This is the order's chain in one list, in that order, which is also roughly the order events happen in.

Its lines. Item lines and non-inventory lines with quantity, SKU, description, amount and cost estimate, then the discount lines and the tax lines. Foreign amounts appear beside the euro amounts on a non-euro order, line by line.

Reading it

A short related-record list is usually timing, not breakage. An order that has shipped but not yet been invoiced has a fulfillment and no invoice, because they are separate upstream transactions that need not arrive together. See item fulfillments.

The cost estimate is an estimate. It is what the order expected the goods to cost. What they actually cost arrives on the fulfillment and is what realised cogs is built from.

Related records are found through classifications, so a transaction that has arrived but not yet been classified does not appear here yet.

Evidence

Sections and fields from templates/main/transactions/salesorderdetail.tpl. Id handling from app/http/transactions/salesorderdetail.php. The related-record set, its order and its join through the classification tables from salesorders->getsalesorderrelatedrecords(). The nav exception from AGENTS.md, Templating and frontend. Basis: code-checked at 30f5313.

On this page
About this document