Acro CommerceAcro Commerce
Crystal Lee
By Crystal Lee

Drupal Wordsmith


Posted in

, 

August 2, 2017

All Articles

Products in Drupal Commerce 2.x | Article

Products In Drupal Commerce 2.x

To the average person on the street, a product is something you buy. Say Joe Blow is looking for a t-shirt. Specifically, he wants a blue t-shirt with the logo of his favourite sports team on the front. He goes to an online store, selects the t-shirt with the appropriate logo, chooses the blue colour, and indicates the size he needs. Simple. He has now purchased a product.

 But in the ecommerce world, a product is much more complicated.

Products: More than meets the eye

If you’re the owner of that online store, you know that every size of that shirt is an individual product that has its own SKU. Knowing whether someone ordered a large or small shirt is important for inventory (so you know how many you have left in stock), pricing (maybe you sell different sizes at different price points), and processing (so you know exactly what has to be shipped). Different colours are also different versions of the same product. So a “product” is really a collection of a whole bunch of products. But when your customers are viewing it, they think of the collection as a single product.

How Drupal Commerce 2.x handles products

In 2. x, you have attributes that are used to make up these different products. Each different colour is going to be a variation, and each different size is a variation, and each different size + colour combination is also a variation. So when you build attributes (size, colour, etc.), you actually build products.

You can also have customizations. If Joe Blow wanted his name on the back of that t-shirt, that isn’t really an attribute, because it doesn’t change the product stock. The store would just print his name on a standard T-shirt. That’s an option that gets applied to a product.

Commerce 2.x also lets you set product types to handle physical, digital, and subscription products differently (you don’t need sizes and weights and things for a digital good, for instance).

How this differs from Drupal Commerce 1

The main difference is that it’s more built-in now. In Commerce 1, there were variations, and then you built your own product by making a node (which was pretty confusing to many people). In Commerce 2.x, you set up a product, and add variations to it, and it’s a much more structured process that takes you through what you need to do.

The bottom line: products in Commerce 2.x is not vastly different; they’re more of an iterative improvement over Commerce 1.

To learn more, check out our High Five episode How Drupal Commerce 2.x handles Products.

Subscribe to our YouTube Channel for more Drupal Commerce goodness! Or,

Sign up for our monthly newsletter. Stay in the know, wherever you go | Acro Commerce | Digital Commerce Development news
June 29, 2026

State of composable commerce for B2B 2026 | Acro Commerce

Composable rewards discipline and punishes shortcuts. What delivered ROI across real mid-market B2B builds in 2026, what backfired, and what comes next.
June 18, 2026

Acumatica spotlight: agent-ready APIs | Acro Commerce

A clean API layer over Acumatica lets AI agents and dealers move at machine speed without overrunning entitlements. Catalogue, pricing and quoting exposed.
June 17, 2026

Acumatica spotlight: AI-ready data | Acro Commerce

The ERP already holds the truth. Reshaping Acumatica product attributes and rolling out schema turns an invisible catalogue into an AI-cited source.