00:00:04.148 --> 00:00:10.396 Stration, where it all starts and uh bear with me as developed
00:00:10.396 --> 00:00:11.288 has been.
00:00:12.918 --> 00:00:17.088 Giving me some issues today, so something may break.
00:00:15.598 --> 00:00:17.838 I couldn't log in today for some odd reason.
00:00:17.658 --> 00:00:19.888 Yeah, I told him about it earlier.
00:00:19.898 --> 00:00:24.688 They fixed it so we will get started.
00:00:21.288 --> 00:00:21.968 OK, cool.
00:00:24.778 --> 00:00:27.188 Alright, so account registration.
00:00:29.898 --> 00:00:37.662 So clarity ourself has a stepped or multiple step registration
00:00:37.662 --> 00:00:38.648 process.
00:00:39.458 --> 00:00:43.743 We have our basic information as the first step with the fields
00:00:43.743 --> 00:00:47.292 that you see displayed here probably the most common
00:00:47.292 --> 00:00:50.908 customization of any stuff project is going to be the
00:00:50.908 --> 00:00:54.188 modification of the account registration fields.
00:00:55.018 --> 00:00:59.568 Sometimes there are some clients that will say you know, this is
00:00:59.568 --> 00:01:00.408 all we need.
00:01:00.418 --> 00:01:01.048 Looks good.
00:01:01.388 --> 00:01:02.718 Let's just use that.
00:01:02.728 --> 00:01:06.600 But 99% of the time, there's going to be certain information
00:01:06.600 --> 00:01:09.963 that a client is going to want to capture with their
00:01:09.963 --> 00:01:10.788 registration.
00:01:11.668 --> 00:01:14.793 Umm, so I'd say that's probably the most common account
00:01:14.793 --> 00:01:15.518 registration.
00:01:15.568 --> 00:01:15.908 Uh.
00:01:15.918 --> 00:01:19.462 Customization that you would see, and while this is an easy,
00:01:19.462 --> 00:01:19.868 easier.
00:01:21.088 --> 00:01:24.478 Modification or customization to make to account registration.
00:01:24.688 --> 00:01:27.678 It is still considered a customization.
00:01:30.858 --> 00:01:36.318 The second kind of scenario, the account registration.
00:01:36.328 --> 00:01:40.175 Umm, that's kind of a larger piece or they can lead to a
00:01:40.175 --> 00:01:43.548 larger piece is around, uh, account or approvals.
00:01:44.278 --> 00:01:48.981 So some clients could request and approval process for their
00:01:48.981 --> 00:01:50.908 users when they register.
00:01:51.318 --> 00:01:56.698 Umm, this does require some additional customization.
00:01:56.708 --> 00:02:01.798 Uh to implement within CEF admin away for the.
00:02:04.608 --> 00:02:10.282 At the client admins and navigate in and approve or deny
00:02:10.282 --> 00:02:10.978 a user.
00:02:11.108 --> 00:02:16.225 While we can set users as inactive on creation, we do need
00:02:16.225 --> 00:02:20.735 that additional time to customize that piece in the
00:02:20.735 --> 00:02:25.418 admin to allow for them to approve or deny that user.
00:02:25.768 --> 00:02:31.398 Alternatively, if they really wanted to save money, we could
00:02:31.398 --> 00:02:37.028 have them manually go to the users and accounts within admin
00:02:37.028 --> 00:02:41.458 SEV admin and change those statuses themselves.
00:02:41.808 --> 00:02:47.110 But typically clients look for at least at minimum, some type
00:02:47.110 --> 00:02:52.070 of UI that shows incoming registrations with some sort of
00:02:52.070 --> 00:02:53.438 approve or deny.
00:02:53.878 --> 00:02:59.887 But uh, another way that we typically approach and approval
00:02:59.887 --> 00:03:01.088 process for.
00:03:03.488 --> 00:03:04.918 Account registration.
00:03:04.928 --> 00:03:08.317 Umm with integrations and I don't know micki, if you want me
00:03:08.317 --> 00:03:11.206 to branch off in the integrations at all, if you're
00:03:11.206 --> 00:03:11.928 just keep it.
00:03:11.838 --> 00:03:13.788 No, that let's let's say again.
00:03:14.498 --> 00:03:18.044 They're definitely relevant in terms of how we customize this
00:03:18.044 --> 00:03:20.788 UI because it could go a lot of different ways.
00:03:20.798 --> 00:03:23.358 So I think that's definitely relevant.
00:03:24.878 --> 00:03:29.547 So on the same scenario of account approvals, one way that
00:03:29.547 --> 00:03:34.691 we kind of offer an alternative to account approval processes as
00:03:34.691 --> 00:03:38.885 well as saving time on integrations with the account
00:03:38.885 --> 00:03:41.338 registration is an action form.
00:03:42.168 --> 00:03:46.890 So basically we would replace out of box CEF registration with
00:03:46.890 --> 00:03:51.312 an action form that would capture the user information and
00:03:51.312 --> 00:03:55.359 email it to the client and then they would input that
00:03:55.359 --> 00:04:00.081 registration information into their ERP and we would sink that
00:04:00.081 --> 00:04:04.128 information back into self and generate the new user.
00:04:04.858 --> 00:04:09.977 This would allow us to have that approval process be checked off
00:04:09.977 --> 00:04:14.702 as Ohm's part of the scope, because we're not automatically
00:04:14.702 --> 00:04:19.427 generating the users they're manually entered by the client
00:04:19.427 --> 00:04:20.608 administrators.
00:04:20.618 --> 00:04:25.286 So that would solve the approval process step and it also saves
00:04:25.286 --> 00:04:29.225 time and budget for the integration because we're not
00:04:29.225 --> 00:04:32.944 having to capture the registration information and
00:04:32.944 --> 00:04:35.278 generate the user within itself.
00:04:35.288 --> 00:04:41.047 And then sync the account and user from self into the clients
00:04:41.047 --> 00:04:41.418 ERP.
00:04:42.178 --> 00:04:44.248 This also helps with.
00:04:47.688 --> 00:04:51.424 The integration simplicity as well as we all have the
00:04:51.424 --> 00:04:55.299 experience integrations with some systems can give us a
00:04:55.299 --> 00:04:59.519 little bit of trouble and just eliminates and extra area for
00:04:59.519 --> 00:05:00.418 integrations.
00:05:01.468 --> 00:05:05.618 But in some scenarios of client does require this level of
00:05:05.618 --> 00:05:10.118 automation and that is something that we can absolutely do with
00:05:10.118 --> 00:05:12.298 additional customization hours.
00:05:13.008 --> 00:05:17.588 So approval process can be handled directly within self.
00:05:18.578 --> 00:05:22.731 We can have a integration between CEF and an ERP for
00:05:22.731 --> 00:05:27.511 account registration with an approval process there and then
00:05:27.511 --> 00:05:32.369 we can have account registration information be passed to the
00:05:32.369 --> 00:05:36.678 client without an integration it through action forms.
00:05:39.028 --> 00:05:40.018 Any questions?
00:05:40.028 --> 00:05:42.648 Or did that all make a little bit of sense?
00:05:45.478 --> 00:05:47.168 I'm going to ask you a question for you, Shelton.
00:05:47.378 --> 00:05:52.545 What are some alarm bells that should ring for the team if they
00:05:52.545 --> 00:05:57.793 hear a client talking about when it comes to registration things
00:05:57.793 --> 00:05:59.488 to pay attention for?
00:05:58.648 --> 00:06:02.668 I actually I had one on that specific point.
00:06:02.678 --> 00:06:05.208 I was gonna say if there's no questions, I have an alarm bell.
00:06:05.898 --> 00:06:06.968 Thank you.
00:06:07.138 --> 00:06:07.848 Perfect, Kyle.
00:06:08.508 --> 00:06:13.348 So anytime somebody brings up multiple registrations, I'll
00:06:13.348 --> 00:06:17.942 just use RX1 for an example where I could register as a
00:06:17.942 --> 00:06:22.864 patient, but I could register as a doctor whenever a client
00:06:22.864 --> 00:06:28.278 brings up multiple registrations if they want it to be automated.
00:06:28.768 --> 00:06:33.458 I mean, even if they don't want it to be automated, that should
00:06:33.458 --> 00:06:38.000 beg the question of, well, what are the roles and permissions
00:06:38.000 --> 00:06:40.198 for when those users register?
00:06:40.208 --> 00:06:43.903 And if they're, you know whether they're they have a process or
00:06:43.903 --> 00:06:47.598 not, whether there's an approval process or or not, what should
00:06:47.598 --> 00:06:50.138 be the roles and permissions for that user?
00:06:50.688 --> 00:06:55.706 Umm, so that's always a red flag that I kind of just like look
00:06:55.706 --> 00:06:59.528 for because that could potentially include more
00:06:59.528 --> 00:07:01.758 development time around you.
00:07:01.848 --> 00:07:06.952 Well, it could lead into well on one side just a role in
00:07:06.952 --> 00:07:09.638 permissions building that out.
00:07:09.648 --> 00:07:13.568 That's time, but that could also allude to other features that we
00:07:13.568 --> 00:07:17.369 didn't discuss or features that you know they might be bringing
00:07:17.369 --> 00:07:20.991 up for the first time of like, ohh yeah, these users they do
00:07:20.991 --> 00:07:24.614 this, this and this and you're like we have not talked about
00:07:24.614 --> 00:07:25.148 that yet.
00:07:25.498 --> 00:07:28.851 So that's just, you know, whenever there's multiple
00:07:28.851 --> 00:07:32.720 registrations, always look at the roles and permissions and
00:07:32.720 --> 00:07:36.652 what those users have to do because it can sometimes uncover
00:07:36.652 --> 00:07:40.521 other features that you know might be implied through those
00:07:40.521 --> 00:07:42.068 different registrations.
00:07:43.258 --> 00:07:43.608 After.
00:07:43.928 --> 00:07:44.878 Thank you, Kyle.
00:07:45.158 --> 00:07:45.358 Yeah.
00:07:45.228 --> 00:07:46.318 Amy, I saw you on mute.
00:07:45.248 --> 00:07:45.468 Yes.
00:07:46.328 --> 00:07:47.098 Did you have a question?
00:07:49.498 --> 00:07:52.198 No, I don't remember what I was gonna say it.
00:07:51.718 --> 00:07:52.018 OK.
00:07:53.518 --> 00:07:57.598 And a good a good example of an active project that's actually
00:07:57.598 --> 00:07:58.828 just came up today.
00:07:58.838 --> 00:08:03.198 Call with the roles is with repro tech ohm.
00:08:03.988 --> 00:08:09.121 We were discussing the different roles for clinics today and we
00:08:09.121 --> 00:08:14.094 were basically saying, OK, so you'll have the clinic accounts
00:08:14.094 --> 00:08:19.307 and acumatica that their ERP and you'll assign the user roles to
00:08:19.307 --> 00:08:23.558 the users and we'll sync that in and apply the role.
00:08:23.568 --> 00:08:28.500 And then they're like, no, no, we need a way for the admin of
00:08:28.500 --> 00:08:32.318 the clinic to assign user roles to their users.
00:08:32.708 --> 00:08:38.118 So the topic of user roles typically leads to at least a
00:08:38.118 --> 00:08:43.337 couple of different areas that are gonna be applied to
00:08:43.337 --> 00:08:47.038 different features within the project.
00:08:47.048 --> 00:08:51.615 So yes, like Kyle said, user roles are very important topic
00:08:51.615 --> 00:08:52.908 to uncover early.
00:08:53.638 --> 00:08:55.178 Uh with the client?
00:08:55.758 --> 00:08:57.248 The that's a great point.
00:08:57.258 --> 00:08:58.998 Who's going to administer set roles?
00:09:00.608 --> 00:09:03.814 They need to have like some place if if the admin of the
00:09:03.814 --> 00:09:07.356 platform isn't doing it, then yeah, that definitely adds a lot
00:09:07.356 --> 00:09:07.918 more time.
00:09:08.838 --> 00:09:13.148 And with with Seth Admin, would the reprotect example.
00:09:13.158 --> 00:09:15.308 That's not something that is out of box.
00:09:15.318 --> 00:09:19.725 If they had a reprotect admin that was gonna access CEF admin
00:09:19.725 --> 00:09:24.202 and assign the user roles to the users for all of the clinics,
00:09:24.202 --> 00:09:27.968 that would be something that we could do out of box.
00:09:27.978 --> 00:09:32.523 After we have built out the the different roles, but they're
00:09:32.523 --> 00:09:36.620 requesting a way for the clinician after they log into
00:09:36.620 --> 00:09:41.016 their portal to be able to assign the user roles, which is
00:09:41.016 --> 00:09:44.368 not something that is out of the box at all.
00:09:45.318 --> 00:09:48.188 OK, sorry, getting off topic talking about Reaper Tech.
00:09:49.018 --> 00:09:49.928 Let's continue.
00:09:49.938 --> 00:09:51.308 All right, let me fill in some.
00:09:55.658 --> 00:10:04.058 Uh, names here and we'll look at the next step of registration.
00:10:12.938 --> 00:10:17.598 So the next step of registration is the address book and the
00:10:17.598 --> 00:10:21.646 address book can lead to a conversation and a lot of
00:10:21.646 --> 00:10:26.077 different areas as far as registration goes, first UM, we
00:10:26.077 --> 00:10:30.889 have the ability for a user to enter their billing information
00:10:30.889 --> 00:10:32.798 and shipping information.
00:10:32.808 --> 00:10:37.795 If it is different than the billing or we have the option to
00:10:37.795 --> 00:10:42.618 copy the billing address here with registration typically.
00:10:44.738 --> 00:10:48.988 Addresses are pretty standard uh clients usually accept the out
00:10:48.988 --> 00:10:49.718 of the box.
00:10:50.168 --> 00:10:54.978 This uh address registration system.
00:10:55.668 --> 00:11:00.420 There are some cases where we capture the information just
00:11:00.420 --> 00:11:05.333 strictly through fields and registration rather than the out
00:11:05.333 --> 00:11:10.407 of box of registration models, but a majority of the time when
00:11:10.407 --> 00:11:15.400 we are doing that, typically that information is being passed
00:11:15.400 --> 00:11:18.138 to and the ERP or an action form.
00:11:18.208 --> 00:11:23.285 Uh, most of the time it's most likely gonna be an action form,
00:11:23.285 --> 00:11:27.878 so the out of the box address model typically is pretty.
00:11:29.208 --> 00:11:32.777 Works pretty well for most clients and really a lot of
00:11:32.777 --> 00:11:36.670 customizations aren't really requested around how addresses
00:11:36.670 --> 00:11:37.318 are input.
00:11:37.598 --> 00:11:41.799 A couple of more topics about addresses with clients that
00:11:41.799 --> 00:11:46.217 typically comes up is when we have an integration between an
00:11:46.217 --> 00:11:47.158 ERP and self.
00:11:47.758 --> 00:11:51.901 Uh, some clients have requirement that the address
00:11:51.901 --> 00:11:57.018 information cannot be modified once we sync it in from the ERP
00:11:57.018 --> 00:11:59.048 to their account and CEF.
00:12:00.818 --> 00:12:06.506 This is a customization for us to go in and modify the UM
00:12:06.506 --> 00:12:12.586 address book to be read only and not allow for any updates or
00:12:12.586 --> 00:12:13.958 modifications.
00:12:14.238 --> 00:12:19.136 Uh, that's a pretty common request for uh from clients with
00:12:19.136 --> 00:12:20.768 regarding addresses.
00:12:23.298 --> 00:12:27.628 Just keep going and this is where I live.
00:12:27.638 --> 00:12:29.858 If you wanna mail me anything, uh.
00:12:34.758 --> 00:12:35.028 OK.
00:12:47.598 --> 00:12:50.638 Or you can additionally Ohh did not put it in the first time.
00:12:51.228 --> 00:12:53.638 No, I clicked off the modal and it went away.
00:12:53.708 --> 00:12:55.808 That was just to use the user error.
00:12:54.038 --> 00:12:55.568 Ohh gosh I was.
00:12:55.578 --> 00:12:56.738 I thought you put it in twice.
00:12:56.748 --> 00:12:57.938 I was like, why didn't you just copy?
00:12:57.078 --> 00:12:58.398 The user error.
00:12:59.598 --> 00:13:04.277 So before we before we continue to the confirmation step, an
00:13:04.277 --> 00:13:08.803 additional step that client sometimes request is the input
00:13:08.803 --> 00:13:13.251 of payment methods and payment information during account
00:13:13.251 --> 00:13:14.248 registration.
00:13:14.738 --> 00:13:18.816 This is not out of box and it's something that would require
00:13:18.816 --> 00:13:20.888 customizations for us to input.
00:13:22.148 --> 00:13:26.467 Those are input the payment method models into account
00:13:26.467 --> 00:13:31.336 registration and capture that information and apply it to the
00:13:31.336 --> 00:13:31.728 user.
00:13:32.928 --> 00:13:38.896 One call out here of kind of a risk area of with uh account
00:13:38.896 --> 00:13:45.163 registration and adding payment methods during that process is
00:13:45.163 --> 00:13:50.832 that the user is not created until the our until account
00:13:50.832 --> 00:13:53.418 registration is completed.
00:13:53.708 --> 00:13:58.439 Um, so if a user does not complete registration then we
00:13:58.439 --> 00:14:03.508 would not be able to assign the payment method to the user.
00:14:06.858 --> 00:14:10.870 Unless they started registration again, it fully completed the
00:14:10.870 --> 00:14:11.188 step.
00:14:11.618 --> 00:14:16.269 This is something that most likely wouldn't ever happen, but
00:14:16.269 --> 00:14:21.148 it's just kind of a a call out of a potential issue that if the
00:14:21.148 --> 00:14:25.875 user doesn't exist then we have nowhere to assign the payment
00:14:25.875 --> 00:14:27.018 information to.
00:14:27.488 --> 00:14:30.703 Umm, so the next step registration is the
00:14:30.703 --> 00:14:31.698 confirmation.
00:14:31.908 --> 00:14:36.380 This is another area that clients request some
00:14:36.380 --> 00:14:40.661 customizations to, usually pretty low effort
00:14:40.661 --> 00:14:42.088 customizations.
00:14:42.098 --> 00:14:47.531 You know, they may have multiple terms or service or agreements
00:14:47.531 --> 00:14:52.540 that users need to accept, sometimes with a clickable text
00:14:52.540 --> 00:14:57.718 or some kind of CTA that will redirect the user to uh, their
00:14:57.718 --> 00:15:01.028 tires and conditions page on the site.
00:15:01.038 --> 00:15:05.758 Something along those lines, but anything outside of the basic
00:15:05.758 --> 00:15:10.028 uh, I agree to the terms of this website out of the box.
00:15:10.038 --> 00:15:14.672 Wording it would be considered a customization even though it is
00:15:14.672 --> 00:15:15.598 rather small.
00:15:17.788 --> 00:15:22.248 And then the next step is the registration success message.
00:15:24.818 --> 00:15:29.128 We currently don't have anything and develop.
00:15:29.138 --> 00:15:33.884 I'm not sure if there's if it's just missing, but if a customer
00:15:33.884 --> 00:15:38.407 wanted to add a registration success message then that would
00:15:38.407 --> 00:15:40.928 be a small customization as well.
00:15:41.438 --> 00:15:43.808 Actually, I think that's just missing Shelton.
00:15:43.818 --> 00:15:47.232 It actually when you finish registration it displays a
00:15:47.232 --> 00:15:49.218 success message of like awesome.
00:15:49.228 --> 00:15:50.348 We've registered you.
00:15:50.358 --> 00:15:54.268 Do you want to shop or do you want to?
00:15:54.478 --> 00:15:55.158 What was it?
00:15:55.198 --> 00:15:56.088 Ohh.
00:15:56.158 --> 00:15:57.388 In her card information.
00:15:57.718 --> 00:16:01.244 So it gives you two options, one leads you to the catalog, one
00:16:01.244 --> 00:16:04.378 leads you to the wallet to set up your payment methods.
00:16:04.968 --> 00:16:07.998 Umm, which is the out of the box 1?
00:16:08.008 --> 00:16:09.698 I don't know why it wasn't displayed.
00:16:09.708 --> 00:16:12.813 We have had some, you know, bugs around that of, you know,
00:16:12.813 --> 00:16:14.338 sometimes it doesn't display.
00:16:14.388 --> 00:16:16.418 Ohh yeah cool.
00:16:16.128 --> 00:16:19.060 But yes, that's the one we do have that built and it should be
00:16:16.468 --> 00:16:17.138 Thank you, Carl.
00:16:19.060 --> 00:16:21.852 out of the box and it should display there and give them an
00:16:21.852 --> 00:16:23.248 option of where they wanna go.
00:16:24.578 --> 00:16:25.048 Perfect.
00:16:25.238 --> 00:16:25.808 Thank you.
00:16:26.798 --> 00:16:31.044 And then the last comment customization, I wanted to talk
00:16:31.044 --> 00:16:35.582 about with account registration would be turning registration
00:16:35.582 --> 00:16:40.047 into a single pane rather than these stepped process that we
00:16:40.047 --> 00:16:44.292 have a lot of customers would like it like to see it as a
00:16:44.292 --> 00:16:48.464 single pane where you just continuously scroll and input
00:16:48.464 --> 00:16:49.708 your information.
00:16:50.358 --> 00:16:54.635 But that is a customization, but it is something that a lot of
00:16:54.635 --> 00:16:57.078 clients like to see on their sites.
00:16:58.728 --> 00:17:01.688 So any questions about account registration?
00:17:05.438 --> 00:17:06.218 Nothing for me.
00:17:07.878 --> 00:17:08.248 Not here.
00:17:12.118 --> 00:17:12.908 Perfect.
00:17:12.998 --> 00:17:16.868 Alright, we shall move on to the catalog.
00:17:16.918 --> 00:17:22.028 So the catalog as you can see, we have our.
00:17:25.368 --> 00:17:29.298 Search term which is the search box that allows us to search all
00:17:29.298 --> 00:17:32.018 products on the site for different keywords.
00:17:32.028 --> 00:17:36.432 We have our product ratings, which is an app setting within
00:17:36.432 --> 00:17:40.468 self and app setting is something that is configurable
00:17:40.468 --> 00:17:41.348 within self.
00:17:41.418 --> 00:17:46.016 Uh, essentially, through the turning on or turning off of
00:17:46.016 --> 00:17:51.010 that setting within the itself admin app settings or something
00:17:51.010 --> 00:17:53.308 that are easily configurable.
00:17:53.658 --> 00:17:58.310 So if you have a client asking for something, and it is indeed
00:17:58.310 --> 00:18:02.962 an app setting, it is a very low lift to turn that app setting
00:18:02.962 --> 00:18:07.688 off and make sure that the the changes are applied to the site.
00:18:08.038 --> 00:18:11.308 Product ratings is an example of those app settings.
00:18:12.058 --> 00:18:15.868 Our next filter option is going to be our categories.
00:18:16.138 --> 00:18:21.524 Categories can be configured in different ways for custom uh
00:18:21.524 --> 00:18:26.292 client project with an integration we can sync in the
00:18:26.292 --> 00:18:30.618 products and have the sync set up to categories.
00:18:30.928 --> 00:18:35.822 Are we can have a developer manually set up the categories
00:18:35.822 --> 00:18:40.965 before we run the product sync and assign the products to the
00:18:40.965 --> 00:18:42.458 preset categories.
00:18:43.428 --> 00:18:47.630 Products do require a category in order to successfully display
00:18:47.630 --> 00:18:51.701 on the site, so if you're ever doing anything with SEF trying
00:18:51.701 --> 00:18:55.640 to add products to the store front and for some reason it's
00:18:55.640 --> 00:18:59.579 not displaying, double check that you have it assigned to a
00:18:59.579 --> 00:19:02.008 category because those are required.
00:19:02.588 --> 00:19:03.058 Umm.
00:19:03.928 --> 00:19:07.478 And our category, OK.
00:19:04.458 --> 00:19:08.597 I have a pop quiz quick pop quiz that Shelton and Kyle here
00:19:08.597 --> 00:19:09.838 allowed to answer.
00:19:11.258 --> 00:19:14.092 Does anybody know how many levels deep are category
00:19:14.092 --> 00:19:15.018 structure can go?
00:19:20.588 --> 00:19:20.958 4.
00:19:23.118 --> 00:19:24.438 And does go out of the box.
00:19:26.318 --> 00:19:26.648 8.
00:19:29.908 --> 00:19:30.508 I have no idea.
00:19:32.378 --> 00:19:32.818 I don't know.
00:19:34.298 --> 00:19:34.918 Belton, how many?
00:19:37.608 --> 00:19:38.968 That's seven and it.
00:19:39.138 --> 00:19:42.958 Yes, Sir, you're close.
00:19:40.648 --> 00:19:41.028 I was.
00:19:41.038 --> 00:19:41.578 I got it.
00:19:41.588 --> 00:19:43.388 You know, we'll under a little over.
00:19:44.368 --> 00:19:45.028 Seven.
00:19:45.038 --> 00:19:47.598 But if you go up to the products Mega menu there.
00:19:48.708 --> 00:19:51.858 It you know, there's your primaries on the left.
00:19:52.428 --> 00:19:55.528 The that's interesting.
00:19:58.138 --> 00:19:58.778 It's developed.
00:19:58.788 --> 00:19:59.548 It's always interesting.
00:20:01.068 --> 00:20:01.868 Fascinating.
00:20:03.688 --> 00:20:07.838 You might want to go to the B2B site B to B dot clarity demos.
00:20:07.958 --> 00:20:08.668 Ah, there we go.
00:20:10.098 --> 00:20:13.904 So yeah, the primaries on the side, secondaries in the middle
00:20:13.904 --> 00:20:17.649 with an image and then third level below those where it says
00:20:17.649 --> 00:20:20.288 no additional there we go for like breaks.
00:20:20.778 --> 00:20:24.827 So automotive is the primary break is the secondary and then
00:20:24.827 --> 00:20:27.348 disk brakes would be the third level.
00:20:27.638 --> 00:20:31.780 If they do want to go farther than that, then we'll have to
00:20:31.780 --> 00:20:33.988 probably figure out a different.
00:20:35.038 --> 00:20:40.434 UI for that mega menu drop down to where it can go deeper, but
00:20:40.434 --> 00:20:45.743 typically if anyone does bring up going that deep we can most
00:20:45.743 --> 00:20:51.053 certainly do it U to 7 levels in CEF with categories here but
00:20:51.053 --> 00:20:54.478 something to always keep in mind it is.
00:20:54.608 --> 00:20:59.078 It's a very kind of arduous process.
00:20:59.088 --> 00:21:03.519 It's very hard to like, get down to the actual category you need
00:21:03.519 --> 00:21:06.858 when it's that level like that many levels deep.
00:21:06.238 --> 00:21:06.538 Umm.
00:21:06.928 --> 00:21:11.195 So it's a really, really kind of, I'll just call it what it
00:21:11.195 --> 00:21:11.408 is.
00:21:11.418 --> 00:21:15.438 It's bad user experience to have them go search all the way down
00:21:15.438 --> 00:21:19.148 7 levels of like if you're actually going to use all seven.
00:21:19.258 --> 00:21:20.818 I just want to have this caveat here.
00:21:23.048 --> 00:21:27.483 But three is what we display out of box, but it can go up to 7
00:21:27.483 --> 00:21:30.298 and we can customize the view from 427.
00:21:30.388 --> 00:21:31.238 However you would like.
00:21:33.828 --> 00:21:34.298 Awesome.
00:21:34.468 --> 00:21:37.050 Alright, back to your regularly scheduled programming Shelton,
00:21:37.050 --> 00:21:37.828 sorry to interrupt.
00:21:37.588 --> 00:21:38.318 Thank you, Carl.
00:21:38.328 --> 00:21:40.198 No, please interrupt if.
00:21:38.938 --> 00:21:39.618 Yeah, that was a good.
00:21:39.628 --> 00:21:40.488 That was a good question.
00:21:40.498 --> 00:21:42.998 I would have known that, so that was a good tidbit.
00:21:42.128 --> 00:21:42.418 Umm.
00:21:45.098 --> 00:21:49.030 So like Kyle, we're saying we have our parent categories with
00:21:49.030 --> 00:21:50.868 our subcategories underneath.
00:21:51.418 --> 00:21:55.672 Uh, these are set up like I was saying through the sync or
00:21:55.672 --> 00:21:59.925 manually within CEF and then products are assigned to them
00:21:59.925 --> 00:22:04.323 either manually through CEF admin or the product importer or
00:22:04.323 --> 00:22:06.918 through a product sync with an ERP.
00:22:06.108 --> 00:22:06.358 Ready.
00:22:10.398 --> 00:22:15.219 You can select your category and then Seth will filter the
00:22:15.219 --> 00:22:19.958 catalog for your selected category and then based on your
00:22:19.958 --> 00:22:24.779 selection it will display the parent and the other related
00:22:24.779 --> 00:22:26.658 category subcategories.
00:22:27.048 --> 00:22:31.198 Uh, based on the category selection that you made?
00:22:34.818 --> 00:22:39.188 Attributes are going to be things like color, size,
00:22:39.188 --> 00:22:40.028 materials.
00:22:40.038 --> 00:22:46.450 Your typical kind of product descriptions product attributes
00:22:46.450 --> 00:22:53.176 can be created manually within self or we can store information
00:22:53.176 --> 00:22:55.278 from a sync product.
00:22:55.338 --> 00:22:59.906 Information from a sync as attributes on the product record
00:22:59.906 --> 00:23:03.408 and that is where these values would display.
00:23:03.838 --> 00:23:08.538 You can select let's say orange.
00:23:10.358 --> 00:23:14.261 Uh, I guess it's probably want a good color, but based on your
00:23:14.261 --> 00:23:18.225 selection, you'll get all orange products that are available in
00:23:18.225 --> 00:23:18.968 the catalog.
00:23:18.978 --> 00:23:24.190 And then from your selection you can drill down into further
00:23:24.190 --> 00:23:29.145 attributes that are available for the all of the products
00:23:29.145 --> 00:23:31.708 based on your first selection.
00:23:35.918 --> 00:23:38.791 Shelton can a product be associated to more than one
00:23:38.791 --> 00:23:39.278 category?
00:23:40.598 --> 00:23:40.718 Yes.
00:23:43.158 --> 00:23:43.548 Right.
00:23:43.618 --> 00:23:44.388 Am I wrong?
00:23:44.438 --> 00:23:45.008 I may be wrong?
00:23:45.658 --> 00:23:46.698 No, I believe you're right.
00:23:47.098 --> 00:23:47.898 That's my understanding.
00:23:47.838 --> 00:23:48.348 Yeah.
00:23:48.358 --> 00:23:51.218 Yes, you can have multiple categories for a product.
00:23:54.808 --> 00:23:57.698 Yes, sorry if I'm second guessing myself.
00:23:55.948 --> 00:23:56.548 That is correct.
00:23:59.028 --> 00:23:59.288 No.
00:23:59.298 --> 00:24:00.278 Yeah, that that's correct.
00:23:59.348 --> 00:23:59.748 OK.
00:24:00.288 --> 00:24:03.375 You can't have multiple categories, so that generator
00:24:03.375 --> 00:24:07.034 could be in manufacturing, but it could also be in electronics,
00:24:07.034 --> 00:24:10.750 or it could also be in whatever you want it to be in, because it
00:24:10.750 --> 00:24:14.408 could be classified as multiple different categories of things.
00:24:16.358 --> 00:24:16.788 Thank you.
00:24:16.798 --> 00:24:21.644 Go umm our next filter option is price range which is like it
00:24:21.644 --> 00:24:26.256 sounds based on the product pricing and the catalog you're
00:24:26.256 --> 00:24:29.538 able to filter for a certain price range.
00:24:29.848 --> 00:24:33.288 Uh did.
00:24:33.298 --> 00:24:37.693 Did we used to have a custom price range or my imagining
00:24:36.378 --> 00:24:38.678 No, it it is those.
00:24:37.693 --> 00:24:38.078 that?
00:24:38.808 --> 00:24:42.958 Yeah, we have those ranges out of the box.
00:24:43.768 --> 00:24:48.515 If they want to change those ranges, it is a customization,
00:24:48.515 --> 00:24:50.018 not a very big one.
00:24:50.228 --> 00:24:53.600 If they wanna do something like a slider like I want it from
00:24:53.600 --> 00:24:57.083 this price to this price, you know like you do for like Zillow
00:24:57.083 --> 00:24:58.188 and stuff like that.
00:24:58.938 --> 00:24:59.538 A.
00:24:59.888 --> 00:25:02.645 When you're like dragging and dropping the min and Max price,
00:25:02.645 --> 00:25:03.978 that would be a customization.
00:25:04.168 --> 00:25:07.631 But yeah, this is the just the stuff that we have out of the
00:25:07.631 --> 00:25:07.858 box.
00:25:07.868 --> 00:25:10.145 If they wanna change those ranges, very small
00:25:10.145 --> 00:25:10.838 customization.
00:25:10.848 --> 00:25:14.867 If they wanna change how that's presented and how that works,
00:25:14.867 --> 00:25:16.358 slightly larger change.
00:25:17.048 --> 00:25:19.158 But if they want to turn it off, we can just turn it off.
00:25:19.448 --> 00:25:20.428 There's a lot of options there.
00:25:22.408 --> 00:25:22.998 Gotcha.
00:25:23.108 --> 00:25:23.598 Thank you.
00:25:24.488 --> 00:25:26.058 Next is brands.
00:25:26.118 --> 00:25:31.818 Uh, this will be the product brand associated to the product.
00:25:32.378 --> 00:25:36.225 If you know products, all products from a storefront, or
00:25:36.225 --> 00:25:40.274 all the same brand, if it's a company that assigns the same
00:25:40.274 --> 00:25:44.458 brand all their products, we would only have one option here.
00:25:44.528 --> 00:25:48.217 But essentially this is just another product data point that
00:25:48.217 --> 00:25:51.967 is retrieved from the sync or created when the product is set
00:25:51.967 --> 00:25:52.148 up.
00:25:52.438 --> 00:25:57.068 Uh, that assigns the product uh to a brand and all associated
00:25:57.068 --> 00:26:00.578 products of that brand are filterable options.
00:26:04.648 --> 00:26:09.778 And then the last filter option is gonna be the compare option.
00:26:10.488 --> 00:26:14.982 This is something that you have to actually apply products to
00:26:14.982 --> 00:26:17.518 before anything will display here.
00:26:17.628 --> 00:26:21.475 So you can see I have my generator here and when you
00:26:21.475 --> 00:26:25.758 hover over the image you get our different options for the
00:26:25.758 --> 00:26:26.338 product.
00:26:26.348 --> 00:26:29.814 So we can add to compare and then if I want to compare it
00:26:29.814 --> 00:26:31.248 against this dress here.
00:26:32.738 --> 00:26:36.862 Once I had my second product, I'll get this modal that
00:26:36.862 --> 00:26:41.435 displays and asking me if I wanna compare these products and
00:26:41.435 --> 00:26:46.233 then once I do that I will get a side by side comparison of all
00:26:46.233 --> 00:26:50.656 the product specifications associated with the product and
00:26:50.656 --> 00:26:55.454 you can just scroll and see all of the information and then you
00:26:55.454 --> 00:26:58.228 will be able to add it to your cart.
00:26:58.328 --> 00:27:03.735 Uh, change the quantity are removed from compare and you can
00:27:03.735 --> 00:27:04.178 then.
00:27:07.118 --> 00:27:13.180 Go back and associate two different products, so compare
00:27:13.180 --> 00:27:13.818 works.
00:27:13.828 --> 00:27:17.614 I mean kind of like exactly how you think it would similar to
00:27:17.614 --> 00:27:21.461 other sites where you picked two products and compare and this
00:27:21.461 --> 00:27:23.598 may may have broken something but?
00:27:24.438 --> 00:27:26.658 Can you only compare two products at a time, Shelton?
00:27:30.098 --> 00:27:30.578 Let's see.
00:27:35.068 --> 00:27:37.808 Yes, I believe that is the case.
00:27:37.138 --> 00:27:37.768 No.
00:27:37.878 --> 00:27:39.028 You have a slider.
00:27:37.948 --> 00:27:38.308 And no.
00:27:39.038 --> 00:27:40.048 You see the thing?
00:27:40.058 --> 00:27:41.228 Yeah, right over there.
00:27:41.238 --> 00:27:47.258 You can actually go to the next page of compared other items.
00:27:48.448 --> 00:27:51.518 You have to have, I think, I think 4 in there.
00:27:51.528 --> 00:27:55.218 I think as it'll stack it's dynamic.
00:27:55.308 --> 00:27:56.858 So see now there's three.
00:27:57.128 --> 00:28:01.038 If you do another one, there may be 4.
00:28:01.048 --> 00:28:03.278 I forget how far it stacks.
00:28:03.288 --> 00:28:07.503 I'm pretty sure it's three and then it goes over to compare the
00:28:06.048 --> 00:28:08.308 To the to the OK.
00:28:07.503 --> 00:28:07.898 other.
00:28:08.248 --> 00:28:08.718 Yeah.
00:28:08.768 --> 00:28:12.868 There you go and they can customize this of course.
00:28:12.878 --> 00:28:16.252 Like you know, if the bulleted specs or is too much information
00:28:16.252 --> 00:28:19.572 there, we can always, you know take a field out, put in what's
00:28:19.572 --> 00:28:20.468 relevant to them.
00:28:20.478 --> 00:28:23.468 Of course it's a customization, but it's not too terribly hard.
00:28:23.478 --> 00:28:29.210 We have the information, we just map it to this this UI, but
00:28:29.210 --> 00:28:34.378 yeah, stacks to three has a button to go to four plus.
00:28:37.038 --> 00:28:38.668 And yeah, customizable.
00:28:41.748 --> 00:28:42.088 Cool.
00:28:42.328 --> 00:28:42.878 Thank you.
00:28:42.888 --> 00:28:45.328 As you can see, I'm still learning as well.
00:28:47.238 --> 00:28:48.078 Seth is a beast.
00:28:47.698 --> 00:28:49.798 We are all always still learning exactly.
00:28:49.738 --> 00:28:51.518 I'm I'm still learning.
00:28:53.198 --> 00:28:54.938 I've been on this platform for five years.
00:28:57.568 --> 00:28:58.198 All right.
00:28:58.208 --> 00:29:01.501 So maybe and I'll into the actual product cards and the
00:29:01.501 --> 00:29:02.618 catalog themselves.
00:29:02.708 --> 00:29:06.560 As you can see, when we hover we get to add to compare add to
00:29:06.560 --> 00:29:08.858 wish list and add to favorites list.
00:29:09.068 --> 00:29:13.940 You can see that these two products have different options
00:29:13.940 --> 00:29:18.977 that I have the in stock alerts option here on the Mens shoe
00:29:18.977 --> 00:29:22.858 trees, but I do not have it as an option here.
00:29:23.408 --> 00:29:29.015 That is because this product stock our product inventory set
00:29:29.015 --> 00:29:34.438 to unlimited, but this is also an is downloadable product.
00:29:34.448 --> 00:29:38.902 So if you have a product that has unlimited stock quantity or
00:29:38.902 --> 00:29:43.428 isn't or isn't is downloadable product, then you won't be able
00:29:43.428 --> 00:29:47.738 to add it to your end stock alerts because the product will
00:29:47.738 --> 00:29:49.318 never go out of stock.
00:29:50.128 --> 00:29:50.758 Umm.
00:29:52.048 --> 00:29:56.672 And then with the product card configuration, we have the
00:29:56.672 --> 00:30:01.296 product title, the skew the stock notifier, our inventory
00:30:01.296 --> 00:30:05.841 notifier and then our short product description, product
00:30:05.841 --> 00:30:06.478 pricing.
00:30:06.688 --> 00:30:10.995 So you can see we have a discounted price associated with
00:30:10.995 --> 00:30:15.748 this product and the out of box functionality is to display the
00:30:15.748 --> 00:30:19.238 base list price and then the discounted price.
00:30:20.148 --> 00:30:24.704 We have our quantity modifier and then the option to add the
00:30:24.704 --> 00:30:29.408 product to the cart or the drop down to add to the quote cart.
00:30:29.598 --> 00:30:34.003 I know teams sometimes doesn't show drop down, so if you if you
00:30:34.003 --> 00:30:37.238 can't see it when you OK you can see it. Cool.
00:30:35.148 --> 00:30:35.618 You can see it.
00:30:39.618 --> 00:30:41.808 So those are our options with the product cards.
00:30:41.818 --> 00:30:46.836 Product cards can be customized, but it would be a customization
00:30:46.836 --> 00:30:51.467 to the project for us to modify these product cards and any
00:30:51.467 --> 00:30:53.628 information that we display.
00:30:53.818 --> 00:30:57.815 While it may be relatively small, it still would be
00:30:57.815 --> 00:31:00.198 considered a customization ohm.
00:31:01.448 --> 00:31:05.239 Some of the different views that we have for the cart are not for
00:31:05.239 --> 00:31:05.698 the car.
00:31:05.708 --> 00:31:09.613 The product catalog is the grid view, which is what you see
00:31:09.613 --> 00:31:09.938 here.
00:31:09.948 --> 00:31:15.878 We have our table view and then we have our list view.
00:31:22.348 --> 00:31:25.348 If a client oh, go ahead, Carl.
00:31:22.478 --> 00:31:23.388 Any good way?
00:31:23.878 --> 00:31:27.569 Ohh, I'm sorry, I was going to say a good way to explain those
00:31:25.358 --> 00:31:26.088 No good.
00:31:27.569 --> 00:31:31.200 grid is the, you know, obviously the typical ecommerce layout
00:31:31.200 --> 00:31:34.422 list view gives you the most amount of information per
00:31:34.422 --> 00:31:38.229 product but the least amount of products per page and then table
00:31:38.229 --> 00:31:41.978 view gives you the most amount of products but the least amount
00:31:41.978 --> 00:31:45.258 of information you're not getting all the specs and the
00:31:45.258 --> 00:31:47.308 short description and all of that.
00:31:47.398 --> 00:31:51.748 The grid view is just a balanced kind of view between the two.
00:31:53.528 --> 00:31:56.248 With table being kind of more of a B to B centric.
00:31:56.258 --> 00:32:00.310 When you're ordering a lot of things at once, and just as a
00:32:00.310 --> 00:32:04.428 side note, if you do zoom in here, it goes from five across.
00:32:04.808 --> 00:32:07.578 I guess Alaina and Amy.
00:32:07.628 --> 00:32:10.722 Are you all pretty up to speed and Mickey up to speed on kind
00:32:10.722 --> 00:32:12.668 of the responsiveness of the platform?
00:32:15.338 --> 00:32:18.808 So I'm not negative.
00:32:16.538 --> 00:32:16.778 No.
00:32:16.898 --> 00:32:17.398 Gotcha.
00:32:17.598 --> 00:32:23.905 Ow responsive just means that as we zoom in now you can see that
00:32:23.905 --> 00:32:29.144 it's A3 wide grid instead of A5 wide grid, so it will
00:32:26.568 --> 00:32:26.908 OK.
00:32:29.144 --> 00:32:34.868 dynamically change responsively to what screen size it is.
00:32:35.038 --> 00:32:39.333 So actually Shelton, if you press F-12 and go into dev tools
00:32:39.333 --> 00:32:43.698 and do you know how to change the thing to mobile responsive?
00:32:46.898 --> 00:32:50.427 So if you click uh up there by console at the very top, you see
00:32:47.278 --> 00:32:47.398 No.
00:32:50.427 --> 00:32:50.978 the thing.
00:32:50.988 --> 00:32:53.498 That's the little icon right next to elements on the left.
00:32:54.338 --> 00:32:55.908 Little computer tap.
00:32:55.918 --> 00:32:56.648 Yeah, that one.
00:32:56.978 --> 00:32:58.028 Yeah, that puts it in.
00:32:58.038 --> 00:33:01.715 So now you can go up to the top and say dimension responsive at
00:33:01.715 --> 00:33:05.220 the drop down at the very top and you can select which phone
00:33:05.220 --> 00:33:06.828 you want to view that UI in.
00:33:06.918 --> 00:33:09.448 So you could do like yeah, iPhone 12 pro.
00:33:09.658 --> 00:33:13.448 This is what the UI looks there and you can see that it changed.
00:33:13.818 --> 00:33:17.729 Now it's stacks everything you have your applied filters at the
00:33:17.729 --> 00:33:21.456 top with your quote, cart and shopping cart and then now you
00:33:21.456 --> 00:33:24.878 Scroll down and now you can see the products in like a.
00:33:25.098 --> 00:33:28.488 You know more of a mobile mobile view.
00:33:28.598 --> 00:33:33.234 If you were, you know, scrolling on your phone, so that's another
00:33:33.234 --> 00:33:34.428 thing to mention.
00:33:35.478 --> 00:33:38.165 If anybody's like, well, you know, most of my users are
00:33:38.165 --> 00:33:39.988 coming to this site from their phone.
00:33:40.058 --> 00:33:43.209 While we do have mobile responsiveness, it can
00:33:43.209 --> 00:33:47.164 dynamically change depending on what device they're using,
00:33:47.164 --> 00:33:51.455 whether it's a phone, a tablet, a desktop computer, whatever it
00:33:51.455 --> 00:33:52.058 might be.
00:33:56.328 --> 00:33:56.778 Yeah.
00:33:56.838 --> 00:33:57.288 There you go.
00:33:57.298 --> 00:33:57.998 IPad Air.
00:33:58.208 --> 00:34:00.578 Yeah, all kinds of stuff.
00:34:00.808 --> 00:34:04.128 But yeah, just a side tangent on responsiveness.
00:34:06.058 --> 00:34:06.448 Thank you.
00:34:06.458 --> 00:34:08.628 I wouldn't have known what that was referring to.
00:34:09.638 --> 00:34:09.858 Yeah.
00:34:12.398 --> 00:34:12.898 Awesome.
00:34:12.908 --> 00:34:13.608 Thank you, Carl.
00:34:14.178 --> 00:34:14.428 Umm.
00:34:16.088 --> 00:34:21.441 And then last, a couple things on the catalog, we have our
00:34:21.441 --> 00:34:22.348 number of.
00:34:23.688 --> 00:34:26.428 Products per page non 18 to 27.
00:34:27.728 --> 00:34:30.959 This just changed the number of products that we're gonna
00:34:30.959 --> 00:34:32.518 display at once on the page.
00:34:33.028 --> 00:34:37.185 Relatively straightforward, and then we have our sort by
00:34:37.185 --> 00:34:37.768 options.
00:34:38.158 --> 00:34:44.152 Umm that you can change from you know price ascending price
00:34:44.152 --> 00:34:50.645 descending well sales there are some product issue but just some
00:34:50.645 --> 00:34:55.639 different sort by options available in the Outbox
00:34:55.639 --> 00:34:56.538 platform.
00:34:56.808 --> 00:35:00.824 If they wanted to implement any other sort by logic or
00:35:00.824 --> 00:35:05.058 requirement, that would be a customization outside of the
00:35:05.058 --> 00:35:06.518 outer box offerings.
00:35:11.868 --> 00:35:12.538 All right.
00:35:12.808 --> 00:35:15.038 Any questions about the catalog?
00:35:22.408 --> 00:35:25.573 Uh, similar to the question I asked when we were on account
00:35:25.573 --> 00:35:28.949 registration, any red flags that we should watch out for when a
00:35:28.949 --> 00:35:32.166 customer is talking about things they might wanna see in the
00:35:32.166 --> 00:35:32.588 catalog?
00:35:34.008 --> 00:35:36.228 Stop now.
00:35:34.228 --> 00:35:36.618 Yeah, go ahead, car.
00:35:36.288 --> 00:35:41.048 It's gonna say starting at price, that's always something.
00:35:39.788 --> 00:35:40.028 OK.
00:35:41.058 --> 00:35:44.958 Well, there's two things starting at price because when
00:35:44.958 --> 00:35:49.275 you have variants associated with the product, like let's say
00:35:49.275 --> 00:35:53.523 that Apple iPhone there, if it just said Apple iPhone X, but
00:35:53.523 --> 00:35:57.979 you have 256 gigabyte, you have the 200 GB and you have the 500
00:35:57.979 --> 00:35:58.188 GB.
00:35:58.478 --> 00:35:59.578 Those are all different prices.
00:36:00.608 --> 00:36:05.089 So what we can display there in that product card if they want
00:36:05.089 --> 00:36:09.498 it to show the lowest price of like starting at this price we
00:36:09.498 --> 00:36:13.551 have to query a lot more products in order to ohh OK for
00:36:13.551 --> 00:36:17.249 this iPhone it has five different variations out of
00:36:17.249 --> 00:36:18.458 those variations.
00:36:18.468 --> 00:36:23.845 This one is the least expensive display that one, so doing that
00:36:23.845 --> 00:36:28.886 takes a lot more time than just displaying the price of the
00:36:28.886 --> 00:36:29.558 product.
00:36:29.648 --> 00:36:33.108 So that's a big one that can kind of have a performance hit.
00:36:33.118 --> 00:36:34.248 We can certainly do it.
00:36:34.258 --> 00:36:37.208 It's a customization, but definitely on the table.
00:36:37.218 --> 00:36:41.938 If they wanna do it that way dynamically, another thing is
00:36:40.328 --> 00:36:40.478 OK.
00:36:41.938 --> 00:36:43.058 the inventory.
00:36:43.298 --> 00:36:47.280 So you can see there on the auditing, humor and other
00:36:47.280 --> 00:36:48.828 oxymorons over there.
00:36:48.838 --> 00:36:53.412 The book on the right it says 11 in stock and they're like, well,
00:36:53.412 --> 00:36:57.500 I wanted display that it's in stock, but I don't wanna let
00:36:57.500 --> 00:36:59.578 them know that there's eleven.
00:37:00.638 --> 00:37:03.088 I don't want to let him know how many I have in my warehouse.
00:37:04.668 --> 00:37:08.174 It's a very common thing that a lot of people ask for, so
00:37:08.174 --> 00:37:11.498 there's a couple of different things to mention there.
00:37:11.748 --> 00:37:16.039 One is well, even if we don't display the number, we just
00:37:16.039 --> 00:37:19.738 display the flag of whether it's in stock or not.
00:37:20.128 --> 00:37:25.964 The UI in the front end tier has to know whether that product is
00:37:25.964 --> 00:37:31.621 in stock or not, and the data for that is technically provided
00:37:31.621 --> 00:37:32.518 to the UI.
00:37:32.668 --> 00:37:37.159 So if somebody was really smart, they could go into dev tools
00:37:37.159 --> 00:37:41.506 like Shelton just did earlier and basically inspect that UI
00:37:41.506 --> 00:37:45.779 element and they could go find the stock that that flag is
00:37:45.779 --> 00:37:50.488 displaying off of and they could technical or they could just go
00:37:50.488 --> 00:37:55.268 to the cart, add that product to the cart and then keep pressing.
00:37:55.278 --> 00:37:57.508 Plus plus, plus, plus or put in 100.
00:37:57.678 --> 00:38:00.901 Right now I'm going to put in 1000 at the point it says out of
00:38:00.901 --> 00:38:01.208 stock.
00:38:01.218 --> 00:38:05.240 Well, now I know how much you have, so there's a lot of
00:38:05.240 --> 00:38:09.764 different things that to really look out for there, because we
00:38:09.764 --> 00:38:14.144 can definitely obfuscate that information, like totally take
00:38:14.144 --> 00:38:18.669 it out of the network calls and just provide the on back order
00:38:18.669 --> 00:38:20.248 in stock out of stock.
00:38:20.648 --> 00:38:24.040 We could just provide those flags to the front end, but
00:38:24.040 --> 00:38:25.978 that's not how we have it built.
00:38:25.988 --> 00:38:29.940 We technically provide that information to the front end for
00:38:29.940 --> 00:38:34.021 both the count of the stock and the flag, so if they just want
00:38:34.021 --> 00:38:38.103 the flag, it's like, well, we still provide that data up there
00:38:38.103 --> 00:38:39.398 to display the flag.
00:38:39.468 --> 00:38:43.477 If somebody smart, they can get it, but there's, you know,
00:38:43.477 --> 00:38:47.417 you'll get kind of what I'm saying or mind, like, totally
00:38:47.417 --> 00:38:48.368 off base here.
00:38:50.368 --> 00:38:51.508 No, I'm following.
00:38:52.078 --> 00:38:52.858 Yeah, you're making sense.
00:38:54.228 --> 00:38:58.666 Yeah, and it it does cost a lot to completely take that out of
00:38:58.666 --> 00:39:02.681 the API call, like the stuff that the front end needs to
00:39:02.681 --> 00:39:03.948 display that data.
00:39:05.478 --> 00:39:09.568 If we take that out, it could we have to do that on the back end.
00:39:09.578 --> 00:39:12.408 Now we have to do it so we're completely different.
00:39:12.498 --> 00:39:16.541 So it does add a lot of cost if somebody just wants to display a
00:39:16.541 --> 00:39:20.273 flag instead of the actual inventory amount or just nothing
00:39:20.273 --> 00:39:20.708 at all.
00:39:21.228 --> 00:39:22.498 Nothing at all is always great.
00:39:22.678 --> 00:39:23.948 It's always so easy.
00:39:24.018 --> 00:39:26.068 It's like, oh, great, we'll just turn that off.
00:39:26.158 --> 00:39:29.768 Every ear a manufacturer you make all of your own products.
00:39:29.778 --> 00:39:30.218 Great.
00:39:30.358 --> 00:39:31.228 It's awesome.
00:39:31.468 --> 00:39:33.618 Like, that's the best case scenario?
00:39:34.888 --> 00:39:35.098 Umm.
00:39:36.228 --> 00:39:39.592 Or if they want to display everything, best case scenario,
00:39:39.592 --> 00:39:42.843 but if you have the middle ground, just always have that
00:39:42.843 --> 00:39:46.321 caveat there that it's kind of hard to do that we'll have to
00:39:46.321 --> 00:39:49.913 customize the network calls up to the front end so that nobody
00:39:49.913 --> 00:39:51.338 can get that information.
00:39:56.568 --> 00:39:58.508 OK, I'm done with my diatribe.
00:39:57.978 --> 00:39:58.388 No.
00:39:58.438 --> 00:39:59.158 Great.
00:39:58.558 --> 00:40:04.668 I apologize, it's just I've seen that blow up so many times.
00:39:59.458 --> 00:40:00.168 Thank you.
00:39:59.848 --> 00:40:00.368 Thank you.
00:40:00.288 --> 00:40:00.928 No, that's good.
00:40:00.878 --> 00:40:01.178 Thank.
00:40:01.188 --> 00:40:01.918 Good point.
00:40:09.558 --> 00:40:15.616 Another area that's kind of A cause for concern area is the
00:40:15.616 --> 00:40:21.674 any kind of role based display of catalog products based on
00:40:21.674 --> 00:40:24.198 user roles and then also.
00:40:27.508 --> 00:40:31.866 Price list account price list different pricing for different
00:40:31.866 --> 00:40:32.498 accounts.
00:40:33.188 --> 00:40:38.150 Those are kind of two areas that while we support price list
00:40:38.150 --> 00:40:43.519 tiered pricing with itself, it's an area that if it's coming from
00:40:43.519 --> 00:40:48.074 an ERP could cause some potential issues as well as the
00:40:48.074 --> 00:40:53.443 build out for role based viewing within the catalog that requires
00:40:53.443 --> 00:40:57.916 customizations and just additional time to ensure that
00:40:57.916 --> 00:41:02.878 the products for the certain roles are displaying correctly.
00:41:02.958 --> 00:41:07.814 So that's two more areas that could cause a little bit of a
00:41:07.814 --> 00:41:12.751 hiccup and require additional time if someone requests hello
00:41:12.751 --> 00:41:17.526 accounts for specific pricing and then uh account specific
00:41:17.526 --> 00:41:19.468 products based on roles.
00:41:20.008 --> 00:41:23.646 If you've had any kind of interaction with Nat, then you
00:41:23.646 --> 00:41:25.688 probably are familiar with that.
00:41:27.718 --> 00:41:32.679 One other thing, umm, it's kind of associated with this page and
00:41:32.679 --> 00:41:37.486 the product details page, but I'm gonna beat the dead horse of
00:41:37.486 --> 00:41:38.478 of inventory.
00:41:39.398 --> 00:41:43.758 Because if any of your clients ever bring up multi warehouse
00:41:43.758 --> 00:41:47.832 multi warehouse inventory, meaning I am fulfilling these
00:41:47.832 --> 00:41:52.049 products for from multiple locations throughout the US and
00:41:52.049 --> 00:41:56.695 throughout throughout the world, it's always good question and I
00:41:56.695 --> 00:42:01.341 I try to ask this right up front and they'll be like Oh yeah, we
00:42:01.341 --> 00:42:05.915 only use one warehouse which is a great answer, but if they use
00:42:05.915 --> 00:42:10.132 multiple you always have to think about OK, what the value
00:42:10.132 --> 00:42:11.418 do I display here?
00:42:11.428 --> 00:42:15.254 Do I display an aggregate of everything that you have across
00:42:15.254 --> 00:42:17.448 all of your warehouses everywhere?
00:42:17.458 --> 00:42:22.216 Or ohh this customers in the US, I'm only gonna display the stock
00:42:22.216 --> 00:42:26.326 for my US warehouse, and if that's out, say it's on back
00:42:26.326 --> 00:42:30.795 order and I have to ship that product into the US in order to
00:42:30.795 --> 00:42:31.588 fulfill it.
00:42:31.598 --> 00:42:32.998 So it's on back order right now.
00:42:33.498 --> 00:42:36.853 So it's always good to know whenever somebody brings up
00:42:36.853 --> 00:42:40.687 multi warehouse inventory to ask those questions of, OK, if you
00:42:40.687 --> 00:42:44.282 have multiple locations that you're storing things at, what
00:42:44.282 --> 00:42:46.318 do I display here in the catalog?
00:42:46.328 --> 00:42:48.058 What do you want your customers to see?
00:42:48.858 --> 00:42:51.508 Umm, same for the product details page.
00:42:51.518 --> 00:42:55.271 Do you want me to just display what's in their area, or do you
00:42:55.271 --> 00:42:58.844 want me to give them an option of ohh I wanna pick my store
00:42:58.844 --> 00:43:00.988 like lowes.com I can pick my store.
00:43:00.998 --> 00:43:05.794 I know exactly how much that store stocks at their location
00:43:05.794 --> 00:43:10.749 and their warehouse at their store, and I can just order from
00:43:10.749 --> 00:43:11.148 them.
00:43:11.628 --> 00:43:15.221 So it's always good to bring that up, especially with these
00:43:15.221 --> 00:43:16.358 ecommerce projects.
00:43:16.368 --> 00:43:19.745 Anytime somebody brings up multi warehouse or multilocation
00:43:19.745 --> 00:43:21.208 anytime that's brought up.
00:43:25.228 --> 00:43:26.158 Hopefully that made sense.
00:43:28.908 --> 00:43:29.038 Yes.
00:43:29.978 --> 00:43:30.268 Mm-hmm.
00:43:34.858 --> 00:43:37.108 All right, it's product details page.
00:43:37.808 --> 00:43:43.876 Uh, so as you can see, we have some of the same items from the
00:43:43.876 --> 00:43:48.498 product cars and the catalog that display here.
00:43:48.508 --> 00:43:53.446 We have pricing stock skew and then our quick description and
00:43:53.446 --> 00:43:58.224 in addition on the product details page, we have our little
00:43:58.224 --> 00:44:03.400 product law and description and then any product specifications,
00:44:03.400 --> 00:44:07.939 these tabs here, these are customizable and if a product
00:44:07.939 --> 00:44:12.478 has a other maybe a better product details page example.
00:44:12.488 --> 00:44:13.588 But if a product has.
00:44:13.188 --> 00:44:16.308 Go to the Acer Acer laptop.
00:44:16.718 --> 00:44:21.368 That's the one that has, like some of the HTML as markup.
00:44:21.538 --> 00:44:24.851 Like if you go over to the notes tab, it has like a really cool
00:44:24.851 --> 00:44:28.215 embedded YouTube video and like really cool stuff that you could
00:44:28.215 --> 00:44:29.198 do with those tabs.
00:44:31.108 --> 00:44:31.438 Yeah.
00:44:31.448 --> 00:44:35.118 So like I was saying, these tabs are customizable.
00:44:35.128 --> 00:44:39.553 So as you can see, we have our specifications tab which is just
00:44:39.553 --> 00:44:43.978 additional information about the product that gets its own tab.
00:44:44.048 --> 00:44:48.823 We can do the HTML embed for any videos or anything related to
00:44:48.823 --> 00:44:49.808 the products.
00:44:50.058 --> 00:44:50.568 Umm.
00:44:51.438 --> 00:44:55.416 So if a client is requesting additional information such as
00:44:55.416 --> 00:44:59.394 videos, or they have a lot of product information that they
00:44:59.394 --> 00:45:01.648 don't want to cram onto one page.
00:45:02.218 --> 00:45:06.809 Uh to where the user scrolls forever, we can add these
00:45:06.809 --> 00:45:11.733 additional tabs with that information, with it coming from
00:45:11.733 --> 00:45:12.818 the products.
00:45:13.028 --> 00:45:16.418 Uh, and then we have the reviews tab as well.
00:45:16.758 --> 00:45:20.541 When a customer release a review for the product, this is where
00:45:20.541 --> 00:45:22.668 those product reviews will be left.
00:45:22.928 --> 00:45:27.754 Side note, far product reviews when a review is left, it does
00:45:27.754 --> 00:45:32.658 have to be approved within CEF admin before it will display on
00:45:32.658 --> 00:45:33.358 the site.
00:45:33.748 --> 00:45:37.728 So people can't leave vulgar reviews, or, you know, any just
00:45:37.728 --> 00:45:41.838 spam bad reviews on a product because they don't like somebody
00:45:41.838 --> 00:45:43.338 for some reason at all.
00:45:43.348 --> 00:45:47.640 Products have to go through an approval process and the admin
00:45:47.640 --> 00:45:50.408 to display on the product details page.
00:45:55.238 --> 00:45:58.940 And then we have our actions that we got from hovering and
00:45:58.940 --> 00:46:03.082 the catalog had to favors add to wish list add to compare and add
00:46:03.082 --> 00:46:04.148 to shopping list.
00:46:04.578 --> 00:46:08.051 We'll get to these in a little bit and look at their
00:46:08.051 --> 00:46:08.968 functionality.
00:46:09.278 --> 00:46:13.683 Umm, but as you can see the product details page is
00:46:13.683 --> 00:46:17.919 essentially just more information compared to the
00:46:17.919 --> 00:46:22.663 product cards with some customization ability for these
00:46:22.663 --> 00:46:28.169 tabs here and any other product information that can't be placed
00:46:28.169 --> 00:46:31.218 on the product card in the catalog.
00:46:34.688 --> 00:46:37.678 All right, I'll just go ahead and add this.
00:46:37.728 --> 00:46:39.308 So we can look at these.
00:46:40.758 --> 00:46:44.967 So when you add something to the shopping list, if you don't have
00:46:44.967 --> 00:46:48.729 anything any shopping list already created, then it'll ask
00:46:48.729 --> 00:46:52.554 you to create a new shopping list, enter the name, and then
00:46:52.554 --> 00:46:53.638 we'll be able to.
00:47:15.168 --> 00:47:16.478 OK, there we go.
00:47:17.088 --> 00:47:19.922 But then once we create the shopping list, you'll get a drop
00:47:19.922 --> 00:47:20.618 down selection.
00:47:20.628 --> 00:47:24.614 If you have multiple shopping lists that'll allow the user to
00:47:24.614 --> 00:47:28.728 select, add the product to the list and then we have the option
00:47:28.728 --> 00:47:30.078 to create a new list.
00:47:30.088 --> 00:47:32.328 Uh, directly from this menu as well.
00:47:36.858 --> 00:47:41.422 Ohh Man, Shopping list is also something that's easily
00:47:41.422 --> 00:47:43.828 configurable for the project.
00:47:43.838 --> 00:47:47.732 If it's something that the client does not want, it is very
00:47:47.732 --> 00:47:51.560 easy to turn that off and it is part of our out of the box
00:47:51.560 --> 00:47:52.468 configuration.
00:47:52.478 --> 00:47:54.328 So that is not a customization.
00:47:55.058 --> 00:48:01.428 In order to remove shopping lists from the uh from the side,
00:48:01.428 --> 00:48:07.484 so the cart, we have our basic product information or the
00:48:07.484 --> 00:48:13.748 image, SKU, name, price and then the remove from CART icon.
00:48:13.938 --> 00:48:18.248 If a client wants to add any additional information to the.
00:48:19.898 --> 00:48:24.034 Cart line items that would be a customization to pull in those
00:48:24.034 --> 00:48:26.068 additional product information.
00:48:27.278 --> 00:48:31.728 Uh, and modify the UI to include more columns.
00:48:32.108 --> 00:48:34.108 UM down here in the bottom left.
00:48:34.158 --> 00:48:38.769 We have our quick add feature which allows for a user to
00:48:38.769 --> 00:48:43.866 search for products on the store front, quickly select one and
00:48:43.866 --> 00:48:48.720 then they will get the option to add multiple quantities if
00:48:48.720 --> 00:48:53.331 necessary and they'll see the product price and they can
00:48:53.331 --> 00:48:55.838 quickly add this to their cart.
00:49:00.568 --> 00:49:01.178 Uh.
00:49:01.568 --> 00:49:02.678 Quantity modifiers.
00:49:02.688 --> 00:49:03.918 Pretty standard.
00:49:04.148 --> 00:49:07.318 Change the quantity as you change the quantity.
00:49:07.688 --> 00:49:09.568 Your cart totals will update.
00:49:11.318 --> 00:49:11.768 Umm.
00:49:11.968 --> 00:49:16.366 Then as you can see here, if a product is on back order, uh,
00:49:16.366 --> 00:49:21.125 you'll get a notification to the user that their products on back
00:49:21.125 --> 00:49:25.018 order and then back order products is something that.
00:49:25.558 --> 00:49:30.335 Umm, some clients may or may not want, so it's always a good
00:49:30.335 --> 00:49:35.346 thing to ask to see if they do want to allow for back orderable
00:49:35.346 --> 00:49:36.598 products or not.
00:49:41.788 --> 00:49:46.308 But other than that, that is pretty much the full CART
00:49:46.308 --> 00:49:47.458 functionality.
00:49:47.548 --> 00:49:51.019 Uh basically just modifying quantities or removing line
00:49:51.019 --> 00:49:54.738 items and then we have the quick add to cart functionality.
00:49:57.028 --> 00:49:58.588 Anything that I missed call?
00:50:01.698 --> 00:50:05.498 The only thing I can think about is what to look for here.
00:50:07.538 --> 00:50:08.978 That would be around.
00:50:10.618 --> 00:50:13.738 These are these are of course customizations, but free
00:50:13.738 --> 00:50:14.248 shipping.
00:50:15.078 --> 00:50:19.004 Anytime somebody brings up free shipping, that happens in the
00:50:19.004 --> 00:50:22.929 cart because we have to know at what point does that customer
00:50:22.929 --> 00:50:24.068 get free shipping?
00:50:24.698 --> 00:50:30.071 Is it when they surpass a order volume of OI can now ship this
00:50:30.071 --> 00:50:33.908 for a lot less because it's a bulk shipment?
00:50:34.378 --> 00:50:38.691 Or is it when you get to a dollar amount, once you get to
00:50:38.691 --> 00:50:43.300 $100, it's free shipping and that all takes place in the cart
00:50:43.300 --> 00:50:47.984 here, which is able to total up the product dimensions if it's
00:50:47.984 --> 00:50:52.371 volume based or the product or product totals the subtotal
00:50:52.371 --> 00:50:54.378 which is the dollar amount.
00:50:54.388 --> 00:50:59.628 So we call those hardened soft stops, soft stop being.
00:51:00.718 --> 00:51:03.588 Hey, you don't have $100 in your cart yet.
00:51:04.538 --> 00:51:07.478 If you wanna go, proceed to check out.
00:51:07.488 --> 00:51:08.808 We have a $50.00 surcharge.
00:51:10.748 --> 00:51:15.236 Umm, that's a soft stop where you can accept a fee to move
00:51:15.236 --> 00:51:19.038 forward of, hey, we're gonna charge you shipping.
00:51:20.728 --> 00:51:24.210 But you know, if you get to this amount, you don't have to pay
00:51:24.210 --> 00:51:25.038 that soft stop.
00:51:25.528 --> 00:51:29.827 Hard stop is hey, you need to buy at least ten of these or you
00:51:29.827 --> 00:51:30.918 can't check out.
00:51:31.288 --> 00:51:32.638 Like, that's a hard stop.
00:51:32.648 --> 00:51:33.878 You cannot do that.
00:51:34.128 --> 00:51:36.678 So that's another thing that I always see.
00:51:36.688 --> 00:51:38.148 Here is a customization.
00:51:38.448 --> 00:51:42.396 Is the logic behind when you can technically go to checkout and
00:51:42.396 --> 00:51:44.308 that's all handled by the cart.
00:51:46.768 --> 00:51:47.638 What's the other thing?
00:51:51.288 --> 00:51:52.618 I think that was the other thing.
00:51:52.628 --> 00:51:55.538 It's not only free shipping, but it's also a minimum order.
00:51:55.548 --> 00:51:59.512 Quantities of like you have to buy these in packs of 12 or you
00:51:59.512 --> 00:52:03.476 have to buy these in cases or pallets or whatever it might be,
00:52:03.476 --> 00:52:07.503 or you have to, you know, get to a certain dollar amount before
00:52:07.503 --> 00:52:10.838 you check out all of that stuff handled by the cart.
00:52:10.848 --> 00:52:14.215 So if you ever hear anything like that, it's a customization,
00:52:14.215 --> 00:52:15.898 but something we definitely do.
00:52:15.948 --> 00:52:21.277 We've done it a lot typically controlled by an ERP so we
00:52:21.277 --> 00:52:25.858 usually sync. Those rules in to tell our system.
00:52:25.868 --> 00:52:31.581 When to let people check out or when to charge certain fees, but
00:52:31.581 --> 00:52:33.778 they can do that in here.
00:52:35.278 --> 00:52:37.848 And if anybody ever does wanna do that, just let him know.
00:52:37.858 --> 00:52:42.587 We can do an extensive training on that, but we use price points
00:52:42.587 --> 00:52:46.734 and things like that that control this cart depending on
00:52:46.734 --> 00:52:47.898 who's logged in.
00:52:47.958 --> 00:52:52.108 So lot a lot happens in the cart.
00:52:52.208 --> 00:52:53.498 The cart is very powerful.
00:52:53.908 --> 00:52:54.828 The power of the cart.
00:52:58.408 --> 00:52:59.788 Is anybody here on Everest Stone?
00:53:01.148 --> 00:53:02.388 No, I am.
00:53:01.768 --> 00:53:01.988 Yes.
00:53:03.308 --> 00:53:09.878 So Everest Stone has trailer orders and container orders.
00:53:09.888 --> 00:53:13.038 Containers come from factories overseas.
00:53:13.098 --> 00:53:14.948 It's literally in a shipping container.
00:53:16.058 --> 00:53:19.771 Factory orders come from in the states, and they're literally on
00:53:19.771 --> 00:53:20.228 a truck.
00:53:20.438 --> 00:53:24.111 It's literally a flatbed trailer, so each one of those
00:53:24.111 --> 00:53:26.248 carts have different capacities.
00:53:26.308 --> 00:53:29.677 I can fit this much on a flatbed, but I can fit this much
00:53:29.677 --> 00:53:30.548 in a container.
00:53:30.898 --> 00:53:35.027 So you have in order to calculate shipping we have to
00:53:35.027 --> 00:53:39.844 total up the amount of weight and volume in that cart for that
00:53:39.844 --> 00:53:44.509 specific shipment from that factory to say OK, you have this
00:53:44.509 --> 00:53:49.326 much volume in your container from that factory you've ordered
00:53:49.326 --> 00:53:50.778 this many products.
00:53:50.788 --> 00:53:53.688 This is how full your container is.
00:53:54.188 --> 00:53:57.201 Same logic for the trailer because it has a different
00:53:57.201 --> 00:53:57.758 threshold.
00:53:57.768 --> 00:54:02.714 It has a different capacity, so that's where a lot is built into
00:54:02.714 --> 00:54:07.660 the cart where we can have logic depending on where that product
00:54:07.660 --> 00:54:12.225 is coming from and what the, I guess threshold of volume or
00:54:12.225 --> 00:54:17.019 weight that you know they can fees and this is on of course it
00:54:17.019 --> 00:54:21.736 B to B scale of very large scale of how much I can reasonably
00:54:21.736 --> 00:54:23.638 ship to you in one order.
00:54:24.548 --> 00:54:25.108 Umm.
00:54:25.938 --> 00:54:29.651 If that all makes sense, any questions I guess on that I kind
00:54:29.651 --> 00:54:30.728 of bounced around.
00:54:33.168 --> 00:54:37.765 Umm, they seemed like a really interesting like summer, which
00:54:35.468 --> 00:54:35.628 No.
00:54:37.765 --> 00:54:42.288 is what they're selling and how they're selling it different
00:54:41.098 --> 00:54:41.608 Exactly.
00:54:42.288 --> 00:54:42.658 than.
00:54:42.668 --> 00:54:46.840 I mean, I know have been on a lot of projects here, but it's
00:54:46.840 --> 00:54:51.217 very different just cause things change with them like you said
00:54:51.217 --> 00:54:52.858 like wait the price and.
00:54:52.498 --> 00:54:55.758 And there there's no integration with them. Right, Kyle?
00:54:53.498 --> 00:54:54.468 And where it's coming from.
00:54:54.998 --> 00:54:55.238 Yeah.
00:54:56.248 --> 00:54:58.658 Yeah, there's no integration, right?
00:54:56.528 --> 00:54:56.888 What's that?
00:54:57.208 --> 00:54:58.078 Correct. Yeah.
00:54:59.088 --> 00:55:00.018 That is right.
00:55:00.028 --> 00:55:03.792 We are actually building a custom shipping provider
00:55:03.792 --> 00:55:07.918 specifically for Everest stone to do those calculations.
00:55:07.928 --> 00:55:13.056 It's based on the total amount of products in the CART times
00:55:13.056 --> 00:55:15.998 like a percentage uplift, I think.
00:55:16.168 --> 00:55:20.827 And we're building that shipping into the platform instead of us
00:55:20.827 --> 00:55:25.485 just integrating with like FedEx International or something like
00:55:25.485 --> 00:55:29.570 that because they have a basically I will call it a flat
00:55:29.570 --> 00:55:29.928 rate.
00:55:29.938 --> 00:55:33.108 They have their own calculated rate for shipping for each one
00:55:33.108 --> 00:55:35.408 of their factories that they get stuff from.
00:55:35.738 --> 00:55:40.989 So we're building that custom for them, which is cool, but
00:55:40.989 --> 00:55:42.858 also kind of complex.
00:55:42.868 --> 00:55:44.828 There's a lot of, you know, testing there.
00:55:45.738 --> 00:55:48.480 When we build something custom because then we have to our item
00:55:48.480 --> 00:55:48.908 to log in.
00:55:48.918 --> 00:55:52.765 Is this fabricator this factory and, you know, put in all their
00:55:52.765 --> 00:55:54.448 metrics and stuff like that?
00:55:55.938 --> 00:56:01.088 Umm, but yeah, every stone going to be a fun project.
00:56:02.088 --> 00:56:04.418 Out very, very cool project.
00:56:07.178 --> 00:56:08.788 But they OK?
00:56:08.798 --> 00:56:10.248 Never mind, I'm getting off topic.
00:56:10.418 --> 00:56:12.208 We'll talk about that later, uh.
00:56:14.588 --> 00:56:19.158 Alright, so check out, so check out.
00:56:19.168 --> 00:56:24.974 Has a lot of different steps and a lot of client customizations
00:56:24.974 --> 00:56:30.417 come into play within checkout with our shipping and around
00:56:30.417 --> 00:56:35.860 some other areas of modifying ship to locations and billing
00:56:35.860 --> 00:56:36.948 information.
00:56:37.088 --> 00:56:39.885 Kind of how it was discussing earlier with account
00:56:39.885 --> 00:56:40.598 registration.
00:56:40.948 --> 00:56:45.922 So one of the first, umm, areas, that's kind of variable client
00:56:45.922 --> 00:56:50.586 to client is gonna be split shipments which is allowing the
00:56:50.586 --> 00:56:55.638 shipping of multiple line items in a cart to different locations
00:56:55.638 --> 00:56:59.990 or if all products within an order must be shipped to a
00:56:59.990 --> 00:57:02.088 singular singular location.
00:57:02.598 --> 00:57:07.175 So out of box it is the split shipment that allows for you to
00:57:07.175 --> 00:57:11.308 ship products to different addresses in a single order.
00:57:11.878 --> 00:57:17.495 We can modify the checkout to allow for single shipment to a
00:57:17.495 --> 00:57:18.968 single location.
00:57:19.318 --> 00:57:23.745 It's not a huge lift, but since it is not out of the box, it
00:57:23.745 --> 00:57:26.938 does require a little bit of configuration.
00:57:27.538 --> 00:57:32.082 I believe it's an app setting call and correct me if I'm wrong
00:57:32.082 --> 00:57:36.770 that we can turn that on, on and off while app settings are very
00:57:32.748 --> 00:57:33.408 That is correct.
00:57:36.770 --> 00:57:41.385 easy to change, there are still is a little bit of testing that
00:57:41.385 --> 00:57:45.568 needs to go in to ensure everything is working correctly.
00:57:48.168 --> 00:57:52.577 The next part of check out that is a big customization area for
00:57:52.577 --> 00:57:56.503 clients is gonna be there shipping provider and shipping
00:57:56.503 --> 00:57:58.018 provider integrations.
00:57:58.828 --> 00:58:00.918 So we'll go with Nat.
00:58:00.928 --> 00:58:05.048 For example, we have a lot of different shipping scenarios for
00:58:05.048 --> 00:58:05.898 that project.
00:58:05.908 --> 00:58:09.138 We have a FedEx integration.
00:58:09.628 --> 00:58:13.758 We have free shipping based on a dollar amount threshold.
00:58:14.048 --> 00:58:18.301 We have some products that are missing weight and dimensions
00:58:18.301 --> 00:58:21.995 that require us to bypass shipping rate calculations
00:58:21.995 --> 00:58:26.456 because we cannot accurately get those rates from FedEx because
00:58:26.456 --> 00:58:30.778 we don't have any weight and dimensions to pass to their API.
00:58:30.868 --> 00:58:36.545 And then we also have bulky products which bypass any kind
00:58:36.545 --> 00:58:42.318 of shipping rate calculation and go directly to the payment
00:58:42.318 --> 00:58:43.568 methods step.
00:58:43.578 --> 00:58:47.958 So some clients will require just as an integration with a
00:58:47.958 --> 00:58:52.486 third party shipping provider such as FedEx or UPS, where we
00:58:52.486 --> 00:58:57.236 would make a call to their API pass in the product information,
00:58:57.236 --> 00:59:01.838 weight and dimensions to the API, and would return a shipping
00:59:01.838 --> 00:59:06.218 rate based on the weight and dimensions of the products in
00:59:06.218 --> 00:59:10.226 the order as well as the shipping address of the user
00:59:10.226 --> 00:59:12.898 with product weight and dimensions.
00:59:12.958 --> 00:59:17.099 One of the most important things to confirm with the client is
00:59:17.099 --> 00:59:20.780 that they do have values present, weight and dimensions
00:59:20.780 --> 00:59:22.488 for all of their products.
00:59:22.498 --> 00:59:27.258 If they are expecting to do an integration with the third party
00:59:27.258 --> 00:59:31.497 provider such as FedEx or UPS, if they do not have these
00:59:31.497 --> 00:59:36.108 values, it is very encouraged for them to get them for all of
00:59:36.108 --> 00:59:40.198 their products and have that information ready for us.
00:59:40.208 --> 00:59:45.464 Or if that is something that they absolutely cannot do, there
00:59:45.464 --> 00:59:50.042 are several options, such as within a T we can bypass
00:59:50.042 --> 00:59:55.043 shipping rates altogether, or we can implement a flat rate
00:59:55.043 --> 01:00:00.045 shipping provider logic to check out and flat rate is just
01:00:00.045 --> 01:00:00.638 simply.
01:00:03.108 --> 01:00:07.642 You know, if you're ordering something, it's $50.00 to ship
01:00:07.642 --> 01:00:07.868 it.
01:00:08.248 --> 01:00:12.482 So a flat light flat rate provider is kind of an easy way
01:00:12.482 --> 01:00:16.788 to get around any uh shipping customizations that can't be
01:00:16.788 --> 01:00:21.241 accomplished without a large lift of customizations or a lot
01:00:21.241 --> 01:00:25.328 of effort on the client side to ensure all the data is.
01:00:27.918 --> 01:00:30.868 Available for waiting to mentions with their products.
01:00:30.878 --> 01:00:36.573 UM, another thing with shipping that is important is to confirm
01:00:36.573 --> 01:00:41.646 which shipping third party shipping provider we would be
01:00:41.646 --> 01:00:44.048 using for our calculations.
01:00:44.178 --> 01:00:49.063 We work with FedEx and UPS a lot and those integrations are
01:00:49.063 --> 01:00:52.808 fairly simple and can be done fairly quickly.
01:00:52.998 --> 01:00:56.208 We just need the credentials from the client.
01:00:56.418 --> 01:01:01.018 If they're using some third party shipping provider that we
01:01:01.018 --> 01:01:05.772 don't regularly work with, that would require additional time
01:01:05.772 --> 01:01:10.448 and then there are some cases where a shipping provider that
01:01:10.448 --> 01:01:15.355 they would like to use may not even have an API endpoint for us
01:01:15.355 --> 01:01:16.658 to interact with.
01:01:17.228 --> 01:01:21.603 So it's very important to confirm with the devs as well as
01:01:21.603 --> 01:01:22.418 the client.
01:01:22.548 --> 01:01:22.868 What?
01:01:23.158 --> 01:01:23.598 Umm.
01:01:24.218 --> 01:01:26.178 Shipping, integration or shipping provider.
01:01:26.188 --> 01:01:30.229 We're gonna be integrating with for the project and make sure
01:01:30.229 --> 01:01:34.400 that if it is something that's gonna be more complex than FedEx
01:01:34.400 --> 01:01:38.310 or UPS or something that we're used to working with that we
01:01:38.310 --> 01:01:42.351 relate to them, that that could be an area where we could see
01:01:42.351 --> 01:01:43.328 some increases.
01:01:43.748 --> 01:01:48.021 And I believe, Kyle, you pretty much get that from them off the
01:01:48.021 --> 01:01:48.888 at the start.
01:01:48.898 --> 01:01:51.388 So that's information we typically.
01:01:50.768 --> 01:01:51.818 I usually need.
01:01:52.668 --> 01:01:56.014 Yeah, I usually try to, but sometimes they're like, well, we
01:01:56.014 --> 01:01:58.318 don't know exactly what we wanna use yet.
01:01:58.328 --> 01:02:02.615 We might go with this one over the other one and it it can
01:02:02.615 --> 01:02:02.978 vary.
01:02:02.988 --> 01:02:06.340 Sometimes I try to get that information and it should be in
01:02:06.340 --> 01:02:09.188 the handoff information that I give to you all so.
01:02:10.898 --> 01:02:13.997 Yeah, I would say 80 to 90% of the time, you should know
01:02:13.997 --> 01:02:17.367 exactly who they're gonna wanna integrate with, but there are
01:02:17.367 --> 01:02:18.128 some outliers.
01:02:22.378 --> 01:02:22.808 Thank you.
01:02:22.818 --> 01:02:23.308 Perfect.
01:02:23.318 --> 01:02:27.390 Uh, and then another area and called correct me if this is
01:02:27.390 --> 01:02:31.738 something we shouldn't do with shipping provider integrations.
01:02:32.008 --> 01:02:37.371 Umm, sometimes clients may be working with a platform that is
01:02:37.371 --> 01:02:42.214 not ideal for what they're trying to accomplish for the
01:02:42.214 --> 01:02:46.798 project, and it may be easier to steer them towards.
01:02:47.188 --> 01:02:51.785 You know FedEx, UPS or some other shipping provider that we
01:02:51.785 --> 01:02:56.304 work with regularly that can accomplish what they need and
01:02:56.304 --> 01:02:59.368 kind of move them away from a platform.
01:02:59.378 --> 01:03:01.898 That's not gonna work well with self and is gonna.
01:03:03.918 --> 01:03:06.128 Cause complications for the project.
01:03:06.338 --> 01:03:11.150 Sometimes a different route and offering that optional platform
01:03:11.150 --> 01:03:15.134 to work with for shipping is something that could be
01:03:15.134 --> 01:03:17.088 beneficial to the project.
01:03:17.098 --> 01:03:21.711 So if there's some off the wall, umm shipping for rider, you
01:03:21.711 --> 01:03:26.021 know, gauging their interest on moving away from that as
01:03:26.021 --> 01:03:30.028 something that could save some time for the project.
01:03:30.508 --> 01:03:35.448 Uh, but that's just got about two cents with that.
01:03:35.458 --> 01:03:37.658 But anyways.
01:03:38.108 --> 01:03:38.508 All right.
01:03:39.078 --> 01:03:39.698 Uh.
01:03:40.108 --> 01:03:44.411 So with our shipping selection address selection stuff you can
01:03:44.411 --> 01:03:48.577 see we have our drop down where we can select the address we
01:03:48.577 --> 01:03:52.743 would like to ship the product to the names bill to and ship
01:03:52.743 --> 01:03:52.948 to.
01:03:52.958 --> 01:03:58.077 That is what I have my addresses saved as in my address book and
01:03:58.077 --> 01:04:03.116 this will always default to my default shipping address which I
01:04:03.116 --> 01:04:05.478 set up within my address book.
01:04:05.548 --> 01:04:10.522 So you make your selection for the addresses that you want to
01:04:10.522 --> 01:04:15.657 ship your product to, and then once you do that, you'll do your
01:04:15.657 --> 01:04:20.791 submit right and get quotes this out of the box example here is
01:04:20.791 --> 01:04:25.043 gonna be just with a UPS integration calling ups and
01:04:25.043 --> 01:04:26.968 getting the return rate.
01:04:27.018 --> 01:04:30.807 Uh, so we're assuming that we have all of our product weight
01:04:30.807 --> 01:04:34.721 and dimensions and that we are just simply calling that API to
01:04:34.721 --> 01:04:35.528 return rates.
01:04:35.538 --> 01:04:40.542 We don't have any kind of special or customized shipping
01:04:40.542 --> 01:04:43.878 right provider for this example here.
01:04:44.288 --> 01:04:48.410 So you can say I get my return values, I get my different
01:04:48.410 --> 01:04:48.978 options.
01:04:49.528 --> 01:04:55.682 One thing that we can do with the return rates from a provider
01:04:55.682 --> 01:04:57.538 is hide or display.
01:04:58.088 --> 01:05:01.398 Umm, the shipping rate options.
01:05:01.808 --> 01:05:06.036 It is a customization, but it is something that we can pretty
01:05:06.036 --> 01:05:06.718 easily do.
01:05:07.348 --> 01:05:12.203 So if someone only wanted to have the option of UPS ground or
01:05:12.203 --> 01:05:17.214 second day error, we could hide the other options returned from
01:05:17.214 --> 01:05:18.858 UPS on the front end.
01:05:19.008 --> 01:05:22.919 UM, we still would get those results back and we call the
01:05:22.919 --> 01:05:26.965 API, but we would just simply hide the results in the front
01:05:26.965 --> 01:05:28.178 end from the user.
01:05:28.388 --> 01:05:30.738 So that's something that's pretty easily done.
01:05:30.748 --> 01:05:34.928 It is a small customization, but something we definitely can do
01:05:34.928 --> 01:05:38.977 if that is a requirement, so we'll make our selection for the
01:05:38.977 --> 01:05:39.368 rates.
01:05:42.838 --> 01:05:47.008 And then once we do that, we'll be able to continue to payment.
01:05:47.078 --> 01:05:53.006 You can see I have my shipping total here and then my grand
01:05:53.006 --> 01:05:58.835 total here and then it also updates in the pricing section
01:05:58.835 --> 01:06:02.688 at the top of the page discount codes.
01:06:04.098 --> 01:06:08.161 Uh, do you know if we have any set up for this call that you
01:06:08.161 --> 01:06:10.158 know off the top of your head?
01:06:10.458 --> 01:06:14.928 My out of the box discount codes OK.
01:06:13.288 --> 01:06:16.428 No, just if any have been set up on develop.
01:06:17.518 --> 01:06:18.908 Ohh I have no idea.
01:06:18.918 --> 01:06:22.118 I used to know when when Christian did all the QA, but I
01:06:18.928 --> 01:06:19.208 Yeah.
01:06:22.118 --> 01:06:22.848 have no idea.
01:06:24.228 --> 01:06:24.738 Gotcha.
01:06:24.748 --> 01:06:27.968 OK, so discounts are something we have out of the box.
01:06:29.548 --> 01:06:34.082 So that's done within Sev Admin you can set up categories,
01:06:34.082 --> 01:06:38.154 specific discounts, product specific discounts, user
01:06:38.154 --> 01:06:42.688 specific discounts, account specific discounts you can set
01:06:42.688 --> 01:06:42.918 up.
01:06:44.528 --> 01:06:47.748 You spend X get Y discount.
01:06:47.818 --> 01:06:51.912 You can set up a percentage off discount or you can set up a
01:06:51.912 --> 01:06:55.938 dollar amount off of a product discount, so there's several
01:06:55.938 --> 01:06:59.696 different ways that you can handle discounts within CEF
01:06:59.696 --> 01:07:00.098 admin.
01:07:00.298 --> 01:07:04.039 Discounts are out of the box, so that is something that if a
01:07:04.039 --> 01:07:06.308 client asks can we set up discounts?
01:07:06.318 --> 01:07:10.888 Yes, you can get pretty creative with the discounts that you can
01:07:10.888 --> 01:07:15.176 set up within self admin, but essentially you would create a
01:07:15.176 --> 01:07:19.534 coupon discount code and stuff admin, type it in and apply it
01:07:19.534 --> 01:07:20.518 to your order.
01:07:21.778 --> 01:07:26.606 We also at discounts you can limit the number of uses per
01:07:26.606 --> 01:07:30.768 count globally or you can make it a one time use.
01:07:30.838 --> 01:07:35.178 You can also set a priority level on your discounts, so
01:07:35.178 --> 01:07:40.137 depending on the discount that you use or if you enter multiple
01:07:40.137 --> 01:07:45.019 discounts based on the priority level, a discount may override
01:07:45.019 --> 01:07:49.048 another discount if it has a higher priority level.
01:07:49.798 --> 01:07:51.768 Uh, sorry.
01:07:51.618 --> 01:07:54.058 Do we have the ability to add multiple discounts?
01:07:55.438 --> 01:07:57.518 Yes, you can add multiple discounts.
01:08:02.938 --> 01:08:06.916 And counter question, do we have a way to say you can only do
01:08:06.916 --> 01:08:08.968 one, that they're not stackable?
01:08:10.868 --> 01:08:11.458 Yes.
01:08:11.518 --> 01:08:16.168 Uh, you can limit the number of users per cart for a discount.
01:08:17.838 --> 01:08:22.188 And you can also set them as exclusive or combinable.
01:08:22.198 --> 01:08:26.580 So exclusive meaning if if that discount is in the cart it's the
01:08:22.948 --> 01:08:23.228 OK.
01:08:26.580 --> 01:08:31.030 only discount that can be in the cart, or if it's combinable, you
01:08:31.030 --> 01:08:33.928 can have it, you know, on multiple things.
01:08:34.528 --> 01:08:41.200 And a good note about the priorities is it will only
01:08:41.200 --> 01:08:42.458 relate to.
01:08:43.838 --> 01:08:45.668 Exclusive discounts.
01:08:45.678 --> 01:08:49.730 I'm pretty sure because if they're combinable, why would
01:08:49.730 --> 01:08:51.578 you care about a priority?
01:08:51.588 --> 01:08:55.460 They're all applying to the cart, you know, but if they're
01:08:55.460 --> 01:08:57.888 exclusive, well, then I have to say.
01:08:57.898 --> 01:09:01.689 Ohh well, that exclusive one is a better deal than this other
01:09:01.689 --> 01:09:05.540 exclusive one that one needs to go first or whatever the logic
01:09:02.568 --> 01:09:02.818 Mm-hmm.
01:09:05.540 --> 01:09:08.658 is there, or if it's just off the priority number.
01:09:08.668 --> 01:09:13.807 But yeah, uh, the priority usually only applies to
01:09:13.807 --> 01:09:18.038 exclusive discounts, if that makes sense.
01:09:18.768 --> 01:09:23.275 Umm does is there anything that a customer could ask for to do
01:09:23.275 --> 01:09:26.208 with discounts that would be a red flag?
01:09:29.538 --> 01:09:32.898 Ah, let's see.
01:09:32.568 --> 01:09:38.053 I usually admire rule of thumb I if if you've ever pulled up the
01:09:38.053 --> 01:09:43.032 discount editor, there is a bunch of associations that you
01:09:43.032 --> 01:09:48.349 can put on that discount which is users, user types, accounts,
01:09:48.349 --> 01:09:51.808 account types, categories, products XYZ.
01:09:51.848 --> 01:09:55.028 There, I think there's 12 to 15 of them.
01:09:55.718 --> 01:10:01.285 I say if you use any more than three of those, let's say it's
01:10:01.285 --> 01:10:06.942 for this category of items, but only for this account type and
01:10:06.942 --> 01:10:12.419 only for you know if if they go 3 levels deep, that's at the
01:10:12.419 --> 01:10:17.897 point where I'm like, we're probably gonna have to test that
01:10:17.897 --> 01:10:23.823 a little bit because even though our system can do it, you're now
01:10:20.578 --> 01:10:20.888 Umm.
01:10:23.823 --> 01:10:28.761 getting into a minutia of different rules that have to
01:10:28.761 --> 01:10:34.238 apply to getting that discount actually applied to an order.
01:10:34.248 --> 01:10:39.255 So that's usually my rule of thumb is if they bring up
01:10:39.255 --> 01:10:44.716 anymore than three or more stipulations on how the discount
01:10:44.716 --> 01:10:50.268 is applied, it's going to take more testing than than usual.
01:10:49.508 --> 01:10:49.768 OK.
01:10:51.208 --> 01:10:55.503 So that would be something long lines of saying like only these
01:10:55.503 --> 01:10:59.663 type of customers can use this coupon on this certain project
01:10:59.663 --> 01:11:01.608 product within this category.
01:11:03.478 --> 01:11:03.828 Yeah.
01:11:03.838 --> 01:11:07.593 If it's any more than that, I would say we need some some
01:11:07.593 --> 01:11:08.758 stringent testing.
01:11:09.568 --> 01:11:09.848 Anger.
01:11:11.168 --> 01:11:15.328 And question making this for the task of discounts.
01:11:15.338 --> 01:11:19.518 Did we ever get those working without a box discounts?
01:11:18.318 --> 01:11:20.098 He did? Mm-hmm.
01:11:19.528 --> 01:11:23.697 We did like a cool that was gonna be an example if we
01:11:23.697 --> 01:11:27.788 weren't able to get those those working but perfect.
01:11:29.018 --> 01:11:29.748 Alright.
01:11:30.658 --> 01:11:32.478 Any more discount questions?
01:11:34.218 --> 01:11:34.768 For me.
01:11:37.408 --> 01:11:41.747 Alright, so once you select your rights, you'll be able to
01:11:41.747 --> 01:11:46.233 continue to payment, so the payment step we have our bill to
01:11:46.233 --> 01:11:50.425 information, we can add a new address here if we need to
01:11:50.425 --> 01:11:54.544 change our billing information and then we have several
01:11:54.544 --> 01:11:58.588 different payment options that are offered out of box.
01:11:58.598 --> 01:12:03.648 We have ACH, we have credit card, we have invoice and we
01:12:03.648 --> 01:12:04.888 have quote me.
01:12:05.378 --> 01:12:10.394 So ACH, you're required to add that payment information into
01:12:10.394 --> 01:12:13.518 your wallet before you can select it.
01:12:13.958 --> 01:12:15.838 Same with the credit card.
01:12:15.848 --> 01:12:22.047 If I have no card in my wallet, I'll need to add 1 before I can
01:12:22.047 --> 01:12:24.758 make my purchase and voices.
01:12:25.208 --> 01:12:29.925 You'll need a PO number out of box in order to submit your
01:12:29.925 --> 01:12:34.642 order as an invoice, and then the quote Me option converts
01:12:34.642 --> 01:12:39.358 your order to a quote and submits the quote to the system.
01:12:41.158 --> 01:12:43.798 I'm trying to think of anything else. It's.
01:12:46.638 --> 01:12:49.838 Ohh, some clients don't require ACH.
01:12:52.328 --> 01:12:56.146 And then some clients have some different scenarios for
01:12:56.146 --> 01:13:00.372 different users that were would require customizations to the
01:13:00.372 --> 01:13:04.530 payment based on the account type or any flags associated to
01:13:04.530 --> 01:13:05.348 the account.
01:13:07.038 --> 01:13:11.233 For example, customers that are on terms versus customers that
01:13:11.233 --> 01:13:15.495 are not on terms uh, customers on terms would see the option to
01:13:15.495 --> 01:13:19.623 pay via invoice customers, not on terms would have the option
01:13:19.623 --> 01:13:23.951 or would not have the option to pay via via invoice and would be
01:13:23.951 --> 01:13:26.348 restricted to a credit card or ACH.
01:13:26.358 --> 01:13:30.364 If that's a payment option, those scenarios are
01:13:30.364 --> 01:13:35.705 customizations for the project where we would need to implement
01:13:35.705 --> 01:13:40.713 the roles are have the flags existing on the account, so we
01:13:40.713 --> 01:13:45.803 can check that flag or role and then determine which payment
01:13:45.803 --> 01:13:49.308 methods are available to the to the user.
01:13:51.258 --> 01:13:52.888 And let me I guess I don't.
01:13:52.938 --> 01:13:54.638 Let me put a card in real quick.
01:13:56.788 --> 01:14:01.786 And one other thing on that Shelton, it also can be further
01:14:01.786 --> 01:14:04.368 dictated by their credit limit.
01:14:04.998 --> 01:14:08.238 I see a lot of customers are like, well, we have a, you know,
01:14:08.238 --> 01:14:11.635 they're on invoice, their terms customer, but they have a credit
01:14:11.635 --> 01:14:11.948 limit.
01:14:11.958 --> 01:14:16.660 They can't put in an unlimited amount of orders per month, so
01:14:16.660 --> 01:14:20.754 they'll have us sync over a limit from the ERP and if
01:14:20.754 --> 01:14:25.228 they're over that limit or if the order total of whatever.
01:14:25.238 --> 01:14:29.264 They have in the cart right now surpasses what their credit
01:14:29.264 --> 01:14:29.868 limit is.
01:14:29.878 --> 01:14:34.842 We have to turn off the invoice payment method like ohh you can
01:14:34.842 --> 01:14:39.572 only do that if your orders you know gonna push you to under
01:14:39.572 --> 01:14:40.968 your credit limit.
01:14:41.138 --> 01:14:45.228 So that's another customization I sometimes see here.
01:14:45.238 --> 01:14:49.460 That's, you know, if anybody brings up credit limits, I would
01:14:49.460 --> 01:14:52.728 definitely poke at the payment methods as well.
01:14:54.588 --> 01:14:58.848 Yeah, in a recent project that's doing that is Rockingham, they
01:14:58.848 --> 01:15:00.778 have different account types.
01:15:01.388 --> 01:15:06.345 One account type does have a credit limit, so like call said,
01:15:06.345 --> 01:15:11.540 when we sync over their current available credit will need to do
01:15:11.540 --> 01:15:16.577 logic at the time of check out to determine if there are ready
01:15:16.577 --> 01:15:21.453 over their credit limit or if this order would put them past
01:15:21.453 --> 01:15:26.489 their credit limit and restrict them from placing an order via
01:15:26.489 --> 01:15:27.128 invoice.
01:15:28.498 --> 01:15:29.008 Ideas.
01:15:29.018 --> 01:15:29.788 Thank you, Carl.
01:15:29.838 --> 01:15:30.828 Good point.
01:15:31.658 --> 01:15:36.287 So once you select your payment method, uh, you can enter your
01:15:36.287 --> 01:15:40.474 CVCV is required every time a customer checks out with a
01:15:40.474 --> 01:15:44.588 credit card, and then we'll be able to place our order.
01:15:54.548 --> 01:15:58.802 And then we get a confirmation message and we see our Master
01:15:58.802 --> 01:15:59.708 order number.
01:15:59.718 --> 01:16:03.353 And then our sub order numbers with the option to continue
01:16:03.353 --> 01:16:07.048 shopping are view our order history and the user dashboard.
01:16:07.108 --> 01:16:12.083 So if we go to the user dashboard, you'll see our two
01:16:12.083 --> 01:16:14.478 suborders displaying here.
01:16:19.108 --> 01:16:24.919 One for my laptop and then if we go back 748 is going to be my
01:16:24.919 --> 01:16:30.268 iPhones and then you can see from the order details page.
01:16:30.278 --> 01:16:34.209 Here we can quickly navigate to the two line items from our
01:16:34.209 --> 01:16:38.205 order and then also view the master order which contains all
01:16:38.205 --> 01:16:39.908 line items from the order.
01:16:42.118 --> 01:16:46.609 Alternatively, you can see any quotes or invoices associated
01:16:46.609 --> 01:16:49.848 with the order whenever an order is placed.
01:16:49.858 --> 01:16:52.988 We do generate an invoice even if it has been paid for.
01:16:52.998 --> 01:16:57.050 As you can see, this invoice has the status of paid because the
01:16:57.050 --> 01:17:00.596 customer paid with a credit card, but we stood still do
01:17:00.596 --> 01:17:03.318 generate that invoice on order completion.
01:17:06.288 --> 01:17:09.038 A quick call out about invoices.
01:17:09.508 --> 01:17:13.842 It's very important to determine where invoices are gonna be
01:17:13.842 --> 01:17:18.389 generated, whether we're gonna be generating those invoices and
01:17:18.389 --> 01:17:22.935 Seth and syncing invoices to an ERP or if they're gonna only be
01:17:22.935 --> 01:17:27.411 generating the invoices within the ERP and then we're gonna be
01:17:27.411 --> 01:17:29.968 pulling in those invoices into SEF.
01:17:31.188 --> 01:17:35.133 So either we're gonna generate them and receive any updates
01:17:35.133 --> 01:17:39.406 from the ERP to the invoice, or we're going to only retrieve the
01:17:39.406 --> 01:17:43.218 invoice from the ERP and not generate them within itself.
01:17:43.498 --> 01:17:47.554 And also another important question around invoices is if
01:17:47.554 --> 01:17:51.330 invoices are planning to be modified in any way after
01:17:51.330 --> 01:17:52.588 they're generated.
01:17:53.418 --> 01:17:58.314 Umm, there's some issues that can arise from invoices being
01:17:58.314 --> 01:18:01.088 modified after they're generated.
01:18:01.098 --> 01:18:06.029 For example, if I make a partial payment on an invoice and then
01:18:06.029 --> 01:18:10.344 the invoice is updated to reflect three more line items
01:18:10.344 --> 01:18:13.348 that I call it in and wanted to order.
01:18:13.358 --> 01:18:17.178 If they place those on the invoice and I've already paid
01:18:17.178 --> 01:18:20.528 partially towards the invoice, then we have some.
01:18:23.928 --> 01:18:28.625 Some issues there with the partial payment and then the new
01:18:28.625 --> 01:18:33.243 updated total for the invoice, so it's important to try to
01:18:33.243 --> 01:18:37.861 steer the clients away from modifying invoices after their
01:18:37.861 --> 01:18:42.714 generation if that's something that they have absolutely have
01:18:42.714 --> 01:18:47.332 to have, then we can put in place ways to handle or try to
01:18:47.332 --> 01:18:51.558 mitigate any risk or errors around modified invoices.
01:18:51.568 --> 01:18:54.886 But it is typically best practice to not modify the
01:18:54.886 --> 01:18:57.118 invoices after they are generated.
01:18:58.608 --> 01:19:05.483 Or at least ask them at what point should a invoice be
01:19:05.483 --> 01:19:07.108 payable like?
01:19:07.118 --> 01:19:08.948 Is it as soon as we generate it?
01:19:08.958 --> 01:19:12.653 As soon as you generate it in your ERP and we sync it over,
01:19:12.653 --> 01:19:14.008 they can pay it or no.
01:19:14.018 --> 01:19:17.821 We create it and you know, we think it over just to let them
01:19:17.821 --> 01:19:21.686 know what we're shipping them and what we're going to invoice
01:19:21.686 --> 01:19:25.489 them, but it could potentially change later on down the road
01:19:25.489 --> 01:19:29.105 and and if it's the latter, you're like, alright, then we
01:19:29.105 --> 01:19:32.845 need to figure out at what point you want them to pay those
01:19:32.845 --> 01:19:36.959 invoices to make sure you're not gonna do anymore changes as soon
01:19:36.959 --> 01:19:39.328 as the final price is on the invoice.
01:19:39.408 --> 01:19:42.806 That's when you want them to pay, just to make sure there's
01:19:42.806 --> 01:19:44.958 no hiccups later on down the line of.
01:19:44.968 --> 01:19:46.118 Well, I already paid that.
01:19:46.128 --> 01:19:50.552 Ohh well, you're price went up and you know all that good jazz
01:19:50.552 --> 01:19:54.836 that can sometimes happen there, but that's also just a good
01:19:54.836 --> 01:19:58.908 question of you can modify it after we generated, but you
01:19:58.908 --> 01:20:03.332 wanna put in failsafes in order to let the customer know that,
01:20:03.332 --> 01:20:05.298 hey, this is still changing.
01:20:06.518 --> 01:20:07.458 Don't pay it yet.
01:20:08.578 --> 01:20:10.018 Type of thing that makes sense.
01:20:13.548 --> 01:20:14.298 It does.
01:20:13.938 --> 01:20:14.248 Umm.
01:20:14.308 --> 01:20:15.718 Thank you, Carl.
01:20:15.768 --> 01:20:16.738 Uh, real quick.
01:20:16.748 --> 01:20:20.525 I wanna go to the wallet and talk about wallets and how
01:20:20.525 --> 01:20:22.278 they're associations work.
01:20:22.548 --> 01:20:27.580 So this was a concept that was rather difficult to get Nat to
01:20:27.580 --> 01:20:29.608 understand about wallets.
01:20:29.618 --> 01:20:34.298 So wallets are assigned at the user level.
01:20:34.588 --> 01:20:38.931 So if I have an account with 100 users, then each user would be
01:20:38.931 --> 01:20:42.662 required to enter their own payment method in order to
01:20:42.662 --> 01:20:44.358 proceed through checkout.
01:20:45.518 --> 01:20:49.455 The users could use the same payment method as other users,
01:20:49.455 --> 01:20:53.457 but you can't enter a payment method for an account and have
01:20:53.457 --> 01:20:55.228 it shared across all users.
01:20:55.238 --> 01:20:59.796 All users will be required to enter their own payment method,
01:20:59.796 --> 01:21:03.838 whether it be unique or the same card as someone else.
01:21:05.548 --> 01:21:09.394 Whatever way that's actually wait so wallet and this is new
01:21:09.394 --> 01:21:09.778 to me.
01:21:09.788 --> 01:21:14.248 Sorry, wallet entries are user specific, not account specific.
01:21:15.228 --> 01:21:16.458 I believe so.
01:21:16.948 --> 01:21:20.739 I mean it, I think that's what Eric said that it's user
01:21:17.738 --> 01:21:18.848 Ohh.
01:21:20.739 --> 01:21:21.348 specific.
01:21:22.848 --> 01:21:23.258 OK.
01:21:24.918 --> 01:21:29.021 Yeah, because you really like, think of it in a company
01:21:25.198 --> 01:21:26.108 On that.
01:21:29.021 --> 01:21:33.417 perspective, this account, this ecommerce account is for my
01:21:33.417 --> 01:21:37.373 company, Acme, you and I are both you know, let's say
01:21:37.373 --> 01:21:41.696 managers for Acme and we're both could be making purchases
01:21:41.696 --> 01:21:42.648 through Seth.
01:21:43.678 --> 01:21:46.748 Well, we both have the same company card.
01:21:47.598 --> 01:21:52.074 Typically that's always been shared by the account, so the
01:21:52.074 --> 01:21:56.550 either you or I could make purchases with that same wallet
01:21:56.550 --> 01:22:00.418 entry, but yeah, that's it because I thought that.
01:21:59.818 --> 01:22:02.068 Well, I I may be wrong.
01:22:02.078 --> 01:22:06.048 I'm Eric may have just misspoken of meeting or something, but.
01:22:06.078 --> 01:22:08.588 I would we can do it well.
01:22:08.598 --> 01:22:13.123 The the point is, we can do it either way, but I'm pretty sure
01:22:13.123 --> 01:22:17.503 out of the box that everything I'm pretty sure everything is
01:22:17.503 --> 01:22:22.171 shared at the account level, so that's orders, invoices, quotes,
01:22:22.171 --> 01:22:26.623 returns, wallet address book, all of that ties to the account
01:22:26.623 --> 01:22:30.717 and users all share that information and can manage that
01:22:30.717 --> 01:22:31.578 information.
01:22:31.588 --> 01:22:35.555 I'm pretty sure is how it works, because if you log in as one
01:22:35.555 --> 01:22:37.218 user I can see all of the.
01:22:38.648 --> 01:22:41.616 Orders under the account and if I log in as another user into
01:22:41.616 --> 01:22:43.818 that account, I can see the exact same thing.
01:22:43.868 --> 01:22:44.918 I can see everything.
01:22:45.448 --> 01:22:46.968 I'm pretty sure that's how it works.
01:22:47.468 --> 01:22:53.581 Well, Micki may have started an argument within AT for no
01:22:51.468 --> 01:22:51.748 Sorry.
01:22:53.581 --> 01:22:54.318 reason.
01:22:55.658 --> 01:22:58.729 Hey, it's not like we haven't done it to me enough times to
01:22:58.729 --> 01:22:59.138 get one.
01:22:59.808 --> 01:23:02.908 Well, I mean, I might be wrong if if somebody's specifically
01:23:02.908 --> 01:23:04.838 told you that it's at the user level.
01:23:04.848 --> 01:23:08.988 I mean, I might be wrong at the wallet level.
01:23:08.998 --> 01:23:12.901 I know it's that way for the orders out of the box, we can
01:23:12.901 --> 01:23:17.201 turn it on to be user specific, but it's account wide out of the
01:23:17.201 --> 01:23:19.648 box for at least for viewing orders.
01:23:20.058 --> 01:23:23.602 I thought the address book in the wallet were the same way,
01:23:23.602 --> 01:23:25.728 because if you come in here to the.
01:23:26.398 --> 01:23:27.248 Yeah, yeah, yeah.
01:23:27.298 --> 01:23:31.186 If you come in here and you go to accounts, I believe if you go
01:23:31.186 --> 01:23:32.158 into the editor.
01:23:34.698 --> 01:23:38.358 For any account, there's a dresses there.
01:23:41.218 --> 01:23:44.624 So addresses I know for sure sociated with the account
01:23:44.624 --> 01:23:48.649 they're not associated with the user because users and addresses
01:23:48.649 --> 01:23:52.178 are both associated with the account in terms of wallet.
01:23:52.228 --> 01:23:55.899 I actually don't think we have a place to manage wallet entries
01:23:55.899 --> 01:23:58.938 from the admin, so that one that's why I don't know.
01:23:59.408 --> 01:24:01.923 On the wall it side of things because that's not on the
01:24:01.923 --> 01:24:04.078 account editor and it's not on the user editor.
01:24:04.428 --> 01:24:06.528 It's not accessible from the admin.
01:24:10.008 --> 01:24:13.618 And it would make more sense to me that it's on the user level
01:24:13.618 --> 01:24:17.343 because generally like you have to have a name associated with a
01:24:17.318 --> 01:24:21.588 Yeah, but it's also sometimes dependent on the token.
01:24:17.343 --> 01:24:17.858 card and.
01:24:21.598 --> 01:24:26.546 For that cart is the token for that card card specific or is it
01:24:26.546 --> 01:24:27.628 user specific?
01:24:28.118 --> 01:24:32.356 Meaning 2 users can have their own token for the same card, or
01:24:32.356 --> 01:24:36.458 this card is the token for this card is shared by two users.
01:24:39.718 --> 01:24:42.074 Because I think it it because we never stored the card
01:24:42.074 --> 01:24:42.588 information.
01:24:42.598 --> 01:24:46.888 It's always a token that's saved by the PCI provider.
01:24:44.188 --> 01:24:44.428 Mm-hmm.
01:24:46.898 --> 01:24:49.717 Whoever the merchant is, whoever's actually doing the
01:24:49.717 --> 01:24:50.708 payment processing.
01:24:50.718 --> 01:24:55.585 So the token for that card for us accessing that I I pretty
01:24:55.585 --> 01:25:00.370 sure it depends on who we go with as the merchant provider
01:25:00.370 --> 01:25:04.993 who's processing the payments will dictate whether those
01:25:04.993 --> 01:25:06.128 tokens can be.
01:25:07.698 --> 01:25:10.218 I guess user specific or card specific.
01:25:15.588 --> 01:25:19.250 Because if it's just one token for the card, every user under
01:25:19.250 --> 01:25:21.848 the account could just use that same token.
01:25:22.868 --> 01:25:25.686 It would be super easy, which I'm pretty sure is how our
01:25:25.686 --> 01:25:26.328 wallet works.
01:25:29.138 --> 01:25:32.138 Looks like Shelton's gonna find out for us here in a second.
01:25:31.948 --> 01:25:37.208 I'm trying to if I can get this to to work.
01:25:56.538 --> 01:25:58.218 We shall see, huh.
01:25:59.458 --> 01:26:00.528 Well, now I'm curious.
01:26:01.638 --> 01:26:02.218 Yes, me too.
01:26:07.318 --> 01:26:11.753 Well, yeah, you just log in as a 2 users under the same account
01:26:11.753 --> 01:26:12.238 put in.
01:26:11.888 --> 01:26:16.611 Yeah, I'm trying to add a user to this account and it's been
01:26:15.638 --> 01:26:16.428 Ohh gotcha.
01:26:16.611 --> 01:26:16.998 slow.
01:26:22.568 --> 01:26:24.708 I made whatever, but it's not like me.
01:26:24.718 --> 01:26:28.974 Like in maybe I just need to go to the user editor or maybe it's
01:26:28.974 --> 01:26:30.938 just not gonna let me develop.
01:26:30.948 --> 01:26:31.968 It's been weird.
01:26:32.578 --> 01:26:35.228 Did you specify a password for your user?
01:26:35.238 --> 01:26:36.738 Did you do the reset?
01:26:37.248 --> 01:26:40.068 I didn't do the reset, I just typed it into the actual.
01:26:41.298 --> 01:26:44.378 Ohh yeah, it should technically work.
01:26:54.898 --> 01:26:55.228 Yes.
01:27:29.578 --> 01:27:30.668 Can you put in the same?
01:27:30.678 --> 01:27:32.698 Can you just put in the email address as the username?
01:27:37.578 --> 01:27:40.722 Just to make sure that that's not, I mean that might be an
01:27:40.722 --> 01:27:43.971 issue because I know that's a setting or whether you use the
01:27:43.971 --> 01:27:46.688 email as the username or just put in the username.
01:27:46.898 --> 01:27:50.981 I think it's because well, since it's editable, you might have it
01:27:50.981 --> 01:27:53.208 the other way, but just to be safe.
01:28:03.528 --> 01:28:04.198 Booyah.
01:28:05.298 --> 01:28:06.188 Ooh yeah.
01:28:06.238 --> 01:28:09.718 Ohh wallets are user specific.
01:28:09.308 --> 01:28:12.628 Yes, thank God.
01:28:12.248 --> 01:28:14.658 Dang, you show me up?
01:28:14.668 --> 01:28:16.458 You taught me something new today.
01:28:16.468 --> 01:28:16.848 Heck yeah.
01:28:17.988 --> 01:28:22.478 Ohh man that's just the ohh.
01:28:18.118 --> 01:28:20.298 Ohh God bless you for figuring that out.
01:28:22.158 --> 01:28:25.098 Because if you go to orders, this is a brand new user.
01:28:25.158 --> 01:28:28.008 So if you go to orders, I can see all the other orders from
01:28:28.008 --> 01:28:29.908 all the other users under this account.
01:28:31.348 --> 01:28:33.748 So that's why I thought it was in all the other addresses too.
01:28:36.288 --> 01:28:42.398 So addresses, orders, invoices, quotes are all account wide.
01:28:42.458 --> 01:28:45.843 Anybody under the account can see him, but wallet and I
01:28:45.843 --> 01:28:47.898 imagine wish list favorites list.
01:28:47.908 --> 01:28:48.648 Can you check those?
01:28:49.248 --> 01:28:50.998 I don't think that yeah, there shouldn't be anything.
01:28:50.848 --> 01:28:51.148 Umm.
01:28:51.008 --> 01:28:55.335 I'm pretty sure all of those are users specific as well, so the
01:28:55.335 --> 01:28:58.038 lists and the wallet are user specific.
01:28:58.048 --> 01:28:59.858 Everything else is account specific.
01:29:02.498 --> 01:29:03.238 Perfect.
01:29:02.808 --> 01:29:03.028 Yep.
01:29:03.538 --> 01:29:04.228 Amazing.
01:29:04.738 --> 01:29:07.682 Well, on that note, thank you Shelton so much for that
01:29:07.682 --> 01:29:08.378 presentation.
01:29:08.388 --> 01:29:09.648 That was wonderful.
01:29:09.978 --> 01:29:13.765 We may do a follow up on this and dig into some other areas of
01:29:13.765 --> 01:29:15.328 CEF together another time.
01:29:15.418 --> 01:29:16.908 This was fantastic.
01:29:16.988 --> 01:29:18.568 Everybody, please do your time logs.
01:29:19.518 --> 01:29:22.488 Please do your uh needs reallocation.
01:29:22.558 --> 01:29:25.843 Make sure everything cleared out of there and have a great
01:29:25.843 --> 01:29:26.288 weekend.
01:29:28.338 --> 01:29:28.828 Awesome.
01:29:29.218 --> 01:29:29.768 Thank you.
01:29:29.778 --> 01:29:33.554 I know it wasn't the uh the best presentation, but thanks for
01:29:29.928 --> 01:29:30.358 You too.
01:29:31.588 --> 01:29:31.798 Sure.
01:29:33.554 --> 01:29:34.528 bearing with me.
01:29:35.198 --> 01:29:35.548 Yeah.
01:29:35.308 --> 01:29:36.738 It was wonderful.
01:29:35.618 --> 01:29:36.388 Thank Shelton.
01:29:35.748 --> 01:29:37.018 You did great shopping.
01:29:36.398 --> 01:29:36.908 Yeah.
01:29:36.978 --> 01:29:37.998 Thanks for doing it.
01:29:37.108 --> 01:29:37.608 Thank you.
01:29:37.388 --> 01:29:38.668 Very informative.
01:29:39.948 --> 01:29:41.888 I learned a lot today as well.
01:29:43.688 --> 01:29:47.038 I'm just glad that the wallet was user specific.
01:29:44.108 --> 01:29:44.658 So did I.
01:29:47.048 --> 01:29:47.978 Uh, that would.
01:29:48.278 --> 01:29:48.648 You didn't.
01:29:48.428 --> 01:29:51.418 That would have been a fine conversation within a T.
01:29:51.988 --> 01:29:57.242 Yeah, after I basically yelled at them because they weren't
01:29:57.242 --> 01:29:59.168 listening to you. Ohh.
01:29:58.138 --> 01:29:59.308 No, I that's what I said.
01:29:59.148 --> 01:29:59.518 I think.
01:29:59.318 --> 01:30:01.248 I was like guys, I might be wrong on this.
01:30:01.258 --> 01:30:04.436 I didn't wanna like throw anything out there because I was
01:30:04.436 --> 01:30:07.990 like, I could easily there could have been a change recently that
01:30:07.990 --> 01:30:09.928 could make me very much wrong here.
01:30:09.938 --> 01:30:11.478 But I was right about the rest of it.
01:30:12.118 --> 01:30:15.468 Umm, best case scenario.
01:30:16.828 --> 01:30:17.278 All right.
01:30:17.288 --> 01:30:18.138 Thank you guys.
01:30:18.148 --> 01:30:19.238 Have a great weekend.
01:30:19.508 --> 01:30:20.798 Yes, thank you.
01:30:19.848 --> 01:30:20.978 See you next week.
01:30:20.288 --> 01:30:20.748 Y'all too.
01:30:20.328 --> 01:30:22.848 Thanks by all.
01:30:20.928 --> 01:30:23.668 You too, uh.
01:30:21.148 --> 01:30:21.888 See you all later.