MACH in practice: how Crate & Barrel and Harry Rosen did it

Rory Dennis
August 24, 2020
15 mins
MachEcommerce

Originally published August 2020. Updated November 2026 to add Harry Rosen’s MACH story, key takeaways and current Amplience product names.

MACH in practice means picking a specialist tool for each job, connecting them through APIs, and letting business teams change content without a developer release. Crate & Barrel and Harry Rosen both rebuilt their ecommerce stacks this way, with Amplience CMS and Amplience DAM managing content and media. Here’s what each built and what changed.

In 2018, Crate & Barrel’s gift guide needed developers to build it. The marketing team had big plans and shipped a cut-down version.

Two years later in Toronto, Harry Rosen’s commerce platform was straining under lockdown traffic while its stores closed. Both teams told their stories at the Amplience Summer Summit in 2020, and they’re still two of the clearest examples of composable commerce working at retail scale.

Key takeaways

  1. MACH stands for microservices, API-first, cloud-native and headless. In practice, a retailer picks the best tool for each job and connects them through APIs.

  2. Crate & Barrel moved its content to Amplience in 2018, took developers out of day-to-day content changes, and started publishing new content daily.

  3. Personalized content managed in Amplience lifted Crate & Barrel’s conversion by up to 60% for targeted segments.

  4. Harry Rosen replaced SAP Hybris with Next.js, Vercel, commercetools, Algolia and Amplience, and launched its first release in 16 weeks.

  5. Content modeling, live preview and caching decide whether a MACH build pays off for the people who create content every day.


What is MACH, and why does it matter to retailers?

MACH stands for microservices, API-first, cloud-native and headless. Instead of one commerce suite doing everything, each job goes to a specialist tool: content, commerce, search, the frontend. APIs connect them, so a retailer can swap or add a piece without rebuilding the rest.

Amplience is a founding member of the MACH Alliance and MACH certified. For the full explainer, read everything you need to know about MACH architecture.

The theory is easy to agree with. The two stories below show what it looks like on a real site, with real deadlines.

How did Crate & Barrel put MACH into practice?

Crate & Barrel was founded in 1962 and is part of the Otto Group, alongside CB2, Crate & Kids and Hudson Grace. It sells houseware, furniture and home accessories through stores and online, and launched its first website in 1999.

“Our purpose is to help people love how they live in the moments that matter.”

Melissa Liotus, then Director of eCommerce, Marketing & Merchandising at Crate & Barrel

A cross-functional ecommerce team runs content, promotions, messaging and merchandising for the Crate & Barrel and Crate & Kids sites and apps. Business leads, frontend developers, copywriters and designers all sit in that one team.

What wasn’t working before?

Commerce and content lived in separate parts of the site. At one point Crate & Barrel overcorrected with so much inspirational content that it got in the way of shopping.

The homegrown CMS made things worse. Version control, content workflows and preview were all missing, and the tool was built for developers rather than the people writing the content. Every copy or design change went through development, so content managers sat closest to the business but couldn’t touch live pages.

“We were not reacting to the business as quickly as we needed to, we had little agility as a team.”

Melissa Liotus

What changed with Amplience?

In 2018 Crate & Barrel adopted a MACH architecture, with Amplience CMS for content and Amplience DAM for assets. Designers build modules and templates once, and those rules hold no matter who creates the content.

Business users now review data and change content without waiting for a deployment. Amplience shows each piece of content in a live preview before it goes out, and SEO and accessibility checks sit inside the workflow, so nobody can skip them.

Updates also went from one-to-one to one-to-many. A single change in Amplience can update every page that uses it, which meant the same team could produce far more without extra hires.

“Now we’ve been able to scale our team’s workload across an additional brand and Canadian versions of multiple sites with personalized regional content. We now launch new and updated content daily.”

Melissa Liotus

How did content move into the shopping path?

With the new foundation in place, the team stopped treating the homepage as the front door. Shoppers were arriving from Google Shopping ads and social posts straight onto product pages.

“Shopping can begin on Google or social media which means every interaction has to reinforce the brand at every moment in the shopping journey to differentiate and inspire purchase.”

Melissa Liotus

