Sale Orders

A sale order is a customer's order for one or more law-book Full Sets or individual monthly parts. This page covers the whole order in the console: creating one, reading the order page, moving it through its 9 states, what Head Office can change after submission, sending an order back, credit and discount approvals, validation overrides, copies already handed over at booking, and printing.

Field app or console — the same order, the same rules

Many orders are captured in the Sales-Executive field app and arrive here already drafted; Head Office also keys orders in directly. Whichever way an order is created, the portal applies the same checks to it, and every button described here is checked again on the server — a stale screen or a hidden button can't get an order past a rule.

Where to find it

Open Sales → Sale Orders in the left navigation. The link appears if your role holds sale_order.view (or you are a super administrator). The list shows reference, customer, salesperson, state, net amount and booking date, newest first. Filter it by State (for example Submitted to HO for everything waiting on HO), by Product (any line), Money to recover (orders with an amount still due after payments and post-approval discounts), Pending request (a discount and/or credit request waiting for a decision) or Cancellation suggested (orders a salesperson has asked HO to cancel — see below). The search box finds an order by its reference or by the customer's name or customer ID, and the Net column sorts by amount.

The 9 states

Every order sits in exactly one state. The order page shows it as a coloured badge under the reference.

The console shows each state with the old system's name, so staff see the same wording as before:

State (diagram below)Shown in the console as
DraftDraft Sale Order
Lines confirmedDraft Sale Order (Lines Confirmed)
Ready for HODraft Sale Order (Ready for HO)
Submitted to HOPending HO Confirmation
Approved for despatchLined Up - Create Moves
In despatchSales Order
SuspendedSuspended
CancelledCancelled
CompletedDone
StateWhat it meansButton that moves it on
DraftBeing keyed. Everything — customer, addresses, lines — can still change.Confirm lines (sale_order.edit)
Lines confirmedThe lines passed their checks and are locked.Mark ready for HO (sale_order.submit)
Ready for HOThe salesperson has finished with it. No money check has run yet.Submit to HO (sale_order.submit) — the first submit also sends the customer an order confirmation when the order type asks for one (Order Types)
Submitted to HOAt Head Office. Payment, credit and discount are settled here; the badge is followed by a sub-status saying what the order is waiting for.Approve (sale_order.approve)
Approved for despatchHO has approved it; nothing has left the warehouse yet.Moves on by itself when the nightly run creates its first despatch items, or Create despatch items now (sale_order.create_despatch_now)
In despatchDelivery moves exist; stock is being reserved, picked and shipped.Completes by itself when the last delivery lands, or Complete despatch
CompletedDone. Terminal.—
SuspendedOn hold, with a reason.Resume (sale_order.cancel) returns it to exactly where it was
CancelledStopped for good, with a reason. Terminal.—
Money is settled at Head Office, not in the field

A Sales Executive can submit an order that isn't paid yet, is going on credit, or carries a discount above their limit. What that order can't do is get approved: Approve refuses it until payment (or approved credit) covers the order and any over-limit discount is approved — unless HO grants an override. Settlement is checked again at release.

An order completes itself

An order in In despatch moves to Completed on its own the moment the last outstanding delivery is recorded on Packages. It completes on delivery, not despatch. If a package is recorded Returned or Lost, its books are re-sent automatically as replacement moves and the order waits for those to be delivered too (see Packages). If an order seems stuck in In despatch, something on it is still open — a part still reserved, in transit, being re-sent or held. Clear or cancel it and the order closes.

Creating an order Built

Select New sale order on the list (needs sale_order.create). The page has three sections.

1. Customer

2. Order

