Japanese real estate CRM needs to integrate with REINS (the Japanese MLS), manage the 重要事項説明 disclosure workflow, and support the Japanese property transaction timeline — which is fundamentally different from Western real estate processes

REINS does not provide a public API for direct integration with third-party CRM platforms. The most practical approach is a synchronisation workflow that triggers a REINS update prompt when a property status changes in the CRM, and an import workflow that pulls REINS export data into the CRM on a scheduled basis. Some property management platforms built for the Japanese market have REINS connectivity built in. For agencies using a generic CRM such as Salesforce or HubSpot, the integration is built using REINS export file parsing and webhook-based triggers for status change notifications. The goal is to ensure that a property status change entered once in the CRM results in a corresponding REINS update without the agent needing to log into both systems separately.

Tracking 重要事項説明 compliance in the CRM requires adding a structured workflow to the deal record with the following stages: document preparation (started, completed), delivery method (in person, electronic), delivery date, acknowledgement receipt confirmation, and contract execution date. A calculated field should confirm whether the time gap between delivery and contract execution meets legal requirements. The pipeline stage for contract execution should be conditional on the completion of the compliance fields. This embeds the legal requirement into the transaction workflow rather than relying on a separate compliance checklist. Electronic delivery via IT-重説 (electronic 重要事項説明) requires additional fields for the electronic delivery confirmation method.

Suumo and At Home send lead notifications by email when a prospective buyer or renter submits an enquiry through the portal. Email parsing workflows can extract the lead data from the notification email — name, contact details, enquiry type, and property reference — and create a contact and enquiry record in the CRM automatically. The property reference in the notification is matched against the property record in the CRM, and the enquiry is assigned to the responsible agent. Where portal API access is available, a direct connection provides more structured data. The configuration requires mapping the email notification format (which differs between Suumo and At Home) to the CRM fields and building the assignment logic.

Japanese address configuration in a CRM requires replacing or supplementing the standard address field with separate fields for: 都道府県 (prefecture), 市区町村 (city/ward/town), 丁目 (district/neighbourhood), 番地 (block and lot number), 建物名 (building name), and 部屋番号 (unit number). The fields should accept full-width Japanese characters as well as half-width numerals. Postcode (郵便番号) should be a separate field with auto-population of prefecture and city fields where the CRM platform supports it. Property records using this structure can be sorted and filtered by area, exported to mapping tools, and matched against REINS records by address component rather than requiring a full-string match.

Japanese real estate agencies use a mix of property-specific platforms built for the Japanese market (including platforms with native REINS connectivity) and general-purpose CRMs configured for property workflows. Kintone is widely used by Japanese businesses including property agencies because it supports custom field structures, Japanese address formats, and workflow automation in a Japanese-language interface. Salesforce and HubSpot are used by larger agencies and developer groups, typically with significant customisation for Japanese property workflows. The platform choice depends on agency size, whether REINS integration is required at the workflow level, and whether the team operates primarily in Japanese. A platform with strong Japanese-language support and custom field flexibility is more important than brand recognition.