Tackle the complexity that comes with deploying a commerce site spanning multiple brands, channels, and countries. See these real stories that depict the typical complications of these complex projects, and learn how to identify, anticipate, and navigate the risks, so your project can succeed. For more from SAP Hybris, please visit: https://hybris.com/en/downloads

1. PUBLIC
Tomas Straka, SAP
October2017
Multibrand, Multicountry:
What Could Possibly Go Wrong?

2. 2PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Multi-country
Multi means contextual
Multi-brand
Multi-currency
Multi-language
Multi-prices
Multi–time zone
Multi-cultural
Multi-channelOmnichannel
Multi-device

3. 3PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Examples
Multiple brands
§ Result of an acquisition process
§ Need for some unification
§ Different business models, product
sets, processes, teams
Multiple business models
§ B2B / B2C / B2B2C
§ Shared product content
§ Channel-specific pricing, ordering,
payment, delivery
§ Distributor-specific content
Multiple countries
§ Global product set, IT organization
§ Local go to market and content
management, local teams

4. 4PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Core focus: to align multiple teams serving multiple brands, countries, and business models
using one solution
“One team does it all” model also exists:
§ Challenges are of a different nature: better understanding of the local context
§ Not our focus during this presentation
Multiple teams
?

5. 5PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Conway’s law:
“Any organization that designsa system (defined broadly) will produce a design
whose structure is a copy of the organization's communication structure.”
Melvin Conway, 1968
Result: design that does not create an appropriate context for customers outside of one
preselected country and brand
Ignore others

6. 6PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
When coding is under way but not every affected
organization has contributed yet

7. 7PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Teams communicate, each comes with its own set of ideas. Without an overarching
authority they tend to build copies of their own solutions on “one platform.”
Examples:
§ Content driven by a rich classification structure
§ Product versions and variants
§ Content driven by rich product references
Result: design that creates several only partially compatible functionalities
Lost in details

8. 8PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
When coding is under way but the design is not
clear yet

9. 9PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Communicating teams with an overarching authority tend to build complex, expensive solutions
Typical requirement:
§ A unified solution where one can launch a new country/brand with one click
§ At the same time, each country/brand will have a specific payment provider, delivery methods, order
fulfillment, product assortment, pricing, go-to-market strategy, and a unique Web design, Web content,
page navigation, and search result page as well
Result: design that is expensive to implement and realistic go-live is far in future
Expensive compromise

10. 10PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
If your backlog looks similar to the requirements in
the previous slide

11. 11PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
When you have to build complex, expensive solutions, the typical answer is to prioritize
requirements and scope management.
It has the same effect as “ignoring others” discussed earlier in the presentation.
Circle

12. 12PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Focus on positive alternatives to the pitfalls instead
§ Ignore others à Have everyone contribute
§ Lost in details à Unified solution
§ Expensive compromise à Quick go-live
Pick two out of three

13. 13PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Multi-brand, multi-country solution landscape
Are you where you want to be?

14. Thank you.
Contact information:
Tomas Straka
Principal Consultant
SAP Hybris Expert Services
e-mail: tomas.straka@sap.com
cell: +420604347972