FieldNotes
Order TypeRequired. Normally Standard. Only active types are offered (an order keeps its own type even if it is later switched off). A line under the select says what the chosen type needs — see Order types.
Subscription schemeThe term the order is booked under (1 Year, 3 Year…). The default scheme is pre-selected; choose No scheme for a one-off product sale. It is a reporting tag only — it doesn't add lines by itself; use Add years from scheme on the Lines tab. Only active schemes are offered (an order keeps its own even if it is later switched off). Draft only. See Subscription Schemes.
Booking dateThe day the order was taken. Can't be in the future. Prices and delivery modes are judged on this date, not today's.
Delivery priorityNormal / High / Urgent. Blank = the customer's default. It becomes the priority of the order's despatch items when they are created.
WarehouseFilled in when you work from exactly one warehouse; otherwise HO picks it. Its default location is where the order's despatch items ship from.
Relationship managerThe salesperson credited with the order. Only HO (sale_order.approve) can change it; for everyone else it is you.
Order brought byWho brought the order in; defaults to the relationship manager.
Last year's order / Parent orderLinks to another order of the same customer (turn on Linked to a parent order to see the parent picker). When the order type needs a parent order, the picker shows straight away and is marked required — you can still save the draft without it, but Submit to HO will refuse. An order can't be its own parent, and parent links can't loop.
NotesFree text.
Business associate (bookseller)The bookseller the order came through — another customer, searched like the customer picker (only customers you can order for). It can't be the customer being invoiced: "The business associate must be a different customer from the one invoiced." Marked required when the order type needs one — you can save the draft without it, but Submit to HO will refuse. Draft only.
Print options (collapsed)Title for print (Mr, Mrs, Ms, Dr, M/s) and Bill date, used on the printed quotation.

3. Lines

Optional — you can add lines after the draft is saved. Each row: product (search by code or name), carrier, quantity (whole copies only), unit price and BA / party / special discounts. The line rules apply: the unit price is locked to the product's price unless you may change it, the carrier list shows only permitted delivery modes, and each product can appear only once per order. Leave Party disc. blank to get the product's default discount.

Under the lines, a totals preview shows each line's gross, discount, GST and net, and the order total with how GST splits (CGST + SGST within the state, IGST outside it). It is worked out by the server with the same maths the saved order will use, and saves nothing. It also tells you:

Create, or Create & confirm lines

If a field is rejected on save (for example an address that isn't the customer's), the message appears under that field and nothing is saved.

Screenshot placeholderThe New sale order page: Customer section with the customer card, Order section, Lines table and the totals preview with an amber discount hint.

The order page Built

The heading is the order reference. Under it: the state badge and, where there is one, the sub-status — what the order is waiting for, or a problem to look at:

StateSub-statusMeans
Pending HO ConfirmationAwaiting free supply approvalA Free Supply or Complimentary Copy order that hasn't had its free-supply approval yet. Checked before everything else.
Waiting Special Disc. ApprovalA discount request is pending, or the discount is over the limit with no approval.
Awaiting credit approvalA credit request is pending.
Awaiting paymentNot paid in full and no approved credit covers the rest.
Ready to approveNothing blocks approval.
Lined UpWaiting ScheduleApproved, but nothing can go out yet: the next set parts aren't released, or every open delivery is scheduled for a later date.
Shipping ExceptionA flag only — the order is not moved. A package came back Returned or Lost, or a delivery is held because the carrier can't serve the address pincode. Check the order's despatch and the package.
Sales Order

The progress bar and the chips

Under the heading, chips repeat the order's Type (and subscription scheme), its priority (only when High or Urgent, in amber), the Warehouse and the Booked date. Below them a seven-step progress bar shows where the order is on its way: Draft → Lines confirmed → Ready for HO → Submitted to HO → Approved for despatch → In despatch → Completed. The current step is green and filled; steps already passed turn light green. A suspended or cancelled order is off this path, so no step is highlighted and a line underneath says so.

The three cards

Collapsed below: Amounts (gross, discount, tax) and Notes.

Money on an order

FigureWhat it is
NetThe order total: gross − discounts + GST.
AllocatedPayments allocated to the order's lines, from vouchers that are not cancelled or dishonoured. This is what counts as "paid" for approval.
ClearedThe part of Allocated whose voucher has cleared the bank. For information.
PADApproved or posted post-approval discounts, on lines or on the whole order.
RecoverableNet − Allocated − PAD, never below zero. Shown as "⚠ ₹X due" in amber when something is still owed.
Credit / DiscountThe latest credit and discount request, e.g. "Pending · ₹1,000.00".

These figures are worked out live from the payment and PAD records, so a cheque that bounces or a PAD that is approved changes them straight away.

The action bar

The order page shows one main button for the next step and puts everything else under More. You only see buttons your role allows.

