B2B ecommerce is just different. When companies transact with consumers online, certain things are taken for granted as "standard"... you and I are going to pay the same price for a product, use a personal credit card to pay for it, and be able to specify where I want the goods shipped to. These "standards" are all turned on their head in the realm of B2B. Different customers pay different prices for the same product, and usually pay a different unit cost based on how many they order (or even when they want it). Payment methods abound, credit card, direct debit, or generation of an invoice to be paid later. And the customer is no longer a single entity, but rather a company made up of multiple users, each with different purchase permissions. Most eCommerce platforms out there were built from the ground up to accomodate B2C use cases and process flows, and when agencies try to utilize these platforms to accomodate complex B2B client requirements, they usually find that they need to heavily customize or "un-do" many of the core capabilities that are built into the platform. Drupal Commerce is different. Using some of the foundational concepts / building blocks that are baked into Drupal (nodes, taxonomies, views, feeds, etc.), savvy Drupal developers are able build eCommerce applications that support complex B2B transaction types without a lot extra code "overhead". This session will reveal just how the complexities of B2B eCommerce pose challenges for traditional commerce platforms, and shed light on yet another scenario where Drupal is the right tool for the job