About This Glossary: This terminology guide covers POS (Point of Sale) and TLOG-specific terms you'll encounter when analyzing transaction data. Terms are organized alphabetically for easy reference.
A
ACE(Advanced Checkout Engine)
Toshiba's point-of-sale software platform used in retail environments. ACE systems generate TLOG files that record all transaction activity. TLOGic supports ACE format TLOG files.
POS System
B
BCD(Binary Coded Decimal)
A method of encoding decimal numbers where each digit is represented by a fixed number of binary digits (bits). Common in TLOG files for storing numeric values like amounts and quantities. TLOGic's WASM parser handles BCD decoding automatically.
Data Format
Byte Offset
The position (in bytes) where a transaction record begins in the TLOG file. Used for direct access to specific transactions and for troubleshooting file structure issues. Viewable in TLOGic's Raw Data view.
File Structure
C
Cashier
See Operator. In retail POS systems, the terms "cashier" and "operator" are often used interchangeably to refer to the person processing transactions at a register.
Personnel
Composite Score
In TLOGic's Operator Analytics, a weighted performance metric that combines multiple factors (sales, speed, accuracy) into a single score. Weights can be customized to match your business priorities.
Analytics
D
Department
A category or classification of merchandise in a retail environment (e.g., Grocery, Electronics, Apparel). TLOG transactions often include department codes to track sales by product category.
Retail Organization
Deep Field Filter
An advanced TLOGic feature that allows filtering transactions based on specific fields within the transaction structure, beyond the basic search criteria. Useful for complex analysis requiring access to nested transaction data.
TLOGic Feature
E
EOD(End of Day)
The process of closing out a day's business operations at a retail location. May include totaling sales, closing registers, and generating reports. Some TLOG files represent a single business day's transactions.
Operations
F
Field Code
A numeric identifier within a TLOG transaction that indicates the type of data stored in a particular field (e.g., amount, operator ID, item code). Field codes are defined in the tlogmetadata.xml schema.
Data Structure
H
Heatmap
A visualization that uses color intensity to represent data values across time periods. In TLOGic, sales heatmaps show transaction volume and amounts by hour and day of week, helping identify peak business times.
Visualization
Hex View
A display mode in TLOGic that shows the raw hexadecimal (base-16) representation of transaction data. Useful for technical analysis and troubleshooting data format issues.
TLOGic Feature
I
IBM TLOG
Transaction log format originally developed by IBM for retail POS systems. Toshiba adopted and extended this format in their ACE and SA systems. TLOGic is designed to parse both IBM and Toshiba TLOG formats.
File Format
Inactive Time
Time periods when a terminal or operator is logged in but not actively processing transactions. High inactive time may indicate inefficiency or staffing issues. Tracked in TLOGic's Operator Analytics.
Performance Metric
K
Key(Transaction Key)
A numeric identifier that categorizes the type of transaction record. Different keys represent different transaction types (sales, returns, voids, etc.) or record types (header, detail, trailer). Keys are fundamental to understanding TLOG structure.
Transaction Type
KPI(Key Performance Indicator)
Measurable values that demonstrate how effectively business objectives are being achieved. In TLOGic, KPIs include metrics like sales per hour, average transaction value, void rates, and operator efficiency scores.
Business Metric
M
Metadata(tlogmetadata.xml)
An XML file that defines the structure and field definitions for TLOG records. It maps field codes to human-readable names and data types. TLOGic includes a standard metadata schema but also supports custom metadata uploads for proprietary formats.
Configuration
N
No-Sale
A transaction type where the register drawer is opened without processing a sale (e.g., to make change for a customer). No-sale transactions are tracked in TLOG files and can indicate security or cash handling issues if excessive.
Transaction Type
O
Operator
The person logged into a POS terminal to process transactions. Also called a cashier. Each operator typically has a unique ID that appears in transaction records. TLOGic provides detailed operator performance analytics.
Personnel
Operator ID
A unique numeric or alphanumeric identifier assigned to each operator/cashier. Used to track transaction activity and performance metrics on a per-operator basis.
Identifier
P
POS(Point of Sale)
The physical location and/or system where a retail transaction is completed. POS systems include the hardware (registers, scanners, payment terminals) and software (ACE, SA) used to process sales.
System
POSLog
An XML-based transaction log format standardized by the retail industry. TLOGic can display transaction data in POSLog XML format for compatibility with other systems.
File Format
R
Record Size
The length (in bytes) of a transaction record in the TLOG file. Varies based on transaction complexity and amount of data captured. Large record sizes may indicate complex transactions or potential data issues.
File Structure
Refund
See Return. A transaction where merchandise is returned to the store and money is returned to the customer. Tracked separately from regular sales in most POS systems.
Transaction Type
Return
A transaction type where a customer returns merchandise for a refund or store credit. High return rates may indicate product quality issues, customer service problems, or potential fraud. Analyzed in TLOGic's department and operator analytics.
Transaction Type
Ring Time
The average time an operator takes to scan or enter items during a transaction, measured from transaction start to completion of item entry. Lower ring times generally indicate better efficiency. Tracked in TLOGic's Operator Performance metrics.
Performance Metric
S
SA(Store Automation)
Toshiba's comprehensive retail management system that includes POS, back-office, and reporting functionality. SA systems generate TLOG files compatible with TLOGic.
POS System
Sale Transaction
The most common transaction type, representing a standard purchase where a customer buys merchandise. Includes item details, amounts, payment information, and operator/terminal data.
Transaction Type
SKU(Stock Keeping Unit)
A unique identifier for each distinct product or item in inventory. SKUs allow tracking of individual product performance, inventory levels, and sales patterns. Item-level analysis in TLOGic is based on SKU data.
Inventory
Suspend/Resume
Transaction operations where a sale in progress is temporarily saved (suspended) to process another transaction, then later retrieved (resumed) to complete. Useful for handling customer inquiries or price checks mid-transaction.
Transaction Type
T
Tender
The method of payment used to complete a transaction (cash, credit card, debit card, check, etc.). TLOG files record tender types and amounts for each transaction.
Payment
Tender Time
The average time an operator takes to process payment after items are scanned, from the start of tender entry to transaction completion. Includes time for payment processing, change calculation, and receipt printing.
Performance Metric
Terminal
A physical POS register or workstation where transactions are processed. Each terminal has a unique identifier (terminal number) that appears in TLOG records. Multiple operators may use the same terminal during a business day.
Hardware
TLOG(Transaction Log)
A binary file format used by IBM and Toshiba POS systems to record all transaction activity. TLOG files contain detailed records of every sale, return, void, and system event that occurs on the POS system. TLOGic is designed specifically to parse and analyze these files.
File Format
Training Mode
A special POS mode where transactions are processed for operator training purposes without affecting actual sales or inventory. Training transactions are marked with a specific transaction type and typically filtered out of business reports.
Transaction Type
Transaction Number
A sequential identifier assigned to each transaction in the TLOG file. Transaction numbers typically increment throughout the day and may reset at the start of each business day. Used for searching and identifying specific transactions in TLOGic.
Identifier
Transaction Type
A classification indicating what kind of transaction occurred (sale, return, void, training, no-sale, etc.). Each transaction type has specific characteristics and business implications. TLOGic color-codes transaction types for easy identification.
Classification
Treemap
A visualization technique that displays hierarchical data using nested rectangles. In TLOGic's Department Analytics, treemap size represents sales volume while color indicates return rates, allowing quick identification of department performance patterns.
Visualization
V
Void
A transaction or line item that is cancelled after being entered but before the transaction is completed. Different from a return, which occurs after a sale is finalized. High void rates may indicate operator errors, pricing issues, or training needs.
Transaction Type
Void Rate
The percentage or frequency of void transactions compared to total transactions, used as an operator performance metric. Calculated as (void count / total transaction count) × 100. High void rates warrant investigation.
Performance Metric
W
WASM(WebAssembly)
A high-performance binary instruction format that runs in web browsers. TLOGic uses WASM (compiled from Rust code) to achieve near-native performance for parsing and filtering TLOG files, enabling fast analysis of large datasets entirely in the browser.
Technology
Weighted Score
In TLOGic's Operator Analytics, a customizable metric where different performance factors (sales, efficiency, accuracy) are assigned importance weights. The weighted score allows businesses to emphasize metrics that matter most to their operations.
Analytics
X
XML(eXtensible Markup Language)
A structured text format used for data exchange. TLOGic can display transactions in XML format (POSLog standard) and accepts metadata definitions in XML format (tlogmetadata.xml). XML provides human-readable structure to complex transaction data.
Data Format