So Crate & Barrel built content into the pages where people already were. Customer interviews, usability studies and workshops with store teams shaped a content plan for each category, delivered through Amplience content built into redesigned product and category templates.

Gift guides show the difference. In 2018 a custom-built guide reached only a fraction of the original idea and wasn’t available in the mobile app. In 2019 the seasonal guides moved into the evergreen gift guide section, managed in Amplience.

“We saw a 77% increase in site visitors YoY, a 40% decrease to bounce rates and a conversion lift of 10% compared to the previous year.”

Katie Patt, then Manager, eCommerce Brand Marketing at Crate & Barrel

Mother’s Day followed the same path. The 2019 page was hand-coded. In 2020, content managers dropped content modules straight into the category template and scheduled daily deals in Amplience ahead of time.

Other examples from the same period:

  • Guided selling. Research showed shoppers didn’t know which bedding material suited them, so the team built a visual material guide and reused it on the homepage and product pages.

  • The Frame. Blog, SEO and brand content moved from a separate blog site into one long-form destination on crateandbarrel.com, built from templates the creative team can use alone.

  • “What’s new” pages. Seasonal trend pages cut exit rates by up to 60% and lifted conversion by 17% for visitors who saw them.

How did a team of 11 scale personalization and testing?

The team that ran all of this had eleven people: four business leads, five designers and two developers. Each business lead owned an area of the site and worked directly with designers.

Katie Patt made one rule non-negotiable: personalized content had to be managed in Amplience. Crate & Barrel ran five segments across homepages and subcategories, adapting content to browsing behavior. The results were conversion up by as much as 60%, bounce rate down 20% and revenue per visitor up by as much as 40%.

Every Amplience template carried a tracking ID, so the team could tie each piece of content to revenue and conversion. In a single year Crate & Barrel ran more than 80 tests. Three stood out:

  • No dead ends. Content blocks at the bottom of every product listing page lifted mobile conversion by up to 20% and desktop by 5%.

  • Inspiration first. Moving promotions out of the hero and below it had no effect on promotional sales, so the brand could lead with inspiration.

  • Keeping visitors on product pages. Extra product options on landing product pages cut bounce by 4% and lifted conversion by up to 15%.

“Now, nothing is too big or too small for us to tackle.”

Katie Patt

How did site speed and accessibility hold up?

Crate & Barrel sells on quality, so the images had to be big and sharp without slowing the site. Developers built image best practice, such as lazy loading, into the frontend modules once. Designers and business users never have to think about it.

Crate & Barrel reported Amplience response times consistently under 125ms, with no performance issues even through the traffic surge of 2020.

Accessibility worked the same way. Focus states, color contrast, readable type and alt text were built into the modules to meet WCAG 2.1, the standard at the time (WCAG 2.2 has since replaced it). The site scored 94 or higher on Google Lighthouse accessibility without extra developer work on each piece of content.

James Conroy, then Senior Interactive Developer, put it in personal terms.

“Amplience allowed me to step away from Crate & Barrel for 9 weeks of paternity leave with no performance, content creation or accessibility concerns.”

James Conroy

What happened when stores closed in 2020?

Every Crate & Barrel store closed, and the business became 100% ecommerce overnight. Traffic hit Cyber Week levels every day for three months, and a roadmap normally planned six months out had to be rewritten.

The team met twice a day. Business owners created and published content in Amplience several times a day, shifting to what customers now wanted: home offices, working from home with kids, virtual happy hours. Before the move to MACH, reacting at that speed wouldn’t have been possible.

You can watch the full Crate & Barrel session on demand.

How did Harry Rosen replatform onto MACH?

Harry Rosen is a Toronto-based luxury menswear retailer, founded in 1954. The brand is known for personal, high-touch service in its stores, and it wanted the same feel online.

For Harry Rosen, a customer-first experience online had to be:

  1. Fast, especially on mobile.

  2. Personalized, putting the right product in front of the right customer at the right time.

  3. A complement to the in-store experience, not a competitor to it.

Customers choose when to shop with an advisor and when to go it alone. Thousands of possible journeys mix store and online moments, and Harry Rosen wanted all of them to feel like one brand.

Why did Harry Rosen move off a monolith?

Harry Rosen was running an older version of SAP Hybris (now SAP Commerce Cloud). The choice was to upgrade or start again. Development on Hybris needed specialist skills and moved too slowly for what the brand had in mind.

