0:00 In this quick tutorial, I'm going to show you how to use our Usage Rules feature for checkout attributes. Now, for many of you, Usage Rules might not be a brand new feature, and it definitely isn't.
0:12 There are other areas of Infigo where this functionality is already in use, but we've now extended that scope so it can be used with checkout attributes as well.
0:22 So it's exactly the same engine you already know from payment and shipping. to control which extra fields appear on your basket page based on customer department or whatever other metric you want to gauge it by.
0:37 So first let's talk a little bit about what this does. So checkout attributes are the custom inputs that you can collect on the cart screen.
0:46 So for example, it might be an extra file upload, special delivery instructions, or any other piece of information you need before the order is confirmed.
0:56 With Usage Rules now available on the checkout attributes, you can choose which, under which conditions those checkout attributes are going to be seen.
1:05 A prime example of this is allowing visibility of certain checkout attributes fired. a department. So users in one department would see certain attributes while another would not.
1:17 It's the identical interface and workflow you already use. Use for payment method and shipping options, usage restrictions. So there's no new concepts to learn.
1:30 Okay, so we're going to do a quick demonstration on this. Uh, and I've set up an example storefront here with some things to note.
1:40 So in our demo storefront, I have set up two customers. So we've got our test user and we've got our administrative user.
1:49 And we'll see as well that they have subsequently been put into two separate departments. So we've got sample department one and sample department two.
1:58 Information on setting up departments is available elsewhere on the Infigo Academy. What we've also set up is two checkout attributes.
2:08 And again, there's full information on checkout attributes available on the Infigo Academy. The two we've set up here are what we call visible checkout attribute, which is an unrestricted check attribute that all users will see and then we've got the restricted checkout attribute which we will restrict
2:30 so a single department is going to see how would we do this from scratch? From your admin window here, first of all, just go ahead and go to the checkout attributes screen.
2:42 You may already have your checkout attributes created or you can create some brand new checkout attributes. And again, there's resources on the Infigo Academy showing you exactly how to do this.
2:53 To actually utilize these usage rules and control- control. Or who can see which checkout attributes we want to utilize these usage rules button here.
3:02 So we're going to restrict this one which we called restricted checkout attribute. Click on usage rules next to that. Now you can see that I've already got a couple of examples in here.
3:13 I'm just going to get rid of those temporarily and we create them again. Now this is a fairly straightforward interface.
3:20 We just need to choose what the requirement type is going to be. And we can control it by a lot of different things.
3:27 So usage requirements by customer roles, by product variants, information, via categories or critics. Basically in this case, which is probably going to be used most often, by departments.
3:41 And what this will allow us to do is to specify a department for which that, checkout attribute can or cannot be seen.
3:49 You see if we select usage rules by department, we get a couple of additional options. We've got one which is just a simple check box allowing us to control whether or not it restricts access.
4:00 And then we just need to put in an identifier. fire. So for the department option that's going to be the department ID which we'll find in a moment, but you might find for example if you go to product variants you'll get a different set of options and a different set of IDs that you need to So for example
4:17 here, you can see it's asking for product variants ID. Let's go back to our departments. We can identify these IDs just by going to the department screen.
4:31 And we'll see that there is an ID on the relevant departments. Now I'm going to restrict it so that sample departments are going which currently contains our test user cannot see this particular checkout attribute.
4:46 So, if I just put department ID 50, which relates to that, and say restricts usage. And we could also do the opposite for the other, uh, department.
4:58 So for example, if I say department number 51. So you can put multiple rules, multiple usage requirements on each one of these, department 51, and we're not going to restrict access.
5:13 And we can put as many options on here as we like, and then just make sure that we have confirmed that and that is all we need to do.
5:22 Now let's see that in action. So I'm just going to go and impersonate those two users in turn. So I'll go to my customer management.
5:34 Start off by impersonating my test user. And then go to my basket. Now I can see him, in my case, in this example, I've already put an item in my basket.
5:46 And I can see there that I've only got one check out. attributes available. Now, this could, as I mentioned, this could be an upload area.
5:53 It could be a drop down list. It could be a text box. In this case, we've left it just as a blank drop down.
5:59 Just as a very simple example. But you can see I've only got one of them visible. And that's because those usage restrictions rules are coming into play here.
6:09 However, if I go and impersonate the other user. So our admin user for which the restriction does not apply. We can see here that both of my checkout attributes are visible.
6:28 And that's it. So that's a base. a basic tutorial of how to use this usage restrictions functionality on a checkout attribute level.
6:37 That's just one specific example. In terms of restricting by department. But you can use this same methodology to create very expansive rules if you're requiring to use them.
