October 26, 2026: StoreCRM Regular Release Announcement

The regular release of StoreCRM is scheduled for October 26, 2026 (Monday) at 11:00 (Japan time).

This time, we plan to deliver scenarios to customers who did not proceed to purchase after adding a cart, share multiple scenarios, and improve the stability of email and LINE delivery and segment aggregation.

The following are the main updates. Please note that the content may change depending on the verification status before release.

Feature additions and improvements

• Added a scenario for customers who didn't proceed to purchase after adding a cart.
  After the product is added to the cart, you can create a scenario that emails or sends LINE messages if the purchase is not completed for a certain period of time. If the purchase is made during the wait period, you can stop subsequent deliveries.
• Share multiple scenarios together
  You can combine multiple scenarios into a single shared code and import them all to another store at once. If the imported scenario has the same name, it will be saved with a recognizable name.
• Add "end of month" to the coupon expiration date
  The expiration date of the coupon can now be specified as the end of the month of issuance or the end of the following month.
• Extended the number of CSV transfers to the re-stock notification destination
  When you switch the notification destination to a different product, you can now specify up to 100 items in a single CSV file. The rows that were not processed can be reviewed in a CSV file with a reason specified.
• Improved email and LINE login settings
  The translated display name will be reflected in the product options within the email. It also supports setting the overall background color of the email, keeping the subject name while editing, and saving templates from existing emails. You can also set the destination URL for when a LINE login fails.

Minor revision

• We have improved the batch delivery of emails and LINE messages, scenario delivery, and the processing of delivery results, improving the wait time and stability of processing during large-scale delivery.
• Fixes an issue where the same scenario is executed and delivered repeatedly when customer tag updates are processed simultaneously.
• The "Date of Count Collection" is displayed clearly in the list of segments and details. Additionally, improvements are made to ensure automatic recovery in the event the count is stopped while being processed, and to allow the remaining count to continue even if there are problems with some customer data.
• We improve the synchronization of customer information and meta fields, and improve stability to prevent synchronization from stalling even when updates are concentrated.
• Other minor corrections