LangChain Retail Japan

Rakuten Group

Customer Service Automation · Enterprise Knowledge Search · Sales Automation

Rakuten wanted to augment both business clients and employees with AI products for market analysis, support, and knowledge work while keeping control over prompt quality, model experimentation, and enterprise data separation across a sprawling multi-business environment.

It only took three engineers one week to get the initial platform up and running.
improve productivity by 20%
intend to roll the product to 32k employees

Reported impact

Business outcome

Rakuten stood up both customer-facing and employee-facing AI products quickly, created a repeatable enterprise prompt-and-eval process, and set the platform up to improve productivity across merchants, hotels, retailers, and internal teams.

  • Customer Experience
  • Productivity Improvement
  • Speed to Market

Solution

Rakuten built a portfolio of AI products on LangChain and LangSmith rather than a single assistant. Rakuten AI for Business serves clients with AI Analyst for market intelligence and chart-backed research, AI Agent for self-serve marketplace support, and AI Librarian for real-time answers over merchant documentation. Internally, the team used LangChain’s OpenGPTs package to stand up an employee platform where teams can build chatbots over internal knowledge. LangChain supplied the reusable chains, agents, and interoperability Rakuten needed to iterate quickly without locking into one model vendor. As usage scaled, LangSmith Hub became the mechanism for distributing the best prompts across teams, while LangSmith Testing and Eval ran custom metrics across models and cognitive architectures inside Rakuten’s own environment with separate development and production access controls.

Data flow

Business clients or employees interact with the relevant Rakuten AI product, LangChain chains and agents pull the right prompts and document context, and LangSmith Hub plus Testing and Eval feed better prompts and experiment results back into the stack while keeping development and production access separated inside Rakuten’s environment.

Solution architecture

8 components · 3 layers
  1. Serving
    • Rakuten AI for Business Acts as the umbrella platform for client-facing AI products.
    • Rakuten AI Analyst Provides market intelligence and data-backed business insights to clients.
    • Rakuten AI Agent Handles self-serve support questions related to marketplace listing and transactions.
    • Rakuten AI Librarian Answers end-customer and prospect questions over business documentation in real time.
  2. Orchestration
    • LangChain Provides reusable chain and agent patterns plus model interoperability for the applications.
    • OpenGPTs Powers the employee chatbot platform over internal documentation.
  3. Governance
    • LangSmith Hub Distributes strong prompts and encourages prompt sharing across teams.
    • LangSmith Testing and Eval Runs custom evaluations across models and architectures to measure results scientifically.

Architecture clues

  • LangSmith is used to compare models, prompts, and cognitive architectures across teams.
  • Rakuten keeps data inside its own environment and separates development access from production access.
  • The same LangChain foundation supports both customer-facing products and internal employee chatbots.

Evidence from the source

By using LangSmith Hub, we could distribute the best prompts
By using LangSmith Testing and Eval with our custom evaluation metrics, we can run experiments on multiple approaches
It only took three engineers one week to get the initial platform up and running.
improve productivity by 20%
intend to roll the product to 32k employees
Transparency Evidence & methodology 90/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. LangChain

    Rakuten Group customer story

    First-party
    https://blog.langchain.dev/customers-rakuten/
    Source type
    Vendor-published customer story
    Published
    Feb 14, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Feb 14, 2024 · LangChain · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.