StateMain buttonIn More
DraftConfirm linesEdit, Suspend, Print quotation, Cancel order
Lines confirmedMark ready for HOReopen, Record payment, Suspend, Print quotation, Cancel order
Ready for HOSubmit to HO (optionally pick an HO assignee)Reopen, Record payment, Suspend, Print quotation, Cancel order
Submitted to HOApproveEdit HO fields, Reset to draft, Request credit, Record payment, Request discount approval, Suspend, Print quotation, Cancel order
Approved for despatchCreate despatch items now (only when a released part is due)Edit HO fields, Record payment, Suspend, Print quotation / delivery report, Cancel order
In despatchComplete despatch; Create despatch items now when a newly released part is dueReserve now, Edit HO fields, Record payment, Suspend, Print, Cancel order
SuspendedResumeEdit HO fields, Print, Cancel order
Completed / Cancelled—Print

The list also offers HO Approve and Cancel directly on each row, with the same rules (the row Cancel asks for a reason and note the same way) — but the approval dialog with the blocking checklist is only on the order page.

The tabs

TabWhat's in it
LinesProduct, delivery mode, quantity, price, discount (with the Party · BA · SPL split), taxable, GST, net, allocated and recoverable ("₹X due"), a "Delivered at booking ×N" badge and the line note, with totals at the foot. On a draft you can add, edit and delete lines here; after submission HO can change a line's delivery mode and edit a line's note, and both sides can keep recovery remarks.
PaymentsPayments applied (voucher, its payment status, line, amount, who allocated it) and Credit requests, with Approve / Reject on pending ones.
AdjustmentsDiscount requests (with Approve / Reject), Post-approval discounts, Refunds and Charges. Add charge (needs charge.create) raises a draft charge against the order; leave the amount blank for the charge type's default rate.
CustomerThe customer's order history — every line across their orders, newest first, this order's rows highlighted, with a "Same product on another open order" badge — and all their phone numbers and emails. Calls & visits Planned shows a placeholder until the CRM module is live.
RelatedParent and child orders; the renewal chain — this order's last-year order, that order's last-year order and so on back, then the orders that renewed this one, oldest first (up to 10 each way), with this order marked "(this order)". An order you aren't allowed to see shows as "An order you can't view" so the gap is visible; when two orders both renewed the same one (say, a cancelled duplicate), the chain follows the latest one that isn't cancelled and names the other as "also renewed by …". And Lead batch — the renewal batch the order belongs to and the lead it was generated from, when it came from a lead (see Leads & Renewals).
Order historyEvery other order of the same customer, line by line, grouped under each order (newest first). Each order heading shows its reference, date and state; each line shows the product, quantity, price, discount, net, paid and what is still recoverable. Click a line to open its order. Only orders you are allowed to see are listed.
TimelineKey dates (received at HO, first/last confirmed and submitted, approved, released, completed, suspended/resumed, reset to draft and how many times, cancelled, and the number of days from first submission to approval) and a newest-first feed of every state change and every field change — header fields, lines and overrides — with who did it and when.
ControlsVisible to holders of sale_order.override_validation or sale_order.approve. Overrides (see below) and Attachments: upload an image or PDF (up to 10 MB; category defaults to Order form), download, delete. Uploading needs sale_order.edit or sale_order.approve; you can't upload to a cancelled order or delete from a completed or cancelled one.
Screenshot placeholderAn order in Submitted to HO: the state badge with "• Awaiting discount approval", the three cards with "⚠ ₹3,000.00 due", the Approve button and More menu, and the tab strip.

Order lines Built

A line is one product on the order. Lines can only be added or changed while the order is a Draft. The same rules apply from the field app, the API, offline sync and this console; a rejected line shows its message under the field concerned. The limits come from each product's settings: see Products.

RuleWhat happens
One line per productA product already on the order can't be added again: "This product is already on the order; change that line's quantity instead."
No price, no lineA product with no price on the booking date can't be ordered: "CODE has no current price and can't be ordered."
Quantity capAbove the product's Maximum quantity per order line: "Quantity for CODE can't exceed N per order line." The console shows the maximum under Quantity.
Price lockThe unit price is the product's MRP on the booking date. Unless the product has Allow rate change on, a different price is refused ("The price for CODE is fixed at ₹…") unless you hold sale_order.approve. In the console the field is greyed out when you can't change it.
Delivery modesIf the product has delivery modes, the carrier must be one valid on the booking date. Leave it empty and the first permitted mode is used; the console lists only permitted modes.
Ordering from the SE appIf the product's Permit orders from SE app is off, the field app can't add it. The console can.
Default party discountBlank party discount = the product's default discount %. Clearing the party discount when editing a line in the console puts the default back.
Delivered at bookingOptional: how many copies were handed over when the order was taken, and from which location. See Already delivered at booking.

