Smaregi Customer Data and Receipt Roller Customer Data Mapping
Explains how Smaregi's customer master is converted into Receipt Roller's customer data (CrmCustomerDto), field by field. Covers the membership number, name, contact info, and date-of-birth correspondence, the priority between mobile and landline numbers, and webhook-based sync timing.
Connecting a LINE Official Account
Explains how to connect a LINE Official Account to ReceiptRoller using a Messaging API channel's Channel ID and Channel Secret.
Setting Up LINE Integration
Step-by-step guide to publishing your Receipt Roller store app as a LINE Mini App: creating LINE channels, entering credentials, running auto-configuration, and submitting for review.
Receipt Handling for Refunds and Cancellations
Explains how e-receipts are handled when a customer requests a refund after checkout, or a mis-entered sale is voided. Covers what customers see and how staff should operate.
Two-Way Member Information Sync with Smaregi/Square
Learn 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.
Order Management (OMS) Overview
An overview of ReceiptRoller's OMS (order management system). It consolidates orders from multiple channels — Web, POS, B2B EC, Shopify, Amazon, and more — into a single view, tracking the full lifecycle from order to shipment to completion.
Where to Find the API Reference
The list of API endpoints and sample request/response formats are published in the Developer Help.
Square Transaction Data and Receipt Roller Transaction Data Mapping
A technical explanation of how transaction data fetched from the Square Payment API is mapped into Receipt Roller's transaction data model. Covers the field mapping table, status code conversion, payment method normalization, resolving line items/customer/staff information, OAuth token auto-refresh, and idempotency and timezone handling.
Smaregi Transaction Data and Receipt Roller Transaction Data Mapping
A technical explanation of how transaction data fetched from the Smaregi Platform API is mapped into Receipt Roller's transaction data model. Covers the field mapping table, status code conversion, payment method normalization, resolving line items/customer/staff information, timezone handling, and idempotency.
Webhooks and Event Notifications
Learn how to register webhooks and which events ReceiptRoller sends notifications for.
Unified Inbox (DM Management)
The unified inbox lets you view and reply to DMs from multiple social channels, including Meta, Instagram, X, and LINE, in a single screen. It also supports per-platform filters and a list of conversation history.
Staff Sync via Square Integration
Explains how stores connected to Square POS can sync Team Member information bidirectionally with ReceiptRoller — job assignments, pay rates, assigned stores, owner permissions, and more, kept aligned with Square.
Setting Up Mini App Pages and Menus
Choose which pages and menu items appear in your LINE Mini App and arrange them to fit your store. Show only the features you want customers to see, in whatever order you like.
Smaregi POS Integration Setup
Steps to set up the POS integration between Smaregi and ReceiptRoller. Install "ReceiptRoller Link" from the Smaregi App Market, log in with your Smaregi account, then select a store and terminal (register) from the "Connect with Smaregi" button on the POS settings screen to complete the connection. Also explains how to sync transaction data after connecting and how to handle multiple stores and terminals.
Square POS Integration Setup
Explains how to connect Square POS with ReceiptRoller. Connect easily via OAuth authentication, and accounting data syncs in real time.
Square Customer Data and Receipt Roller Customer Data Mapping
Explains how customers registered in Square Customer Directory are converted into Receipt Roller's customer data (CrmCustomerDto), field by field. Covers the given_name / family_name correspondence, address decomposition logic, and how reference_id is handled.