Purchase History by Customer (POS Integration)
From the CRM customer detail screen, you can review each customer's purchase history at the receipt level. Receipts issued by connected POS systems like Smaregi or Square are automatically attached based on member number or customer profile, letting you see at a glance "when and at which store this customer purchased what."
This article covers how to view purchase history, the conditions under which receipts appear, the difference from paper receipts, how privacy is handled, and access via the API.
Where purchase history is displayed
Go to the store management screen → "CRM" → open the detail screen for the customer you want to check. From the "Purchase History" tab, you can review receipt-level history. Each receipt displays the following:
- Transaction date/time
- Store name (when operating multiple stores)
- Total amount
- Receipt number (the one issued by the POS)
- Link to receipt details (click to view the itemized details)
History is displayed in newest-first order. The default display count is 50, and it can be increased as needed.
Conditions for appearing in the history
Not all purchases are automatically loaded into the history. The conditions under which a receipt is reflected in a customer's purchase history are as follows.
- The receipt must be one issued by a POS (Smaregi, Square, etc.)
- That receipt must be attached to the given customer with high accuracy — only when the POS customer ID exactly matches the ReceiptRoller member number/contact information
- The purchase must have occurred after POS-CRM integration was enabled in ReceiptRoller (retroactively reflecting past purchases requires a separate backfill process)
Receipts scanned from paper are not shown
Receipts that a customer scanned themselves from a paper receipt using the app are not shown in this customer's purchase history. This is intentional design, not a bug.
Paper receipts are registered by the customer themselves for their own receipt management, so the purchase is not necessarily tied to a sale from your store (there are cases where receipts from other stores are scanned together). From a customer privacy standpoint as well, these are not shown to store operators.
Only POS-issued receipts allow store operators to reliably track "purchase history of items sold at our store."
How member matching works
For a receipt issued by the POS to be attached to a CRM customer, the customer needs to be identified through one of the following methods (in priority order).
- The POS ties the customer ID to the transaction at issuance — such as when a customer presents their membership ID at the register. This is the most reliable method
- The member code/loyalty number provided by the POS matches the ReceiptRoller member number — a pattern where the code issued on the POS side can be used as-is
- The POS reads the ReceiptRoller member barcode — when the POS reads the barcode from Wallet membership verification
Receipts that could not be identified through any of these methods are not attached to a specific CRM customer, but are still included in the store's monthly aggregate totals — they simply won't appear on the customer's purchase history screen.
For multi-store operations
If you operate multiple stores, the purchase history displays purchases across all stores. Since entries are shown side by side with the store name, you can see which stores each customer frequents.
If you want to view purchases from a specific store only, you can select the store from the "Filter by store" option above the purchase history tab.
Total amount and average purchase amount
Above the purchase history screen, aggregate information about the customer's purchases is displayed.
- Cumulative purchase amount: total purchases across all stores
- Cumulative visit count: counted at the receipt level
- Last visit date
- Average purchase amount: cumulative purchase amount ÷ visit count
These figures are aggregated only from the confirmed receipts shown in the purchase history. Scanned paper receipts are not included.
Using this for segments
Purchase history data can be used as a filter condition for customer segments.
- Loyal customers with cumulative purchases over ¥100,000
- Dormant customers with no visits in the last 30 days
- High-value customers with an average purchase amount over ¥5,000
- Repeat customers who made multiple purchases at a specific store
For details on creating segments, see the separate article "Specifying Distribution Segments."
Access via API
You can also retrieve purchase history from an external system.
GET /api/v1/store/customers/{id}/purchases?storeId={storeId}&take=50- id: customer ID or member number
- storeId (optional): filters to purchases at a specific store only
- take (optional): upper limit on the number of results returned. Defaults to 50, maximum 200
Each returned receipt includes the receipt ID, store ID, store name, total amount, transaction date/time, receipt number, and master reference (StoreReceiptRef). For details, see the separate article "API Reference."
How privacy is handled
ReceiptRoller handles customer receipts according to the following principles.
- Receipts issued by the store: visible to both the store operator and the customer. Displayed in the CRM purchase history
- Receipts a customer scanned from paper: visible only to the customer. Not shown to the store operator. Since there's a possibility the customer scanned a receipt from another store, it isn't treated as a purchase at a specific store
This rule allows store operators to use only the reliable data of "what was actually sold at our store" for business purposes, while preserving customer privacy.
Notes
- Receipts from before this feature was enabled are not automatically reflected in the history. If you need a backfill of past data, please contact our support team
- Receipts where POS and member matching could not be established are not shown in the history, so if a customer asks "why isn't my purchase showing up even though I bought it at your store," please confirm that member linking on the POS side was done correctly
- For customers with a large volume of receipts (several thousand or more), the initial purchase history screen may take a few seconds to display
Related help
-
Two-Way Member Information Sync with Smaregi/SquareLearn how ReceiptRoller's member information syncs bidirectionally with connected POS systems like Smaregi and Square. Covers which fields sync, sync timing, conflict priority rules, new customer matching, supported POS systems, and troubleshooting.
-
Customer-Targeted PromotionsDeliver coupons and specials targeted to specific customer segments, linked to CRM customer data. Narrow your audience by region, age range, and membership rank to boost promotion effectiveness.
-
Customer SegmentsClassify customers by attribute using tags and groups so you can target initiatives instead of sending the same message to everyone. Build segments from visit count, spend, membership rank, and more.
-
Audience Segments and Broadcast CastingSNS CRM lets you segment followers and DM contacts, then send one broadcast message to each segment. Deliver focused communication to customers based on specific attributes and behavior history.
-
Customer Data ManagementCentrally manage customer profiles, visit history, and purchase records. Search, tagging, and notes let all staff quickly check up-to-date customer information.