STORES

Name: STORES
Brand: ヘイ株式会社

Leader

Just for Fun. こだわりや情熱、楽しみに駆動される経済をつくる

Est 2012|Valuation $768.3M|Raised $208.6M

LinkedIn 376|Website|Web traffic 21K|FTEs 332|HQ Tokyo, Japan

MarketseCommerce Software Invoicing & Payment Processing

Published Sep 26, 2026

01Common complaints

- If enterprise-grade compliance evidence beyond PCI (e.g., SOC 2 Type II report) is required as part of vendor risk assessment and cannot be obtained from the vendor. - If rapid, high-touch support and uninterrupted settlement timing are critical to operations and any payout delays would pose severe business risk; independent complaint aggregators contain signals about support responsiveness and bank-side payout delays that should be considered. - If an exploratory or short-term trial is needed without financial risk, since early termination fees and hardware purchases can make trial-and-error expensive compared to purely usage-based alternatives. - If primary requirements center on global e-commerce scale (multi-market storefronts, extensive apps, complex logistics), other platforms may offer a larger ecosystem, albeit often at higher total cost when app fees are included.

Deal disqualifiers (poor fit)

Organizations that require documented SOC 2 or ISO 27001 attestations and advanced enterprise IAM capabilities that are not publicly documented by the vendor
Organizations requiring extensive global e-commerce customization and a very large third-party app ecosystem (other platforms may be preferable)
Organizations that require month-to-month arrangements with no exit fees and are unwilling to accept potential contractual termination costs

Limitations/signals from sources

- Support and UX complaints: independent aggregator posts include reports of slow responses, confusing forms, and perceived promotional clutter in some user experiences. - Payout/settlement realities: vendor notices indicate that bank-side factors can cause delays; merchants should plan cashflow buffers and confirm settlement schedules. - Contractual constraints: bundled plan terms and cancellation fees can materially affect exit costs; buyers should align commitment terms with business horizons.

Roadmap (not publicly available)

No formal public product roadmap with dates was located in the reviewed materials. The vendor blog shows ongoing engineering work but does not constitute a dated product roadmap commitment. Buyers should request a product roadmap or feature timeline where relevant to procurement.

Scale limitations

Scale metrics (maximum throughput, recommended store count per account, SKU limits) were not documented in the materials reviewed. Request reference architectures and performance limits if deploying at larger scale.

02Why they buy

Unique selling points supported by accessible evidence

The vendor has published a claim of PCI DSS v4.0 compliance covering payments and online shop components.
Public messaging and pricing pages position the vendor as offering a bundle of multiple store tools under a single monthly plan referenced at ¥3,300/month.
Press coverage and vendor messaging reference specific card-present rates for certain plans; organizations should verify eligibility and the condition set associated with those rates.

Where competitors have clearer advantages

Some alternative platforms provide a larger third-party app ecosystem, broader international expansion tooling, or different enterprise-grade security attestations; buyers should compare along the dimensions most relevant to their business.

03Field reports

Review-platform coverage (G2 / TrustRadius / Gartner Peer Insights)

Major English-language review platforms (such as Gartner Peer Insights, G2, TrustRadius) did not surface STORES-specific product review pages in the crawl results used for this report. Coverage on those platforms may be limited or restricted; organizations should perform targeted searches and request references from the vendor.

Japanese review / complaint aggregators (example: みん評)

- Aggregated user posts on Japanese sites show mixed feedback with recurring themes including support responsiveness, confusing flows, and UX concerns. Example signals identified in the accessible review content: - Reports of slow support response in some user posts. - Complaints that certain application flows are confusing. - Feedback about promotional content or cross-promotion being intrusive in some user experiences. - Instances of marketplace trust issues or dissatisfaction with specific merchants listed on vendor-hosted storefronts; these reflect marketplace moderation and merchant vetting challenges rather than only software quality.

Vendor-authored content vs independent reviews

Vendor-authored posts report improvements in app ratings and product engineering changes following product updates; these are vendor-provided signals and are not substitutes for independent reviews. Organizations should seek independent user references when assessing support and operational performance.

App store listing (signal)

App store listings provide feature descriptions and target industry signals but are not a substitute for representative independent review samples.

Common reasons cited for choosing the product (observed in comparisons and pricing discussions)

Bundled plan messaging and pricing structure that groups multiple store tools under a single vendor and plan.
Reported card-present rates within certain plans that may be competitive for merchants who meet plan eligibility conditions.

Churn / reasons some customers leave (signals from sources)

Frustration with support response times and unclear processes reported on complaint aggregators.
Payment operations issues such as payout delays (including bank-side delays) can damage merchant trust even when the vendor has processed transactions.

Vendor-published engineering/security work (proxy for maturity)

The vendor product blog contains technical posts that describe architectural and engineering changes. These posts indicate an engineering organization working on maintainability and scalability, but they do not constitute independent customer outcome case studies.

PCI DSS v4.0 compliance announcement (security case)

The vendor announced PCI DSS v4.0 compliance and describes related governance. This is a vendor-published statement; the materials reviewed did not include an independent audit report or downloadable attestation.

Lack of independently verified ROI case studies

No detailed, independently verified customer ROI case studies were identified in the materials accessed for this report. Prospective buyers should request references in their vertical, before/after metrics with methodology, and incident/support SLA history to support procurement decisions.

04Best fit

Company sizes

Micro to SMB: sole proprietors to organizations of several dozen employees (typical for merchants using integrated POS/booking/e-commerce workflows). Buyers with larger scale or enterprise requirements should request scalability references.

Industries / verticals

Salons, beauty, wellness, fitness studios (booking + POS + payments synergy)
Small retail (POS + payments + light e-commerce)
Clinics and other appointment-based services

Roles and personas

Owners and operators of SMB storefronts
Store managers responsible for daily reconciliation and staff operations
Administrative staff managing bookings and customer communications

Qualification criteria (good fit)

Organizations seeking a single vendor for multiple store functions to reduce vendor management overhead
Organizations operating primarily in Japan that require Japan-specific payment and operational conventions
Organizations that accept the vendor's contract terms, including any early termination provisions and hardware purchase expectations

05The pitch

What the product does (core value proposition)

STORES (STORES, Inc.; domain: vendor domain redacted) is a Japan-focused store digitalization suite aimed at small and mid-sized merchants that operate omnichannel workflows. The product family commonly includes: - STORES ネットショップ (e-commerce / online store builder) - STORES 決済 (in-person and some online payments; payment terminal + app) - STORES レジ (iPad/iPhone POS register) - STORES 予約 (appointment booking / scheduling) - STORES 請求書決済 (invoice-style card payments / pay-by-link for invoices) - Additional related merchant tools and content for merchant operations A key positioning element is bundling multiple merchant workflows (online store, POS, payments, booking) into a single plan and a unified administration/support experience. STORES markets a bundled plan at published monthly bundled plan pricing available from the vendor (see Pricing).

Target market and market positioning

Primary: Japanese SMBs (single-location and small chains) in retail, salons/beauty, wellness/fitness studios, clinics, small service businesses, and small e-commerce brands.
Positioning: a domestic alternative to pairing separate tools (for example, an e-commerce platform plus a separate payments/POS vendor and a booking system), with features and pricing configured for Japan-specific payments and operations.

Get a comprehensive analysis of STORES including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →