# Loading Request

<p class="doc-lead">A Loading Request prepares goods for dispatch against a sale order. It lists the items and rolls to be loaded at a center, then moves through a load-and-verify workflow before a packing slip is created. A Loading Request is a preparation and verification document — it does not post to stock or accounts.</p>

<div class="doc-toc">
<p class="doc-toc-title">On this page</p>
<div class="doc-toc-section">
<span class="doc-toc-group-title">Getting started</span>
<div class="doc-toc-links">
<a href="#/inventory/loading-request?id=overview">Overview &amp; List View</a>
<a href="#/inventory/loading-request?id=quick-start">Quick Start</a>
</div>
</div>
<div class="doc-toc-section">
<span class="doc-toc-group-title">Form reference</span>
<div class="doc-toc-links">
<a href="#/inventory/loading-request?id=header-fields">Header Fields</a>
<a href="#/inventory/loading-request?id=item-lines">Item Lines</a>
</div>
</div>
<div class="doc-toc-section">
<span class="doc-toc-group-title">More</span>
<div class="doc-toc-links">
<a href="#/inventory/loading-request?id=workflow">Loading Workflow</a>
<a href="#/inventory/loading-request?id=actions-status">Actions &amp; Status</a>
<a href="#/inventory/loading-request?id=posting">Posting Behavior</a>
<a href="#/inventory/loading-request?id=master-update">Master Update</a>
<a href="#/inventory/loading-request?id=view-tabs">View Tabs &amp; Widgets</a>
<a href="#/inventory/loading-request?id=best-practices">Best Practices</a>
<a href="#/inventory/loading-request?id=faq">FAQ</a>
<a href="#/inventory/loading-request?id=related">Related Topics</a>
</div>
</div>
</div>

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

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

The Loading Requests list shows every request with its id, number, customer, loading center, the linked sale order, employee, date, and status. Use the quick filter tabs to switch between views, and Advanced Filters to narrow the list. From the list you can create a new request, open an existing one, edit a draft, or delete a draft.

<b>List columns</b>

| **Column** | **Shows** |
|------------|-----------|
| Id | Request reference number. |
| Number # | Loading request number. |
| Customer | Customer the goods are being loaded for. |
| Loading Center | Center the goods are loaded from. |
| Sale Order | Linked sale order. |
| Employee | Employee handling the request. |
| Date | Request date and time. |
| Status | Current status of the request. |

<b>Quick filter tabs</b>

| **Tab** | **Shows** |
|---------|-----------|
| Default | All requests except cancelled ones. |
| Approved | Requests that have been approved. |
| Draft | Requests saved but not yet started. |
| Cancelled | Requests that have been cancelled. |
| Closed | Requests that have been closed. |

<b>Advanced Filters</b>

Id, Bill No, Customer, Loading Center, Employee, Item, Notes, Status, Date, and Created date.

<b>List row actions</b>

| **Action** | **Available when status is** |
|------------|------------------------------|
| Edit | Draft |
| Delete | Draft |
| View | All statuses |

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

<h2 id="quick-start">Quick Start — Create a Loading Request</h2>

<h3>1. Navigate</h3>
Go to <b>Inventory → Loading Requests</b> from the left menu.

<h3>2. Create new request</h3>
Click <b>New</b> to open the request entry screen.

<h3>3. Fill in details</h3>
<ul>
<li>Set the <b>Date *</b> and, if numbering is manual, the <b>Number</b>.</li>
<li>Pick the <b>Sale Order Id</b> to load against, then confirm the <b>Customer *</b>.</li>
<li>Set the <b>Loading Center</b> and <b>Employee</b>.</li>
<li>Review the item lines — items, rolls, and quantities are pulled in from the sale order.</li>
</ul>

<h3>4. Save</h3>
<ul>
<li><b>Save</b> — keeps the request as a <b>Draft</b>.</li>
<li><b>Reset</b> / <b>Cancel</b> — clears or closes the form without saving.</li>
</ul>

<h3>5. Load and verify</h3>
Use <b>Start</b> to begin loading, <b>Verify</b> to scan and confirm the loaded items, then <b>Create Packing Slip</b> once the request is approved. See <a href="#/inventory/loading-request?id=workflow">Loading Workflow</a>.

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

<h2 id="header-fields">Header Fields Reference</h2>

| **Field** | **Description** |
|-----------|-----------------|
| Date * | Date and time of the request. |
| Number | Loading request number. Hidden when numbering is auto-generated. |
| Sale Order Id | Approved sale order the goods are loaded against. Picked from the sale order list. |
| Customer * | Customer the goods are loaded for. |
| Employee | Employee handling the loading. |
| Loading Center | Center the goods are loaded from. |
| Branch | Branch for the request. |
| Notes | Remarks about the request. |

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

<h2 id="item-lines">Item Lines — ITEMS</h2>

Item lines are pulled from the linked sale order and are read-only on the request.

| **Column** | **Description** |
|------------|-----------------|
| Sl Num | Line serial number. Auto-numbered. |
| Item | Item being loaded. |
| Roll No. | Roll number for roll-tracked items. |
| Length | Roll length, where applicable. |
| Width | Roll width, where applicable. |
| Quantity | Quantity to load. For rolls, calculated from length × width. |
| Unit | Unit of measure. Defaults from the item. |
| Status | Line status during loading — <b>Pending</b>, <b>New</b>, or <b>Verified</b>. |

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

<h2 id="workflow">Loading Workflow</h2>

A Loading Request moves through a load-and-verify cycle before it is fully approved:

