- POS data is more than sales totals: line items, tenders, discounts, refunds, staff and location sit on every transaction.
- Every system exports differently, and several limit how much you can download at once or how far back reports go.
- To compare locations, use sales per hour open and per staff member, on one shared definition of net sales.
- PCI DSS limits card data: security codes and full chip or stripe data are never kept after a payment is approved.
What is POS data?
POS data is everything your point-of-sale (POS) system records when you sell something. The POS system is the register software, card reader and back office that rings up each sale. Every sale leaves a transaction record, and each transaction holds smaller records: the items sold, how the customer paid, any discount or refund, who rang it up and at which location.
Service businesses add a second layer. A salon, barbershop, gym or car wash usually books the work before it sells it, so its booking system holds the appointment, the staff member booked, the service, the status (booked, confirmed, cancelled, no-show, completed) and the sale that closed it. Point of sale data and booking data together show what was planned and what actually happened.
| Record | What it holds | Typical fields |
|---|---|---|
| Transaction | One sale or refund | Date and time, location, device, total, tax, tip, status |
| Line item | One product or service on the sale | Item or service name, SKU, quantity, price, discount |
| Tender | How the customer paid | Card brand and last four digits, cash, gift card, split payments |
| Discount, refund and void | Changes to the sale | Amount, reason, staff member who approved it |
| Staff | Who sold or served | Employee ID, role, shift, location |
| Appointment | A booked service (service businesses) | Booked time, service, provider, status |
| Customer | Who bought, when known | Name, phone, email, visit history, notes |
| Inventory | Stock behind the items | Item, location, on hand, received, sold, adjusted |
What does retail transaction data look like in an export?
Most exports have one row per line item, so a sale with three items fills three rows. Shopify's order export works this way: "orders with multiple line items display their additional line items on separate lines" (Shopify Help Center). For in-store sales the same file has a Location column, "The location of the POS that sold the order", and an Employee column, "The name of the employee that sold the order".
Customer details often sit right next to the sale. Square lets you search transactions by "Customer information (name, phone number, email)" and by the last four digits of a card (Square). So an export can hold personal details, while card numbers appear only in masked form.
Totals need a definition before you compare them. In the US and Canada, Toast defines net sales as "gross sales minus discount and refund amounts" (Toast). Other systems treat tips, tax and gift card sales differently. Write down which definition each system uses before you compare locations or years.
How do you export POS data from Square, Toast, Clover, Lightspeed and Shopify?
Each system has its own export path, and most have limits that matter once you want years of history rather than last week. The table sums up what each provider's own help pages say.
| System | Where the export is | Limit to plan around |
|---|---|---|
| Square | Dashboard: Transactions, then Export; or Reports, the export icon, then Start export (CSV) | Transaction details download as CSV only from the Dashboard, not the app |
| Toast | Toast Web: Reports, then the download icon on each report (CSV); Email Export on some reports | Data for the last 48 months, filtered six months at a time; no single full export |
| Clover | Reports in the dashboard; the Export API for bulk orders and payments through an installed app | The Export API covers at most 30 days per request |
| Lightspeed Retail (X-Series) | Sell, then Sales History, filter, then Export List (CSV) | Each export is limited to 1,000 sales |
| Shopify POS | Orders, filter, then Export (CSV) | Large exports arrive by email |
| Vagaro | Reports, then Export to Excel or PDF on each report | Only the business owner can export the customer list |
In the providers' words: Square says "you can only download transaction details as a CSV file in your Square Dashboard" (Square), and its reports export when you "Click Start export to download a CSV file to your device" (Square reports). Toast says "You can access data for the last 48 months, and you can filter a report for six months at a time" and "there is no single export of your Toast data" (Toast); its reports download "as a CSV that you can open in Excel or Google Sheets" (Toast reports). Clover's Export API has a "Maximum time range is 30 days" (Clover). Lightspeed says "The sales history export is limited to 1000 sales" (Lightspeed). Vagaro says "only the business owner can export the customer list" (Vagaro).
Every limit has the same fix: export in slices (by month, by location or by status) and keep a log of which slices you have and when you pulled them. For the Shopify order file column by column, see how to export Shopify orders. For the accounting side of the same sales, see how to export QuickBooks data.
How do you analyze POS data across several locations?
POS data analysis for a multi-location owner starts with one question: are the locations comparable? Put every location on the same calendar, the same time zone, the same definition of net sales and the same item and service names before you compare anything. Then look at rates, not just totals.
- Net sales per hour open, by location and day of week. This corrects for different opening hours.
- Average ticket and items per ticket. For service businesses this shows how often a service comes with a retail sale.
- Discount, refund and void rates by staff member. These are the usual first sign of a training gap or misuse.
- Service and product mix by location, which shows what each site is known for.
- For booked services: no-show and cancellation rates, rebooking rate and the time between visits.
- Use of staff time: booked hours against available hours, by provider and by location.
Booking systems hold the statuses you need for the last two. Vagaro's appointment report counts statuses such as "No-Show" and "Cancelled", filters by business location, and can "Include data for employee profiles removed from your business" (Vagaro). Include past staff when you look at several years; otherwise their work drops out of the totals.
How long should you keep POS data, and what card data can you keep?
For taxes, the IRS says you generally "must keep your records that support an item of income, deduction or credit shown on your tax return until the period of limitations for that tax return runs out", which is three years in the usual case, and employment tax records "for at least 4 years after the date that the tax becomes due or is paid, whichever is later" (IRS). Many owners keep sales history much longer for their own planning.
Card data follows stricter rules. The Payment Card Industry Data Security Standard (PCI DSS) is the security standard the card brands set for anyone who stores, processes or transmits card data. The PCI Security Standards Council's guide for small merchants says "The best way to protect against data breaches is not to store card data at all" (PCI SSC guide). Its data storage fact sheet says "Sensitive authentication data must never be stored after authorization - even if this data is encrypted", and that "The first six and last four digits are the maximum number of digits that may be displayed" (PCI SSC). Sensitive authentication data means the full chip or magnetic stripe data, the card security code and the PIN.
Most cloud POS systems replace the card number with a token, so exports show a card brand and the last four digits. Full numbers tend to hide in older places: a legacy register database, a spreadsheet copied from it, notes fields and photos of receipts.
Worked example: three salon locations compared
This is an illustration written for this page, not a real business's data. A fictional salon group compares one ordinary week at its three locations after putting all three on the same definition of net sales.
| Location | Hours open | Net sales | Net sales per hour open | No-show rate | Discount rate |
|---|---|---|---|---|---|
| Downtown | 60 | $18,000 | $300 | 4% | 3% |
| Suburb | 48 | $15,600 | $325 | 9% | 2% |
| Mall | 72 | $17,280 | $240 | 5% | 8% |
Downtown sells the most, but the suburb earns the most for each hour it is open, and it loses the most bookings to no-shows: reminder messages or a deposit policy would help there first. The mall's discount rate is more than twice the others. Split by staff member, most of it traces to one stylist, which is a conversation about policy, not a pricing problem. Fictional figures, written for this page.
Common mistakes with POS data
Most problems appear when files from different locations, systems or years are stacked together.
- Comparing sales without checking when each system counts a sale. Toast's Sales Summary "records a sale when a check is first opened, not when the payment is processed" (Toast).
- Exporting each location with a different date range or time zone, then stacking the files.
- Dropping refunds and voids, which hides both returns and staff misuse.
- Leaving out past employees, so years of work vanish from staff reports.
- Renaming items and services over the years without a mapping table, so one haircut appears under four names.
- Keeping card numbers or security codes in spreadsheets, notes fields or receipt photos.
- Waiting until a contract ends. Toast says "When you close your Toast account, your data will be accessible for 60 days" (Toast).
Is years of POS and booking data worth anything beyond reporting?
It can be, when it covers several locations and many years. AI data buyers have asked Origin for multi-year point-of-sale, booking and customer-support history from multi-location service and retail businesses, starting with a small proof-of-concept sample. The value is in the joined history: each sale linked to the booking behind it, the staff member who did the work and any support conversation about it, across years of openings, price changes and staff turnover.
What must come out first: card data of every kind, customer names, phone numbers and emails (replaced with consistent codes), client notes that mention health or other sensitive details, and staff personal details. Records that belong to a POS provider or a franchisor stay out. The guide to licensing multi-location POS and booking records covers ownership in cloud systems and the sample buyers ask for first. Origin is an independent data partner. Your company decides what is shared and signs any license itself, and a buyer may pay Origin when a deal closes.
Does your company hold records like these? See what your data is worth.
Common questions
What is included in point of sale data?
Point of sale data includes each transaction with its date, time, location and device, every line item with quantity and price, the tender used, discounts, refunds and voids, and the staff member who made the sale. Service businesses also hold the appointment behind each sale. Many systems add customer names, phone numbers and visit history.
How do I export my POS data?
Open the reports or transactions area of your POS back office, set a date range and location, and download the CSV. Square exports from the Dashboard, Toast from each report in Toast Web, and Lightspeed X-Series from Sales History. Most systems limit each export, so pull the history in monthly slices and keep a log of what you have.
How do I export Shopify POS orders by location?
In the Shopify admin, filter your orders, click Export and choose orders by date. Large exports are emailed to you and the store owner. The CSV has one row per line item, plus Location, Employee and Device ID columns for POS sales, so you can split the file by store once it arrives.
What is POS data analysis?
POS data analysis means reading sales records to answer business questions: which location earns most per hour open, which items sell together, which staff members discount or refund most, and when customers come in. For a multi-location business it starts with putting every location on one calendar, one time zone and one definition of net sales.
Can a business store credit card numbers from its POS?
Only if it has a real business need and protects them under PCI DSS, and most small merchants do not need to. The PCI Security Standards Council says the best protection is not to store card data at all. Card security codes, PINs and full chip or stripe data must never be kept after a payment is approved.
How long should a business keep POS records?
Keep sales records at least as long as the IRS can question the tax return they support, which is three years in the usual case and longer in some situations. Employment tax records need at least four years. Many owners keep sales history far longer for planning, but card data should be kept only when there is a business need.
Why do POS sales totals differ between reports?
Usually because the reports count different things or count them at different times. One report may show gross sales and another net sales after discounts and refunds. Some systems record a sale when the check is opened, others when it is paid. Tips, tax and gift card sales are also treated differently from system to system.
Sources and further reading
- Square Support Center: View and search transactions
- Square Support Center: Print, export, or email your reports
- Toast support: Can I download a backup of all of my Toast data?
- Toast support: Export a Filtered Report With Custom Columns
- Toast support: Sales Summary Report Overview
- Clover developer docs: Export merchant data
- Lightspeed Retail (X-Series): Exporting your Sales Data
- Shopify Help Center: Exporting orders
- Vagaro Support: Export Your Customer List
- Vagaro Support: Run the Appointments Summary Report
- PCI Security Standards Council: Data Security Essentials for Small Merchants, Guide to Safe Payments
- PCI Security Standards Council: PCI Data Storage Do's and Don'ts
- IRS: How long should I keep records?
