Bluespark Drupal 8 Ecommerce Site

The Obermeyer project began with a broad set of challenges, including three separate websites, three distinct audiences, and independent ERP and B2B ordering systems. The goal was to optimize Obermeyer’s digital processes and consolidate their connections with customers through a single, well-integrated platform. Working with Drupal 8 and Drupal Commerce 2.x, the Bluespark team — along with Commerce Guys — designed and developed an enterprise ecommerce solution to facilitate a friction-free purchasing experience for B2C, B2B, and VIP audiences alike.

Klaus Obermeyer created Obermeyer in 1947 and had one goal in mind — to help his ski school students stay warm and dry. Obermeyer remains a family-run, privately held company and is located in Aspen, Colorado.

Here's a video of a presentation given about this project:

Why Drupal was chosen: 

Bluespark has been working with Drupal since its founding in 2009, and focuses on many enterprise-level projects that include content and digital asset management (DAM).

Drupal 8 and Drupal Commerce 2 were chosen over Drupal 7 to give Obermeyer a platform that would have a greater lifecycle and longevity, future proofing the platform and making maintenance simpler.

By being an early adopter to Drupal Commerce, in its alpha stages, the project was able to push forward functionality and priorities in the development of Drupal Commerce 2. With this the Obermeyer project was able to build on a truly flexible ecommerce platform able to support their processes in ways an off-the-shelf solution may not.

Describe the project (goals, requirements and outcome): 

The Obermeyer commerce system is unique. To meet the needs of each audience — or user group — we prioritized user experience throughout the design process. Here is what we had to consider:

  • B2C: Obermeyer honors its long-standing retailer relationships by driving shoppers to complete purchases on 3rd-party dealer sites, requiring an experience that builds trust as the users move through the buying process.
  • B2B: In a fundamentally different sales and shopping process, B2B users buy product in bulk quantities with purchase orders (no cash transactions) often aided by internal sales staff, requiring a solution serving both groups
  • VIP: VIP users (e.g. loyalty program participants) are provided discounts on items that can be purchased directly from Obermeyer in exchange for completing brief online training.

Collaborating closely with Obermeyer to understand how each audience interacts with their business and systems, we leveraged Drupal's flexibility to craft custom experiences for B2C, B2B, and VIP audiences on top of a single, integrated ecommerce and content marketing platform. The outcomes for each user group are important.


  • Seamless integration with 3rd-party dealer sites for inventory and shopping cart handoff
  • Product merchandising and recommendation tools
  • Catalog creation from imported ERP & PLM data and image assets
  • Improved content and catalog management features
  • Updated UI and UX and responsive mobile experience


  • ERP & PLM systems integration for inventory, pricing and order submission
  • Tailored experience for B2B buyers and product line orders with order history
  • Sales representatives can develop orders for multiple stores and locations


  • Product discounts offered in exchange for completed sales associate training
  • One-time discounts for friends, family, and industry professionals
  • Payment gateway integration for online payments
  • ERP & PLM systems integration for inventory, pricing, order submission, and tracking

The combination of Drupal 8 and Drupal Commerce 2.x equipped Obermeyer to streamline such processes as B2B ordering and direct-to-consumer purchasing.

There were a number of outcomes and features driven forward because of the project, including:

  • Sponsored development of the Commerce module
  • Decision to put promotions and coupons as a core 2.x module and initial development
  • Inspiration for the order receipt in 2.x
  • Architecture and requirements for order types, checkout flows, and product attributes
  • Example use case for using Migrate and Commerce Migrate to import external data into Drupal Commerce 2
Why these modules/theme/distribution were chosen: 

Drupal Commerce 2.x: By being an early adopter of Drupal Commerce 2.x, we were able to build a truly flexible ecommerce platform for Obermeyer.

Additionally, the requirements set forth in the Obermeyer project helped validate architecture decisions made for order types and checkout flows in Drupal Commerce 2, and pushed their development. The add to cart form and product attributes were driven in development by this project. The project also brought forth the rendering of product variation fields in parent project, and the AJAX replacement of their display when changing products in the add to cart form.

Organizations involved: 
Project team: 

Michael Tucker - President
Ashleigh Thevenet - COO & Project Manager
Brant Schlatzer - CTO
Rusty Segars - Creative Director & User Interface Designer
Mark Dodgson - User Experience Strategist
James Wilson - Senior Drupal Engineer
Pablo Cerda - Drupal Engineer
Pablo Lopez - Drupal Engineer

Commerce Guys
Matt Glaman - Drupal Commerce Consultant and Project Liaison
Ryan Szrama - CEO

Obermeyer Ecommerce Website_Homepage
Obermeyer Ecommerce Website_Product Page
Obermeyer Ecommerce Website_Outfits Page


rphair’s picture

Ryan Szrama or Matt Glaman mentioned a white paper about this design in their talk at DrupalCon Dublin 2016; perhaps from Bluespark but I can't find anything that detailed on their own web site (there is a nicely illustrated HTML page here). If there is something more detailed available about the implementation, would someone please post it here?

rszrama’s picture

Sorry about that - if we said that, we misspoke and really meant the existing case study. If we publish anything more in depth, we'll be sure to link to it from here. : )