Skip to content
User Manual · Chapter 3 — Sales

Sales Order

Figure 3.2 — The Sales Order form. Drawing to be produced after the UI/UX pass: annotated capture of the order form naming the customer and currency header, the dimension fields, an order line, and the totals block.

  • Credit hold banner — not a field but a warning the form carries when the order is held: the reasons, since when, and any override in force (§3.5).
  • Code — the order number (SO-…), from your sequence, quoted on every document that follows from this order.
  • Sales Channel — where this sale came through (direct, or a marketplace). It feeds channel reporting and explains marketplace fees on receipts later.
  • Customer — choosing one sets the document's currency, fills the exchange rate from the stored table, pulls the territory and sales rep, re-prices any lines already present, refreshes every line's tax, and shows the customer's credit position as a hint while you work.
  • Date — the order date; the exchange rate follows it.
  • Required Date — when the customer needs the goods; the date fulfilment is planned against.
  • Valid until — read-only once the order exists: the date this order's prices are guaranteed to, stamped at creation from your company's sales validity days. It moves only through the Extend validity or Re-price actions, deliberately, never silently.
  • Currency and Exchange rate — the currency this order is promised in, defaulting from the customer. The rate fills from the stored rates for the order's date; where no rate is stored the field stays blank rather than inventing one, and an order in a foreign currency cannot proceed until a rate exists. The rate is frozen onto the order — it is part of the promise.
  • Branch, Department, Sales rep, Territory — the dimension fields, shown for the dimensions your company tracks (0.6). They default from you and from the customer's allocation, and they follow the document into the reports that slice by them.
  • Campaign — optional: the campaign this order belongs to, where you are tracking one (§3.9). Stamping an order ties it to that campaign directly; leaving it blank is always fine, and an unstamped order inside a campaign's dates is still counted alongside it by date.
  • Narrative — free text: the story of this order, carried with it permanently.

The Order Lines repeat for each product:

  • Product — picking one brings its selling price from the price grid (Chapter 6): a price set directly in the order's currency where one exists, otherwise the catalogue price converted at the order's rate.
  • UOM — the unit the quantity is counted in; defaults from the product, changeable where the product allows conversions.
  • Warehouse — where these goods will be delivered from.
  • Quantity — how many, in that unit.
  • Unit Price — in the order's currency. You may override the grid price; the figure you leave here is the figure the customer was promised, and the invoice will inherit it. Separately, the line quietly freezes the product's list (grid) price at the moment of sale: discount and margin analysis compares what you actually charged against the list price the sale was made against — never against today's list, which may have moved since. Lines from before this capture carry no frozen price and are left out of that comparison, with the coverage stated.
  • Ext. Amount and VAT — computed per line: quantity × price, and the tax that follows from the customer's tax position and the product's tax code. You read them; you do not type them.

Order Totals close the form: Subtotal, VAT, and Order Total — the value of the commitment, and the amount that will count against the customer's exposure once approved.

Snapshot: portal-v0-2026-11-10