Skip to main content

Salesforce B2C Commerce Cloud Implementation for Beauty Goods Company

Implementing an eCommerce website from scratch starting from the idea and UX design and finishing with accessibility (ADA)

Published by jetbi
05 July 2023
Salesforce

Project description

The customer is a major skincare and face care brand that needs to allow the buyer to comfortably choose and buy the right product online. To accomplish this, we will develop a user-friendly website, based on Salesforce Commerce Cloud (SFRA).

 

Challenge

Implementing an eCommerce website from scratch starting from the idea and UX design and finishing with accessibility (ADA), the solution had to be fully compliant with SFRA. Multiple UX components of the solution for over 10 forms were architected to be reusable and thus customizable. Additionally, full responsiveness of the design and using the same components for different screen resolutions was a requirement. Pagination had to work properly for every resolution showing the optimal number of records on each screen size

 

Project scope

  • Requirements review and technical solution design.
  • Add custom templates for the product details page (PDP) following the UX design (Figma-based), and also add a personalized recommendation section with the product, based on the customer demography and the product selected.
  • 5 eCommerce websites for different brands on one core eCommerce instance.
  • The "Contact Us'' section includes 12 variations of the forms. These forms will provide customers with the ability to describe questions or problems they may have. The data collected by the forms were sent to a third-party service using AJAX on the client side. On the server side, a dedicated controller was created to handle the data submission process.
  • Customer profile page. This page was technically designed with several templates such as Order history, Client profile information, as well as variations for a registered client and a guest. Additionally, templates for tracking order status and product location during delivery were implemented.
  • Search results page. This task included separate templates for both the results block and search results page, ensuring they will be optimized for various devices such as mobile and desktop. The templates will be adapted to display the appropriate number of matches found and will accommodate different brands. Also, the admin ability to configure the search results to be displayed either as a modal popup or as a right sidebar, depending on the site.
  • Create the configuration for Content Assets and Content Slots, Content assets configuration for both static content like advertising banners and images, as well as specific categories of individual banners and recommended products. This configuration will enable easy management and customization of content throughout the website, allowing for seamless integration of various types of content assets in different slots.

 

Result 

The result of this project is a modern, scalable, and customizable web-store solution for 5 brands managed centrally through one eCommerce core system. Conventional user experience, fully responsive and accessible across mobile, desktop, and tablet devices. It adheres to the accessibility requirements and provides a user-friendly admin panel (Business Manager in Salesforce Commerce Cloud) for efficient management of products, orders, and email communication. The store also features a user-friendly interactive form “Contact Us” to address customer inquiries effectively. Additionally, a highly flexible product filtering system is implemented, enabling customers to quickly find the desired products based on their specific preferences.

Start your project now
Expertise
JET BI TEAM
  • 1 Certified Frontend/Salesforce Commerce Cloud Developer
  • 1 Certified QA Engineer
  • 1 UX designer
TECHNOLOGIES
  • Salesforce
  • APEX
  • Git
PROJECT TIMELINE
  • 10 months
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026