Add or Change a Designated Printer

In the TCS application on the computer that needs the printer added or changed.

• First, the printer needs to be added to Windows, it MUST exist in Windows before it can be added to the TCS application. You may need to reach out to your school IT department to add the printer to your computer.
• Once the printer exists in Windows, you close/start the TCS application.
• Select the ‘Properties’ icon on the tool bar,
• Select the tab ‘Other’,  
• Select the Printing Type that you need to make the change for, the options are
  • Receipt Printing
  • Report Printing
  • Barcode Printing
  • Display Pole Printing
  • Alt Printers.
• Once the printing type is selected, use the drop down menu to select which printer to use for the associated printing type.  
• Select the option to ‘Apply’ and then ‘Close’ to save the changes.    

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.

Unique Field Options

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.

Unique Field Options

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.

Unique Field Options

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.

Unique Field Options

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.

Common Practices

• Populate as few fields as possible to get the information you need.
  • Data presented in a report is information that meets every single field criteria.
  • If you get a response of “0 records to display” then consider widening your parameters. Filling out every single field will rarely work.
  • e.g. If you specify: “Store 1, Register 101, Beginning Date 8/1/18, Ending Date 8/1/18, Department 90, Class 101, SKU 9781234567890, Tran Type RT, WEB Transactions N, History file N” you probably won’t get anything.
    • If you remove the tran type criteria, or the department and class fields (you’re specifying the item anyways) then you may get some results.
• Multiple criteria can be entered into most fields by separating them with a comma.
  • e.g. If you want to report on class numbers 101,102 and 103 you will enter them as 101,102,103
• There is currently no way to report on “everything except” unless you enter every valid option.
  • e.g. If you want to report on every class other than 101 you would have to enter every class code except 101, into the Class field.

Common Fields

• Store: Entering a value for Store restricts the report to only display results for the specified store.
  • Note that some items are not store specific, e.g. Class codes or fee codes are store agnostic.
• Register: Entering a value for Register restricts the report to only display data on the specified register.
  • Multiple registers can be entered by separating them with a comma. e.g. 101,102,103 will report on all three registers.
• Beginning Date: A “start date” that limits the data to not include information before this date.
  • e.g. A transaction search with a start date of 7/1/18 will not include any transactions prior to July 1st, 2018.
• Ending Date: Specifies the “stop date” in the data, nothing after this date will be displayed.
  • e.g.A transaction search with a stop date of 7/1/18 will not include any transactions done on 7/2/18 or after.
  • To report on a single day make the beginning and ending date the same.
• Department: Restricts the report to include data that falls under the specified department
• Class: Restricts the report to data that includes items that fall under that class
• SKU: Enter a SKU, ISBN, Fee Code, etc. to only report on data that includes this item
• Detail: Is used to display as much information as possible for that data being reported on.
  •  For example, a report against transaction data with Detail flagged will display every line item in the transaction, the cost, quantity and total for every transaction for the date range specified.
  • The majority of reports are either Detail or Summary, but there are a few exceptions that will report the detailed information and include a separate summary section at the bottom. One example would be inventory valuation reports that will list all of the inventory items and then include summary totals for each inventory class.
• Summary: The summary flag will combine and summarize the data reported on various break points.
  • For example, a transaction report with Summary flagged will simply report the transaction total instead of every single line item, their cost, and the total for the date range specified.
• History: Almost always a N.
  • This is not a “include History as well” flag.This is a hard switch, meaning it reads from the History ONLY and will not report on current data.
  • Data can be moved to history to separate it from current data without throwing it away.
  • Once it has been moved to history then the History field would have to be a Y to read it from the History file.
• Web: Almost always an N or empty. Entering a Y will restrict the report to ONLY web transactions similar to the History field only reporting on the History file.

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.

Unique Field Options

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.