Overview
Sale runs allow you to reproduce sale shipments for customers on a regular basis. This is ideally suited to fixed non-stock charges like service fees.The process creates sale shipments not sale orders, so it does not suit cases where stock needs to be back ordered regularly. If stock does need to be back orders. You can click a button on the sale shipment to create a sale order. The sale order will track the back order quantity.
...
Field | Description |
---|---|
Type | SALRUN (Sale Run). Transaction type |
Number | Unique transaction number generated by the system |
Status | Position of the transaction, OPEN, POSTED, INPROGRESS |
Date | Date on the Sale Run. This is the date that the system will use when you generate a Invoice |
Description | Best describes the Sales run |
Sale Run Type |
|
Workflow Status | Active or Inactive |
Sale Run Set | The name of the Sale Run Set templated used |
Last Run For | The date the sale run was to run for based upon the settings on the General Tab |
Last Run Actual | The date the sales run actually ran (date created) based upon the settings on the general tab and weekend handling |
Combine Charge To | If this tick is ON and you have a range of customers with the same Charge to Cardid on the Card itself, the system will create a single shipment/invoice for each chargeto customer in that sale run |
Lines Tab
Field | Description |
---|---|
Product | Product to be Invoiced on the Sale Run |
Name | Name of the product |
Qty | Quantity to be invoiced |
Unit | Unit of measure for the product |
Unit Quantity On Hand | Stock on hand |
Price Ex | Price Ex GST |
Price Inc | Price Inc GST |
Disc | Discount percentage if applied |
Tax Code | Tax Code on the product |
Tax Value | Value of tax |
Tender | Ability to set a default tender to the run |
Value | Total Value of each product line to be invoiced |
...