Latest / Inside Commerce: Ecommerce Strategy, CX and Technology Podcast / EP339: Rebuild & Unify Everything: Deconstructing Lupine’s Hybrid B2B/B2C Migration Strategy
Transcript
- 0:00If we are aiming for simplicity, it's not just for the sake of
- 0:03simplicity, it's it's more about total cost of ownership.
- 0:07If we have to invest money into making some flow of simplicity,
- 0:11it may turn out that it doesn't make sense from a practical
- 0:14point of view. So this video is is always North
- 0:17Star for us. You listen to Inside Commerce, a
- 0:21weekly ecom strategy, technology and CX focus podcast hosted by
- 0:24experienced digital consultants and re platform specialist James
- 0:27Get and Paul Rogers. Get insights into ecom strategy,
- 0:29leading brands, hear from industry thought leaders and
- 0:31leading tech vendors with practical advice to help you
- 0:33improve your online CX. This episode is sponsored by
- 0:39well Pay. Thanks for tuning in again to
- 0:41Inside commerce got an interesting conversation today.
- 0:44So we're looking at the the mechanics of of re platforming
- 0:48and deconstructing a hybrid B to BBT migration and looking at
- 0:54this from a case study point of view of of what drives a
- 0:58project. How do you approach it?
- 0:59How do you architect it? How do you handle some of the
- 1:01challenges in AB to BBT set up making decisions about going
- 1:05native versus third party? And, and the reason why we
- 1:09wanted to do this is we got so Michael who I introduced in a
- 1:12minute and some of you will know anyway who works commerce UI and
- 1:17has got a stack of experience in running RE platform projects
- 1:20across different types of business.
- 1:21But we wanted to comment from an angle that that RE platforming
- 1:27every project is different. Every technology decision is
- 1:31different. The complexity varies.
- 1:33The commonality though is that every project has challenges,
- 1:37every project has a change management process to get people
- 1:40over the line and there are compromises that have to be made
- 1:43in order to get an optimal out output and to be able to deliver
- 1:46on time. So I find these case studies
- 1:48really interesting to explore. So Michael, let rather than me
- 1:52telling everyone about who you are and what you do, do you want
- 1:55to give people a flavour for for commas you are and yourself And
- 1:58what sort of work do you do? Yeah, sure.
- 2:01So yeah, hi James, hi everyone, pleasure to be here.
- 2:05So yeah, I'm Michael Claim. I'm Co founder and city at
- 2:08Commerce Y basically leading 30 around 30 people teams of highly
- 2:15skilled engineers, designers and builders.
- 2:18We are a petite studio doing doing storefronts.
- 2:21I guess we excel at bringing aesthetics and merging it to
- 2:26together with with technology. So yeah, that's that's that's
- 2:30about us. Yeah.
- 2:32And what I love as well is that you've got a lot of experience
- 2:35across building storefronts and themes versus building headless.
- 2:40And this is really important actually because part of the
- 2:42conversation I have about how you make that decision.
- 2:45And I think there's, I think the market's matured in its
- 2:48understanding of a head solution, not a goal, But I
- 2:51think there's still sometimes people who aren't used to these
- 2:54projects get a bit confused about or how would you make a
- 2:56decision. So really looking forward to, to
- 2:59understanding the decision factors in the, in the
- 3:01technology stack. Let's get back context.
- 3:04So this is with Lupine, so well established brands and we're
- 3:11going to talk through the design bit as well.
- 3:13But what I wanted to start with is the brief.
- 3:15So from what I've understood, the brief that you were given
- 3:18was to rebuild everything, unify everything and rebrand
- 3:21everything, which is which is a big and broad brief.
- 3:24How did you then approach discovery and the delivery side?
- 3:28How would you take that and turn that into a technical discovery
- 3:30that covers those three elements?
- 3:33Yeah. So essentially there were two
- 3:36completely separate teams working on a on a discovery.
- 3:39So on one hand, as you mentioned, so or maybe let me
- 3:43start from the from the beginning.
- 3:45So Benedict Bong, who is Lupine CEO came to us with this, you
- 3:50know, bold vision that OK, we have a very, very good brand
- 3:56with, you know, 35 years of experience building lighting,
- 4:01excellent engineering, excellent product, but the digital
- 4:06experience or digital side hadn't keep up basically with,
- 4:10with the hardware. So he he had this bold vision
- 4:15that encompasses rebranding, which was done by, by another
- 4:23team. I have whole digital UIUX
- 4:28rebuild B2B unification at the same time improving operations
- 4:34and of course, the storefront that that manages it all, both
- 4:38B2C and B2C side. So essentially our discover
- 4:42process was was done by two teams.
- 4:48So on one hand, we had to understand their branding and
- 4:52and the vision behind their branding.
- 4:53So there. And it was bold like Benedict,
- 4:58they didn't they didn't want to be for lupine to be just another
- 5:01brand selling, you know, hardware.
- 5:05He wants to put a story behind it.
- 5:07And there was this the slogan shine on it was very right from
- 5:12the beginning. It was very bold.
- 5:14So we had to think about it for in terms of UIUX, in terms of
- 5:21the storefront, how to actually convey that message to old
- 5:26vision to to the to the e-commerce.
- 5:28At the same time, there are many, many structural
- 5:32limitations to how e-commerce should look.
- 5:36So on one, like we discovered very early that they have, so
- 5:43they, they, their assets, their graphics, their videos, photos,
- 5:48they're so great. Like from a visual standpoint,
- 5:51they, they were so, so nice, you know, like those dramatic, very
- 5:58well liked photo shoots, videos and so on.
- 6:01So we knew right from the beginning that we want to use
- 6:03that and give them more, more room to breathe and more room to
- 6:07show. And yeah, we, we knew straight
- 6:13from the straight from the beginning that we will, will
- 6:16have something to work with. So on one hand, those assets
- 6:19I've mentioned and another we, we had the stocks around how to
- 6:27actually show a physical product that produces light in this kind
- 6:32of a 2D specs like showing, you know, like a photo of, of a
- 6:39light of a light itself or, you know, or a bike lamp itself.
- 6:47That's just part of the story. I would say the the not, not the
- 6:51big part of the story. So showing how those devices
- 6:55actually produces light, how what are the characteristics of
- 6:59light? That's, that's completely
- 7:01another one. So, so you had to understood and
- 7:05find the right balance between, you know, showing something that
- 7:09is appealing to, to, to somebody that that is new to, to it and
- 7:15at the same time producing something that is also appealing
- 7:20to, to, to more, more of a professional type of, of the
- 7:24users who looks for actual characteristics of light, actual
- 7:29technical specification and so on.
- 7:30So we have to combine that on a solution slash development side
- 7:36of things. The discovery revolves mainly
- 7:39around the B to B complexities. There are 15 professional
- 7:44groups, groups there with customer bars and processes and
- 7:49so on. So we have to map that out and
- 7:51actually try to, to translate that to Shopify capabilities
- 7:55and, and no, no, what, what fits and what doesn't.
- 8:04At the same time, there was this third challenge.
- 8:07So they wanted to have something simpler and they wanted to
- 8:12simplify their operations. So that was another part of the
- 8:17discovery. So OK, how we take your current
- 8:20flows and map them to, to, to, to the new solution.
- 8:24So do do we need something beside the Shopify?
- 8:28It's just able to handle it completely.
- 8:33Is your current flows work in the in the way they work because
- 8:39it's your actual flow or it's just you had you had some
- 8:44limitations and you designed around those limitations.
- 8:46So yeah, it was actually like a three-part, three-part
- 8:50discoverer process. Ready to grow your business
- 8:53online? With World Pay e-commerce, you
- 8:56can deliver fast, secure payments your customers love,
- 9:00backed by global reach and real people powered support.
- 9:04Scale with confidence and enhance your customers
- 9:07experience with World Pay E-commerce.
- 9:11And I find it really interesting actually, because typically with
- 9:14light, the creative direction is bright.
- 9:18It's bold to to bring in that feeling of you're in a light
- 9:22environment. But the loop on site is very
- 9:24distinctive, as you say, like visual identity is very dark,
- 9:27cinematic. Some of it is almost media.
- 9:28There's a lot of sort of those night time shots, like dusk time
- 9:31shots around people, around roads, people are cycling on the
- 9:34bikes. How do you And there's, there's
- 9:37like the transitions as well across products where it goes
- 9:41from a standard product shop to like a darkened out one with a
- 9:44light coming out of it and it, and it shows the, the field of
- 9:48the light in a, how far the light travels.
- 9:50So it gives you like a relative understanding of the light.
- 9:54How did you arrive at a direction?
- 9:57And how did you, I guess, how did you balance that with the
- 10:00commerce goals? Because the end of the day, the
- 10:02site's there to sell. And maybe you could highlight a
- 10:04a few of the key unique features that that you and the and Leap
- 10:08Leapine are proud of. Yeah, so the the the the first
- 10:11one would be the one that actually shows the light.
- 10:15So there is a comparison model, the module that you can actually
- 10:19pick a couple of different lights or lumps and then you can
- 10:26actually see side by side what's the actual, like the actual
- 10:31photo of of the light itself. So how, how, how it's how it
- 10:35beams the light, is it white or is it narrow?
- 10:39Is it far or not? So those kind of days matter to,
- 10:44to to to whole professional or semi professional users.
- 10:48So I like to think about it in a way, you know, like if you are
- 10:53in like, if you are like 3004 thousand meters above the sea
- 11:00level and it's snowing you, you will care about how how how your
- 11:06lamp is working basically, and what type of light it will it
- 11:10will cast. So the Benedict bomb is is I've
- 11:14been in himself quite well known actually.
- 11:17So he is this kind of first, first hand experience into that.
- 11:22So that's that's one feature. Another one is that every, every
- 11:27light, every product cart with a light has this kind of a graph
- 11:31that besides, you know, besides having the photo of how the
- 11:35lights work, actually we have this graph which helps you to
- 11:39scan very easily the characteristics of the light
- 11:42itself. So yeah, that was like the the
- 11:47one of the main main changes and main driving force behind the
- 11:56design. So to show the light itself, not
- 12:00just, you know, a nice casing around the lamp and so on, but
- 12:05the, the, the light itself. So, and I guess from that point
- 12:09of view, the dark background, the dark theme around the around
- 12:15the site is perfect because yeah, it's, it's just line
- 12:18shines through through, through darkness basically.
- 12:20And it's a perfect background for for shot light.
- 12:25The the other thing that I want to look at is it from an
- 12:27architectural point of view, you, you're you and your agency
- 12:32are well known for head less and hydrogen implementations.
- 12:34You've done quite a few prohypropores I think like
- 12:37Carhartt's one of them, isn't it?
- 12:38If I. Yes, exactly.
- 12:40Yes. So you've gone with a store
- 12:44theme and we'll look at more detail in a bit, but did you
- 12:47consider Headless this project? If not, why not And why did you
- 12:51end up going to Liquid? What'd be great is to hear what
- 12:55was the technical decision making process and the criteria
- 12:58that made you go for a theme. Yeah.
- 13:01Like, yeah, we, we did consider headless.
- 13:03We, we always consider headless the same way we always consider
- 13:06liquid for a project like I would say like liquid or or
- 13:10headless those just another tools in the toolbar basically
- 13:15that we have. So for me always that discussion
- 13:20between headless and liquid wasn't that that simple.
- 13:24I would say like there are many, many dimensions to it, your team
- 13:28composition, your future plans, performance, UIUXAI readiness
- 13:33nowadays. But the B2B was, was the one
- 13:41thing that that that was obvious that that gave the liquid
- 13:46obviously some, some advantage there.
- 13:50So it's not that you cannot do B2B operations on Hallucy.
- 13:57You most certainly can. But then you have to build a lot
- 14:01of things around it, especially in, in CMS and how you handle
- 14:04content, how you handle switching the context of the
- 14:08user. And it's, it's, it's, it is
- 14:10possible. And it can even take this
- 14:14further than liquid. But with liquid out-of-the-box,
- 14:18like the way they handled, you know, mixing B to B content or,
- 14:24or B to B context with international context, for
- 14:29example, and having the option to, to manipulate that.
- 14:32They've done such a great job there.
- 14:35So yeah, that that was one of the main, main decision factors
- 14:42for for going liquid. Another one was like the the
- 14:48design vision was, was bold, bold enough.
- 14:51But we knew and I guess this is like a common misconception
- 14:55around the liquid that you cannot do something bespoke,
- 14:59something custom in terms of UYOX on liquid, it's not true.
- 15:03You can and I guess lupine, lupine is a good example of
- 15:08that. So that wasn't the case of
- 15:11performance also because you can do perform very performance side
- 15:17on the liquid. So yeah, B2BB2B moved us towards
- 15:22the towards the the liquid. There were there, there was a
- 15:29question mark there because we knew that we wanted more from
- 15:33the P2P first. So there's this, there's
- 15:37professional groups, groups that needs unbarred into
- 15:40notification. So then we thought, OK, we need
- 15:43something around Shopify that helps us do that because we need
- 15:47some custom data mapping, custom endpoints and so on.
- 15:52So we did use a bit of a headless in in this project, but
- 15:56it says basically we use hydrogen as an API gateway for
- 16:00that. But it works with Shopify file,
- 16:03it works with with the liquid liquid base.
- 16:06So I guess we have best of both both worlds there.
- 16:12Interesting. And, and that leads me on to
- 16:14like the architectural decision because I haven't worked on
- 16:17loads of projects as well across different verticals, whether
- 16:19it's single storefront or it's AB to C and AB to B or it's also
- 16:24international and you've got different locales.
- 16:27There's always a decision process around domain
- 16:31management, single storefronts, multiple storefronts, markets,
- 16:35not markets. Can you talk us through how you
- 16:41approach this? You know, I think they had two
- 16:44separate sites, duplicated catalog, lots of B to B customer
- 16:47groups. How do you how did you get what
- 16:51solution did you get to and how? Because one of the key things
- 16:54businesses want is simplicity of manage where they don't want to
- 16:57have multiple logins, everything separate, having to duplicate
- 17:00tasks across different storefronts because it it comes
- 17:03frustrian. So yeah, I'd love to hear what
- 17:06solution you came up with and why.
- 17:08Yeah. So for us it's always boils down
- 17:12to to this total cost of ownership.
- 17:15But we, we counted very, very free.
- 17:17So at the end of the day, we, we, you know, if the site is
- 17:24simple, if we, if we are aiming for simplicity, it's not just
- 17:28for the sake of simplicity, simplicity sometimes you, it's,
- 17:34it's more about, you know, the total cost of ownership.
- 17:38So if we have to invest ton of money into making some flow
- 17:43very, very simplistic, it may turn out that it's it it doesn't
- 17:48make sense from a practical point of view.
- 17:50So this video is, is always like a North star North Star for us.
- 17:57The simplest systems are, you know, it's when you don't have
- 18:02to go out of the platform to do things and you don't have to go
- 18:06through free admin partners to to actually manage your site.
- 18:10So we always look at the problems from a Shopify
- 18:15perspective like can Shopify actually handle that?
- 18:18Can, can, can editor editor teams do do that in the Shopify
- 18:25admin? Do we need something external?
- 18:28And in this case, it was actually quite, quite changing
- 18:32and requires some creative approach there.
- 18:35But after initial discovery, we thought, OK, that that that
- 18:40should actually be possible to, to power everything through
- 18:45through Shopify and make the whole whole landscape much, much
- 18:50easier for, for Lupan. So, and it, it, it came out true
- 18:55basically. So yeah.
- 19:00OK, interesting. Yeah, it's, it's always fun,
- 19:03especially when you've got like domain challenges as well across
- 19:08multiple sides. I've seen that especially in
- 19:09international when you've got different domain structures,
- 19:13different team ownerships and there's never A1 size fits all
- 19:17solution. That also then leads me nicely
- 19:20on to the B to B bit because I think it's, it's completely fair
- 19:25to say Shopify is not AB to B leader.
- 19:28They haven't been historically, but they are rapidly catching up
- 19:31in what I call the the non non enterprise complex B to B.
- 19:35So wholesale, smaller accounts, etcetera.
- 19:41They've added a lot of additional functionality opening
- 19:44up like multiple products, catalogues, etcetera.
- 19:48But they came from AI guess a low base in order to try and hit
- 19:52into the core B to B market. I'd love to hear where where you
- 19:57think Shopify is now at because they they're gradually removing
- 20:00barriers to consider them for B to B commerce.
- 20:02Where do you think overall Shopify B to B is and how have
- 20:07you found working on on? I think this is your first large
- 20:10B to B project. Is it?
- 20:12Yeah, if you you can say so like they did like first one that is
- 20:16mainly focused in that way on on, on, on B to B.
- 20:20So yeah, in, in general, I agree, like Shopify B to B, like
- 20:26built in capabilities are pretty nice, but maybe not not for for
- 20:31enterprise great yet. But at the same time, I think
- 20:36the B2B like Shopify B2B is, is a bit further than than general
- 20:43discourses basically. And for me it boils down like
- 20:48they're the, the, the pieces like the building pieces for
- 20:54Shopify are there are not so many pieces out there like there
- 20:58are catalogues. There is the functionality with
- 21:01our connection with, with markets and so on.
- 21:04There's a lot of things done already.
- 21:08But out-of-the-box, you cannot compare it to like purposely
- 21:13built B to B platform. But at the same time shopping
- 21:17fine access at I would say being open.
- 21:21So you, you have a lot of pieces already there, like those low
- 21:25level pieces. You have Shopify flow, which is
- 21:29like building I pass platform. Basically you have meta objects,
- 21:34which is which, which allows you to to to build custom data in
- 21:38Shopify. The API is great.
- 21:41It's very much open. You can you can do a lot through
- 21:44through the APIs and control, control a big surface of of of
- 21:49your Shopify configuration. You have Shopify functions, you
- 21:53have validations, check out extension, etcetera.
- 21:57There's a lot of pieces that allow you to build your custom
- 22:01logic around Shopify. And for me B2B is, is basically
- 22:05custom logic. So of course there are pieces
- 22:08that that have to be there and lots of of B2B will follow that.
- 22:15But apart from that, it's, it's mostly custom and Shopify allows
- 22:20you to build a lot of custom solutions around, around, around
- 22:25it's platform. So given also the times we live
- 22:30in and the fact that, you know, development is commoditizing a
- 22:33lot, which is, which is part that's actually an advantage of
- 22:40Shopify. I would say I would like from a
- 22:43technical point of view, as as a CTRI would, I would, I always
- 22:48favours more open platforms that allows you to build something,
- 22:52you know, like the, the, the ceiling is higher for them of
- 22:55things that you you can achieve. And it's just make me feel
- 23:00safer. That's when some requirement
- 23:02came to us. We can actually find the way
- 23:04around it. So yeah, I'd love to drill into
- 23:07that because I think I think flow is a is a phenomenal tool.
- 23:11And I even me as a non CEO, non tech, a person has been able to
- 23:16create some really cool flows that avoid using third party
- 23:19apps, say like automatic generation of ticketing in in
- 23:23like gorgeous, for example, for customer services based on
- 23:25specific criteria. It's great.
- 23:27The one area where I'm really nervous about it is when it it
- 23:30at scale, when there are thousands of operations running
- 23:33through a single flow, because I have seen challenges there where
- 23:37it had some breakdown. So what I'd love to hear is how
- 23:40reliable do you think it is at scale?
- 23:42And can you talk us through a couple of examples of how you're
- 23:45using flow as the backbone for B to B?
- 23:48Yeah. So at scale you, you start to
- 23:51see some, some cracks, some some queries are failing the, the
- 23:57queuing system is not not perfect error handling or
- 24:02retrying of the errors is, is not not there.
- 24:05So if we're talking at scale and if we're talking like about
- 24:09multiple orders per minute, for example, or a second that that
- 24:13is, that is somewhere that you you can actually start seeing
- 24:18some some issues. You can optimize around those to
- 24:22some extent, but that would be A1 harp limitation for me in, in
- 24:27flow nowadays when it comes to, you know, triggers.
- 24:33So what triggers the, the, the Shopify flow, you can basically
- 24:38do do everything you want and then you can transform the data
- 24:42any way you want and you can actually invoke some actions.
- 24:46So in a way it's a, it's a full blown hyperstatform.
- 24:52The scatter is, is, is the limitation there.
- 24:56But at the same time, if we're talking about automating
- 24:59operations, this case is not always the issues.
- 25:03So, so basically like for example in Lupine, we use
- 25:10Shopify flow heavily to to power up the onboarding process.
- 25:15So every BB2B customer have to be unboarded in some way.
- 25:20So, you know, sending up some documents, going through through
- 25:26the verification process and then actually being invited to
- 25:30the platform. And for those kind of flow
- 25:34flows, flow is, is, is basically perfect.
- 25:37And at this point in Lupai it it powers all the the the support
- 25:42team with, you know, automated automating operation.
- 25:47On top of that, when the client is on boarded, after some time,
- 25:52there is this kind of a verification process that OK,
- 25:55after a year somebody had to renew, renew or or show another
- 26:01documents to to actually maintain its status.
- 26:04That is always also something that that flow is very good at.
- 26:09So yeah, I would be very careful when it comes to to Skype, to
- 26:14processing thousands of queries per or 100 queries per per
- 26:19minute. But when it comes to powering up
- 26:24even complex flows, I guess Shopify flow is is is farther
- 26:29than than a lot of people think. Yeah.
- 26:34I mean, I guess what's interesting is how they've been
- 26:37extending it. And I think this is the the true
- 26:39test of any middleware, whether it's a middleware within a
- 26:42platform or it's a separate middleware that connects to
- 26:44other platforms is, is extensibility and connectability
- 26:48to third parties. And I think that's, that's a bit
- 26:50I'm definitely interested in is how Shopify is able to then
- 26:54connect out to third parties within its ecosystem, not just
- 26:56to run functions within the Shopify environment and admin.
- 27:01So yeah, interesting that you you have used that quite
- 27:05extensively on a BSP. I've not seen it used because I
- 27:08don't do that. I'm done B to B on shop find on
- 27:10other platforms. I have interests and decision
- 27:14making. I guess, you know, there was
- 27:18like this point in time that Shopify flow started to be the
- 27:22series still when it's it starts to be able to connect with
- 27:26external endpoints, because that basically means you can do
- 27:30anything and you can connect to, to to to anything.
- 27:34And you can spin up the hydrogen API endpoints and you can do ton
- 27:39of ton of stuff there. Like I mentioned, the error
- 27:43handling the trying process is, is a bit of a challenge.
- 27:46But otherwise, I would say I see bigger limitation in, in third
- 27:52parties vendor AP is or lack of them than in Shopify.
- 27:56Because yeah, I, I, I would always say that that Shopify API
- 28:00is a is an excellent one. I'm intrigued.
- 28:05So for agencies listening on this who are evaluating, maybe
- 28:10they're, they're used to like the B to C Shopify's generating
- 28:14more interest from people who have got hybrid models as well
- 28:16about the the ability to consolidate on a single tech
- 28:20just as Centre has done in the fashion space with its wholesale
- 28:23and its B to C offering. And that's really popular with
- 28:25its client base. So what I'd love to hear about
- 28:28this is that so agencies evaluating whether how to do B
- 28:32to B and looking at flow versus custom app and Woodwell or even
- 28:36a specialist like Spark Glare has got a really strong
- 28:38reputation in the Shopify world as being a, a kind of a more
- 28:43robust B to B like what what's the reason to not look for an
- 28:47external one where he might get additional functionality?
- 28:50How do you see this progressing over time?
- 28:51Like from what you're seeing and hearing in Tenley?
- 28:54Are you, is this an area where you actually think Shopify is
- 28:57really focused on building out a mature B to B product over time
- 29:01like it has with B to C? Yes, yes, definitely.
- 29:06I, I Shopify is is very focused on that.
- 29:09We can see this in in amount of updates to to to things like
- 29:13though to to things like meta place API functions and and so
- 29:18and the B2B itself, it progresses so, so quickly over
- 29:23the the the last three years basically.
- 29:25So yes, that that's definitely there.
- 29:31I guess if, if you're, if you're running, you know, like tons of
- 29:38like you, you, you thinking about Shopify as a proper CPQ
- 29:42system with thousands of rules and so on that, that that's not
- 29:47yet there. But otherwise I would, I would
- 29:50always consider it. And also because there's this
- 29:55opening in in in the API basically.
- 29:59And coming on to like the last question of B2B before we go
- 30:04into some of the storefront stuff, it's a bound
- 30:08underestimated complexities in AB2B and B2C unified set up
- 30:11because I think sometimes it's a simple thing.
- 30:13All right, well, it's a, it's just different, different
- 30:16storefront or market and it's a different pricing catalog.
- 30:19But actually B2B can be unique price catalogues per customer,
- 30:24or it can be customer groups with specific pricing within the
- 30:27case. You can have different
- 30:28customers. Then you've got account
- 30:31structures. It's not just a single customer
- 30:33with a customer account. It can be a business that can
- 30:36have subdivisions. It can even be a three level
- 30:39hierarchy of a parent, a child and and like grandchild set up
- 30:43and they can have different invoicing structures and
- 30:46different commercial terms. You you're suddenly depending on
- 30:48this, on the complexity of the the accounts.
- 30:51You can have a lot of challenges are texting it.
- 30:55What from what you've seen, what was the most?
- 30:57What's the most underestimated complexity and a combined B to
- 31:00BB to C set up and and what do you need to think about in order
- 31:04to get the right approach? Yeah, I guess if we're talking
- 31:09about most underestimated convexity, because yeah, that's
- 31:14a, that's a interesting perspective on that because I
- 31:18guess everyone knows that B to B is complex or everyone expect
- 31:22that B to B is complex and for for right reasons basically.
- 31:26So I guess the most underestimated thing is, is, is
- 31:34on the UIUX side of things on the start front, like how, how
- 31:38actually you present the product to very, very different types of
- 31:44users. So on one hand, the DTC user, I
- 31:49would say it would be this kind of a low intent user.
- 31:51So this is our want to be LED basically and and exploring the
- 31:58sign and want to know more about the product, product history,
- 32:00what it does and may not may be completely new to to the to the
- 32:05to the entire field. On the other hand, I B to B user
- 32:11is like this high intent user that knows exactly what, what
- 32:17she wants or if she wants and basically want to buy it as
- 32:21quickly as possible, as efficiently as possible and
- 32:24know, know more about maybe details and how to, how to push
- 32:29it further. So, and then the Starfront had
- 32:33to accommodate both of those of those groups.
- 32:36So if we talking about this, you know, highly polished, polished
- 32:41D2C experience, it's, it's getting even harder because now
- 32:46you have to, to, to put the P2B experience, which is completely
- 32:50different, like the widgets for, for the, even the discovery of
- 32:55the products or widgets for, for buying the products should be
- 32:58completely different. And you have to actually squeeze
- 33:01that in into the D2CD2C UIUX, which is, which can be an
- 33:08advantage because the B2B experience is, is suddenly is
- 33:12not much worse than the DTC one. But you have to think about this
- 33:17as a 2 completely different paths to, to, to, to check out,
- 33:22to buying a product. And you have to accommodate for
- 33:25that right from the beginning in order to actually design and
- 33:29then build something, something beautiful and working at the
- 33:33centre. Yeah, yeah, that makes a lot of
- 33:38sense. Now let's let's talk to some of
- 33:41the, I guess the more theme based solutions that you built
- 33:45to support the, the product data model needs of the the pine.
- 33:51Now you built from what I must say, you built a product
- 33:53configuration. You've you've talked about that
- 33:54you post about this on LinkedIn research.
- 33:57It's a really interesting article.
- 33:59You built a product Configurator entirely in Shopify using like
- 34:01the metro objects metadata model rather than going down the route
- 34:04of a third party or some custom tech to do that.
- 34:09I'd love to can you talk people through listening like what,
- 34:12what the solution is and and why the meta object meta field route
- 34:17is was was the right one? Because from my point of view,
- 34:20when I look at it as the more that you can use native and the
- 34:24more you're on the existing infrastructure, the better.
- 34:27You've got one less point of failure, one less ask to
- 34:29maintain and manage, one less app that could suddenly
- 34:32decrement functionality or decide that they'll no longer
- 34:35support their one less app fee to pay.
- 34:39And I'm seeing more and more brands actually buying into
- 34:42this, that when they move into an ecosystem like Shopify,
- 34:46become a centre that actually building on that platform using
- 34:49the extensibility is good. So yeah, can you talk us through
- 34:52that? And yeah, what was it?
- 34:54What, what made this the right option?
- 34:56Yeah. So let me maybe start with with
- 35:01a bit of a story. So before, like this was a major
- 35:05operational Harlow cause basically banking had to
- 35:10duplicate all of the products whenever they wanted to have a
- 35:14different price of it on it. So basically one product could
- 35:19be actually 10 products because it was sold in 10 different
- 35:22contexts or even more. And you can imagine actually how
- 35:27it, how it may, how complex it may be it, it was to, to
- 35:34actually manage this product, this enormous product, suddenly
- 35:37you have 10 times more products that you actually need and there
- 35:41are no visible connections between them.
- 35:43So on one hand, and the fine products are, I would say,
- 35:50inherently modular. So the lights are combined with
- 35:54different batteries, traps or different technologies.
- 35:57So we, we, you, you can see right from the beginning that
- 36:01this, those parts are actually separate products.
- 36:05And if you combine, if you architect them like that, you,
- 36:08you, you don't have to actually build a ton of products for
- 36:13every permutation possible. On top of that, we have B2P on a
- 36:20Shopify file, which allows us to have different catalysts for
- 36:23different products. So that's solved the pricing,
- 36:27pricing complexity and yeah, parts are designing the the
- 36:34product around parts and not the the outcome product itself.
- 36:38So another one. But if you design it that way,
- 36:41So suddenly you have to think about, OK, how do I connect
- 36:45them? How I make this meaningful
- 36:47connection for one, for the users and for for the editors
- 36:53also. And meta meta objects are, are
- 36:55great for that because you can actually build this custom
- 36:58editor experience around it and build those custom connections
- 37:01between, between the products and they get very, very complex
- 37:06because OK, one product, one configurable product can consist
- 37:13from, you know, 10 to different 4:50 to 10 different parts.
- 37:18And then there's an option to, to actually buy a preset, which
- 37:24is a ready made configuration prepared by the pine team.
- 37:28And then there are options that allow you to personalise the
- 37:32products, like maybe add some engraving, for example, and it
- 37:38changes dynamically. And that leads us to the to the
- 37:42to the first issue with third party apps, like third apps,
- 37:46party apps can be very powerful, but your business model will
- 37:51change and it will change magnetically.
- 37:53And something that is right now can be not right in, in, in in a
- 38:00year or so. Having this kind of custom
- 38:03structure, the, the meta objects shock finality, having like
- 38:06playing around those primitives allow you to, to actually
- 38:12configure it in the way that you you need and change the
- 38:15configuration you are not dependent on on somebody else's
- 38:18road map. So that's the first thing.
- 38:22Another dimension I would say is that is very important.
- 38:26Like we live in this AI or era and once again, Shopify has a
- 38:34very, very great API and that means that LMS can actually
- 38:40interact with it. Third party apps for a lot of
- 38:44time doesn't have great APIs and they're more close because they
- 38:49that's basically their business model to to actually provide you
- 38:53this box functionality that is unique to them.
- 38:57So yeah, you, you you actually benefit from from the fact that
- 39:05if you structure this around the meta objects, you can easily
- 39:09surface that structure, that connection to the labs.
- 39:14So that's another thing. Yeah.
- 39:17First thing is basically the performance and the UYUX of the
- 39:21whole solution like third party solutions have to be generalized
- 39:27like they they always have to serve bigger group of people and
- 39:34by that they they bring a lot of blood to the to the goat and
- 39:37they will always like the you kind of mainly done look and
- 39:42feel very seamless with the rest of the layout.
- 39:45With the custom solution, you can actually do that pretty
- 39:48pretty easily. The same goes for performance.
- 39:51You can actually optimize it pretty heavily because you
- 39:55because basically you own the the the front end experience
- 39:58also. Yeah.
- 40:00Well, having worked with a lot of apps in different
- 40:03environments, one of I think one of the right, it's the they're
- 40:06generalist and you always find a a functional limitation.
- 40:11I've seen this in my discount apps where a specific type of
- 40:13discount or exclusion can't be done and therefore they have to
- 40:18do a bit of custom development, which is a charge anyway in
- 40:22order to get it. So you you do end up you reach
- 40:24the point where as a bit you're as a business need evolve you,
- 40:28you then either have to pivot to a different app provider, which
- 40:32then means reset up and then you potentially come to that limit
- 40:34again or you're paying custom development anyway, but you
- 40:37don't have the control over how it's working.
- 40:40So you're interested to hear that thought process.
- 40:43I would say it's like I, I guess there is a place for those third
- 40:48party configurators. If, if it's not your main or
- 40:52primary product line and you have maybe one product that is
- 40:57configurable and already tried to experiment with, with
- 41:01introducing such products like third parties are great like
- 41:04they, they allow you to, to, to move quickly to to experiment
- 41:07quickly. But if your business is the
- 41:11centre around configurable product, make it make it to
- 41:15yours. Yeah, I think that's a really
- 41:17good delineation actually because often when I'm working
- 41:20with clients and they want to test the Configurator that is
- 41:23the MVP approaches do a basic one.
- 41:27If you don't have a really complex configurable parts and
- 41:31different logic gates based on if you select a then it refines
- 41:35the selection for the the next input point that it's a really
- 41:38good way to test the waters and see whether it has a commercial
- 41:41impact. You're right.
- 41:44Final question I've got actually two final questions is coming
- 41:49back to pricing And one of the one of the big limitations
- 41:53native shop find BC is that it doesn't have price books.
- 41:57You have a single price, you have a compare out price for
- 41:59discounting your B to B. You have price books, you can
- 42:03have multiple price books. So you're in a world now with
- 42:07lupine where you're, you've got AB to C price for product,
- 42:09you've got theatre prices, potential different pricing
- 42:11across the B to B customer groups.
- 42:14How do you handle that architecture and data wise in
- 42:18the commerce engine and and what what issues did you find and how
- 42:23did you get around them? Yeah, that's a part that
- 42:26actually gets a bit of a bit complex.
- 42:30It is possible to, to, to, to run it on a Shopify, but it's a
- 42:33mix of many, many different tools and, and the mix has to be
- 42:39basically strategized around and documented.
- 42:42And, and it, you know, it's a combination of, of.
- 42:46So on one hand you have this Shopify catalogues which allows
- 42:51for each customer group to, to have its own appropriate
- 42:55pricing. Then then it's combined,
- 42:59combined with with basically setting up automatic discounts
- 43:07or individual discounts on on a different level.
- 43:11So for resource and so on. Also those cutouts can within
- 43:18the company itself, those there could be some, some special
- 43:26rules for one individual or one location.
- 43:29So you have to accommodate for that.
- 43:31It's once again, it's another specified Shopify catalog or, or
- 43:37a discount itself or a automatic discount or a manual discount
- 43:41itself. So you have to actually
- 43:43strategize an architect around all of those tools that you have
- 43:47available and build the system around it.
- 43:51And it's not perfect, honestly. So it's, it is possible to to
- 43:57architecture around it, but it's not, it's not visible straight
- 44:03straight away. So, so you have to build our
- 44:05dependation around it. It's a bit of a, you know, this
- 44:08kind of magical knowledge that that you and, and hopefully your
- 44:12client have and you you do, you've done the proper hand off
- 44:16for the client how to to actually establish this.
- 44:19So it's not definitely not straight straightforward and.
- 44:25From having gone through this process and haven't got into
- 44:27this detail about the architecturing hybrid model, I
- 44:31guess what what are the key learnings that you've taken away
- 44:34from the project where if you're in another project that's got
- 44:37the similar challenges will help you to like make smarter
- 44:40decisions or quicker decisions? The tech is one thing when it
- 44:46comes like especially for this complex project there it, it
- 44:50does plays a major role and you have to carefully plan and round
- 44:54it and, and and prepare your test tack, test tack to to be
- 44:59ready for of this complexity. But I guess what the part that
- 45:04is always underestimated is the change management on the client
- 45:07side. So with this whole migration
- 45:11with the PTP, you, you're not changing just the test stack,
- 45:15you're not changing the vendors list.
- 45:17You're actually changing how the how the client team is
- 45:22operating. And they have to get accustomed
- 45:25to, to all of the new flows of the new ways of doing doing
- 45:31things. And they will be doing that
- 45:35during the project, during the project development, during the
- 45:40project life cycle. And with that, with gathering
- 45:46this new knowledge of getting accustomed to the new project,
- 45:49their expectation will also change at some point because
- 45:52maybe they didn't thought that something was possible or should
- 45:56be done in a way. So you have to be prepared for a
- 46:00bit of an yeah, you have to be prepared for a bit of a bit of a
- 46:09surprise there. And actually managing early does
- 46:13does this change management preparing the client for that
- 46:16how how the new system will operate, how your flows will
- 46:19change and map those flows very early on the project is is a
- 46:23good thing to to to prepare? Yeah, agreed.
- 46:26I think all projects the you come to the point where it's
- 46:29actually some of the assumptions you have at the start have to be
- 46:32changed during a project and therefore it has an impact on
- 46:35process flows. And I'm just going throughout a
- 46:37client at the moment around customer service and having a
- 46:39customer service training guide for their team so they know what
- 46:42they're doing and how. And yeah, it's really, really
- 46:44important to bring people on the journey.
- 46:45So but Michael always enjoyed Torchy.
- 46:47Always enjoy reading your updates on LinkedIn about the
- 46:51projects you deliver. Anyone else wants to follow
- 46:54Michael? I'd I recommend it on LinkedIn,
- 46:56always post really interesting insights into like new, new
- 46:59projects, technology solutions and decision making behind it.
- 47:03His contact details on the landing page.
- 47:05If you've got a particular challenge or this is resonating,
- 47:08you want to discuss any particular like projects within,
- 47:12then please do reach out. But Michael, thanks very much
- 47:15for joining us. Thanks, Dennis.
- 47:17Pleasure to be here. Take care.
- 47:20And thanks, as always to everyone for listening.
- 47:21Keep your ears peeled for the next episode.
- 47:24Take care everyone. You're listening to the
- 47:28Insidecommerce podcast, hosted by experienced consultants James
- 47:31Gert and Paul Rogers. Insidecommerce is your fast
- 47:34track to digital knowledge. Featuring interviews with
- 47:36leading E. Commerce, Retailers, Industry.
- 47:38Thought leads and the C-Suite key tech companies.
- 47:40To explore the latest digital. Strategy, customer experience,
- 47:43and tech. Discover what the latest trends
- 47:45really mean and get practical advice based on the experience
- 47:48to help fine tune your E Comm. Strategy and text.
- 47:51Follow us on LinkedIn and reach out to James and Paul.
- 47:54If you'd like to discuss an e-commerce project.
- 47:56We hope you enjoy the. Latest episode.