How to understand POS API report data?

TB Reports · library · Last updated August 18, 2026 · Version 1

This process works in apps: TB Reports

This article will teach you that every TB Reports template pulls from the Tire Base POS V1 (legacy) API and what to check if numbers look off.

TB Reports is built only for Tire Base POS V1 (legacy). Sales Journal, Transactions Report, Payments Report, and Profit & Loss all call the Tire Base POS API — they are not Books, TB POS (POS Lite), or WMS reports. That split is historical, not a bug. Knowing the source prevents false panic when Books AR and POS V1 sales differ during parallel operation. On the Transactions Report, line Quantity is inventory movement (invoices often show a negative qty) while Dashboard sales, tax, gross profit, and P&L use the document type so sales stay positive and returns/POs reduce the right totals.

Steps

• Open the report and read its description / data source label.
• Confirm it explicitly references Tire Base POS API when applicable.
• Run with a narrow date range you can manually spot-check in POS.
• Note store/location filters — POS API reports may use store IDs.
• On Transactions Report, expect invoice Quantity to be negative (stock out) and credit memo / refund / PO Quantity to be positive (stock in). Amount follows the opposite pattern for credits, refunds, and POs.
• Use Subtotal Sales, Total Sales, and Profit and Loss for sales and purchase totals — do not treat the Quantity footer as units sold.
• If totals look off, verify the POS store connection with an admin and capture screenshots with report name, filters, and date range for support.

Conclusion & best practices

Do not force Books and legacy POS reports to match line-for-line without a migration plan. Negative invoice quantity on the Transactions Report is how POS now sends inventory, not a sign that sales are reversed. Document which leadership meetings use which source until Books fully replaces POS reporting for your tenant.