# Sale Types

<p class="doc-lead">Sale Types define form types for sale transactions — supply type, document headers, bill numbering, required fields, tax behaviour, footer notes, and item filtering for the sale app.</p>

<div class="doc-toc">
<p class="doc-toc-title">On this page</p>
<div class="doc-toc-section">
<div class="doc-toc-links">
<a href="#/sales/sale-types?id=overview">Overview</a>
<a href="#/sales/sale-types?id=fields">Fields</a>
<a href="#/sales/sale-types?id=how-it-works">How It Works</a>
<a href="#/sales/sale-types?id=actions">Actions</a>
<a href="#/sales/sale-types?id=faq">FAQ</a>
<a href="#/sales/sale-types?id=related">Related</a>
</div>
</div>
</div>

<hr class="doc-section-divider">

<h2 id="overview">Overview &amp; List View</h2>

Go to <b>Sales → Settings → Sale Types</b> from the left menu.

Every sale quotation, order, invoice, and related document uses a sale type (Form Type) that controls numbering, tax rules, print headers, and validation.

<b>List columns</b>

| **Column** | **Description** |
|------------|-----------------|
| Id | Form type record ID. |
| Name | Form type name shown on sale documents. |
| Supply Type | Regular, Export, Deemed Export, SEZ, GCC Export, etc. |
| Bill Heading | Additional heading on printed bills. |
| Bill Sub Heading | Additional subheading on printed bills. |
| Branch | Branch limit when multi-branch is enabled. |
| Status | Active or Suspended. |

<b>Quick filter tabs</b>

| **Tab** | **Shows** |
|---------|-----------|
| Active | Active sale types (default). |
| Suspended | Suspended types. |

<b>Advanced filters</b>

| **Filter** | **Description** |
|------------|-----------------|
| Name | Filter by form type name. |
| Branch | Filter by branch. |
| Brand | Filter by brand when brand tracking is enabled. |
| Status | Active or Suspended. |
| Created Date | Date the type was created. |

<b>List row actions</b>

| **Action** | **Description** |
|------------|-----------------|
| View | Opens read-only type details. |
| Edit | Opens the edit form. |
| Delete | Removes the type when not referenced. |
| Suspend / Activate | Disables or re-enables the type. |

<b>Sale Types</b>

<img src="sales/images/saletype1.webp" alt="Sale Types list" loading="lazy">

<b>New Sale Type</b>

<img src="sales/images/sale-types.webp" alt="New Sale Type" loading="lazy">

<hr class="doc-section-divider">

<h2 id="fields">Fields</h2>

<h3>Basic Information</h3>

| **Field** | **Description** |
|-----------|-----------------|
| Name * | Sale type name. Must be unique. Shown as Form Type on sale documents. |
| Supply Type | Regular, Export, Deemed Export, SEZ with Tax, SEZ without Tax (India), GCC Export (Bahrain). Affects tax and compliance behaviour. |
| Description | Optional notes. |

<h3>Document Headers</h3>

| **Field** | **Description** |
|-----------|-----------------|
| Document header for sale invoice | Printed title for sale invoices using this type. |
| Document header for credit note | Printed title for credit notes. |
| Additional Heading for bills | Extra heading on printed bills. |
| Additional SubHeading for bills | Extra subheading on printed bills. |

<h3>Tax &amp; Field Settings</h3>

| **Field** | **Description** |
|-----------|-----------------|
| Require tax for every item | Blocks save when any line has no tax. |
| Exclude in tax reports | Excludes transactions of this type from tax summary reports. |
| Select Required Fields | Employee, Brand, Route (in Sale invoice), LPO Number — must be filled before approve. When <b>LPO Number</b> is selected, <b>LPO / FPO Id</b> is shown and required on documents using this sale type. |
| Select Disable Fields | Tax — hides tax fields on bills using this type. |
| Item Groups | Limits items selectable on the sale app to these groups. |
| Branch | Default branch when multi-branch is enabled. |
| Brand | Default brand when brand tracking is enabled. |