Add years from scheme

For a multi-year subscription, open the draft's Lines tab and select Add years from scheme (needs sale_order.edit; drafts only). Pick the Scheme (pre-filled with the order's scheme, else the default) and the First year product. The system takes that product and follows each product's next year product link until it has as many products as the scheme's term — e.g. 3 Year from AIR Manual 2026 adds AIR Manual 2026, 2027 and 2028 — and adds one line of quantity 1 for each, then tags the order with the scheme.

GST on order lines

When a line is added it keeps a copy of the product's tax category and GST rate, so a later rate change doesn't re-price existing orders. Tax is worked out on quantity × price − discounts, at the rate for the state of the Ship-to address (CGST + SGST within the home state, IGST otherwise). Changing the Ship-to address on a draft recalculates tax. A line at 0 % GST carries no tax and needs no state on the address.

Checks at Confirm lines

Confirm lines refuses the order, listing every problem at once, if: the customer isn't verified, is flagged "do not accept order", has an expired subscription or no category; there are no lines; a product isn't orderable or has no tax category; a line needs a delivery mode or its mode is no longer permitted; the Ship-to address needs a valid state (when any line has GST) or has a placeholder pincode or region.

Discounts above the salesperson's or the product's limit don't block confirmation or submission — they send the order to HO discount approval.

Editing after submission Built

Once an order leaves Draft its customer, addresses and lines are locked. What can still change depends on the state:

StateStill editableWho
DraftEverything, via Edit and the Lines tabsale_order.edit
Lines confirmed, Ready for HOOnly title for print, bill date, notes — use Reopen to change moresale_order.edit
Submitted to HOPriority, warehouse, order brought by, relationship manager, title for print, bill date, notes; a line's delivery mode and notesale_order.approve
Approved for despatchPriority, warehouse, relationship manager, title for print, bill date, notes; a line's delivery mode and notesale_order.approve
In despatch, SuspendedTitle for print, bill date, notes; a line's notesale_order.approve
Completed, CancelledNothing—

HO uses More → Edit HO fields, which shows exactly the fields allowed in the order's current state. If someone else changed the order since you opened the page or the dialog, the save is refused with "This order was changed by someone else. Reload to see the latest." — reload and redo the change. Every change is recorded on the Timeline tab.

A warehouse can't be changed to one that doesn't contain the location recorded for copies delivered at booking.

Sending an order back: Reset to draft vs Reopen Built

