Mixed commercial model
The platform needed to support jewelry sales, service requests, repair paths, and gold intake without forcing every flow into a simple product-card pattern.
Guldina Jewelry
A commerce foundation for jewelry, repairs, and gold intake.
Guldina needed more than a storefront. The platform had to connect catalog, content, identity, checkout, and precious-metal workflows into one flexible foundation.
Platform blueprint
The case study now uses a responsive information model instead of a fake product mockup.
01
Storefront
A Next.js experience for product discovery, service journeys, educational pages, and future customer-facing flows.
02
Commerce engine
Medusa-backed catalog and order foundations that can evolve with product, repair, and intake workflows.
03
Trust layer
Authentication, checkout, and pricing integrations designed around higher-trust Nordic commerce expectations.
04
Content operations
Contentful-managed pages so business and marketing content can move without waiting for a release cycle.
- Client
- Guldina AB
- Industry
- Jewelry and precious metals
- Scope
- Commerce, content, authentication, gold workflows
- Window
- 2024-2025
Brief
One platform for the messy reality of jewelry commerce.
A jewelry business does not behave like a simple product catalog. It needs product sales, repair requests, gold valuation, customer trust, campaign content, and secure account flows to support each other.
The work focused on creating a platform foundation that can keep evolving as Guldina adds services, content, and commerce flows.
High-trust interactions
Pricing, identity, payment, and transaction context matter more when customers are dealing with jewelry and precious metals.
Content ownership
Campaigns, education, and service pages needed a content operation that did not require engineering for every update.
Platform approach
Separate the layers so the business can keep moving.
The architecture story is deliberately plain: each layer has a responsibility, and no single layer should block the others.
01
Storefront
A Next.js experience for product discovery, service journeys, educational pages, and future customer-facing flows.
02
Commerce engine
Medusa-backed catalog and order foundations that can evolve with product, repair, and intake workflows.
03
Trust layer
Authentication, checkout, and pricing integrations designed around higher-trust Nordic commerce expectations.
04
Content operations
Contentful-managed pages so business and marketing content can move without waiting for a release cycle.
What was built
A stronger commerce baseline without pretending the case study has finished proof assets.
Headless foundation
Independent storefront and backend deployment paths with room for new services and future workflow changes.
Flexible catalog thinking
A model that can support products, service-like journeys, repair requests, and gold-related flows.
CMS-managed pages
Content models for campaigns, service pages, and educational material so the business can move faster.
Nordic trust baseline
Authentication and checkout foundations aligned with customer expectations for high-trust transactions.
Technology stack
Built on a headless, API-first stack.
The stack choices reflect a need for separable commerce, content, and customer-facing surfaces.
Next.js 15ReactTypeScriptMedusa.jsContentfulBankIDPostgreSQLRedisStripeVercel