After connecting Smaregi to Receipt Roller, Smaregi's staff master is automatically converted into Receipt Roller's staff data (StaffDto). This article summarizes the field-by-field correspondence and the quirks specific to Smaregi.

To sync, click "Sync with Smaregi" from the menu in the top-right of the Staff screen. For details, see Smaregi POS integration setup.

Field mapping table

Fields that are not imported

Because of how the Smaregi /pos/staffs endpoint is specified, there is no corresponding data for the following Receipt Roller fields. Register these separately on the Receipt Roller side — they are never overwritten on re-sync.

• Phone number (Phone)
• Date of birth (DateOfBirth)
• Hire date (HireDate)
• Employment type (EmploymentType) — full-time, part-time, contract, etc.
• Hourly rate (HourlyRate)
• Address / emergency contact
• Job title (Position) — Smaregi returns a roleId, but resolving it to a job title requires a separate endpoint, which is not yet supported in the current version
• Assigned stores (AssignedStoreIds) — Smaregi's /pos/staffs does not return store assignments
• Name reading / kana (LastNameKana / FirstNameKana) — StaffDto has no corresponding field yet. staffNameKana is planned to be used once the field is added

Matching and new registrations

When staff are imported from Smaregi, matching against existing staff is done solely by an exact match on SmaregiStaffId. If there is no match, the staff member is registered as new. No automatic matching by name or employee number is performed.

Sync timing

• Smaregi → Receipt Roller: Triggered manually with the "Sync with Smaregi" button in the menu at the top-right of the Staff screen. All staff are fetched from /pos/staffs and matched by SmaregiStaffId to add or update records.
• Behavior on re-sync: For existing staff (matched by the same SmaregiStaffId), EmployeeNumber / LastName / FirstName / DisplayName / Email / IsActive are overwritten. Fields added on the Receipt Roller side — HourlyRate / HireDate / EmploymentType / Position / AssignedStoreIds / emergency contacts, etc. — are preserved.
• Receipt Roller → Smaregi: Not supported in the current version. Staff registered on the Receipt Roller side are not automatically reflected back to Smaregi.

Resolving the staff attributed to a transaction

Keeping the staff master synced allows the staffId in transaction data (PosTransactionDto) to be automatically resolved to a Receipt Roller staff record. This means receipt displays and per-staff sales totals show the "name registered in Receipt Roller" rather than the "Smaregi internal ID."

If the staff master has not been synced, the staffName included in the transaction data (the name as displayed on the Smaregi side) is used as-is.

Points to note

• If a staff member is physically deleted on the Smaregi side, matching by that SmaregiStaffId stops working. On Smaregi, we recommend hiding staff via displayFlag instead of deleting them.
• Even if a staff member is set to IsActive = false (treated as having left) on the Receipt Roller side, resolving the staff attribution of past transactions continues to work. Do not delete the records of staff who have left.
• The automatic name-splitting is a simple process that splits into two at the first space. Compound surnames or names with three or more words may be split in unintended ways. You can correct this individually on the Receipt Roller side after syncing.
• If a single staff member is assigned to multiple stores, set multiple stores in AssignedStoreIds on the Receipt Roller side after syncing.

Related guides

• StaffDto reference (for developers) — full field specification of the canonical model
• Smaregi Platform API: GET /pos/staffs (external — official reference)
• Smaregi transaction data mapping
• Smaregi customer data mapping
• Smaregi product data mapping
• Smaregi POS integration setup