ReopenReset to draft
WhoThe salesperson side — sale_order.editHead Office — sale_order.approve
FromLines confirmed or Ready for HOSubmitted to HO only
ReasonNot neededRequired (up to 500 characters); shown on the order and sent to the salesperson
Credit / discount requestsNot touched (requests can't exist before submission)Pending ones are rejected; approved ones are superseded (marked rejected, "Superseded: order reset to draft", the original approver kept on record). The corrected order needs fresh approval.
OverridesKeptKept, and still shown on the order
CountedNoYes — the Order card shows "Reset to draft N ×" and the Timeline lists first/last reset
NotificationNoneThe salesperson gets "Sale order reset to draft"

After either one the order is a Draft again and goes through Confirm lines, Mark ready for HO and Submit to HO as before.

Changing a line's delivery mode Built

On a Submitted to HO or Approved for despatch order, HO (sale_order.approve) can use Change delivery mode on a row of the Lines tab. The list offers the product's delivery modes valid on the booking date (or all active carriers if the product has none). The order's amounts don't change. Once the order is released the moves exist and the mode can no longer be switched here; on a draft, simply edit the line.

HO can also use Edit note on a row to change the line's note (up to 255 characters) while the order is Submitted to HO, Approved for despatch, In despatch or Suspended. The change is recorded in the order's history.

Recovery remarks

From Submitted to HO until the order is Completed (not on a cancelled order), each line can carry two notes about recovering its payment: the SE remark (needs sale_order.edit) and the HO remark (needs sale_order.approve), up to 500 characters each. Use Recovery remarks on the row of the Lines tab; you can only change the remark your role allows. Both are internal — never printed for the customer — and every change is recorded in the order's history. Turn on the SE recovery remark / HO recovery remark columns from the table's column menu to see them in the list. Scheduled recovery reminders are Planned.

Suggesting a cancellation Built

A salesperson who learns an order should not go ahead — the customer changed their mind, a duplicate booking — can flag it for Head Office instead of cancelling it: More → Suggest cancellation, with a reason (up to 500 characters). It needs sale_order.edit and works in any state before Completed or Cancelled. The order's state does not change; it gets a red Cancellation suggested badge next to its state, the reason (with who and when) on the Order card, and it appears under the list's Cancellation suggested filter. The order's HO assignee, if it has one, gets an in-app notice.

Suggesting again replaces the reason. More → Withdraw cancellation suggestion removes it. When HO cancels the order (or it completes) the suggestion is cleared automatically. Every suggestion and withdrawal is recorded on the Timeline.

Order types Built

Every order has a type. The type is the order's policy: how much discount it can carry, whether it has to be paid before despatch, and what it needs before Submit to HO. Administrators set types up on Order Types; the types delivered with the system are:

TypeDiscount caps (party / BA / special / per line)Payment before despatchAlso needs
StandardNone of its own — only your and the product's limitsYes—
New Subscription, Renewal10 % / 5 % / 15 % / 20 %Yes—
On Credit10 % / 5 % / 15 % / 20 %No upfront payment — the unpaid balance goes on credit at submit—
CODNone of its ownNo — paid on deliveryAn order total above ₹0
Free SupplyNot checked (free supply)NoEvery line fully discounted; free-supply approval at HO
Complimentary CopyNot checked (free supply)NoEvery line fully discounted, and an attachment (the approval letter); free-supply approval at HO

Hand delivery

A line sent by a hand-delivery carrier can only go to an address in a region the order's warehouse serves (the warehouse's Regions list; a warehouse serving a state or district covers every place inside it). If it doesn't, submit is refused — "Hand delivery isn't available from Pune WH to Nagpur." — and at release the delivery move is held as "not serviceable". Fix it by mapping the region to the warehouse, choosing another delivery mode, or (HO) granting a Hand delivery / warehouse override. An order with no warehouse yet isn't checked at submit; release checks the warehouse of the source location. Addresses with no region aren't checked.

Credit and discount approvals Built

Both are raised while the order is Submitted to HO, from More. An order can have one active (pending or approved) credit request and one active discount request at a time.

Salesperson's yearly credit limit (November 2026)

Each salesperson can have a Yearly Credit Limit (set by an administrator on Users → the user → Staff Details, next to Max Credit Outstanding; blank = no yearly limit). It is the credit they may give in a financial year (1 April – 31 March) without HO. Every approved credit on an order where they are the salesperson counts against it, whoever approved it, by the date it was approved. Payments do not give it back — if the limit is ₹1,00,000 and ₹20,000 of credit was given to one customer, ₹80,000 remains for the year even after that customer pays. It comes back only if the order is cancelled, or the credit request is rejected or superseded (Reset to draft).

An approved discount only clears approval while it still covers the order's discount; if the order's discount grows after approval, a new approval is needed.

Validation overrides Built

An override lets one order past one specific check, with a recorded reason. Grant it on the Controls tab with Grant override; only holders of sale_order.override_validation (or super administrators) see the button. A reason is required. The salesperson gets an in-app notice, and the override shows on the Order card and in the Approve dialog.

OverrideWhat it lets throughWhat it does not bypassCan be granted / revoked while the order is
Discount limitApproval without a discount approval, however far over the limits the discount is.Anything else.Draft → Submitted to HO
Payment / settlementApproval and despatch-item creation without full payment or approved credit, and the "payment pending" hold on its delivery moves.The other despatch holds — order-line credit, credit limit, full-set payment, COD or RBP/OLP packages out, pending return, carrier serviceability, minimum allocation — and stock availability. See Why a move is held.Draft → In despatch (despatch items are created for later parts while the order is in despatch too)
Duplicate productSubmission when the same customer already has one of these products on another open order, and silences the "already supplied" warning at approval.The one-line-per-product rule within the order.Draft → Submitted to HO
GST registrationSubmission and approval when the order type needs the customer's GSTIN and the customer has none (or an invalid one).Anything else; the customer form still checks the GSTIN format.Draft → Submitted to HO
Hand delivery / warehouseThe hand-delivery region check at submit, and the "not serviceable" hold on its delivery moves — for hand delivery and for a courier pincode marked unserviceable alike.Every other despatch hold, and stock availability.Draft → In despatch (so a held move can still be let through; the next reservation run frees it)
Overrides are a deliberate exception

