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.
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 |
|---|---|
| Draft | Draft Sale Order |
| Lines confirmed | Draft Sale Order (Lines Confirmed) |
| Ready for HO | Draft Sale Order (Ready for HO) |
| Submitted to HO | Pending HO Confirmation |
| Approved for despatch | Lined Up - Create Moves |
| In despatch | Sales Order |
| Suspended | Suspended |
| Cancelled | Cancelled |
| Completed | Done |
| State | What it means | Button that moves it on |
|---|---|---|
| Draft | Being keyed. Everything — customer, addresses, lines — can still change. | Confirm lines (sale_order.edit) |
| Lines confirmed | The lines passed their checks and are locked. | Mark ready for HO (sale_order.submit) |
| Ready for HO | The 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 HO | At 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 despatch | HO 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 despatch | Delivery moves exist; stock is being reserved, picked and shipped. | Completes by itself when the last delivery lands, or Complete despatch |
| Completed | Done. Terminal. | — |
| Suspended | On hold, with a reason. | Resume (sale_order.cancel) returns it to exactly where it was |
| Cancelled | Stopped for good, with a reason. Terminal. | — |
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 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
- Customer — search by customer number, name or phone number. You only see customers you are allowed to order for (your geography or customer scope, or everyone with sale_order.view_all).
- Picking a customer shows a customer card: name and number, a Verified / Not verified badge, categories, region, phone, how many open orders they have and their last order. It also fills in their default addresses and their delivery priority.
- Customer already has a draft order. If the customer already has a Draft order for the same relationship manager (you, unless you pick someone else), the portal says so ("This customer already has a draft order (SO-…)") and opens that order instead. Add your lines there. Another salesperson's draft is never reused, and orders made from renewal leads always start fresh.
- A red Customer does not accept orders banner means the customer is flagged "do not accept order". The order can't be saved for them.
- Bill to, Ship to and — behind Invoice to a different address — Invoice to. Only the customer's own addresses are offered. Ship to sets the GST place of supply. Invoice to follows Bill to unless you change it.
2. Order
| Field | Notes |
|---|---|
| Order Type | Required. 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 scheme | The 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 date | The day the order was taken. Can't be in the future. Prices and delivery modes are judged on this date, not today's. |
| Delivery priority | Normal / High / Urgent. Blank = the customer's default. It becomes the priority of the order's despatch items when they are created. |
| Warehouse | Filled 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 manager | The salesperson credited with the order. Only HO (sale_order.approve) can change it; for everyone else it is you. |
| Order brought by | Who brought the order in; defaults to the relationship manager. |
| Last year's order / Parent order | Links 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. |
| Notes | Free 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:
- "Product default party discount ₹… applies." when you left party discount blank;
- ✕ in red — something the save will refuse (the product is already on the order, quantity below 1, not a whole number, or over the product's maximum);
- ⚠ in amber — a discount above the salesperson's or the product's limit: "… — HO approval will be needed." These don't stop the save; they mean HO must approve the discount (or override it) before the order can be approved.
Create, or Create & confirm lines
- Create saves a Draft with a new
SO-YYYY-#####reference — unless the customer already has a draft for the same relationship manager, in which case your lines are added to that draft and its header is kept. - Create & confirm lines (needs sale_order.edit) saves the draft and immediately runs Confirm lines. If confirmation fails, the draft is still saved and a notification lists every problem to fix.
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.
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:
| State | Sub-status | Means |
|---|---|---|
| Pending HO Confirmation | Awaiting free supply approval | A Free Supply or Complimentary Copy order that hasn't had its free-supply approval yet. Checked before everything else. |
| Waiting Special Disc. Approval | A discount request is pending, or the discount is over the limit with no approval. | |
| Awaiting credit approval | A credit request is pending. | |
| Awaiting payment | Not paid in full and no approved credit covers the rest. | |
| Ready to approve | Nothing blocks approval. | |
| Lined Up | Waiting Schedule | Approved, but nothing can go out yet: the next set parts aren't released, or every open delivery is scheduled for a later date. |
| Shipping Exception | A 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
- Financial overview — the net amount in large type, the money figures as tiles, and the recoverable amount in an amber box when something is still due. See below.
- Customer — name, number, verified badge, city, category, phone, relationship manager, brought by, the customer's current relation manager, and the bill-to / ship-to (and invoice-to, if different) addresses.
- Order parameters — type, priority, booking date, received at HO (first submission), warehouse, HO assignee, parent and last-year orders (clickable when you can see them), the business associate (when set), print title and bill date, how many times it was reset to draft, any overrides in force, and the reason for the current reset, suspension or cancellation.
Collapsed below: Amounts (gross, discount, tax) and Notes.
Money on an order
| Figure | What it is |
|---|---|
| Net | The order total: gross − discounts + GST. |
| Allocated | Payments allocated to the order's lines, from vouchers that are not cancelled or dishonoured. This is what counts as "paid" for approval. |
| Cleared | The part of Allocated whose voucher has cleared the bank. For information. |
| PAD | Approved or posted post-approval discounts, on lines or on the whole order. |
| Recoverable | Net − Allocated − PAD, never below zero. Shown as "⚠ ₹X due" in amber when something is still owed. |
| Credit / Discount | The 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.
| State | Main button | In More |
|---|---|---|
| Draft | Confirm lines | Edit, Suspend, Print quotation, Cancel order |
| Lines confirmed | Mark ready for HO | Reopen, Record payment, Suspend, Print quotation, Cancel order |
| Ready for HO | Submit to HO (optionally pick an HO assignee) | Reopen, Record payment, Suspend, Print quotation, Cancel order |
| Submitted to HO | Approve | Edit HO fields, Reset to draft, Request credit, Record payment, Request discount approval, Suspend, Print quotation, Cancel order |
| Approved for despatch | Create despatch items now (only when a released part is due) | Edit HO fields, Record payment, Suspend, Print quotation / delivery report, Cancel order |
| In despatch | Complete despatch; Create despatch items now when a newly released part is due | Reserve now, Edit HO fields, Record payment, Suspend, Print, Cancel order |
| Suspended | Resume | Edit HO fields, Print, Cancel order |
| Completed / Cancelled | — |
- Approve opens a dialog that lists what would stop approval (Blocking), anything to be aware of (Warnings — e.g. "Product X was already supplied on SO-… (completed)") and the Overrides in force. While anything blocks, the confirm button is disabled. Fix the cause — allocate the payment, approve the credit or discount request — or grant an override.
- Record payment (November 2026) — under More from Lines confirmed until the order is despatched, while anything is still unpaid; needs payment.create and payment.allocate. Enter the amount (pre-filled with what is still due), the method (Cash, Cheque, DD, NEFT, RTGS or IMPS — gateway, wallet and COD money arrive by their own routes), the instrument number, date and drawee bank where the method needs them, the collection date and an optional receipt number and remarks. One click creates the payment voucher for the order's customer, submits it, and allocates it to the order's unpaid lines in line order, so the order shows it as Allocated straight away and Approve stops blocking on payment. The voucher then follows its usual approval, deposit and clearing steps on Payment Vouchers — a despatch item is only reserved once the money covering its line has cleared.
- Create despatch items now creates the order's despatch items straight away instead of waiting for the night's run. There is nothing to choose: items ship from the order warehouse's default location. Reserve now runs the reservation checks on the order's waiting items at once. See Despatch items.
- Suspend, Resume and Cancel order need sale_order.cancel. Suspend and Cancel ask for a Reason picked from a list — Cancel offers the cancel reasons, Suspend the suspend reasons, and a few (Customer Dispute, Other) appear in both — plus an optional Note (up to 500 characters). With Other the note is required: it is the reason. The order and its Timeline show the reason's name followed by the note (for example "Duplicate Order — Same as SO-2026-00012"). Some reasons also tell the customer: with the delivered list, Customer Requested Cancellation texts the customer "Your order … has been cancelled: Customer Requested Cancellation." — the note is never sent. Which reasons exist, and which notify, is managed on Cancel/suspend reasons. Resume puts the order back in the exact state it was suspended from and clears the reason.
- What happens to the stock. Cancel order cancels every part of the order that hasn't left the warehouse, so any stock reserved for it goes back to available at once; parts already despatched or delivered (including copies handed over at booking) are untouched. Suspend pauses the order's waiting parts with the hold reason Order suspended — their reserved stock is freed while the order is on hold, the nightly reservation job leaves them alone, and the customer gets no "on hold" message. Resume releases only those paused parts: each part that was reserved goes through the same payment and credit checks as the nightly reservation run — a part that now fails one is held under that reason instead (for example full set payment) — and otherwise re-reserves its stock if it is still there (otherwise the nightly job reserves it once stock arrives); holds for other reasons, such as unpaid parts, stay as they were.
- Suggest cancellation (sale_order.edit, any state before Completed/Cancelled) — see Suggesting a cancellation.
- Stock already on a picking wave. If any part of the order is on a picking wave that hasn't been despatched or cancelled yet, Cancel and Suspend are refused: "This order has stock packed for despatch; unpack it before cancelling." A wave despatches everything on it, so the part would leave anyway. Cancel the wave on Picking Waves while it is still a draft or has items identified, then cancel or suspend the order. Once labels are printed a wave can no longer be cancelled — let it despatch and handle the return. A part that went out only partly on a wave that has already left does not block: cancelling or suspending acts on the part that is still in the warehouse.
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
| Tab | What's in it |
|---|---|
| Lines | Product, 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. |
| Payments | Payments applied (voucher, its payment status, line, amount, who allocated it) and Credit requests, with Approve / Reject on pending ones. |
| Adjustments | Discount 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. |
| Customer | The 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. |
| Related | Parent 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 history | Every 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. |
| Timeline | Key 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. |
| Controls | Visible 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. |
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.
| Rule | What happens |
|---|---|
| One line per product | A 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 line | A product with no price on the booking date can't be ordered: "CODE has no current price and can't be ordered." |
| Quantity cap | Above 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 lock | The 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 modes | If 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 app | If the product's Permit orders from SE app is off, the field app can't add it. The console can. |
| Default party discount | Blank party discount = the product's default discount %. Clearing the party discount when editing a line in the console puts the default back. |
| Delivered at booking | Optional: 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.
- Normal line rules. Each line is added exactly as if you added it by hand (price, rate lock, delivery mode, default party discount). Every year's product is priced at the order's booking date, like every other line. A next-year product whose price only starts later (a rolled-over product is priced from 1 January of its year) takes its first scheduled price instead; a product with no price at all stops the whole scheme. Adding such a product by hand is still refused until its price starts.
- Already on the order. A product already on this order is skipped, not duplicated; the message says how many were added and how many were already there.
- All or nothing. If the chain is too short ("3 Year needs 3 consecutive year products, but the chain from CODE stops after 2 (…). Create the next year product first.") or any one line breaks a rule, nothing is added.
- Afterwards the lines are ordinary lines: change or remove them freely. The create page's line list has no scheme button — create the draft, then use the Lines tab.
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:
| State | Still editable | Who |
|---|---|---|
| Draft | Everything, via Edit and the Lines tab | sale_order.edit |
| Lines confirmed, Ready for HO | Only title for print, bill date, notes — use Reopen to change more | sale_order.edit |
| Submitted to HO | Priority, warehouse, order brought by, relationship manager, title for print, bill date, notes; a line's delivery mode and note | sale_order.approve |
| Approved for despatch | Priority, warehouse, relationship manager, title for print, bill date, notes; a line's delivery mode and note | sale_order.approve |
| In despatch, Suspended | Title for print, bill date, notes; a line's note | sale_order.approve |
| Completed, Cancelled | Nothing | — |
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
| Reopen | Reset to draft | |
|---|---|---|
| Who | The salesperson side — sale_order.edit | Head Office — sale_order.approve |
| From | Lines confirmed or Ready for HO | Submitted to HO only |
| Reason | Not needed | Required (up to 500 characters); shown on the order and sent to the salesperson |
| Credit / discount requests | Not 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. |
| Overrides | Kept | Kept, and still shown on the order |
| Counted | No | Yes — the Order card shows "Reset to draft N ×" and the Timeline lists first/last reset |
| Notification | None | The 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:
| Type | Discount caps (party / BA / special / per line) | Payment before despatch | Also needs |
|---|---|---|---|
| Standard | None of its own — only your and the product's limits | Yes | — |
| New Subscription, Renewal | 10 % / 5 % / 15 % / 20 % | Yes | — |
| On Credit | 10 % / 5 % / 15 % / 20 % | No upfront payment — the unpaid balance goes on credit at submit | — |
| COD | None of its own | No — paid on delivery | An order total above ₹0 |
| Free Supply | Not checked (free supply) | No | Every line fully discounted; free-supply approval at HO |
| Complimentary Copy | Not checked (free supply) | No | Every line fully discounted, and an attachment (the approval letter); free-supply approval at HO |
- Discount caps. For each line the strictest of three limits applies: yours (the salesperson's), the product's and the order type's. A type cap of 0 % means the type adds no cap. A discount tier the type doesn't allow can't be used at all on its orders.
- No payment needed. On a type that doesn't require payment, HO can approve the order, and its despatch items are created, with nothing paid and no override. The Approve dialog lists this under Warnings ("COD order: no payment is required before despatch."; for free supply: "… supplied free of charge — no payment or discount approval is required; it needs the free-supply approval before this one.").
- On Credit (November 2026). No payment is needed up front. When the order is submitted to HO, whatever is unpaid goes on credit by itself: the part that fits in the salesperson's yearly credit limit (and in the customer's credit limit, if that is enforced) is approved at once in the salesperson's name; anything beyond waits as a pending credit request, so the order shows Awaiting credit approval until HO approves or rejects it. Nothing happens if the order is already fully paid or already has a pending or approved credit request (for example when it is resubmitted after a reset). The order is not held at despatch for a minimum payment by its type (the product's own minimum, if any, still applies).
- Free-supply approval (November 2026). A Free Supply or Complimentary Copy order needs no payment and no credit (credit can't be requested on it), but it does need an approval: while it is Submitted to HO its sub-status is Awaiting free supply approval and Approve is refused with "Free supply needs approval first." Someone with sale_order.approve_free_supply clicks Approve free supply on the order page (the field app/API:
PATCH /api/v1/sale-orders/{id}/approve-free-supply); HO can then approve the order as usual. Reset to draft clears the free-supply approval, because the order can change. - Free supply. Free Supply and Complimentary Copy orders are exempt from every discount limit — yours and the product's too — so they never need a discount approval. Their lines are priced at ₹0 automatically (November 2026): when you add or edit a line, its whole value goes on the special discount. Switching a draft to a free-supply type zeroes its existing lines; switching it back puts them on normal pricing (the product's default party discount) for you to adjust. Submit still checks that every line nets to ₹0.
- Parent order. A type that needs a parent order refuses submit until Parent order is set: "This order type needs a parent order."
- Attachment. A type that needs an attachment refuses submit until the order has at least one: "This order type needs an attachment (e.g. the approval letter) before it can be submitted." Upload it on the Controls tab (Attachments → Upload), or the salesperson attaches it from the field app.
- GSTIN. A type set to need the customer's GSTIN refuses submit until the customer has a valid 15-character GST registration number (e.g.
27ABCDE1234F1Z5) on their customer record: "This order type needs the customer's GST registration number (GSTIN)." HO approval checks it again, so removing the GSTIN after submit blocks approval. None of the delivered types asks for it — administrators turn it on per type. HO can let one order through with a GST registration override. - Business associate. A type set to need a business associate refuses submit until Business associate (bookseller) is set: "This order type needs a business associate (bookseller)." None of the delivered types asks for it — administrators turn it on per type.
- Product minimum payment and no-upfront-payment types. (November 2026) On Credit, COD, Free Supply and Complimentary orders are not held by a product's own minimum payment % (per line or for the whole order) — they take no payment up front by design. A minimum % set on the order type itself still applies.
- Minimum payment for the whole order. A type that requires payment can also set a minimum share of the whole order that must be paid before anything is despatched. The stricter of the type's and the product's minimum applies; until it is reached the order's delivery moves are held as "minimum allocation". Types that don't require payment (COD, free supply) ignore the type's value.
- COD needs an amount. A COD order must have something to collect: an order whose total is ₹0 (for example a fully discounted copy) is refused at submit — "A COD order must have an amount to collect." Use a free-supply type for free copies.
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.
- Request credit (credit.request_approval or credit.grant_directly) — amount (blank = the unpaid balance) and a reason. With credit.grant_directly the credit is approved at once, within the customer's credit limit, your own ceiling and — on your own orders — your yearly credit limit; otherwise it waits for approval. Not available on free-supply orders.
- Request discount approval (discount.request_approval) — asks HO to approve the order's current total discount. Refused if the discount is already within limits.
- Deciding — on the Payments tab (credit, credit.approve) or Adjustments tab (discount, discount.approve), use Approve or Reject on the pending row, with optional remarks. When a request is rejected, the person who raised it gets an in-app notice ("Discount request rejected" / "Credit request rejected") with the remarks.
- Editing the reason — while a request is pending, the person who raised it, or anyone who can approve it, can correct its reason with Edit reason on the row (up to 1,000 characters). Once decided, the reason is fixed.
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).
- When the salesperson grants credit on their own order, or approves a credit request on it, the amount must fit what is left: "Your yearly credit limit has only ₹X left." The On Credit automatic credit uses the same limit.
- HO (anyone else with credit.approve) can approve beyond the salesperson's limit; the amount still counts as used.
- The limit, used and remaining amounts show under the field on the user page, in the credit request Approve dialog (for the order's salesperson), and in the field app (
GET /api/v1/me→yearly_credit).
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.
| Override | What it lets through | What it does not bypass | Can be granted / revoked while the order is |
|---|---|---|---|
| Discount limit | Approval without a discount approval, however far over the limits the discount is. | Anything else. | Draft → Submitted to HO |
| Payment / settlement | Approval 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 product | Submission 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 registration | Submission 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 / warehouse | The 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) |
- Only one override of each kind can be active on an order. The Grant override list only offers kinds that are still open for the order's state and not already active.
- Once the order has passed the check an override bypasses, it can no longer be granted or revoked (the window column above). Overrides can't be changed on a suspended or cancelled order.
- Revoke on an active override ends it; the row stays in the history with who revoked it and when.
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:
- 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.
- Issues copies already delivered at booking
See below.
- 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.
- 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.
- 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.
- When the order's first despatch items are created, those copies are taken out of stock at that location straight away, as a completed delivery move marked "Delivered at booking". No reservation or hold checks apply to them — they have already left. If that location doesn't have the stock, creation stops with "Insufficient stock of CODE at LOCATION for the copies delivered at booking."
- Only the remaining quantity gets a normal delivery move.
- If every line was fully delivered at booking, there's nothing to despatch: the order goes straight to Completed when those copies are issued.
- The Lines tab shows a "Delivered at booking ×N" badge, and the delivery report prints the quantity.
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.
- Print quotation — with the company header; Print quotation (no header) for pre-printed stationery. Shows the title for print, bill-to (the invoice address if set), "Through: …" with the business associate when one is set, the bill date (or the approval date), lines, CGST + SGST or IGST, and the amount in words. Available in every state.
- Print delivery report — each line with its delivery mode, copies delivered at booking and its delivery moves. Only once the order is approved, in despatch or completed.
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.
See also
- Customers — the customer record, addresses and scoping.
- Payment Vouchers — recording and allocating the payments that settle an order.
- Order Types — setting up the types and their policy.
- Discounts, Refunds & Charges — discount limits, PADs, refunds and charges.
- Stock Moves — the despatch items created for an order, and why one may be held.
- Picking Waves and Packages — what happens after reservation.
- Notifications — the notices an order's state changes send.
- Subscription schemes — the multi-year terms and their year-line helper.
- Cancel/suspend reasons — the reasons offered when cancelling or suspending, and which ones notify the customer.