Data Cleaning for Restaurant POS Exports: Toast, Square, Clover, Lightspeed, Revel and TouchBistro Customer Data Hygiene
On this page
The Restaurant Data Mess
A restaurant in 2026 collects customer data from more sources than most technology companies. There is the POS system (Toast, Square, Clover, or Lightspeed) recording every transaction. The online ordering platform (ChowNow, Olo, BentoBox, or the POS's built-in online ordering) capturing names, emails, phone numbers, and addresses for delivery and pickup orders. The third-party delivery apps (DoorDash, UberEats, Grubhub) with their own customer records. The reservation system (OpenTable, Resy, Yelp Reservations, or SevenRooms) tracking guest preferences and visit history. The loyalty program (whether built into the POS or through a third-party like Thanx, LevelUp, or Paytronix) linking purchases to member profiles. The catering inquiry form on the website. The private event booking system. The email marketing platform (Mailchimp, Constant Contact, or a restaurant-specific tool like Popmenu or BentoBox).
Each of these systems creates its own customer records, independently, with no cross-referencing. A regular who dines in twice a week, orders delivery once a month through DoorDash, has a loyalty account, and booked a private dining room for a birthday party exists as five or more separate customer records across five systems.
This fragmentation matters because the restaurant's understanding of that customer is fragmented too. The POS sees a dine-in guest with 100+ visits. DoorDash sees an occasional delivery customer. The loyalty program sees a member with moderate points. The event system sees a one-time booking. None of these systems knows this is the same person, and none can calculate the customer's true lifetime value or send them a communication that acknowledges their full relationship with the restaurant.
Exporting from Restaurant POS Systems
Each POS system exports customer data differently, and understanding what each export contains is essential for successful consolidation.
Toast exports customer data from the Marketing section of Toast Web. The export includes guest name, email, phone number, order history, total spend, visit count, and marketing opt-in status. Toast also exports detailed order data that can be matched to customer records. Toast's online ordering module captures additional data (delivery address, order preferences) that may not appear in the standard customer export -- export online ordering data separately if your Toast account includes it.
Square for Restaurants exports customer data from the Customer Directory (Customers, then Export). The export includes name, email, phone, creation date, total spend, visit count, and any custom fields or notes. Square's customer directory is shared across all Square products (POS, Online, Appointments), so if you use Square for in-store and online ordering, the directory may already be partially consolidated -- but duplicates are common when the same person uses different payment cards or provides different email addresses.
Clover exports customer data from the Customers app on the Clover dashboard. The export includes name, email, phone, order count, and total spend. Clover's third-party app ecosystem means that different apps (online ordering, loyalty, marketing) may create their own customer records that are not reflected in the main Customers export.
Lightspeed Restaurant (formerly Upserve) exports customer data from the Guests section. The export includes guest profiles with visit history, average spend, favorite items, and contact information. Lightspeed's guest profiles are more detailed than most POS systems because they track guest preferences and server notes.
Revel exports customer data from the Customer Management section. The export includes name, contact information, order history, and loyalty program data if the Revel loyalty module is enabled.
TouchBistro exports customer data from the reporting dashboard. The export format varies depending on which TouchBistro modules are active (dine-in, online ordering, loyalty, reservations).
The Third-Party Delivery Problem
Third-party delivery apps (DoorDash, UberEats, Grubhub) present the biggest data cleaning challenge for restaurants. These platforms control the customer relationship and share limited customer data with restaurants.
DoorDash and UberEats provide the customer's name and delivery address for each order but may mask the customer's email and phone number, routing communications through their own systems. Grubhub historically shared more customer data, but access varies by market and partnership level.
For restaurants that want to own their customer data from delivery orders, the strategy is to drive delivery customers toward direct ordering channels. Include a card in every delivery order: "Order directly from us next time and save. [Website URL]. Same food, lower prices (no delivery app markup), and you support us directly." Customers who switch to direct ordering provide their real contact information, which can then be matched against their delivery platform history by name and address.
Export whatever customer data the delivery platforms provide. Even if emails are masked, names and addresses can be used for matching against your POS and direct ordering customer records, identifying overlap between delivery and dine-in customers.
Consolidation Process
Export customer data from every source: POS system (dine-in transactions), online ordering platform (pickup and delivery), reservation system, loyalty program, catering and events system, email marketing platform, and any third-party delivery data available.
Upload all exports to Email Extractor to extract and deduplicate email addresses across all sources. This is the critical first step because it identifies customers who exist in multiple systems under the same email address, collapsing a five-record customer into a single contact.
Download as CSV with sources. The source column reveals the customer's relationship breadth: a customer appearing in POS + online ordering + loyalty + reservations is a high-value regular whose total spend and visit frequency across all channels should be calculated together for accurate lifetime value assessment.
For records without email overlap (common with third-party delivery and reservation-only guests), secondary matching by phone number or name-plus-address provides additional consolidation. This matching is less precise (common names produce false matches), but for a restaurant with a few thousand customer records rather than millions, manual review of potential matches is feasible.
Using Clean Data for Marketing
A unified customer database enables marketing that individual system data cannot support.
Lapsed customer reactivation: Identify customers who visited regularly (10+ visits in any 3-month period) but have not visited in the past 60 days. These are lapsed regulars -- customers who loved the restaurant but stopped coming for some reason. A targeted reactivation email with a specific incentive ("We have missed you. Here is a complimentary appetizer on your next visit") is one of the highest-ROI marketing tactics in the restaurant industry.
Channel migration: Identify customers who order delivery through third-party apps but rarely or never dine in. Send them a dine-in incentive: a complimentary drink, a special menu item, or a reservation priority. Dine-in customers have higher average checks, no delivery commission, and stronger loyalty than delivery-only customers.
Event and catering upsell: Identify high-spending customers (top 10% by total spend) who have never booked a private event or placed a catering order. These are customers who already love the food and would be receptive to a private dining or catering pitch for their next celebration or business meeting.