<h3>Transaction ID Format</h3>

Per transaction (Sale Quotation, Sale Order, Sale Invoice, etc.):

| **Column** | **Description** |
|------------|-----------------|
| Transaction | Document type (read-only). |
| Auto generate id | Yes/No — system assigns the next number on save. |
| Prefix | Bill number prefix. |
| Starting No | Starting sequence when auto-generate is on. |
| Suffix | Bill number suffix. |

<h3>Footer Notes</h3>

WYSIWYG footer text per document type: Sale Invoice, Sale Order, Sale Quotation, Credit Note, Pro Forma Invoice, Commercial Invoice, Sale Return Order.

<hr class="doc-section-divider">

<h2 id="how-it-works">How It Works</h2>

<ul>
<li><b>Form Type selection</b> — When a user picks a sale type on a quotation, order, or invoice, numbering rules, headers, footers, and field requirements from that type apply immediately.</li>
<li><b>Customer default</b> — Customers can have a default sale type that auto-fills Form Type on new transactions.</li>
<li><b>Tax resolution</b> — Sale type is the first key in <a href="#/sales/sale-tax-config">Sale Tax Config</a>. Item group and item rows override defaults for the same sale type.</li>
<li><b>Numbering</b> — Auto-generated bill numbers use the prefix/suffix and sequence configured per transaction on this sale type.</li>
<li><b>Sale app filtering</b> — Item Groups on the sale type restrict which items field sales users can select in the mobile sale app.</li>
</ul>

<p><b>Connected reports:</b> Filter by sale type on <a href="#/sales/reports/sale-report">Sale Report</a>, <a href="#/sales/reports/sale-report-adv">Sale Report Advanced</a>, <a href="#/sales/reports/month-wise-einvoice-summary">Month Wise Einvoice Summary</a>, and tax-related reports.</p>

<hr class="doc-section-divider">

<h2 id="actions">Actions</h2>

<b>List header:</b> <b>New</b>

| **Action** | **Description** |
|------------|-----------------|
| Edit | Opens the sale type form |
| Delete | Removes the type when not referenced |
| Suspend / Activate | Disables or re-enables the type |

<b>Form buttons:</b> <b>Save</b> / <b>Update</b>, <b>Reset</b>, <b>Cancel</b>

<hr class="doc-section-divider">

<h2 id="faq">FAQ</h2>

<b>Can two sale types share the same bill prefix?</b><br>
Prefixes should be unique per auto-generate configuration to avoid duplicate bill numbers when <b>Prevent Duplicate invoice number</b> is enabled in Sale Settings.

<b>How do footer notes appear?</b><br>
Footer notes configured here print on the corresponding document type when that sale type is selected.

<b>What are required fields on a sale type?</b><br>
Required fields (Employee, Brand, Route on sale invoice, or LPO Number) must be filled before approve. Missing LPO Number blocks approval with <b>LPO number is missing..</b>.

<b>Can a sale type require tax on every line?</b><br>
Yes. When enabled, approve fails if any item line has no tax. Pair with <a href="#/sales/sale-tax-config">Sale Tax Config</a> for defaults.

<b>How does supply type affect the bill?</b><br>
Supply type drives tax and statutory fields on quotations, orders, and invoices. Use separate sale types when domestic and export flows differ.

<b>Why was my approve blocked for duplicate bill number?</b><br>
If <b>Prevent duplicate invoice number</b> is on in <a href="#/sales/sale-settings-config">Sale Settings</a>, each sale type's auto-number prefix must stay unique.

<hr class="doc-section-divider">

<h2 id="related">Related Topics</h2>

<ul>
<li><a href="#/sales/sale-tax-config">Sale Tax Config</a></li>
<li><a href="#/sales/sale-quotation">Sale Quotation</a></li>
<li><a href="#/sales/sale-settings-config">Sale Settings</a></li>
<li><a href="#/sales/sale-settings">Sale Settings hub</a></li>
</ul>