<ul>
<li><b>Start</b> — begins loading. The request moves into loading and lines start as <b>Pending</b>.</li>
<li><b>Verify</b> — scan or enter the barcodes of the rolls and items actually loaded. Matched lines are marked <b>Verified</b>; any scanned items not on the request are added as <b>New</b> lines.</li>
<li><b>Resolve</b> — settle outstanding lines so every line reaches a verified state. When all lines are resolved or verified, the request is approved automatically.</li>
</ul>

Once approved, you can create a <a href="#/inventory/packing-slip">Packing Slip</a> for the loaded goods.

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

<h2 id="actions-status">Actions &amp; Status</h2>

<h3>View toolbar actions</h3>

| **Action** | **Description** | **Available when status is** |
|------------|-----------------|------------------------------|
| Edit | Opens the request for editing. | Draft |
| Delete | Permanently removes the request. | Draft |
| Clone | Creates a copy of the request. | All (if permitted) |
| Print | Prints the request. | All |
| Export | Exports the request to a spreadsheet. | All |

<h3>More menu (⋮) actions</h3>

| **Action** | **Description** | **Available when status is** |
|------------|-----------------|------------------------------|
| Start | Begins loading on the request. | Draft |
| Verify | Opens the verification screen to scan loaded items. | Loading in progress |
| Resolve | Settles outstanding lines so loading can complete. | Loading in progress, awaiting resolution |
| Create Packing Slip | Opens a new packing slip for the loaded goods. | Approved, Closed |
| Cancel | Cancels the request. | Approved, Closed |
| Add/Update Note | Adds or edits a note on the request. | All |
| Master Update | Updates selected header fields without reopening the full form. See <a href="#/inventory/loading-request?id=master-update">Master Update</a>. | Approved, Closed, Returned, Partially Returned |

<h3>Statuses</h3>

| **Status** | **Description** |
|------------|-----------------|
| Draft | Saved but not yet started. Can be edited or deleted. |
| Approved | Loading completed and verified. Ready for a packing slip. |
| Closed | Request is closed — typically once a linked packing slip is processed. |
| Returned | Goods loaded against the request have been returned. |
| Partially Returned | Some of the loaded goods have been returned. |
| Cancelled | Request has been cancelled. |

> While loading is underway the request shows an in-progress state, and each line carries its own status of <b>Pending</b>, <b>New</b>, or <b>Verified</b>.

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

<h2 id="posting">Posting Behavior</h2>

A Loading Request does <b>not</b> post to inventory or to your accounts. It is a preparation and verification document that lists what should be loaded against a sale order and confirms what was actually loaded. Stock movement happens on the documents created downstream, such as the <a href="#/inventory/packing-slip">Packing Slip</a> and the dispatch and invoicing documents.

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

<h2 id="master-update">Master Update</h2>

<b>Master Update</b> lets you change selected header fields on an approved request without editing the full document or item lines. Open the three-dot menu on the request and select <b>Master Update</b>.

| **Field** | **Can be updated?** | **Notes** |
|-----------|---------------------|-----------|
| Date * | Yes | Cannot be set before the accounts closing date. |
| Sale order, customer, item lines | No | These come from the linked sale order and cannot be changed here. |

Click <b>Confirm</b> to save changes or <b>Cancel</b> to close without saving.

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

<h2 id="view-tabs">View Tabs &amp; Side Panels</h2>

When you open a request in full view, the right side shows tabbed panels. Click the expand icon on a tab to open the same data in a larger modal.

<h3>Top panel</h3>

| **Tab** | **What it shows** |
|---------|-------------------|
| Summary | Documents linked to this request, such as the sale order and packing slips. |

<h3>Bottom panel</h3>

| **Tab** | **What it shows** |
|---------|-------------------|
| History | Activity log — who created, started, verified, or cancelled the request and when. |
| Attachments | Files uploaded to this request. |

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

<h2 id="best-practices">Best Practices</h2>

<ul>
<li>Pick the correct <b>Sale Order Id</b> so the right items and rolls are pulled into the request.</li>
<li>Use <b>Start</b> before loading, then <b>Verify</b> by scanning so the loaded goods are confirmed against the request.</li>
<li>Use <b>Resolve</b> to clear any unverified lines before the request completes.</li>
<li>Create the <a href="#/inventory/packing-slip">Packing Slip</a> only after the request is approved, so packed quantities match what was loaded.</li>
</ul>

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

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

<b>Does a loading request reduce stock?</b><br>
No. It prepares and verifies goods for dispatch. Stock movement happens on the packing slip and the dispatch and invoicing documents that follow.

<b>Why are the item lines read-only?</b><br>
Item lines come from the linked sale order. Loading and verification update line status rather than the lines themselves.

<b>What happens when I scan an item that isn't on the request?</b><br>
During <b>Verify</b>, an unexpected scanned item is added to the request as a <b>New</b> line so it is captured.

<b>When does the request get approved?</b><br>
The request is approved automatically once every line is verified or resolved.

<b>What is the loading workflow after approval?</b><br>
Create a <a href="#/inventory/packing-slip">Packing Slip</a> from the request, then a delivery note or invoice to move stock and bill the customer.

<b>Can I cancel a loading request?</b><br>
Yes, while no approved packing slip or delivery is linked. Cancel downstream documents first if they exist.

<b>Does loading request affect available stock?</b><br>
No. It verifies quantities against the sale order; stock moves on the delivery note or invoice.

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

<b>Related documentation</b>
<ul>
<li><a href="#/inventory/packing-slip">Packing Slip</a> — pack the loaded goods for dispatch.</li>
<li><a href="#/inventory/goods-delivery-note">Delivery Note</a> — record goods leaving stock for the customer.</li>
<li><a href="#/inventory/shipment">Shipment</a> — capture transport documentation for the consignment.</li>
<li><a href="#/inventory/inventory-item">Item</a> — configure items and roll tracking used on the request.</li>
</ul>
