Website design / PROJECT CASE STUDY

Skincare Ecommerce Case Study: Dew

A skincare shopping experience with ingredient-led comparison, skin-preference filters and product information placed beside purchase actions.

Skincare collection discovery
Industry
Beauty & skincare
Focus
Ecommerce
Experience
Responsive web

Project brief and workflow decisions

The shopping journey needs to support a considered comparison rather than rely on product photography alone. The supplied desktop screen makes texture, key ingredient, use timing and price available in a consistent product layout, while the skin-preference control narrows the comparison.

01

Comparable product information

Products use a shared information order: name, price, texture, key ingredient and when to use the item. A customer can compare those fields without opening several unrelated descriptions or relying on visual packaging differences.

02

Preferences before selection

A skin-preference filter sits next to the product comparison. Shop, Ingredients and Routine navigation support different browsing intentions: finding an item, understanding an ingredient or considering several products together.

03

Purchase actions with context

Each comparison column keeps its add-to-bag action beneath the same essential product fields. The layout ties the decision and the action together. The project’s mobile views present the shopping experience on a narrower screen without discarding product context.

For products people compare carefully, make the comparison criteria part of the interface. The ecommerce platform should support that information model and the team responsible for keeping it accurate.

Explore the relevant development service for this project workflow to discuss your requirements.

Enterprise reference architecture

A proposed engineering design for this workflow. The enterprise scenario and stack below are illustrative architecture choices; they are separate from the confirmed project screens.

The enterprise scenario

A skincare retailer expands into several markets with product variants, ingredient-led discovery and stock supplied by an external operations platform.

Architecture objective: Keep comparison content flexible while making the commerce platform authoritative for the purchase and the operations platform authoritative for agreed inventory fields.

Proposed technology stack and rationale

Storefront

WordPress, a custom theme and WooCommerce blocks

Develop reusable comparison and product-detail components over the supported WooCommerce storefront.

Commerce boundary

WooCommerce REST API and a payment gateway extension

Use supported catalogue, cart and checkout capabilities; assess extension requirements and plugin upgrades separately.

Product enrichment

Variable products, product attributes and Advanced Custom Fields

Separate approved ingredient and routine content from transactional price and inventory.

Integration layer

PHP, Action Scheduler and MySQL

Validate provider events, retain integration references and reconcile stock changes with external operations.

Operations

Sentry and synthetic purchase-path checks

Observe catalogue freshness, webhook failures and checkout handoff without recording sensitive payment information.

Technical challenges and design approach

1

One product, several content owners

Pricing, ingredients and availability have different authorities. Define field ownership and publishing rules before introducing synchronisation.

2

Repeated provider events

A webhook retry should not repeat a stock adjustment. Persist the provider event identity and make the mutation idempotent.

3

Market-specific buying rules

Currency, shipping eligibility and product restrictions change the journey. Resolve the applicable context before presenting a purchase choice.

How the proposed workflow fits together

  1. Approved catalogue and ingredient records populate the storefront read model.
  2. The visitor applies preferences and compares consistent product attributes.
  3. A cart request is validated through supported commerce APIs rather than a browser-owned price calculation.
  4. The checkout handoff remains with the payment-capable commerce platform.
  5. Order and inventory events pass through a validated queue and a periodic reconciliation process.

Acceptance and failure-path checks

  • A stale product page cannot override the authoritative cart price.
  • Duplicate and out-of-order webhook events do not apply the same adjustment twice.
  • The comparison remains usable when optional enrichment content is unavailable.
  • A migration rehearsal checks product identifiers, redirects, variants and representative orders.

The tradeoff

A customised WooCommerce store adds theme, plugin and upgrade responsibilities. A standard theme with a few well-supported extensions is a better starting point when it already satisfies the buying journey.

Architecture references: WooCommerce developer documentation and Action Scheduler documentation. These describe engineering patterns, rather than certify this project’s implementation.

What the project brings together

  • Skin-preference filtering
  • Ingredient, texture and use-time comparison
  • Product-level add-to-bag actions

Let’s create what’s next.

Bring your idea. We’ll help you find a clear way forward.

Discuss your project