Case Study

Berlet

ScopeE-commerce // Client portal

Year2026

Berlet fine jewellery portrait with a ruby ring

01

E-commerce and a custom client portal

Berlet needed more than an online store. The challenge was to sell premium pieces while preserving the workshop-led approach of demanding bespoke work: a precise client journey, creative approvals, production tracking and support after purchase.

The main difficulty was fragmented operations. Product information, design status, client feedback, appointments and support lived in separate channels. That led to delays, lost context and poor traceability on high-value orders.

The project objective was to rebuild the full journey, from acquisition to private client follow-up, with a premium front-end experience and reliable operations behind it.

02

Approach

We approached the project as two connected layers. The first is an e-commerce system with a catalogue, product pages, basket, secure checkout, order tracking and consistent stock data. The second is a private client portal built in React and connected to Firebase to coordinate bespoke interactions.

The client portal organises short approval cycles: sharing designs, contextual feedback, a record of decisions, private messaging and appointment scheduling. A dedicated sharing mode also lets clients show a visual preview without exposing sensitive information.

Berlet diamond ring
Berlet interlaced ring

03

Our solution

Storefront

  • Clear, premium e-commerce journey
  • Structured product pages that reduce cognitive load
  • Focused, secure checkout
  • Consistent stock and order management

Client portal

  • Designs, feedback and approvals in one place
  • Private messaging linked to each order
  • Decision history and clear status updates
  • Visual sharing without exposing sensitive data

Operations

  • Naming conventions and request prioritisation
  • Checkpoints that avoid unnecessary back-and-forth
  • Clear approval roles, timing and criteria
  • Improvement backlog prioritised by business and client impact

04

Technical architecture

The e-commerce front end is designed to reduce cognitive load: clear product hierarchy, readable technical information, explicit calls to action and a consistent mobile journey.

The React/Firebase portal uses structured data: clear case statuses, differentiated permissions, conversation history and time-stamped events. This supports the transitions between creation, approval, revision and confirmation.

05

Outcomes

Berlet now has a complete system: acquisition and conversion through e-commerce, followed by closer client collaboration in the private portal. Conversations are centralised, decisions are recorded and the premium experience remains consistent from the first click to final approval.

During the first production cycles, the team moved faster on bespoke orders: fewer exchanges, quicker decisions and better continuity between e-commerce and the private portal.

6-10h Recovered each week from client coordination and manual follow-ups.
1 source Messages, versions, statuses and approvals brought together in a private space.
Premium A consistent experience across purchase, personalisation, production and follow-up.

06

Visual direction

Interface

Premium minimalism, clear hierarchy, dark surfaces and useful details rather than decoration.

Experience

A clear separation between the storefront that sells and the portal that manages delivery, so their roles do not blur.

Delivery

Short weekly reviews, a backlog prioritised by impact and focused checks at sensitive stages.

FAQ

Clear answers. No guesswork.

Why separate the online store from the private portal?

The storefront needs to convert quickly, while the portal manages longer, contextual and confidential approvals.

What does Firebase bring to the project?

A real-time database for tracking statuses, recording exchanges and managing permissions across the team, clients and orders.

Can the system evolve?

Yes. The architecture was planned in phases, with a backlog prioritised by business and client impact.

What is the main operational benefit?

Fewer manual follow-ups, less ambiguity and better continuity between purchase, personalisation and production.

Let’s
Collaborate

Contact