A payment override sends goods out unpaid. Grant it only with a reason someone reviewing the order later will understand. The Dashboard's "awaiting payment" count leaves out orders with an active payment override.

Despatch items Built

An approved order needs no "release" step. Every night at 01:00 the portal creates a despatch item (a delivery stock move) for every part each Approved for despatch or In despatch order is owed: one per order line for a book, and one per released part for a subscription set. An order approved in the middle of the year gets every part already released in one go; after that it gets each new part on the night after it is released. Nothing is created twice, and a part whose item was cancelled is created again by the next run (unless the line was stopped — see below). See Background Schedulers.

Create despatch items now (sale_order.create_despatch_now, "Create Despatch Items Now") does the same for one order straight away. It shows only on an approved or in-despatch order that is owed something:

  1. Checks the money again

    If the order is no longer fully paid or credit-approved — say a cheque bounced since approval — no items are created, unless a payment override is in force. The nightly run checks the same and skips the order.

  2. Issues copies already delivered at booking

    See below.

  3. Creates a despatch item for each part owed

    From the order warehouse's default location, or — when it has none — its only in-use stock location (or only main stock location). If that doesn't settle it, the order is refused with "No despatch source location for …: set the Default despatch location on its warehouse (Warehouses > Edit)." (see System Configuration). Items carry the order's delivery priority (Normal → normal, High → urgent, Urgent → critical) and the part's value, fixed at that moment. For a set, the line's value is shared across its parts by each part's Price weight in set.

  4. Leaves them for the reservation run

    The items wait as Confirmed and are reserved — or held, with a reason — by the 02:00 reservation run. To reserve straight away, use Reserve now (stock_move.edit, in More on an in-despatch order): it runs the same hold checks on every waiting item, reserves the ones that pass — even where the carrier or warehouse is not auto-reserved — and lists the ones still held, with why.

  5. The order moves to In despatch

    With its first items. If the order type has Text the customer on, the customer is told once that the order is being prepared for despatch.

When nothing is due yet (no part released, or every item already exists), the button is hidden and the API answers "Nothing is due: every released part already has a despatch item, or no part is released yet."

Stopping later parts of a subscription

Cancelling one part's item on Stock Moves normally stops the line from that part on: later parts are never created for the order, and any later items not yet despatched are cancelled. Parts already despatched or delivered stay as they are, and the order no longer waits for the stopped parts, so it can complete. The same happens when a returned package is marked cancel subscription — the line stops from the next part. The Lines tab shows a red Stopped from part N badge on such a line.

Resume later parts on the line (stock_move.edit, approved or in-despatch orders) clears the stop: the next run creates every part released since, including ones that were cancelled.

Overriding the holds for a whole line

Override despatch holds on a line (stock_move.ignore_rules, "Override Despatch Holds") lets every open despatch item of that line past the credit and hold checks at reservation. A reason is required and each item records who did it. Stock still has to be there. To do it for one item, or to take it back, see Stock Moves.

Already delivered at booking

When an SE hands copies to the customer at the time of the order, record them on the line (Lines tab, while Draft): Delivered at booking (a whole number, 0 up to the line quantity) and Delivered from — a physical location, inside the order's warehouse when it has one. The line keeps its full quantity and price; the handed-over copies are still billed on it.

Printing Built

From More, each opens a print-ready page in a new tab; use your browser's Print (or Save as PDF). Needs sale_order.view.

Visibility — you may not see every order

With sale_order.view_all (or as super administrator) you see every order. Everyone else sees an order only if its customer is in their geography or customer scope (see Customers) or they are its salesperson. The same rule decides which customers you can pick on a new order, which orders show in a customer's history and which related-order links you can open. If a colleague mentions an order you can't find, it is almost always this scoping.

Permissions at a glance

sale_order.create new orders · sale_order.edit drafts, lines, Confirm lines, Reopen · sale_order.submit Mark ready, Submit · sale_order.approve Approve, Complete, Reset to draft, Edit HO fields, Change delivery mode, Edit note, relationship manager, non-MRP prices · sale_order.cancel Cancel, Suspend, Resume · sale_order.override_validation overrides · sale_order.create_despatch_now Create despatch items now · stock_move.ignore_rules Override despatch holds · sale_order.approve_free_supply Approve free supply · credit.* and discount.* the approval requests. See Roles & Permissions.

See also