0:00:10 Hello, everyone. Uh, welcome to today's webinar. This is a brand new system I'm trying out at the moment, so please do bear with me.
0:00:18 Um, but at the moment, uh, so the, the usual check I do of can you hear me, can you see my screen, uh, can you see me, applies more than ever.
0:00:29 So there should be a chat window somewhere on the screen you've got there would somebody be able to put a message in there for me.
0:00:38 Excellent. Thank you. Cool, cool, cool. Okay, I'll just get started straight away then. So the webinar we're going to be doing today is about, well it's a lot of tools or some tools aiming to help you build your storefronts faster.
0:00:59 Primarily aimed at people who might need to set up quite a few storefronts. I want to get them rolled out as quickly as possible, which of course if you're making a lot of storefronts is exactly what you want to do.
0:01:10 When I was advertising this webinar, it was initially built as focused on just this smaller area of inheritance, which I'm still going to talk about in some detail, but I realized as I was researching this, there's a much more expansive topic, so I expanded that a little bit just to focus on how information
0:01:28 can be shared between different storefronts and the platform and the storefronts and that kind of thing. So you should get some very useful information from this.
0:01:37 So the webinar is about one hour in duration. Those that come to these quite a bit know that are sometimes run over but hopefully this one will be a little bit shorter as I've tried to constrain the scope a little bit.
0:01:50 And as always we have a member of the infigo team looking after the chat as well if you've got any questions.
0:01:56 So this time we've got Harper and pleased to say that Harper as who was in the QA side of in Figo.
0:02:04 So a bit of an area which you might not be too familiar with in terms of the people that work from Figo.
0:02:09 Harper's Moot from QA over to the Academy. So you will all be seeing and hear and go out more of Harper as she starts getting stuck into creating tutorials and that kind of thing and she'll be assisting me with these webinars.
0:02:25 And that's just the same people are waiting for me. Okay, so let's get started. So this webinar is going to be a little bit more presentation and PowerPoint based than most, but I will still be going into infigo for various demonstration purposes.
0:02:48 So an agenda of what we're going to cover today. So first off, I want to make sure that everybody understands the differentiation between platforms and storefronts.
0:03:00 Very, very brief, I'm sure most of you here will know unless you're very, very new. I then want to talk about the different forms of what I'm calling inheritance, which are available.
0:03:11 So this is how we share things between the platform and the storefront level. Then I want to talk about various advanced options that we have available, just extra things that we've recently we introduced to our idea to control which data is brought from the platform and which might be locally sourced
0:03:29 on the storefront. I want to give you some guidance on how you might apply these to both new storefronts that you create and existing storefronts that you've already got.
0:03:39 That will cover the vast majority, this whole inheritance bubble. But then I also want to talk a little bit about copying products as well.
0:03:47 So we've recently introduced a feature which allows you to copy products between storefronts rather than just copy them onto the same storefront.
0:03:55 It's very easy to do. Demonstrating it will take about 30 seconds. I just want to talk about sort of what resources are included in that copy and how you might be able to utilize it.
0:04:07 And then I want to round off with some additional bulk tools that we have available. So I think other things we've got just to speed up your storefront build process.
0:04:16 I'm not going to go into those in too much detail as I have covered them in previous webinars, but when we get there, if in my 32nd explanation of each of those is something new to you and you want to hear more, please just fire something into the chat and I can spend a bit more time talking about it
0:04:33 . That being said as well, Harper is here to answer your questions as I mentioned, so anything that comes up as we go along, please do put the questions in.
0:04:41 We'll try to answer as we go otherwise we'll get back to you after the webinar with the answers to your questions.
0:04:50 Okay so the main focus as I talked about is streamlining your software and setup in something which I've dubbed for this webinar as a global config hub just because I needed the snappy title and I couldn't think of anything else.
0:05:05 So before we go into all this as I say we just want a very, very brief understanding of what the differentiation is between platform and storefront as these are the two concepts I'm going to be talking about a lot.
0:05:21 And I say most of you will know this. However, your platform, your infigo platform is kind of your parent level.
0:05:26 You will only have one platform available to you for the vast majority of customers. And then on that platform, you can have multiple different storefronts available.
0:05:35 And each of these storefronts are going to be different websites differently commerce environment essentially for your different clients most in most cases.
0:05:46 So, why would you actually configure this global config hub that I'm talking about and first of all, what is it?
0:05:54 So, what is often considered or what is often thought about within figure is that all your storefronts kind of sit in isolation.
0:06:02 So, you set up a storefront, you're putting all that work with all your products and all your configuration, fantastic, brilliant job.
0:06:10 But then in most cases, you might say, okay, well, I need a new storefront and I need to do that whole setup again.
0:06:15 I need to go over and redo that whole setup. There are many instances where configuration options that we have inside infigo don't have to be compartmentalized onto those storefronts.
0:06:30 There are many where that the settings can be inherited on storefront level from that parent platform So this does give that potential if you start thinking about it for this global configuration hub So the potential to actually start setting things up on your platform level and have that filtering down
0:06:50 to all of your relevant Storefronts now, of course, they're a caveat to this that I'll cover during the course of the webinar so So why is this kind of thing important?
0:07:01 Why would you utilize it? So anyone who's started creating a lot of different storefronts and hasn't been utilizing this global configuration setup, let's say, might realize how taxing it can be.
0:07:17 Because there is, although we can do so much different stuff in Infigo, the time it takes to actually configure all these things and set these things up can be a significant time commitment in order to get a great storefront house at the end of it.
0:07:33 However, what you might find when you're setting these up, if you're setting a lot of storefronts up, is that a lot of these storefront setups and configurations might have a lot of common elements associated with them.
0:07:45 So, for example, you might use the same disclaimers. You might use pretty much identical email templates. You might use the same header layout or something like that.
0:07:57 So the question then comes in, why, if you've got those shared elements, would you create them more independently when you could create them on a shared resource and just have them filter down to these storefronts and only override them where you have to override them?
0:08:12 And that's what we'll discuss today. So a few of the benefits or potential benefits of this global configuration hub I'm hating that term more and more every time I say it.
0:08:28 So we're going to start off with the big one. If you are launching new storefronts, it will allow you to do it much, much faster.
0:08:36 So by setting up loads of things on your platform level, whenever you create a new storefront, you'd be able to see to that storefront with loads of pre-configured data, which could save you loads of time.
0:08:49 The next thing is content updates. So what I want to make clear here and I will do a couple of times during the webinar is when you create this new storefront, it's not just sort of a one time copy.
0:09:01 And then it's severed. It is for lack of a better term a live link between the platform and the storefront.
0:09:09 So what this means is that when you actually go ahead and change something in your platform level that the storefront is already inheriting, that will then filter down to the storefront.
0:09:20 So, it is a live link, you can change platform settings and it will filter down to all the relevant storefronts that are inheriting that particular value.
0:09:30 Another potential thing you could do with this is fast-to-policy roll-outs. So let's say, for example, you've got legal things you need to get involved, cookie banners, password rules you need to implement platform-wide and that kind of thing, rather than having to rapidly implement these legal changes
0:09:48 or something, or any related topic on every single storefront, especially if you have a lot of them, you could do it on one level on your platform and get it inherited everywhere it's being utilized.
0:10:02 The next one I've got is multi brand networks. So what I mean by this is there might be certain scenarios where storefronts, they love touch on this before.
0:10:16 Storefronts are basically identical, but you might need you different branding. You might obviously need your own isolated products and that kind of thing.
0:10:26 So you could inherit loads of different stuff. The user experience, the structure of some elements of your content, transactional copy and certain places, all of this can be inherited.
0:10:37 And I'll be showing you lists later on of some examples of the things which can be included in this inheritance.
0:10:47 And then the last thing I've got in here is language as well. So one of the things that included in this inheritance is all of the language strings which I'm sure a lot of you are familiar with.
0:10:57 So this allows you to sort of customize the text on pretty much every area of your infigo site. And again, it works in the same principle.
0:11:09 so if you've got the same sort of terminology that you would use throughout your entire platform, you could put it on the one platform level and have it filtering down.
0:11:27 Okay. I've seen that. I will come up to that in a little while, and unfortunately, I don't think you're going to like the answer just to give you a heads up.
0:11:37 So, before we progress on with this, I do want to talk about the default behavior. So making it very clear here that this webinar is not prompted by this inheritance behavior being brand new.
0:11:54 It isn't. This is something which has been a concept and utilising in Figo for a long time in various degrees.
0:12:01 We have recently added a few little features which do assist in this. I'll talk about them later, but they allow you to choose certain areas where you can have things that are inherited or local.
0:12:15 But ultimately, in terms of the whole concept we're talking about here, this is a fairly minor upgrade to a fairly big area.
0:12:23 So yeah, it is a existing concept that we've had for a long time. So the default behavior is of this inheritance structure.
0:12:34 So by default, storefronts that you make and storefronts that you have made will utilize values that are taken from the storefront where they can.
0:12:43 If at the moment when you're creating a new storefront, you just see that most of those values are empty. It's just because you've not specified them on the platform.
0:12:51 It's not that it's sort of a blank default. It's just taking from that platform level. So yeah, final point there.
0:12:59 Much of what I will discuss today is already used on your platform, but I think many people don't realize what the hit inheritance can do, so it is underutilized.
0:13:12 Okay, this is just saying that there was a little preset up before the webinar, so I will be utilizing a kind of split screen approach, which I hope is visible enough on my screen.
0:13:24 I can zoom in on whatever later on, but just so you're aware that on the left hand side, we have the platform.
0:13:33 So anything I show you there will be coming from the platform. And then over on the right, we have a storefront which is on that platform.
0:13:39 So I'll just be comparing what the different settings look like sometimes just to clarify. And all I've done in terms of setting up for this is I've configured a few things on the actual platform itself.
0:13:52 And then I've created a brand new storefront, which is indicating those values, just so you can see how the distribution occurs.
0:14:06 Okay, so what I want to talk about now, it's another term which I've just made up for lack of a better option is configuration buckets.
0:14:16 So the reason I've said this is that when you're talking about all these different configuration elements inside your platform, and I'm using that term very loosely because it could be content templates, it could be your header content, it could be language strings, it could be settings, and that kind
0:14:36 of thing. They might all have different names, you might call them different things, so I'm kind of referring them to a global configuration set of options.
0:14:46 However, they tend to fall into three different categories and they'll all behave in slightly different ways. And what you'll find is that even though we have these general categories that I've tried to put them in for you, there is no steadfast rule into which one or four and to which if something will
0:15:02 be inherited, if something won't, often this kind of functionality has been driven by development over many years, sometimes for specific customers and that kind of thing.
0:15:13 So although most of it is predictable behavior, you might find a few outliers. I'm just warning you there that it means you might need to do a little bit of careful attention if you do implement this just to make sure everything's copied over and inherited as you expect.
0:15:30 But I will show you examples of these three elements and weirdly I'm going to start off at the bottom of my list at what I'm calling platform controlled.
0:15:40 So these are elements which some of you will probably have come across before, which if they've been created on the platform, then they will only ever be available to be modified on the platform.
0:15:54 And I'll show you some examples in a moment. There is often a case as well where you can create these elements on the storefront level itself.
0:16:02 So one good example is email accounts, let's say. So you can set up email accounts on your platform level, which all the storefronts can use, and then you can, if you want to, add a new email account on your platform level, but you can't take the platform level email account and modify it to make it 
0:16:25 local. They are different entities, and that's kind of what I mean by platform controlled in this respect. If you want to modify something that is platform controlled, when was created on the platform, then you would have to return to the platform level to make those adjustments.
0:16:42 Some examples of this. So we've got things like customer roles, email accounts, custom content templates, template sets, hot folders, tax categories, and that is just an example.
0:16:55 It's not a complete and exhausted list. So how you might have actually seen this previously in how these might manifest themselves, so I think a good one for this one is email accounts, just to show you.
0:17:17 So I've got email accounts here. They are both appearing on, well, the email accounts is appearing on both the platform and the storefront levels.
0:17:27 However, I can only modify this email account on the platform level because that's where it was created. I can see the details and potentially try and modify the details on the storefront as well which I can see over on the right hand side but if I try and save it is telling me that it doesn't exist 
0:17:44 there it exists on a different level so we need to go and modify it in that particular location and you'll see similar things for a lot of these platform controlled elements let's say.
0:17:58 So for example if I go to hot folders. Again, many of you will be familiar with this. You can see that it's saying that that particular hot folder that I'm working out here was created on the platform level.
0:18:09 So I will have very limited adjustment opportunities on the storefront. Okay, the next option is what I've called a local only.
0:18:25 So these are areas of Enfigo which don't normally have association with the platform level. So these constitutes what you won't consider the more unique areas of each storefront and things which you would generally have multiple of each element.
0:18:41 So think of things like customers and products and product attributes and all this kind of thing. Things which might not lend themselves too much in most cases to having across multiple storefronts and inheriting, they will just be local only and what that means is that you would have to create them 
0:19:01 independently on each of those storefronts and they sit in isolation. As we'll see later on, it doesn't mean they are constrained to that storefront, you can still copy them over to various degrees and in various different ways, but you will not get any interaction with the platform in that respect.
0:19:18 One example I'll show you with this just to really drive that home is in many cases is you can create a lot of these elements on the platform level itself.
0:19:27 So for example, I've on my platform level got a simple stock product created and configured. However, when I created the new storefront, that did not come over.
0:19:42 That was not relevant and did not transfer. Okay, and there's some examples of where that would apply. So as I mentioned, products are a lot of things to do with products, so attributes, categories, that kind of thing, customers and a lot of things to do with customers as well.
0:20:06 So address books, departments, customer attributes, all of these things you'll be setting up on a storefront level. There are some outliers on here as well, which I was talking about earlier on.
0:20:20 So one of the exceptions, I'm going to soon talk about inheritance where things are getting brought in from the platform level.
0:20:26 And one of those areas it applies mostly is settings pages. However, one outlier in this is the appearance settings page.
0:20:35 So, I think most of you all have used appearance settings at one time or another. It's where you start putting in your logo and your brand cause and that kind of thing.
0:20:46 But this page in terms of inheriting from the storefront does appear to be in complete isolation. So it does work completely independently.
0:20:55 So if I go to appearance settings on both of these. I wouldn't really count logo and brand colors because they're set up when you create a storefront.
0:21:09 But if we start going to some of the more nuanced settings down the bottom, this one for example. So thumbnail mode, it hasn't copied that over.
0:21:19 So appearance setting is an outlier. OK, and then last but not least, and this will take up the bulk of this is our inheritable configuration.
0:21:34 So what I mean by this is settings which are either inherited or local. Inherited meaning they're being read from the platform level, local meaning they're meaning they're owned by the storefront itself.
0:21:52 Inherited entries, as I mentioned earlier on, will always utilize what the platform is using. So if you change something on the platform level, it will propagate down to all the storefronts that are inheriting it.
0:22:04 Local entries do not update, so you could change the platform, it will not have any impact on those local entries because it is localized to the storefront.
0:22:16 And each of the entries that I'm talking about, each of the configuration options I'm talking about will be one or the other, it will be inherited or local and we've got a couple of different ways we can do it.
0:22:27 So you can modify settings and config and stuff individually, and that particular element will be considered local. So, basically, if it's, if you context, if you're inheriting a setting from the platform level, if you go into your storefront, modify something and save it, that then converts the settings
0:22:49 that you've modified into your local options, your local settings. So that is now independent to the storefront and won't inherit anymore.
0:22:59 So that's how you change it from one to the other. We also have the ability, which we'll show in a moment, to sort of mass apply local or inherited options on new storefronts that you create.
0:23:12 So in scenarios where it's not applicable to inherit everything from the platform and it can cause more problems than it solves, you can just set a pre-configured local set of options, which I'll cover later on.
0:23:29 Great. So here's a few options or examples of things that count as inheritable and I devise this list by testing this the other day so I can say they're all true of the moment.
0:23:41 And what you can see is that this is a lot of areas of infigo. So this is a lot of things that you're able to pre-configure if it suits your particular setup.
0:23:49 So not to go on along everything, but just to mention a few, so first and foremost, is like with the all settings pages.
0:23:58 So what I mean by these, just to make it absolutely clear, if you go to, I can remember where they are, configuration and settings, there's a lot of pages, generally which will have settings written at the end, and they're just general configuration options.
0:24:16 check boxes, drop down lists. You're not, you're heavily customizing any specific thing, any specific element of your storefront, it's sort of configuring general storefront options, which I think makes sense.
0:24:31 But what I basically mean is that you could go into here, and in the vast majority of cases, if you start changing settings and changing text boxes and that kind of thing, they will all be inherited.
0:24:44 And this applies to things like search engine optimization, basket settings, catalog settings, customer settings, all of these will be inherited.
0:24:58 Another one I've mentioned is language strings. So for those that aren't aware, and I think most of you will be, we have the concept of language strings, which will allow you to customize various bits of text on your storefront.
0:25:14 And I'm not talking about the sort of general text content, which appears on your store, which is controlled kind of using editable content blocks, which we'll again, we'll cover later on.
0:25:26 I'm talking about sort of text that's ingrained into your storefront. So for example, if we start going to the header here where we've got my account links, you can see I've got a little bracket there with inherited written on it and that's where I've actually changed one of the language strings which
0:25:45 is associated with this. Or if we start going to the basket we can change those language strings. We've also got the ability to change the language strings on the admin area as well if you want to change that for whatever reason.
0:26:04 Okay, and how those are changed, just in case anybody doesn't know, is within the languages section. So here is where you can apply different languages and apply those to your storefront.
0:26:16 And then within this section here, few string resources, you have the ability to search for and modify any of those embedded language strings which are on your storefront.
0:26:29 And you can change those to whatever you like. And then they will all propagate down to your storefronts if you've chosen to inherit them.
0:26:43 Okay, but it's not just these obscure settings. It also applies to a lot of the content on your storefronts as well.
0:26:49 So content pages, things like the abouters page, the contacters page, terms and conditions, anything which might be quite common on different storefronts.
0:27:01 You can create those on the platform level fully configure those and then just draw them in into your individual storefronts and then they'll apply to all of those.
0:27:09 And of course, if some of them aren't relevant, you can just delete them on the storefront level. It's not a problem.
0:27:15 CSS override, if that applies, you can do that. Content, template blocks, so things like your header, your footer, your banner, and everything in between.
0:27:26 They can all be done with inheritance controls as well. Things like tax providers, delivery or shipping setup, various elements of that can be inherited.
0:27:39 And then what I found as well is that you seem to be able to inherit a lot of the settings for your, um, connect configurations as well.
0:27:49 So for example, if you've got credentials in there for your connect configurations or your shipping providers or your payment operators, you might use the same account for every single storefront.
0:28:01 So you can put it on your platform level and that should propagate down to your storefronts if you want, just saving your time sort of configuring those.
0:28:08 If the setup is applicable for your individual storefronts. So hopefully that gives you a good summary of what's available and it's a lot of things that are in the storefront.
0:28:20 Now a couple of slides I've just put in for clarity sake. Hopefully they're not required by this point but really just to drive the point at home as to how inherent what inheritance is and how it works.
0:28:30 So what I've got here is three columns. I've got the platform level. I've got one storefront which is assuming is inheriting everything on one storefront which is local for everything.
0:28:41 So let's just say we've created a brand new storefront, and we've got a bunch of values which are available within the platform web that we pre-configured.
0:28:51 If our brand new storefront is inheriting all those values, it will read the platform values. If our storefront is using all local values, then it will contain a bunch of local bundle values, which means that it will not inherit anything my platform and it will use a pre-configured version of default
0:29:10 settings. Okay, so then what happens if we update something in the platform on the individual, what happens to the individual storefronts?
0:29:24 So as we mentioned before, change something on the platform that propagates down to all of the storefronts that are inheriting the thing that you changed.
0:29:32 So in our inherited storefront, that will update based on the platform changes. In our local storefront, it will not receive any changes.
0:29:41 So it will stay local. It will not change. And then if you update the storefront, what happens then? So there's no feedback up to the platform.
0:29:49 So if you change anything on the storefront, there's no effect on the platform. If you change something on the storefront for the inherited, what we're the inherited storefront, then that particular thing you've edited will become local, so it will no longer went to the platform.
0:30:06 And if you change something on the local storefront, then it will remain local, so nothing will change. And hopefully that makes sense.
0:30:17 Okay, Yurg, I've just seen your question about how can we pull settings from the platform level to existing storefronts? This kind of falls into the thing I spoke about earlier on, where the default configuration is the inheritance configuration.
0:30:33 No changes are needed for this. So I actually stumbled across this during my own prep for this webinar. I enabled some things on the platform level, just a few random settings that I've never touched before.
0:30:45 And what I found is that those propagated down to all of my existing storefronts, including the academy. And this This comes on to some of the warnings that I'm going to give you later on in guidance in terms of you need to be quite careful if you are going to start playing around with this, that things
0:31:02 do propagate down to your existing storefronts, unless you've made things local on your existing storefronts already. In terms of making things local back to inherited, that's a bit of a harder job, I'll briefly if we cover that later on.
0:31:24 Okay, and then I'll just spend a few seconds on here. So, clarifying inheritance again, this is just specifying that you don't have to have the same configuration on every storefront.
0:31:35 Like, you don't have to have all settings inherited on all storefronts. You don't have to have all language strings inherited on all storefronts.
0:31:43 There can be different configurations for each, so you can completely customize these storefronts. you're not limiting your customization options, you're just pre-configuring some things, basically, and keeping a live update.
0:31:54 I know I'm repeating myself a lot here, but I guess it can be quite a convoluted, confusing topic. So I'm really trying to make it clear and I hope that's working.
0:32:06 Okay, so what I'm gonna show here is some of the changes we did make, which did actually prompt this webinar to begin with before it's exploded into a completely oversized topic.
0:32:21 So these are inheritance options, which were added to the storefront creation window. So what you'll find is that this feature is probably not available to you by default.
0:32:33 It's one of those where if you want access to it, then you'll need to request it via support. But to be honest, it's fairly limited in scope in what it does.
0:32:43 So it will give you a brand new window. Let me just go on here, we demonstrate this one. So we're just looking at PowerPoints all day.
0:32:52 So if I go to my storefront management window, of course, we have to be on the platform level in order to be able to do this because we're creating a new storefront.
0:33:03 I'm going to go to add new storefront. And if you've got this option available, you'll have this second tab up here.
0:33:10 This is our advanced options and what this is basically doing is just categorizing loads of different settings in infigo, loads of different configuration areas into four different sections essentially.
0:33:27 I'll get onto what generally is covered in those in a moment but in terms of the functionality all you've got to do is say whether you want it to be local or you wanted to be inherited by default, whatever is included within that category.
0:33:40 So the way this works, if that toggle is on, the new storefront will have a pre-configure local bundle for those group of configuration options.
0:33:52 So that setting is on. The, for that particular group, there'll be no link to the platform. It'll just be local by default.
0:33:59 If you have that setting off, then that's where we go back to the default behavior, which is the inheritance behavior.
0:34:05 so we pull what's coming in from the platform for that particular group of settings. Okay, so very generally, what is in each of those?
0:34:20 So we're talking about, so we're talking about settings first of all, that's probably one of the easiest. All of those pages that have the word setting in it, That is basically all those settings pages.
0:34:36 So again, there's some exclusions like the appearance settings and probably certain settings within those pages themselves. But generally speaking, any of those settings, catalog settings, basket settings, connect settings, they will all be in that particular category.
0:34:57 Localizations, they were talking more about those language strings I showed earlier on editable content and content pages. Again, hopefully fairly self explanatory.
0:35:07 So content pages, we're talking about the area of the same name, which again is stuff like your terms of conditions, about us, contact us, all those pages.
0:35:21 Editable content, we're talking about all those editable content blocks that many of you will be familiar with, where we're looking at things like your header, footer, banner, check out various elements of your entire site, which are controlled by that edit area.
0:35:38 I'm sure all of you have spent various lengths of time in this particular section and are somewhat familiar with it by this point.
0:35:49 I think email templates are also included in that editable content section as well. So if you do pre-configure email templates, it can bring those through into the storefronts as well, if you've got something very similar on multiple stores.
0:36:03 And then the final option there is default dynamic product config. So that's a very specific one. I think just relates to one particular page.
0:36:14 This is if you've got default settings identified for your mega edit products. So many of you will be familiar with the when you open up the mega edit window and open up the mega edit editor, you've got an option in the little drop down, which is product options.
0:36:28 And that gives you a page of about 3 million settings, which allows you to customize things on that particular mega-edit product.
0:36:36 Well, maybe it's a bit less known, and I suppose also is a way to speed up your store from builds, is that you can define default settings, default values for your mega-edit products, any new ones that you create anyway.
0:36:51 And what this is doing is allowing you to actually create another level of defaults. So you can set it on your platform level and then it comes down to your storefronts.
0:37:02 And this is on mega-edit product settings. And I believe that the primary of that group is this product configuration tab.
0:37:17 And that should pretty much mimic that long list of options that you see in your individual mega-reddit products under product options.
0:37:24 So you can set defaults here and propagate it down to the storefronts. Okay, I've talked about those, what happens if the toggles are on and off.
0:37:39 Right, so a couple of limitations with the inheritance features as it stands at the moment. So these are just things that we've found as we've been going through prepping for this webinar.
0:37:53 So one of them is the knowledge base that stands behind this. There's currently no really comprehensive list to understand which individual entries will and won't be inherited or if they're local only or if they will be one of those which are platform controlled.
0:38:11 there's no definitive list unfortunately as it stands at the moment. Also difficult and not available in the UI is the current state of any settings.
0:38:22 So at the moment as it stands there's no way to tell if a setting or a configuration option is inheriting or if it's a local option.
0:38:32 And also reversions as well as I very briefly mentioned earlier on. So if you have got something which is currently be local on a storefront and you're wanting to get it back to inherited, there is currently no way in the user interface to do that at the moment.
0:38:52 OK, I think there is ways to do it, I believe, but at the moment there's no user interface. So if it's urgent, I has it to say that you could probably contact customer support and they might be able to help you out, but it would be on a case by case basis.
0:39:08 I don't want to throw over to support that having to sort of mass, mass revert things from local to inherited.
0:39:15 But I agree with what both you were saying there. That should be something which we include. Thank you. Okay, so with that in mind and the potential problems that we're discussing here guidance for new and existing storefronts.
0:39:37 So if you're talking about making brand new storefronts with this, so ideally if you're making multiple new storefronts, then you might want to consider what we've been talking about.
0:39:50 So actually creating a partial or a complete template at your platform level, which could then be used to seed any new storefront that you generate.
0:40:02 And that will give you an instant head start in any new storefront that you make. Even if it's just a few settings or a few configuration options or a few credentials or something like that, a big boost and a big head start.
0:40:17 If you're looking to create more unique storefronts, so let's say it's a storefront which is nothing like any of your others, then it's the it's the case where if you inherit things, then it's and you've already configured a lot of things on your platform, it has the potential to cause a lot more problems
0:40:33 than it solves. So in that's the case, then you might want to get this advanced options things activated and just utilize those to create the local copies.
0:40:48 Sorry, it gives me a notification every time someone tries to join. Okay, and then for existing storefronts, this is where it becomes a little bit trickier.
0:41:06 And you should really think hard before you start implementing these options. So remember that inheritance is not new and it is the default even if it's a new term that we're kind of utilizing here.
0:41:19 So long standing just to remind you familiar on is that in Figo will take configuration options from the platform level.
0:41:27 It is just the case that it stands at the moment. Most people don't utilize those options at the platform level.
0:41:32 So when you create a new storefront, most of those options are blank or just in a basic configuration. But it is still inheriting.
0:41:42 So you want to be careful in this case if you do have existing live storefronts, if you are willing to implement this kind of platform level in template.
0:41:54 So you just want to ask questions really and really check your existing storefronts. So have you, If you're implementing anything on as a template on the platform level, is it stuff that you've already addressed on your individual storefronts?
0:42:13 If you're not doing anything new and it's stuff that you already do on your individual storefronts, then everything on your storefronts should be local anyway.
0:42:21 So you shouldn't have a problem, but you should still definitely check carefully if you do. You need to have a think of whether your existing stores will be impacted by any proposed platform changes and you should really ensure possibly, but it might be a big task if possible that if you have got a storefront
0:42:42 that is great and it's up and running that all the settings that you find relevant are localized. But this is just general guidance.
0:42:49 What I really want to say is if you are working to implement this and you already have a lot of storefronts, do think about it carefully.
0:42:55 It might save you a lot of time in the future in terms of spinning up brand new storefronts, but short term thought is required for your existing storefronts.
0:43:10 Right, that took longer than I thought. So let's go for copying products next. Fortunately this won't take too long. So this is something which people have been asking for for a long time.
0:43:21 Hopefully you have seen this in the release note and you all started using it right away. But what we've introduced now is the ability to, in a nutshell, copy products either onto the same platform, or onto completely different storefronts on your platform.
0:43:38 So it doesn't mean that you have to complete setup brand new products, even if they're very simple when you create your new storefronts.
0:43:46 So let's take a little look at these three scenarios. We've got copy to the same storefront, copy a single product to another storefront and copy multiple products to another storefront.
0:44:00 All are very very simple to do and I'll demonstrate rather than showing a PowerPoint. So, let me just navigate to a different storefront for a second.
0:44:31 So, I have a storefront here which I use for keeping a lot of products that I make for various webinars and that kind of things.
0:44:43 So, I think a lot of you will be familiar with these. So, there's a lot of different product types and stuff available.
0:44:50 So let's start off with copying to the same storefront. So I'm just going to choose one of these and all of you will be familiar with this, but just to complete in a sake, if I go to edit on the product, in there I have our copy product option.
0:45:05 And that will create a carbon copy of the product on this same storefront, giving you the ability as well to choose whether you want to include images, whether you want to include extended data like mega-edit options and assets, static PDFs that are attached, and that kind of thing.
0:45:24 Most of you should be aware of that, I'm pretty sure. The new functionality comes with copying between storefronts. So if we go back to our product management page, we have the ability now with this updated interface to select one or multiple poor products that are very interested in.
0:45:42 So if I just go to one of these, find a good one. Let's keep it simple to begin with. So I'll go for this one here.
0:45:55 Select one product just to begin with, go to our actions drop down at the top right of the screen and we have the ability to copy products all found, which is all the products in your database, assuming you have less than 500 because I think 500 is the limit or you can copy the selected products which
0:46:15 is probably more realistic. I'll go for that. We then get the option to copy either specify either a name or a prefix so if you have just one product selected you're entering a new name for that product.
0:46:31 If you've got multiple products selected then you're entering a prefix that will be put on to every single one of those products when it's copied over.
0:46:40 So I'll just call this copied product. I can specify whether or not it's published immediately and whether or not we're using the same images.
0:46:53 I'm then going to select which storefront I want this to be moved over to and then just hit copy. And that is it.
0:47:02 That will do it in the background. And this one should be quite quick as it's fairly simple product. So I'm just going to my product management.
0:47:26 I can see there that I've got a carbon copy of my product. And I'll talk about the elements that we're all over later on.
0:47:33 But a lot of the elements that you add to the product and that are associated with the product will be included in the transfer.
0:47:42 So so I'm going to specific later, but things like attributes, all of your descriptions, a lot of your pricing information.
0:47:49 It's not just your basic product information, it is a lot of associated things as well, which come over with it.
0:47:56 And that extends to more complex products like multi-part products and mega-edit products as well. And to round that off, let's just show copy and go over multiple products.
0:48:07 So this time, we just want to select a couple of things. Let's go for a bit more of a selection, so one multi part and two mega edit.
0:48:25 This time we're just going to add a prefix, I can type and then copy those over. Now as I mentioned there's a lot more, this just take over a lot of assets with the product.
0:48:40 So this will probably take a bit more time to copy as it is having to to move all that over.
0:48:48 But it should still be fairly quick to do and you can still operate whilst it's doing that. It does do it as a background task.
0:48:58 Darrell, so the, I know I've missed a few queries. For us, he harpers on it with a lot of those.
0:49:06 So Darrell, I've just seen yours about copying a multi part. So the what I've actually found is with my testing.
0:49:13 So the pit stop profile will not come over. However, the XML, so if it's a completely customized XML, that will come over and if it includes the references to the pit stop profile, the references will still be in there, but you'd have to upload the pit stop profiles again.
0:49:38 Okay, so those are moved. So now we should have all of those products in there. And in theory, they should all work absolutely fine as a completely usable product.
0:49:55 So, for example, if I go to this mega-edit product from a previous webinar, everything that was specified has been brought over and all of its assets.
0:50:25 So all of the stuff to do with mega-edit, stock, canvases, anything, any invent mex package with all its associated variables and all that kind of stuff has been brought over, all the functionality still works.
0:50:40 If there's attributes on the landing page, they'll be brought over, all of the associated things copied over. And it extends further than this as well.
0:50:48 So it's not just directly product related things. It is also things which can be assigned to the product. And I've just got a little example here of that scenario.
0:51:00 So again, this is just sort of a general guide. There's probably exceptions to each of these, but generally these core categories will get transferred when you copy products from one to the other.
0:51:11 So we're looking at our core product. So things like all your product descriptions, your images if you select them, any display settings that you've specified on the product and that kind of thing.
0:51:23 Those will be copied over. Category structures is an interesting one. So if you copy over a product, the entire category structure will be copied over with it, even if it's in a nested category structure.
0:51:36 So for example, if I go, I've got this one here, which I've just brought over, that's in just what just one level of category, the advanced grouping, but you can see that it's created that category for me.
0:51:53 And I can see there that multiple different categories have been created, including nested categories or child categories, if they are applicable.
0:52:06 And it also includes details for the category as well. So in this one, I've just specified a picture, but it brings that over to pricing and stock.
0:52:17 So things like if you're just using base pricing, if you're using tiered pricing, if you specify stock levels, they will all be brought over.
0:52:28 One of the exceptions, which is in the not so discreet box on the bottom right, is pricing scripts. There's currently a bit of an issue we get in pricing scripts to come over and the global additional data that comes with it.
0:52:41 They're not currently supported, but maybe in the future would just be aware of that one. tax and delivery. So if you've specified kind of associated tax categories and stuff like that or delivery options, they will delivery options associated with the product, they will be brought over discounts.
0:53:00 So again, you can assign discounts to a product. If they are assigned, they will be brought over all of your attributes and attribute combinations, they will all be brought over as well, including the details associated with them.
0:53:16 So hopefully some of these products have got attributes, not very many, not very detailed unfortunately, but all of the details for the attributes will be brought over as well, including if you've got default values and stuff like that.
0:53:33 Things that are associated with your products, as I've mentioned, will be brought over as well. So for static PDFs, that will include the PDFs that are already attached to that particular product if they're still relevant for multi-part products as you as you mentioned Darryl so that will bring over 
0:53:49 the XML if you specified that and the associated configuration options exception being it doesn't at the moment seem to bring over the pitstop profile as that's specified those are actually put in in a different area but may do in the future but at the moment you would have to re-specify or re-upload
0:54:06 those pitstop profiles and then all of your mega-edit resources we brought over as well. So cliparts that are associated with your product fonts, canvases, all that good stuff so that you can get a fully operational mega-edit product as soon as you copy it over.
0:54:26 As I mentioned, there is a few exemptions, few things that don't. Again, it's not a complete list. It's just a few examples.
0:54:34 So pitstop profiles, downloadable product files related to products, certain elements of 3D products you might struggle with as well. So I have a look at those quite carefully if you're looking to copy a 3D product over.
0:54:47 Although I did try one in advance of this and it seemed to operate, it seemed to work fine. But I've been warned that there are some nuances with 3D products.
0:54:57 But in the most case, it will copy everything to do with your products. Okay, and then the last section here is very rapid fire.
0:55:07 So it should fit within our timeframe. It's just other bulk tools. And I think most of you are familiar with these because I've covered them into the webinars.
0:55:15 and I've got a lot of regulars at this point. So, just five things, four or five things I want to draw attention to.
0:55:25 So, first one is the ability to bulk import and modify products. You might consider this to be surplus to requirements now because we've got copy products between storefronts.
0:55:37 But let's say you want to bulk update a set of products. you could do it by downloading the entire product database as a CSV, making your changes, and then re-uploading it to your storefront again.
0:55:50 And that will bulk update. Alternatively, you could update and import it into a different storefront to create your products there.
0:55:57 There's content on the academy for all of these ones, for example, because I'm just going through them very quickly. We have the ability to do the same kind of functionality with customer information.
0:56:10 So in the software, you have the ability to download a template of what customer information we can accept. You can fill in loads of different rows of information, upload that back in and it will create all of those customers for you.
0:56:25 Again, just a big time save of for you for setting up your storefronts. In that same vein, we have the ability to create address books, which I'm sure a lot of you have at least heard of.
0:56:38 Again, these have import capabilities, and address books give you the ability to create different books with thousands of potential addresses in each one.
0:56:47 So doing that manually, or by a sort of process, would be hell on earth, basically. So we've got the ability to import those address books from CSVs or Excels, CSVs I would have thought just to create those quickly, and again, you can use those on multiple for storefronts if required, although seen as
0:57:08 they're address customer-based, it's probably not as applicable, it would just be on one storefront. And then we've got various other import areas scattered throughout the platform.
0:57:20 One of the key areas might be scopes, targets and rules in access permissions. So if you've got quite complex setups, creating all of these different scopes and targets manually could probably be a bit of a chore.
0:57:34 So if you've got the capability to sort of create that in a spreadsheet format, you could just re-import those and it'll create them all in one go for you.
0:57:46 And then finally is content templates. So I mentioned that these can be actually utilized with the inheritance behavior, but we have the ability to create both standard content templates, which you can save and then reuse over and over again, but we also also have the concept of these custom content 
0:58:07 templates, where you can create a completely customized format, which you can reuse over and over again. Based on the time we've got left now, we'll take a bit too long to explain that in more detail, but if that has peaked your interest, then you can walk aboard with that stuff on the academy.
0:58:24 There's content for every single one of those. If you are interested in those, just let me know in the chat and I'm happy we send you the resources for those.
0:58:34 Okay, right. That is about it for the webinar. A lot of repetition as I know, but hopefully I've really nailed down what that inheritance thing can do.
0:58:47 And hopefully I've warned you of its potential risks of its potential rewards that you might get from it. And I hope it's been a useful webinar for you all.
0:58:58 If you do have any questions, we'll keep the chat open for a little bit longer so you can ask those and we'll reply in the chat.
0:59:05 Otherwise, the recording will be available after the webinar and I'll speak to you all next time. Thank you very much.