Print Pickslip
In POS.26.13 (Print Pickslips) the ‘Status’ has been modified to have a ?? button and a new option of O,E has been added that will print any un-printed orders regardless as to weather or not it has an ebook only.
In POS.26.13 (Print Pickslips) the ‘Status’ has been modified to have a ?? button and a new option of O,E has been added that will print any un-printed orders regardless as to weather or not it has an ebook only.
Department Sales
Below is an overview of the Department Sales report.
Path: POS-RP-1-5-2
Purpose: Display the gross to net numbers by department.
Output: Date, Department Codes, Department Sales, Department Returns, Department Discounts, Department Markdowns, Department Net, Merchandise Net, Non-Merchandise Net, Non-allocated Discounts, Total Taxes, Transaction Net.
The summary output combines the sales information for the entire day.
The Detailed version breaks the sales figures out by register.
Below is an overview of the Store Sales by Store by Register by Date report which is virtually identical to the Store Sales by Store by Date by Interval.
Path: POS-RP-1-4-1 and POS-RP-1-4-2
Purpose: These reports are used to display the number of transactions, dollar amount and item count for a given time period. This can be in detail or summary format, with store and/or date sub totals.
Output: Register, Date, Time Interval (default 30 mins) Time Transactions (transactions in time period), Time LI (line items per time period) Time Sales (dollar amount sold in time period) Time Elapsed (time between sales) Average Tran.Time (average transaction time), Secs Per Line Item, Cust Count (edge case typically not used)
A Summary can be run to get the ending value for each day, but the true value is in the detailed version of the report.
Below is an overview of the Class Detail by Date by Class report. General information on what fields are available, what they do and what data is presented in the report.
Path: POS-RP-1-3-3
Purpose: This report is used to display high level information of class dollar amounts per day.
Output: Store, Report Group (optional), Description, Sales, Returns, Markdowns, Discounts, Class Net, Cost Quantity.
Over a one day date range this report looks very similar to other class reports. Just like those reports though, the multiple days is what makes the report unique.
This screenshot shows a single day with the “Sort by Report Code” field set to a Y. The Y for this field triggers the optional Report Group column. If this field is a N then the column is removed.
In this example we have six days worth of data. The format of this report remains the same, the numbers simply include more days.
Sort by Report Code: Allows you to override the numerical listing of class codes into their class report group. This is essentially an override of the default numerical sorting of class codes.
Creating a class Report Category is found in POS-22-3-5. Once a category has been created you can assign it to the classes belonging to that report category in POS-22-3-2.
Note: the most common fields are covered in the Reports: Best Practices and Procedures article. Only special usage scenarios or options are covered in this article.
Below is an overview of the Detail by Transaction Number report. General information on what fields are available, what they do and what data is presented in the report.
Path: POS-RP-1-3-2
Purpose: This report is used to display high level class dollar amounts per class.
Output: Class, Class Description, Sales, Returns, Net Sales, Markdowns, Discounts, Class Net, Cost, Quantity and Margin.
At first glance the data is very similar to the Class Detail by Date by Class report if you only run it for one date.
However, the format changes when you run it for multiple dates. The focus is on the class data, then by date. So class 100 is all grouped together across the date range, totaled for the date range, and then class 101 is reported for the date range, etc.
This example is for a six day span.
There are no unique fields in this report.
Note: the most common fields are covered in the Reports: Best Practices and Procedures article. Only special usage scenarios or options are covered in this article.
Below is an overview of the Class Detail by Date by Class report. General information on what fields are available, what they do and what data is presented in the report.
Path: POS-RP-1-3-1
Purpose: This report is used to display high level information of class dollar amounts per day.
Output: Class, Class Description, Sales, Returns, Net Sales, Markdowns, Discounts, Class Net, Cost, Quantity and Margin.
What makes it unique from the other class reports is the formatting when it spans multiple days. The focus is on the date, then the class totals. So the report displays the first date with all class totals, then the next day with its class totals, etc.
The screenshot below shows data on two days.
There are no unique fields in this report.
Note: the most common fields are covered in the Reports: Best Practices and Procedures article. Only special usage scenarios or options are covered in this article.
Below is an overview of the Consolidated by Register report. General information on what fields are available, what they do and what data is presented in the report.
Path: POS-RP-1-2
Purpose: This report is used to display a high level summary of the transactions done on each register. The total amount of money done, total markdowns, cost of goods sold, gross margin of goods sold, etc. for the date range specified.
Output: Register, Quantity, Sell Price Extended, Item Discount Total, Item Markdown Total, Transaction Discount Markdowns, Net Sales, Tax Total, Trans Total, Tender Total, Net Cost Extended and Gross Margin.
A/R Invoice: Allows you to specify an AR Invoice number to view the other transaction details.
Note: the most common fields are covered in the Reports: Best Practices and Procedures article. Only special usage scenarios or options are covered in this article.
Below is a list of the most common report fields and what they do. The purpose of this article is to avoid having to specify “the Store field restricts the report to the specified store” on every single report article.
There is also a best practices on the more optimal ways of running reports. This includes how to report on multiple class or department codes, what to do when you get a “0 records listed” response as well as other things.
Below is an overview of the Detail by Transaction Number report. General information on what fields are available, what they do and what data is presented in the report.
Path: POS-RP-1-1
Purpose: This report is used to display detailed information on every transaction that meets the selection criteria.
Output: Register, Transaction #, Date, Time, Cashier Code, Transaction Type, Post Void status, Scanned Items, Item Descriptions, Quantity, Sell Price Extended (qty * price), Item Discounts, Transaction Discounts, Tax Total, Transaction Total and Tender Code.
A/R Invoice: Allows you to specify an AR Invoice number to view the other transaction details.
Note: the most common fields are covered in the Reports: Best Practices and Procedures article. Only special usage scenarios or options are covered in this article.
Below is the layout of the Reports menu in the POS module in an ordered list. The purpose of this page is to allow for a searchable list of reports. This is a constant work in progress, so some details may not be available at this time.
Clicking on a report name will navigate to a page with an example of what the report looks like, a brief summary of what the report will report on as well as explanations of the fields used to generate the report. Please note that every field definition is not listed for every single report, instead the most common fields are covered in the Reports: Best Practices and Procedures article. Only special usage scenarios or unique field options are covered in the individual report articles.
The numbering of the list reflects the path numbering of the reports. For instance, the Tender/Register Summary Report (RP-2-21) is down in section 2; Tender Reports, option 21 for Tender/Register Summary. At first glance it can be a little jarring to see the list go from 5 to 21 but it was necessary to keep the options true to the screen layout.