Purchase History by Customer (POS Integration)
On the customer detail page in Customers (CRM), you can review each customer's purchase history at the receipt level. Receipts issued by connected POS systems like Smaregi or Square are attached to the customer automatically by member number, so you can see at a glance when, at which store, and how much this customer bought.
This article covers how to read the 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
Open the customer in Customers (CRM). The "購入履歴" (Purchase history) section of the customer detail page lists that customer's 30 most recent receipts, newest first. Each row shows:
- Date and time (Japan time)
- Store
- Receipt number (the one issued by the POS)
- Amount
Click the date to open that receipt's details. The link appears only for members who can view transactions (Owner, OperationsManager, POSManager, FinanceManager). Other members see the date as plain text.
For a customer without a member number, the page says purchase history cannot be shown. Sales are matched to customers by member number.
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 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 a Wallet membership card
Receipts that could not be identified through any of these methods are not attached to a specific customer, but are still included in the store's monthly aggregate totals — they simply won't appear in the customer's purchase history.
For multi-store operations
If you operate multiple stores, the purchase history shows purchases across all stores in the business account, merged newest first. Since each row shows the store name, you can see which stores each customer frequents. The customer detail page has no store filter.
Figures on the customer detail page
The top of the customer detail page shows these figures:
- 来店回数 (Visits)
- 累計購入金額 (Total spent)
- 予約数 (Bookings)
- 今後の予約 (Upcoming bookings)
- 出席率 (Attendance rate, only when there is booking history)
- 無断キャンセル (No-shows)
Visits and total spent are counted from POS receipts reliably matched to the customer. Scanned paper receipts are not included. Below the purchase history, a "予約履歴" (Booking history) section lists the customer's bookings with date, store, party size and status.
Using this for segments
Visits, total spent and the last visit date can be used as customer segment conditions.
- Loyal customers: Total spent (yen) at least 100000
- Dormant customers: Days since last visit at least 30
- Regulars at one store: Visits at least 5, and Store is that store
For details on creating segments, see the separate article "Customer 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. If omitted, purchases at all of the customer's stores are merged
- take (optional): upper limit on the number of results returned. Defaults to 50, maximum 200
Receipts are returned newest first. Each 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 purchase history on the customer detail page
- 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
- The customer detail page shows the 30 most recent receipts. Use the API if you need older ones
Related help
-
Matching Smaregi and Square Sales to CustomersHow Smaregi and Square sales are matched to your ReceiptRoller customers. Member and customer information is not synced with the POS; matched sales update the customer's purchase history and visit count.
-
Customer data when a customer merges accountsWhat happens to your store's customer data when a customer merges two ReceiptRoller accounts, and how to join two records of the same customer.
-
Customer-Targeted PromotionsGroup customers with a customer segment and offer coupons and specials to them through a push notification sent to that segment.
-
Customer SegmentsGroup customers by visits, total spent, days since last visit, rank, tag, prefecture, and store, and save the group as a segment. Choose a segment as the audience of a push notification.
-
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.