“eCommerce in a box is a commodity.”

Ian Rosen, then VP Digital & Strategy at Harry Rosen

The team decided APIs were the key to recreating store processes online. Harry Rosen wanted to own the frontend and connect backend systems behind it, picking the best component for each job.

Harry Rosen hired Orium (then called Myplanet) for architecture planning, vendor selection and build. Two in-house developers handled ongoing maintenance, and internal business analysts turned store processes into project requirements. Orium and Harry Rosen spent a lot of time in stores, talking to staff and customers about how the brand actually sells.

Which tools did Harry Rosen choose?

The monolith was broken into specialist parts:

  • Next.js as the frontend framework, hosted on Vercel.

  • Amplience CMS and Amplience DAM for the experience layer: navigation, pages, slots, content types and media.

  • commercetools for commerce: catalog, carts, orders, pricing and promotions.

  • Algolia for search, used by customers online and by staff in store.

Then Covid-19 hit. Hybris struggled with rising traffic and shifting promotions, stores began closing, and the new stack had to go live fast. Orium split the work into short sprints and brought the first release down to a 16-week deployment.

How did Harry Rosen model content for a component-based frontend?

Monolithic platforms build pages from one template engine. A Next.js frontend is made of components, so every component that editors control needs a matching content type in Amplience.

Harry Rosen mapped those content types to frontend components at a granular level, using slots and delivery keys rather than whole pages. A simple content block, for example, holds a title, an image and a call to action. Editors can drop it into any page or listing, and a matching frontend component renders it.

Nesting builds more complex types when they’re needed, but keeping types simple makes them easier to build and maintain. Designing components first in a tool like Storybook lets stakeholders and editors agree on scope before anyone writes a schema in Amplience.

How do editors preview content before it goes live?

Once a component and its schema exist, editors can preview it in Amplience before scheduling or publishing. Orium built the preview app on Amplience’s virtual staging environment, which serves unpublished content to the frontend code.

The preview runs the same code as production, so what editors see is what customers get. After setup, developers drop out of the loop and editors stop waiting on anyone.

How does product data get into content?

Amplience’s Product Selector extension lets editors search commercetools and add products to content without leaving Amplience.

A product carousel stores only the commercetools product IDs in Amplience. The frontend uses those IDs to pull fresh prices and details from commercetools at render time, so nothing needs bulk syncing. Merchandisers and content teams work independently, and customers always see current data.

How does caching keep the site fast?

Vercel hosts the Next.js site, its serverless functions and its CDN. Plain client-side React apps render a blank HTML page and then load content, which hurts SEO, so Harry Rosen renders on the server and caches pages and API responses at the edge.

Most requests go through a serverless caching layer rather than straight to commercetools or Amplience. The exceptions are Algolia search and images and video from Amplience Dynamic Media, which already has its own CDN.

Harry Rosen uses a stale-while-revalidate approach. Vercel serves the cached response straight away and refreshes it in the background once it’s more than 24 hours old, so normal traffic keeps the cache current. Harry Rosen reported response times typically two to four times faster, and the APIs behind the site are shielded from traffic spikes.

What happened next for Harry Rosen?

The stack has kept growing, with Bold Commerce for checkout and Convictional for onboarding new suppliers, according to the MACH Alliance case study. Harry Rosen and Orium went on to win Best Retail Project at the first MACH Awards.

You can watch the Harry Rosen session and the technical deep dive with Amplience, commercetools and Orium on demand.

What can other retailers take from these two stories?

Crate & Barrel started with content and put it inside the shopping path. Harry Rosen started with the whole stack. Both got the same thing out of it: business teams who change the site themselves, fast.

A few patterns show up in both:

  • Model content around components. Amplience content types that match frontend components are what let editors build pages without developers.

  • Give editors a preview they can trust. Live preview in Amplience removed the last reason to call a developer.

  • Build quality in once. Image handling, accessibility and caching live in the code, so content teams don’t have to remember them.

  • Measure every piece of content. Tracking IDs in Amplience templates turned Crate & Barrel’s design debates into tests.

Thinking about MACH for your next project? Talk to an Amplience expert about where to start.