00:00:03.279 --> 00:00:08.472 Up is down and uh, we can't mess with the demo sites, so we will
00:00:08.472 --> 00:00:13.265 go through different actions of how to create things within
00:00:13.265 --> 00:00:16.859 stuff, but we will not actually create them.
00:00:16.919 --> 00:00:20.776 So you're just gonna have to pretend that they're there until
00:00:20.776 --> 00:00:24.509 develop gets fixed, and then you can have at it and go play
00:00:23.549 --> 00:00:26.439 You guys wanna and then?
00:00:24.509 --> 00:00:25.939 around and make things.
00:00:25.949 --> 00:00:31.980 But uh, today we're going to run through our basic CEF components
00:00:31.980 --> 00:00:37.919 and abilities, capabilities that are available to our customers,
00:00:37.919 --> 00:00:43.584 and a lot of the actions that they frequently will use within
00:00:40.349 --> 00:00:40.809 Like this?
00:00:43.584 --> 00:00:43.949 CEF.
00:00:44.199 --> 00:00:48.621 Some of the more advanced topics we'll save for a different call
00:00:48.621 --> 00:00:51.409 where we can focus on them specifically.
00:00:48.939 --> 00:00:49.939 Yeah, yeah, yeah.
00:00:51.259 --> 00:00:51.929 I forgot the word.
00:00:51.819 --> 00:00:54.629 So today, apologies if you already know this.
00:00:54.979 --> 00:00:58.961 Some of this information, but with Cassie uh being a little
00:00:58.961 --> 00:01:03.076 bit newer, I think it would be good to go through some of the
00:00:59.089 --> 00:01:00.679 They happens here.
00:01:03.076 --> 00:01:07.389 basics of functions and just to give everyone a quick refresher.
00:01:03.909 --> 00:01:04.159 Right.
00:01:08.959 --> 00:01:15.291 So with the surf platform, we have the ability for users to
00:01:09.479 --> 00:01:09.699 OK.
00:01:15.291 --> 00:01:17.929 register within the site.
00:01:17.999 --> 00:01:21.682 So let me just share my screen and we'll talk about account
00:01:21.682 --> 00:01:22.479 registration.
00:01:23.609 --> 00:01:28.985 So with our out of the box account registration for itself,
00:01:26.239 --> 00:01:26.479 Good.
00:01:28.949 --> 00:01:29.479 We need.
00:01:28.985 --> 00:01:32.569 we have a stepped registration process.
00:01:32.579 --> 00:01:37.173 So as you complete one step of registration, you proceed to the
00:01:37.173 --> 00:01:39.469 next one area of customizations.
00:01:39.479 --> 00:01:42.409 That's typically seen with projects.
00:01:39.529 --> 00:01:39.689 Right.
00:01:42.419 --> 00:01:45.864 Not always, but some clients will request that their
00:01:45.864 --> 00:01:49.894 registration be a single page rather than the different steps
00:01:49.894 --> 00:01:51.129 within the process.
00:01:51.599 --> 00:01:54.999 It is something that we do a good bit, but it is a
00:01:54.999 --> 00:01:56.999 customization for the project.
00:01:56.529 --> 00:01:56.749 Yeah.
00:01:57.059 --> 00:02:00.840 So if you encounter a client that wishes to have a single
00:02:00.840 --> 00:02:04.556 page rather than multiple steps of registration, that is
00:02:04.556 --> 00:02:08.338 definitely something we can do, but would be considered a
00:02:08.338 --> 00:02:10.619 customization towards the project.
00:02:12.219 --> 00:02:15.829 As you can see in our first step of registration here, we have
00:02:15.829 --> 00:02:19.209 our basic information fields that we capture from the user
00:02:19.209 --> 00:02:21.729 first name, last name, email, phone number.
00:02:22.339 --> 00:02:27.360 Within Seth, we populate the username using the email address
00:02:27.360 --> 00:02:28.979 entered by the user.
00:02:28.989 --> 00:02:34.232 So user name is not going to be a editable or customizable field
00:02:34.232 --> 00:02:38.749 compared to the email with out of the box registration.
00:02:39.079 --> 00:02:43.592 So as you enter in your email address, the username will
00:02:43.592 --> 00:02:48.421 update to reflect the email address entered by the user when
00:02:48.421 --> 00:02:52.933 it comes to customizing the information that we captured
00:02:52.933 --> 00:02:57.525 during account registration, similar to a single page, if
00:02:54.869 --> 00:02:55.489 Oh my God.
00:02:57.525 --> 00:03:02.592 they wanted to continue with the stuffed process but modify the
00:03:02.592 --> 00:03:07.421 information we're collecting, it would be a customization to
00:03:07.421 --> 00:03:11.458 account registration to accommodate those new data
00:03:11.458 --> 00:03:14.229 points that we will be collecting.
00:03:16.289 --> 00:03:20.183 Additionally, with account registration, uh, there are some
00:03:20.183 --> 00:03:24.400 scenarios where customers would like to have an approval process
00:03:24.400 --> 00:03:24.919 for the.
00:03:27.129 --> 00:03:30.747 Clients or customers or end users that are going to be using
00:03:30.747 --> 00:03:31.399 their site?
00:03:31.489 --> 00:03:36.281 Uh, some common scenarios or ways that we handle approval
00:03:36.281 --> 00:03:41.156 processes for customers is through action forms or through
00:03:41.156 --> 00:03:43.799 a registration approval process.
00:03:44.229 --> 00:03:48.714 So with action forms, one thing that we would do is we would
00:03:48.714 --> 00:03:52.905 create registration to be an action form with the fields
00:03:52.905 --> 00:03:57.023 required by the client that they'd like to capture from
00:03:57.023 --> 00:03:58.199 their customers.
00:03:58.209 --> 00:04:00.939 We would create that action form as registration.
00:04:01.389 --> 00:04:06.426 The user would complete the registration via the action form
00:04:06.426 --> 00:04:11.545 and on submit we would send this action form to a back office
00:04:11.545 --> 00:04:13.279 email for the client.
00:04:13.369 --> 00:04:18.617 The client would review that information and either create
00:04:18.617 --> 00:04:23.953 the user manually within CEF directly through CEF admin, or
00:04:23.953 --> 00:04:29.022 through an integration if the project is uh, is using an
00:04:29.022 --> 00:04:30.089 integration.
00:04:30.359 --> 00:04:33.389 So that's one scenario of approval.
00:04:33.809 --> 00:04:38.486 Umm that we do with some clients is through an action form when
00:04:38.486 --> 00:04:43.089 action forms are utilized, the user is not created within CEF.
00:04:44.199 --> 00:04:48.312 Upon account registration completion and must either be
00:04:48.312 --> 00:04:52.352 manually created within CEF admin or synced in from an
00:04:52.352 --> 00:04:52.939 outside.
00:04:54.379 --> 00:04:57.889 Platform via an integration with connect.
00:04:58.359 --> 00:05:01.059 So any questions so far about any of that?
00:05:03.409 --> 00:05:03.929 No, Sir.
00:05:05.149 --> 00:05:05.679 Anybody else?
00:05:07.109 --> 00:05:09.339 What would an example of an action form be?
00:05:09.349 --> 00:05:12.869 Would it be like a like a pop up where they're asking For more
00:05:12.869 --> 00:05:13.539 information?
00:05:13.549 --> 00:05:15.609 Or what would be an example of that?
00:05:17.179 --> 00:05:21.913 So an action form is essentially just A and that is going to be
00:05:21.913 --> 00:05:26.647 the worst explanation I've ever heard, but an action form would
00:05:26.647 --> 00:05:30.716 look no different than a registration that creates the
00:05:30.716 --> 00:05:31.899 user within SEV.
00:05:32.289 --> 00:05:36.707 Essentially what the action form is doing is rather than sending
00:05:36.707 --> 00:05:40.989 the information to the back end within CEF and generating that
00:05:40.989 --> 00:05:45.474 user would then SEF it, captures the information place within the
00:05:45.474 --> 00:05:49.008 form and we apply that information to an email that
00:05:49.008 --> 00:05:50.639 sends out to the client.
00:05:50.649 --> 00:05:55.678 So you can think of action forms as the information you put into
00:05:55.678 --> 00:06:00.398 the form gets captured and then gets sent via email, or, you
00:06:00.179 --> 00:06:04.009 Let me fix myself my blindness and.
00:06:00.398 --> 00:06:02.409 know, sent somewhere else.
00:06:02.889 --> 00:06:06.846 But at the user's not created within seven band, you may be
00:06:06.099 --> 00:06:07.049 So yeah, I can.
00:06:06.846 --> 00:06:07.769 able to, yeah.
00:06:07.059 --> 00:06:09.369 I can chime in on that too, a little bit just and I won't.
00:06:09.379 --> 00:06:11.029 I won't talk a lot on it, but I'll just stick.
00:06:11.039 --> 00:06:12.469 It's basically just DNN.
00:06:12.519 --> 00:06:17.003 It's DNN form builder, so you know you can make all manners of
00:06:17.003 --> 00:06:17.999 forms with it.
00:06:18.009 --> 00:06:22.346 Any kind of form you want pretty much in some use cases rather
00:06:22.346 --> 00:06:26.545 than using cefs registration built-in registration form like
00:06:26.545 --> 00:06:31.088 in situations where clients want to do a detailed vetting process
00:06:31.088 --> 00:06:35.012 and then manually like enter them on the back end, which
00:06:35.012 --> 00:06:39.279 which we've had, you know, some with certain certain clients.
00:06:39.289 --> 00:06:42.855 That's a really great use case for that, because in in that
00:06:42.629 --> 00:06:42.909 OK.
00:06:42.855 --> 00:06:46.362 sense users can go on, they'll fill out this quote unquote
00:06:46.362 --> 00:06:50.047 registration form right in this form builder called DNN sharp
00:06:50.047 --> 00:06:50.819 action forms.
00:06:51.229 --> 00:06:54.319 It's built on top of DNN in the content management system.
00:06:54.399 --> 00:06:57.859 It fires off an email to as like a back office email.
00:06:57.869 --> 00:07:01.194 So someone on the clients and would receive that and you know
00:07:01.194 --> 00:07:04.358 in this scenario they would start the vetting process from
00:07:04.358 --> 00:07:04.679 there.
00:07:04.689 --> 00:07:06.349 So then they would do whatever.
00:07:06.979 --> 00:07:10.487 Uh falls in line with their their process to to add them to
00:07:10.487 --> 00:07:13.819 the system and invite them to log in for the first time.
00:07:14.399 --> 00:07:15.509 Hopefully that helps.
00:07:15.519 --> 00:07:16.649 It's just a form builder.
00:07:15.989 --> 00:07:16.099 Yes.
00:07:16.819 --> 00:07:20.599 It's not related to Seth at all, and it can be installed
00:07:20.599 --> 00:07:24.775 completely separately from CEF and just DNN by itself, because
00:07:24.775 --> 00:07:26.499 it's a, it's a DNN module.
00:07:28.119 --> 00:07:28.729 That helps.
00:07:28.739 --> 00:07:29.079 Thank you.
00:07:29.359 --> 00:07:32.369 Thank you, Ben, for that explanation.
00:07:30.409 --> 00:07:30.819 You bet.
00:07:33.049 --> 00:07:33.509 Perfect.
00:07:33.519 --> 00:07:35.489 Does that answer your question, Cassie?
00:07:35.989 --> 00:07:36.849 Yes, thank you.
00:07:38.019 --> 00:07:38.629 Awesome.
00:07:38.639 --> 00:07:40.999 And then another scenario that we work with.
00:07:41.349 --> 00:07:45.580 Uh, pretty frequently is the account registration approval
00:07:45.580 --> 00:07:49.811 process through CEF, so we've had several clients requests
00:07:49.811 --> 00:07:53.539 this rather than an action form for their approval.
00:07:54.169 --> 00:07:58.837 We use these CEF registration to create the user upon
00:07:58.837 --> 00:08:04.456 registration completion, but put them into a pending status upon
00:08:04.456 --> 00:08:07.049 uh, account and user creation.
00:08:07.099 --> 00:08:11.995 So the users would be created with himself upon registration,
00:08:11.995 --> 00:08:16.733 but the users will not become active until they're reviewed
00:08:16.733 --> 00:08:20.839 and approved by the client admin within CEF itself.
00:08:22.429 --> 00:08:25.838 So when that case, there's a couple of different ways the
00:08:25.838 --> 00:08:29.247 clients typically you know request this some requests you
00:08:29.247 --> 00:08:32.774 know just for the user to be created within CEF so they can
00:08:32.774 --> 00:08:35.595 go and review that and then approve or deny the
00:08:35.595 --> 00:08:36.359 registration.
00:08:36.649 --> 00:08:41.073 And then we have some that like an email notification that, you
00:08:41.073 --> 00:08:45.565 know upon registration the they would receive an email, you have
00:08:45.565 --> 00:08:46.809 a new account. Uh.
00:08:47.059 --> 00:08:47.849 Request.
00:08:47.859 --> 00:08:49.329 Please go to review the account.
00:08:50.319 --> 00:08:55.637 Here's you know, a link to CEF admin to review that, and then a
00:08:55.637 --> 00:09:00.456 more complex workflow with emails and new account request
00:09:00.456 --> 00:09:05.109 is building out actual buttons within the email itself.
00:09:05.319 --> 00:09:09.966 Proven deny buttons that on click by the client admin in the
00:09:09.966 --> 00:09:13.699 email we would either approve or deny an update.
00:09:13.709 --> 00:09:19.039 The status of the account within CEF based on their selection in
00:09:19.039 --> 00:09:19.859 the email.
00:09:19.869 --> 00:09:24.622 So it's kind of three different, I guess tears or scenarios of
00:09:24.622 --> 00:09:29.299 approvals, uh, through CEF with emails are strictly just with
00:09:29.299 --> 00:09:34.127 creating the account, placing it in the pending status and then
00:09:34.127 --> 00:09:38.804 having everything done directly through CEF rather than using
00:09:38.804 --> 00:09:41.519 emails to accomplish that workflow.
00:09:44.909 --> 00:09:48.760 Alright, so the next thing I wanted to talk about was
00:09:48.760 --> 00:09:50.899 existing account associations.
00:09:51.129 --> 00:09:55.417 So we have some customers that come to us and they have
00:09:55.417 --> 00:10:00.010 existing accounts within their current ERP or they want the
00:10:00.010 --> 00:10:04.757 ability for new users coming to the site if they're part of a
00:10:04.757 --> 00:10:09.274 company or a corporation and they already have an existing
00:10:09.274 --> 00:10:14.173 account within self, they would like for them to be able to add
00:10:14.173 --> 00:10:16.929 their user to the existing account.
00:10:17.049 --> 00:10:19.459 Uh, this is something that we can do.
00:10:19.469 --> 00:10:24.617 But one thing that is important to note with the clients is the
00:10:24.617 --> 00:10:28.799 possible risk of how we make this association work.
00:10:30.279 --> 00:10:34.698 It is something that typically we ask the clients to, you know,
00:10:34.698 --> 00:10:38.218 do you have a certain set of security questions or
00:10:38.218 --> 00:10:42.222 information within the accounts that only members of that
00:10:42.222 --> 00:10:43.879 organization would have.
00:10:45.589 --> 00:10:49.777 We don't want it, you know, random users or disgruntled ex
00:10:49.777 --> 00:10:53.964 employees or anyone like that coming in and, you know, one
00:10:53.964 --> 00:10:58.009 field of you know, what's the address of on the account.
00:10:58.019 --> 00:10:58.899 They type that in.
00:10:58.909 --> 00:11:04.473 They create a user and they can go in and cause mischief on the
00:11:04.473 --> 00:11:06.559 account of that company.
00:11:07.149 --> 00:11:10.378 So it's important to note that while even though you have
00:11:10.378 --> 00:11:10.879 multiple.
00:11:13.609 --> 00:11:17.522 Validation questions to make that account association to the
00:11:17.522 --> 00:11:18.099 new user.
00:11:18.489 --> 00:11:23.585 It is still a risk that there could potentially be, umm, some
00:11:23.585 --> 00:11:28.352 bad actor that could get a user associated to an existing
00:11:28.352 --> 00:11:29.009 account.
00:11:29.919 --> 00:11:33.507 So that's something that's always worth calling out with
00:11:33.507 --> 00:11:37.095 the client to ensure that they know that that's always a
00:11:37.095 --> 00:11:40.872 possibility with, you know, registration being an area that
00:11:40.872 --> 00:11:44.711 users can associate themselves to existing accounts, even if
00:11:44.711 --> 00:11:45.529 they do have.
00:11:48.239 --> 00:11:50.559 Multiple verification questions.
00:11:52.279 --> 00:11:57.597 Alright, so we'll take a quick look at the address book and
00:11:57.597 --> 00:12:00.699 then we'll move on to the catalog.
00:12:00.979 --> 00:12:06.302 So once you enter your basic information username and
00:12:06.302 --> 00:12:07.189 password.
00:12:15.379 --> 00:12:17.529 And proceed to the address book.
00:12:17.599 --> 00:12:21.588 This is where users would be managing their address
00:12:21.588 --> 00:12:26.113 information within CEF, so you can see we have billing and
00:12:26.113 --> 00:12:30.562 shipping addresses that are available to the users during
00:12:30.562 --> 00:12:31.559 registration.
00:12:32.869 --> 00:12:35.089 You they would enter their address information.
00:12:45.859 --> 00:12:48.849 And this may OK.
00:12:49.339 --> 00:12:54.727 Once I enter their billing, they have the ability to copy that uh
00:12:54.727 --> 00:12:59.543 to their as their shipping address are to enter a separate
00:12:59.543 --> 00:13:04.603 shipping address as well prior or after user registration the
00:13:04.603 --> 00:13:09.501 address book is something that's accessible within the user
00:13:09.501 --> 00:13:12.929 dashboard to modify or add new addresses.
00:13:13.819 --> 00:13:16.832 So for out of the box registration, we capture the
00:13:16.832 --> 00:13:18.309 basic information fields.
00:13:18.319 --> 00:13:22.069 We just saw and the address information for the user.
00:13:22.439 --> 00:13:26.121 Any additional field customizations or changes would
00:13:26.121 --> 00:13:30.081 be a customization for the project and this is something
00:13:30.081 --> 00:13:34.528 that a majority of the time we are going to be implementing for
00:13:34.528 --> 00:13:35.639 client projects.
00:13:38.249 --> 00:13:41.269 Alright, so any questions?
00:13:41.349 --> 00:13:44.399 Um there or Kyle are micki.
00:13:44.409 --> 00:13:46.209 Anything you think I may have skipped over?
00:13:47.969 --> 00:13:48.789 No, not for me.
00:13:49.419 --> 00:13:50.219 Not top my head.
00:13:52.079 --> 00:13:52.469 Perfect.
00:13:52.149 --> 00:13:52.539 Great.
00:13:53.709 --> 00:13:56.779 Alright, so let's take a look at the catalog.
00:14:16.999 --> 00:14:17.699 Little right?
00:14:19.379 --> 00:14:23.029 So the first thing here is our product Mega menu.
00:14:23.079 --> 00:14:26.135 Before we get into the catalog, we'll talk about this a little
00:14:26.135 --> 00:14:26.329 bit.
00:14:26.799 --> 00:14:30.643 This is a quick way for the users to navigate to different
00:14:30.643 --> 00:14:31.359 categories.
00:14:32.789 --> 00:14:33.119 Uh.
00:14:33.129 --> 00:14:36.507 Within the the site for the products that are going to be
00:14:36.507 --> 00:14:38.079 visible within the catalog.
00:14:38.249 --> 00:14:42.303 As you can see, some of these uh parent categories here have
00:14:42.303 --> 00:14:45.559 subcategories associated with them, some do not.
00:14:45.669 --> 00:14:50.383 It's not a requirement to have child categories of a parent,
00:14:50.383 --> 00:14:54.479 but it is something that is available to the client.
00:14:54.779 --> 00:14:59.515 Uh would then Seth, you can have up to 7 layers of child
00:14:59.515 --> 00:15:00.429 categories.
00:15:01.579 --> 00:15:04.369 That is supported within the catalog.
00:15:04.659 --> 00:15:09.958 So as you create your parent categories and child categories,
00:15:09.958 --> 00:15:15.514 those will display here for the users to quickly navigate to and
00:15:15.514 --> 00:15:20.215 categories can be set up manually within self or if an
00:15:20.215 --> 00:15:25.685 integration is being used we can set up those categories on the
00:15:25.685 --> 00:15:30.129 sync of the product categories from the client ERP.
00:15:32.129 --> 00:15:36.608 Alright, so talking about our filters here, we have search
00:15:36.608 --> 00:15:41.238 term which is as it sounds, I type in a product, I'll get my
00:15:41.238 --> 00:15:45.109 results of the related products to my search term.
00:15:45.429 --> 00:15:51.947 So like to product and then search and I'll get the results
00:15:51.947 --> 00:15:53.359 of my search?
00:15:53.409 --> 00:15:53.979 Uh.
00:15:54.029 --> 00:15:54.569 From that?
00:15:57.529 --> 00:16:01.578 Product ratings, product ratings, or something that is
00:16:01.578 --> 00:16:03.859 configurable withoutabox stuff.
00:16:03.869 --> 00:16:08.575 It is not a requirement to leave on for the site if a client does
00:16:08.575 --> 00:16:12.924 not want product ratings on their side, it is something that
00:16:12.924 --> 00:16:17.416 is easily configurable to turn off, but does take a little bit
00:16:17.416 --> 00:16:20.339 of time to implement that configuration.
00:16:20.799 --> 00:16:25.421 So while it is out of box to have it on or off, if they do
00:16:25.421 --> 00:16:29.808 want to remove it from their site, it does take a small
00:16:29.808 --> 00:16:34.743 amount of time to remove product ratings and it's not entirely
00:16:34.743 --> 00:16:35.369 removed.
00:16:35.829 --> 00:16:39.248 Essentially, it's just turned off, so if a client initially
00:16:39.248 --> 00:16:42.724 doesn't want product ratings, but then later change to their
00:16:42.724 --> 00:16:45.459 mind, it's something that is easily reversible.
00:16:47.519 --> 00:16:49.529 Next, we have our actual categories.
00:16:49.839 --> 00:16:53.438 So you can see we have our parent categories displaying
00:16:53.438 --> 00:16:57.358 here and then our plus that allows us to drill down into the
00:16:57.358 --> 00:17:00.249 child categories associated with the parent.
00:17:02.799 --> 00:17:08.944 So if you select breaks it will drill down to the uh first child
00:17:08.944 --> 00:17:14.427 category, and then as you can see, I have performance now
00:17:14.427 --> 00:17:19.059 displaying as an additional subcategory of well.
00:17:22.679 --> 00:17:22.959 Sorry.
00:17:30.639 --> 00:17:34.891 It's sorry column botching this, but it's performance just a
00:17:34.891 --> 00:17:37.539 related here is that why I'm getting.
00:17:40.199 --> 00:17:42.829 For formance, that is actually, yeah.
00:17:42.839 --> 00:17:45.409 It's one of the subcategories of automotive.
00:17:45.479 --> 00:17:50.601 So basically you have breaks applied and that's also one of
00:17:50.601 --> 00:17:51.369 the Subs.
00:17:51.379 --> 00:17:54.231 So if you wanted to pick another sub, it would replace it to like
00:17:54.231 --> 00:17:55.009 click performance.
00:17:55.519 --> 00:17:59.329 We'll test it, so we'll swap it out for that subcategory.
00:17:55.559 --> 00:17:56.859 Yeah, gotcha. OK.
00:18:01.859 --> 00:18:03.329 And then a sub category.
00:18:03.339 --> 00:18:04.199 OK, I see.
00:18:04.319 --> 00:18:04.829 Yes.
00:18:05.299 --> 00:18:09.821 So like I would say in you have your first child category and
00:18:09.821 --> 00:18:13.832 then you have your next subcategory of your previously
00:18:13.832 --> 00:18:17.915 selected and then as you continue to drill down it will
00:18:17.915 --> 00:18:22.583 update based on the additional subcategories of your previously
00:18:22.583 --> 00:18:23.749 selected filter.
00:18:25.549 --> 00:18:28.228 Yeah, that is interesting that it doesn't display exhaust and
00:18:28.228 --> 00:18:30.691 wheels when you go to breaks, but it does when you go to
00:18:30.691 --> 00:18:31.209 performance.
00:18:32.429 --> 00:18:35.408 I think that's just, you know, I think it has something to do
00:18:35.408 --> 00:18:38.338 with the relationship between the categories or the products
00:18:38.338 --> 00:18:41.077 possibly I would have to actually look into that because
00:18:41.077 --> 00:18:41.989 that's interesting.
00:18:46.479 --> 00:18:47.669 Gotcha. Alright.
00:18:47.759 --> 00:18:48.199 Let's see.
00:18:50.509 --> 00:18:55.055 So like I said earlier, with categories we can support up to
00:18:55.055 --> 00:18:56.769 7 layers of categories.
00:18:56.779 --> 00:19:00.383 Uh parent categories and subcategories within the
00:19:00.383 --> 00:19:00.959 catalog.
00:19:03.779 --> 00:19:09.076 So while we're on the topic of categories, I'd like to go to
00:19:09.076 --> 00:19:13.938 CEF admin and take a look at how we create products and
00:19:13.938 --> 00:19:16.369 categories within CEF admin.
00:19:17.859 --> 00:19:21.749 So first we're going to create a new category.
00:19:22.689 --> 00:19:26.889 Umm, so we have our category editor section.
00:19:27.189 --> 00:19:29.169 Let me go back and flicking go too fast.
00:19:29.979 --> 00:19:33.839 So the categories section here you can either create a new
00:19:33.839 --> 00:19:35.539 category or view existing.
00:19:36.809 --> 00:19:40.464 So to create a new category, you'd click the new button or go
00:19:40.464 --> 00:19:42.939 to view and then the add category button.
00:19:42.949 --> 00:19:44.839 Here in the top left.
00:19:45.409 --> 00:19:48.669 So with products and categories.
00:19:49.119 --> 00:19:53.372 UH-1 issue I guess, and it may not be as common as I think it
00:19:53.372 --> 00:19:57.076 is, but with products and categories, if you create a
00:19:57.076 --> 00:20:01.261 product within CEF and try to get that product to display on
00:20:01.261 --> 00:20:05.582 the storefront, but you do not yet have a category assigned to
00:20:05.582 --> 00:20:09.698 the product, then the product will not display in the store
00:20:09.698 --> 00:20:10.109 front.
00:20:10.979 --> 00:20:14.950 So Mickey and you may be able to correct me as something that
00:20:14.950 --> 00:20:18.984 people have struggled with that, but that is an issue that may
00:20:18.984 --> 00:20:23.083 come up as clients are creating products and wondering why they
00:20:23.083 --> 00:20:24.299 are not displaying.
00:20:24.479 --> 00:20:29.766 That could be a potential issue that they have not assigned a
00:20:29.766 --> 00:20:32.409 category to the product itself.
00:20:32.739 --> 00:20:37.983 So with category creation you can see we have our name here
00:20:37.983 --> 00:20:39.469 for our category.
00:20:40.719 --> 00:20:45.292 So we can call it, you know, test category, our display name
00:20:45.292 --> 00:20:49.640 which is going to be how the category is going to display
00:20:49.640 --> 00:20:51.289 within the storefront.
00:20:54.929 --> 00:20:56.819 And then our category key.
00:20:57.409 --> 00:21:00.189 So this is the key assigned to the category.
00:21:01.509 --> 00:21:04.239 Uh to identify the category itself.
00:21:04.769 --> 00:21:09.353 So you can just give this you know whatever category key you
00:21:09.353 --> 00:21:10.179 would like.
00:21:10.249 --> 00:21:14.698 The only option for the type is going to be general, so you
00:21:14.698 --> 00:21:19.369 would select general as the type and then we have our options.
00:21:19.439 --> 00:21:24.642 Options here for is visible this like it sounds with toggle the
00:21:24.642 --> 00:21:29.357 visibility of the category within the storefront and then
00:21:29.357 --> 00:21:32.609 include in menu is also go into effect.
00:21:32.659 --> 00:21:38.204 The category filter options within the storefront itself, so
00:21:38.204 --> 00:21:41.839 we have our basic category information.
00:21:41.849 --> 00:21:44.139 Uh, you can give a description to the category.
00:21:49.129 --> 00:21:53.248 If you would like SEO information, this is something
00:21:53.248 --> 00:21:56.589 that's typically is handled by the client.
00:21:56.959 --> 00:22:02.594 Umm, but it's something that is necessary as SEO is very
00:22:02.594 --> 00:22:08.129 important for the site performance and site visibility.
00:22:08.139 --> 00:22:13.688 Once the site is up and running and in production, so this is
00:22:13.688 --> 00:22:19.237 the basic information that is needed to create a category for
00:22:19.237 --> 00:22:20.669 the products of.
00:22:20.679 --> 00:22:24.059 I'm not going to create it as we're in the demo site.
00:22:24.069 --> 00:22:26.279 I don't want to add any junk.
00:22:26.569 --> 00:22:32.816 Umm here umm so once you enter this information you can then
00:22:32.816 --> 00:22:39.268 save your category and it will be available to assign products
00:22:39.268 --> 00:22:39.780 to O.
00:22:42.479 --> 00:22:47.732 So once you create a category, you can then create a product to
00:22:47.732 --> 00:22:50.029 assign to your new category.
00:22:53.799 --> 00:22:59.051 Within the product editor, similar to uh category, we have
00:22:59.051 --> 00:23:01.009 our basic information.
00:23:01.539 --> 00:23:07.051 So our product name and then our product SKU, a lot of the times,
00:23:07.051 --> 00:23:12.062 uh, this information is going to come from existing product
00:23:12.062 --> 00:23:15.319 records that the clients already have.
00:23:15.789 --> 00:23:19.483 In the case of a UI, we're not gonna be syncing in any
00:23:19.483 --> 00:23:23.378 products, but they'll be manually creating products based
00:23:23.378 --> 00:23:25.459 on their existing product data.
00:23:25.509 --> 00:23:29.907 So the product SKU would be something that uh usually would
00:23:29.907 --> 00:23:33.937 match up with an existing product information that the
00:23:33.937 --> 00:23:35.989 business is currently using.
00:23:36.959 --> 00:23:41.553 So once you enter that, you can continue down and you can see we
00:23:41.553 --> 00:23:44.309 have our different product types here.
00:23:45.019 --> 00:23:49.903 So we'll have general, which will be a standalone product, a
00:23:49.903 --> 00:23:55.027 kit which would include, uh, a bundle or, uh, several products,
00:23:55.027 --> 00:23:57.509 uh, within a kit or a grouping.
00:23:58.139 --> 00:24:01.299 Can you also say the drop down and no team sometimes doesn't?
00:24:00.789 --> 00:24:01.109 No.
00:24:03.169 --> 00:24:03.549 Working.
00:24:03.439 --> 00:24:04.339 Does not show.
00:24:04.799 --> 00:24:09.136 Umm, so we have general which is a standalone product to kit
00:24:09.136 --> 00:24:12.549 which would combine the products into a bundle.
00:24:12.849 --> 00:24:18.369 Uh, we have a variant which is, you know, with medication.
00:24:18.379 --> 00:24:22.897 For example, we may have Abby, Profen uh, and then you know
00:24:22.897 --> 00:24:25.909 Abby Profen, 5 milligram, 10 milligram.
00:24:26.179 --> 00:24:27.649 You know different counts.
00:24:30.389 --> 00:24:35.878 Umm for the product, so as a variant we would have our master
00:24:35.878 --> 00:24:41.366 product or master variant and then we would have sub variants
00:24:41.366 --> 00:24:42.959 of that master uh.
00:24:43.319 --> 00:24:47.468 So the different types of products that are typically
00:24:47.468 --> 00:24:51.847 used, uh, almost storefronts are gonna be the standalone
00:24:51.847 --> 00:24:55.766 products, which is just a general product and then
00:24:55.766 --> 00:25:00.068 variants which will have a variant master product and a
00:25:00.068 --> 00:25:03.909 variant of the sub variant of the master product.
00:25:06.919 --> 00:25:09.919 Short description yeah, go ahead and Mickey.
00:25:07.549 --> 00:25:13.326 And one ohh just one other thing in terms of how you can get this
00:25:13.326 --> 00:25:14.639 stuff into CEF.
00:25:14.729 --> 00:25:16.379 Obviously, Shelton talked about you.
00:25:16.389 --> 00:25:18.339 Can we can sync these things in clients?
00:25:18.349 --> 00:25:20.469 Can manually add them, but we do also have the importer.
00:25:21.569 --> 00:25:23.957 Didn't know if you were going to touch on that Shelton, but just
00:25:23.957 --> 00:25:25.499 so you know that there's lots of options.
00:25:27.899 --> 00:25:28.289 Yes.
00:25:28.299 --> 00:25:29.189 Thank you, Mickey.
00:25:29.899 --> 00:25:31.069 The product importer?
00:25:31.079 --> 00:25:33.339 Yes, that completely slipped my mind.
00:25:33.349 --> 00:25:33.809 Thank you.
00:25:34.259 --> 00:25:35.809 Yes, we'll take a look at that.
00:25:35.819 --> 00:25:37.029 And just a second.
00:25:39.609 --> 00:25:44.479 So we have our basic information here short and long description.
00:25:44.769 --> 00:25:48.362 This is gonna be the product description that displays on the
00:25:48.362 --> 00:25:48.999 storefront.
00:25:49.249 --> 00:25:53.688 If we switch back over real quick, you can see we have, you
00:25:53.688 --> 00:25:58.348 know, this description here for our Generac generator and then
00:25:58.348 --> 00:26:02.712 on the product details page, we'll have our more complete,
00:26:02.712 --> 00:26:05.449 uh, long description of the product.
00:26:06.019 --> 00:26:10.039 So on the catalog itself, the short description will display
00:26:10.039 --> 00:26:14.125 and then once we drive into the product details page is where
00:26:14.125 --> 00:26:16.959 our long description would become visible.
00:26:19.879 --> 00:26:21.709 What you enter your bicycle information?
00:26:21.719 --> 00:26:23.529 Then you can set up your pricing.
00:26:24.179 --> 00:26:29.003 As you can see, we have two different pricing options as
00:26:29.003 --> 00:26:31.119 well as a taxable toggle.
00:26:31.189 --> 00:26:34.969 UM so is taxable versus tax exempt?
00:26:34.979 --> 00:26:40.000 That would denote to itself that this product is or is not
00:26:40.000 --> 00:26:45.360 taxable, and then we have our default list based pricing which
00:26:45.360 --> 00:26:49.529 is going to be the default price of the product.
00:26:50.039 --> 00:26:52.529 And then we have our cell pricing.
00:26:52.539 --> 00:26:57.027 So if you wanted to input your product for $1000, that's
00:26:57.027 --> 00:26:59.939 typically what it is in your system.
00:27:01.139 --> 00:27:05.369 But she wanted to sell the product for $1200.
00:27:05.469 --> 00:27:06.979 Then based on the.
00:27:09.239 --> 00:27:10.289 Sell price.
00:27:10.659 --> 00:27:16.394 That's going to be what the user would be purchasing within the
00:27:16.394 --> 00:27:17.469 store front.
00:27:17.779 --> 00:27:21.249 The pricing that they would be charged within the storefront.
00:27:24.769 --> 00:27:31.914 Shipping shipping is also another important uh category of
00:27:31.914 --> 00:27:34.699 the E product creation.
00:27:35.069 --> 00:27:35.559 Umm.
00:27:36.369 --> 00:27:40.895 If the customer is using a shipping provider, integration,
00:27:40.895 --> 00:27:45.650 product weight and dimensions is something that's going to be
00:27:45.650 --> 00:27:49.945 very important to receiving those calculations from the
00:27:49.945 --> 00:27:51.709 shipping rate provider.
00:27:52.069 --> 00:27:57.048 If a customer does not have the weight and dimensions for their
00:27:57.048 --> 00:28:02.027 products at the beginning of a project and they are planning to
00:28:02.027 --> 00:28:06.772 use, uh, a shipping provider integration that product weight
00:28:06.772 --> 00:28:11.828 and dimension data is something that is going to be necessary to
00:28:11.828 --> 00:28:16.185 be able to implement that shipping provider integration
00:28:16.185 --> 00:28:17.429 for the project.
00:28:17.639 --> 00:28:23.009 That is something that is on the client to complete.
00:28:23.229 --> 00:28:27.500 Obviously, if they wanted to pay US money to get a list of their
00:28:27.500 --> 00:28:31.705 weight and dimensions and input it for their products, we would
00:28:31.705 --> 00:28:33.019 be happy to do that.
00:28:33.029 --> 00:28:36.787 But typically that responsibility is going to fall
00:28:36.787 --> 00:28:41.577 all on the client to provide us with those weight and dimensions
00:28:41.577 --> 00:28:45.556 in order to pass that to the shipping provider during
00:28:45.556 --> 00:28:49.682 checkout and return a accurate shipping rate from their
00:28:49.682 --> 00:28:51.229 integration provider.
00:28:55.249 --> 00:29:00.096 Alternatively, if a client does not have product weight and
00:29:00.096 --> 00:29:05.186 dimensions and would like to use a flat rate shipping provider
00:29:05.186 --> 00:29:09.709 for their project, that is something we can do as well.
00:29:10.709 --> 00:29:14.132 Flat rate shipping providers would be a customization that we
00:29:14.132 --> 00:29:16.119 wouldn't implement for the project.
00:29:16.129 --> 00:29:19.903 Uh, based on the shipping rates that they would like to use
00:29:19.903 --> 00:29:20.909 their checkouts.
00:29:21.189 --> 00:29:25.199 Typically these are universal for all customers and products.
00:29:25.709 --> 00:29:29.927 Flat rate shipping providers can because some US further, if the
00:29:29.927 --> 00:29:33.561 client does have additional logic during their checkout
00:29:33.561 --> 00:29:37.389 process where different users are different products could
00:29:37.389 --> 00:29:40.309 receive different flat rate shipping values.
00:29:43.679 --> 00:29:44.389 Product images.
00:29:48.849 --> 00:29:51.199 As a client, you know creates their products.
00:29:51.209 --> 00:29:54.156 They'll need to include product images if they wish to have them
00:29:54.156 --> 00:29:55.379 display on the store front.
00:29:55.639 --> 00:30:03.077 Uh, I believe that it resizes images as best it can as they're
00:30:03.077 --> 00:30:07.799 a set value call of a size restriction.
00:30:07.809 --> 00:30:09.429 I can't remember it off the top of my head.
00:30:09.359 --> 00:30:13.966 So I don't think there's a limit per se, but when you get too
00:30:13.966 --> 00:30:15.749 large it starts to well.
00:30:15.979 --> 00:30:17.409 Actually, I'm not even gonna say that.
00:30:17.639 --> 00:30:20.950 So the best practice is to upload the highest resolution
00:30:20.950 --> 00:30:21.879 picture you got.
00:30:21.889 --> 00:30:26.112 What CEF actually does is I think it produces 5 or 6
00:30:26.112 --> 00:30:30.893 thumbnails that are compressed that show up on the shopping
00:30:30.893 --> 00:30:31.689 cart page.
00:30:31.699 --> 00:30:35.202 The product details page is the small little widgets in the
00:30:35.202 --> 00:30:35.669 catalog.
00:30:35.679 --> 00:30:40.691 Basically it generates the right size image using your highest
00:30:40.691 --> 00:30:41.009 res.
00:30:41.099 --> 00:30:45.229 So the best practice is you know do like 1000 by 1000 or as high
00:30:45.229 --> 00:30:48.913 res as you want and then CEF will actually compress those
00:30:48.913 --> 00:30:52.789 down so that they populate in different parts of the catalog
00:30:52.789 --> 00:30:56.537 without having to load the entire high res picture if that
00:30:56.537 --> 00:30:57.299 makes sense.
00:31:02.379 --> 00:31:02.809 Yes.
00:31:02.449 --> 00:31:03.059 And nine.
00:31:02.819 --> 00:31:03.509 Thank you, Carl.
00:31:05.299 --> 00:31:06.019 Good, Cassie.
00:31:06.949 --> 00:31:08.499 You know, I'm just getting ahead of myself.
00:31:08.509 --> 00:31:09.769 Sorry, go ahead, Shelton.
00:31:11.439 --> 00:31:14.970 In the case of multiple product images, as you can see, I've
00:31:14.970 --> 00:31:16.069 uploaded to images.
00:31:16.079 --> 00:31:18.429 Here we have different image types.
00:31:19.189 --> 00:31:23.623 Uh product image is typically what most clients are going to
00:31:23.623 --> 00:31:27.839 use, and then we have our toggles here for primary image.
00:31:27.849 --> 00:31:32.086 Our a secondary image, so if it is a primary image, that would
00:31:32.086 --> 00:31:36.458 be the first image that would be shown on the product within the
00:31:36.458 --> 00:31:40.695 catalog and the product details page and then secondary images
00:31:40.695 --> 00:31:41.569 would follow.
00:31:44.029 --> 00:31:45.689 That main product image.
00:31:47.319 --> 00:31:48.979 Did you have another question, Cassie?
00:31:49.909 --> 00:31:53.722 That was just noticing I was trying to understand like how it
00:31:53.722 --> 00:31:57.473 was gonna be associated to the product, but I now understand
00:31:57.473 --> 00:32:01.347 you're just going through each screen that originated with the
00:32:01.347 --> 00:32:04.729 first product look with the start of the build, right?
00:32:04.109 --> 00:32:04.589 Yes.
00:32:04.599 --> 00:32:07.789 So these are all just tabs of the product editor.
00:32:08.069 --> 00:32:11.563 So if you come back to details, this is our the basic product
00:32:11.563 --> 00:32:12.239 information.
00:32:12.249 --> 00:32:16.336 And then as you proceed through the different tabs, you access
00:32:16.336 --> 00:32:19.449 different areas of information for the product.
00:32:20.099 --> 00:32:20.309 Look.
00:32:22.059 --> 00:32:24.429 So after you upload your images.
00:32:24.509 --> 00:32:24.829 Uh.
00:32:24.839 --> 00:32:26.849 Then you could come down to categories.
00:32:26.859 --> 00:32:31.299 This is where we would apply the already created categories from
00:32:31.299 --> 00:32:35.670 async are the categories that we created manually within CEF to
00:32:35.670 --> 00:32:36.489 the product.
00:32:38.029 --> 00:32:43.321 You can assign multiple categories to a product, so if
00:32:43.321 --> 00:32:49.575 you have, you know, uh, a power drill that could be considered a
00:32:49.575 --> 00:32:54.482 tool as well as a electronic or an industrial tool
00:32:54.482 --> 00:32:55.829 manufacturing.
00:32:56.069 --> 00:33:00.657 So if you have products that are associated with different
00:33:00.657 --> 00:33:05.245 categories within your business, you can't assign multiple
00:33:05.245 --> 00:33:07.889 categories to a singular product.
00:33:15.389 --> 00:33:20.153 Also, you have the ability to associate one product to
00:33:20.153 --> 00:33:25.524 another, so if you are creating a product, uh, let's say that
00:33:25.524 --> 00:33:27.169 you're going to uh.
00:33:31.029 --> 00:33:36.159 Going to be selling a power cable for a laptop and you want
00:33:36.159 --> 00:33:41.459 people to know, you know, this power cable goes to this Acer.
00:33:43.789 --> 00:33:48.252 17 inch gaming laptop you can add that as an associated
00:33:48.252 --> 00:33:48.889 product.
00:33:49.619 --> 00:33:50.139 Uh.
00:33:50.859 --> 00:33:55.409 Within the editor and if we navigate to the product details
00:33:55.409 --> 00:33:59.352 page you can see that the associated products would
00:33:59.352 --> 00:34:03.219 display at the bottom of the product details page.
00:34:03.229 --> 00:34:06.219 So Apple iPhone, obviously it's the cell phone.
00:34:06.229 --> 00:34:09.657 And then we're also selling a Samsung, which is also a cell
00:34:09.657 --> 00:34:09.999 phone.
00:34:10.149 --> 00:34:13.789 So this would be a related product to the iPhone.
00:34:17.679 --> 00:34:19.829 Next section is gonna be inventory.
00:34:20.199 --> 00:34:24.813 So inventory has a couple of different areas that you can
00:34:24.813 --> 00:34:25.369 modify.
00:34:25.429 --> 00:34:26.979 You can change your unit of measure.
00:34:28.459 --> 00:34:28.949 Umm.
00:34:29.579 --> 00:34:34.639 Typically it's gonna be each stock quantity you can enter in
00:34:34.639 --> 00:34:36.629 a custom stock quantity.
00:34:36.639 --> 00:34:40.551 If you would like to have counted quantity, you have the
00:34:40.551 --> 00:34:43.089 ability to change that to unlimited.
00:34:44.459 --> 00:34:48.617 If you change a product inventory value to unlimited,
00:34:48.617 --> 00:34:53.545 then the stock quantity is not something that's going to affect
00:34:53.545 --> 00:34:58.549 the availability of the product on the storefront and will allow
00:34:58.549 --> 00:35:02.784 for users to continue to purchase that product without
00:35:02.784 --> 00:35:06.479 any worry of the product becoming out of stock.
00:35:06.689 --> 00:35:13.164 However, if a client is using stock quantities, we do have the
00:35:13.164 --> 00:35:17.789 ability to set a product as back, orderable.
00:35:18.199 --> 00:35:24.313 What that does is allows for the product to be purchased when the
00:35:24.313 --> 00:35:30.056 stock quantity has reached 0, but it will not be filled until
00:35:30.056 --> 00:35:36.169 the product is back in stock and we'll switch back here and let's
00:35:36.169 --> 00:35:39.689 see if we can find a product that is.
00:35:43.729 --> 00:35:45.159 We'll just do this book here.
00:35:45.169 --> 00:35:47.279 So you can say we have three left in stock.
00:35:47.989 --> 00:35:51.975 If I try to add 4 to my cart so you can see and this is
00:35:51.975 --> 00:35:55.605 something that is not backorderable so I would get
00:35:55.605 --> 00:35:59.519 this message that I cannot order four of this product.
00:35:59.529 --> 00:36:03.479 But if I go back to three then it will place it into the cart.
00:36:04.129 --> 00:36:05.749 If I go back to the catalog.
00:36:08.509 --> 00:36:09.459 And.
00:36:15.799 --> 00:36:20.749 Do you know if we have the is back orderable on here?
00:36:20.759 --> 00:36:22.589 Cause a filter or no?
00:36:23.869 --> 00:36:27.439 No, that's usually something custom that people request.
00:36:27.449 --> 00:36:28.679 Uh, there's no filter.
00:36:27.629 --> 00:36:28.029 Gotcha.
00:36:28.689 --> 00:36:32.184 Yeah, it would be nice cuz I imagine we always get that
00:36:32.184 --> 00:36:36.052 request of can I filter by only products that are in stock or
00:36:36.052 --> 00:36:39.858 you know, can I just see the products that are on back order
00:36:39.858 --> 00:36:42.229 or you know uh so on and so forth so.
00:36:44.339 --> 00:36:45.239 Those are custom though.
00:36:44.739 --> 00:36:47.659 You don't happen to know product off the top of your head?
00:36:47.669 --> 00:36:49.929 That's back orderable, do you?
00:36:49.739 --> 00:36:51.349 Uh, I don't.
00:36:50.039 --> 00:36:50.599 Let's see.
00:36:51.359 --> 00:36:52.389 I usually just uh.
00:36:52.399 --> 00:36:55.547 If you do your show size to 27 and you just kind of start
00:36:55.547 --> 00:36:58.369 flipping through them, you might be able to find 1.
00:37:05.789 --> 00:37:06.869 Let's just try the.
00:37:07.129 --> 00:37:08.439 Oh, this is on B2B.
00:37:08.449 --> 00:37:11.254 Ron usually keeps this one pretty up to date with a lot of
00:37:11.254 --> 00:37:11.729 inventory.
00:37:14.459 --> 00:37:14.629 Yeah.
00:37:14.639 --> 00:37:15.069 There you go.
00:37:15.119 --> 00:37:16.019 That's way to do it.
00:37:15.239 --> 00:37:15.669 Yeah.
00:37:15.719 --> 00:37:20.062 So so if a product has been set to be back orderable, then if
00:37:20.062 --> 00:37:24.195 you try to uh, add more than what's available in the stock
00:37:24.195 --> 00:37:28.398 quantity to your cart, you'll receive this message that the
00:37:28.398 --> 00:37:30.849 sales quantity of 20 will convert.
00:37:30.859 --> 00:37:34.619 It will be converted to a normal cells quantity of 15, which
00:37:34.619 --> 00:37:38.440 means once I place my order the 15 that are available will be
00:37:38.440 --> 00:37:42.385 sent to fulfillment immediately and that I will have a quantity
00:37:42.385 --> 00:37:45.836 of five that are on back order for my order and will be
00:37:45.836 --> 00:37:48.979 fulfilled once the product comes back and stopped.
00:37:51.049 --> 00:37:53.984 If you have an item on back order within your cart, you'll
00:37:53.984 --> 00:37:54.829 see this message.
00:37:54.839 --> 00:37:58.684 Here you'll see the quantity for the order line item, and then
00:37:58.684 --> 00:38:02.224 you'll have your identifier of the number of back ordered
00:38:02.224 --> 00:38:04.299 products that will display below.
00:38:10.039 --> 00:38:14.309 Vendors will skip over this one for now.
00:38:14.499 --> 00:38:20.472 We'll do a separate training on stores, vendors and some more
00:38:20.472 --> 00:38:24.229 advanced areas of CEF at a later date.
00:38:24.279 --> 00:38:28.161 Uh, the last common area for products is gonna be our product
00:38:28.161 --> 00:38:28.849 attributes.
00:38:30.319 --> 00:38:35.694 So as you can see, we have items such as material color is
00:38:35.694 --> 00:38:40.977 digital download, so you know your basic size, your basic
00:38:40.977 --> 00:38:42.799 product information.
00:38:42.809 --> 00:38:48.315 So if I'm selling AT shirt, so multiple T-shirts, red, blue and
00:38:48.315 --> 00:38:53.390 white, and I'm making my red T shirt product, then I could
00:38:53.390 --> 00:38:58.896 assign the color attribute to be red and then if I come back to
00:38:58.896 --> 00:39:04.229 the catalog here you can see within my attributes I have size
00:39:04.229 --> 00:39:05.949 brand where's color.
00:39:12.119 --> 00:39:17.064 I guess we have no color attributes, but as you can see I
00:39:17.064 --> 00:39:18.939 have my material size.
00:39:22.939 --> 00:39:26.937 Attributes here and based on the attributes of my products that
00:39:26.937 --> 00:39:27.749 are assigned.
00:39:29.989 --> 00:39:33.999 Within CEF Admin I have my different size options here.
00:39:34.009 --> 00:39:40.211 So if I'm looking for uh, a 16 ounce 5 gallon uh bucket set, I
00:39:40.211 --> 00:39:46.412 could filter by that attribute specifically and attributes can
00:39:46.412 --> 00:39:49.759 be assigned to multiple products.
00:39:50.389 --> 00:39:56.196 So if I have a more generic attribute of no just found a
00:39:56.196 --> 00:39:58.029 good example here.
00:40:01.829 --> 00:40:02.679 Uh brand.
00:40:02.689 --> 00:40:06.759 So you know, I have 28 Nike products on my storefront.
00:40:06.889 --> 00:40:11.258 UH-28 products would have the attribute of Nike assigned as
00:40:11.258 --> 00:40:15.481 the brand, so you can have multiple products assigned and
00:40:15.481 --> 00:40:16.209 attribute.
00:40:17.189 --> 00:40:21.200 And as you assign that same attribute to multiple products,
00:40:21.200 --> 00:40:25.344 then that this number here would continue to grow and you can
00:40:25.344 --> 00:40:28.419 also assign multiple attributes to a product.
00:40:28.889 --> 00:40:33.996 So attributes are something that are configurable by the client
00:40:33.996 --> 00:40:38.623 within CEF admin requires no special implementation, it's
00:40:38.623 --> 00:40:43.171 something that can be created and edited directly within
00:40:43.171 --> 00:40:43.729 itself.
00:40:43.739 --> 00:40:44.139 Admin.
00:40:45.779 --> 00:40:48.949 So let's switch over to attributes.
00:40:49.039 --> 00:40:49.529 Uh.
00:40:49.669 --> 00:40:52.576 Or before I go, is there any questions about anything with
00:40:52.576 --> 00:40:53.019 products?
00:40:58.539 --> 00:40:59.179 I don't think so.
00:41:00.509 --> 00:41:01.219 Perfect.
00:41:01.309 --> 00:41:01.859 All right.
00:41:01.869 --> 00:41:04.129 So we'll take a look at an attribute.
00:41:05.919 --> 00:41:09.949 So with attributes we have the ability to create.
00:41:12.379 --> 00:41:15.159 Several different scenarios for our attributes.
00:41:19.639 --> 00:41:22.609 Are naming convention display naming key?
00:41:22.619 --> 00:41:27.904 This will all be something custom entered by the user
00:41:27.904 --> 00:41:32.699 during attribute creation, and then our toggles.
00:41:32.709 --> 00:41:35.479 Here you can say we have hide from storefront.
00:41:35.489 --> 00:41:37.379 This is as it sounds.
00:41:37.389 --> 00:41:41.151 If this is selected from as yes, this attribute won't display in
00:41:41.151 --> 00:41:42.019 the storefront.
00:41:42.409 --> 00:41:43.939 Hide from catalog views.
00:41:43.949 --> 00:41:47.959 Same thing, it will be hidden from the storefront.
00:41:48.129 --> 00:41:50.299 Is a filter, yes or no?
00:41:50.309 --> 00:41:54.823 This can be assigned to an attribute on a product, but it
00:41:54.823 --> 00:41:59.415 can be removed as a filtering option within the storefront
00:41:59.415 --> 00:41:59.959 itself.
00:42:00.029 --> 00:42:03.977 It will still be an attribute on the product, but it won't be
00:42:03.977 --> 00:42:07.924 something that will appear in our attribute filtering list on
00:42:07.924 --> 00:42:10.789 the left side of the page is comparable, uh.
00:42:10.799 --> 00:42:15.211 So this would allow for the attribute to be something that
00:42:15.211 --> 00:42:18.949 is compared against where that multiple products.
00:42:18.959 --> 00:42:26.633 So if I go back to the catalog here and I want to compare this
00:42:26.633 --> 00:42:31.139 generator against uh this shoe tree.
00:42:34.949 --> 00:42:37.049 And I'll take a look at the products here.
00:42:38.639 --> 00:42:42.892 If I create an attribute that I do not want to display on this
00:42:42.892 --> 00:42:43.769 compare list.
00:42:43.819 --> 00:42:48.783 Uh, you would use the as comparable toggle, selected as
00:42:48.783 --> 00:42:49.049 no.
00:42:49.099 --> 00:42:53.766 If it's not something that's gonna be comparable, or yes, if
00:42:53.766 --> 00:42:58.356 it is an attribute that you would like to have displayed on
00:42:58.356 --> 00:43:02.869 the comparison screen here, hide from product detail view.
00:43:02.879 --> 00:43:06.848 Same thing if you don't want this attribute to display on the
00:43:06.848 --> 00:43:10.817 product details page, then you could select this no or if you
00:43:10.817 --> 00:43:14.529 would like to display select yes it's product detail tab.
00:43:14.739 --> 00:43:21.234 So let's go back real quick to the attributes and we will look
00:43:21.234 --> 00:43:27.935 at one of these and change that toggle and we can take a look at
00:43:27.935 --> 00:43:28.759 it this.
00:43:37.919 --> 00:43:40.679 As a product detail.
00:43:42.969 --> 00:43:43.569 Tab.
00:43:50.069 --> 00:43:50.339 Ohly.
00:43:56.949 --> 00:44:01.739 Do I need to index the products call for it to update?
00:44:02.929 --> 00:44:10.303 Yes, actually, if you go into the site maintenance, if you go
00:44:03.089 --> 00:44:03.619 Most likely.
00:44:10.303 --> 00:44:16.369 up to the top and down to yeah, go to clear cache.
00:44:16.379 --> 00:44:23.199 Well yeah, index products, but there's also if you go to your
00:44:23.199 --> 00:44:29.689 caches and you Scroll down to products, I believe there is
00:44:29.689 --> 00:44:30.129 one.
00:44:32.649 --> 00:44:34.279 Ohh, I'd like go up to a.
00:44:34.369 --> 00:44:35.309 It's an attributes.
00:44:36.689 --> 00:44:37.349 I think there is.
00:44:37.359 --> 00:44:41.899 Yeah, there's uh, attribute types, general attributes.
00:44:42.259 --> 00:44:43.429 Attribute tabs.
00:44:42.389 --> 00:44:43.199 I just.
00:44:43.549 --> 00:44:45.899 Yeah, just a be safe.
00:44:46.249 --> 00:44:49.609 I always clear those just to make sure as well as index
00:44:49.609 --> 00:44:50.149 products.
00:44:50.159 --> 00:44:52.914 Pretty much any caches that are associated with what you're
00:44:52.609 --> 00:44:56.759 And I'm gonna jump in here if you don't mind showing.
00:44:52.914 --> 00:44:53.189 doing.
00:44:54.009 --> 00:44:54.959 I usually do those.
00:44:56.769 --> 00:44:57.679 Can you go back where you were?
00:44:57.189 --> 00:44:59.059 Umm yes.
00:44:58.719 --> 00:45:00.289 I love showing this trick.
00:45:00.379 --> 00:45:03.109 Click other tasks right where you are site maintenance.
00:45:03.119 --> 00:45:05.259 Other tasks should have very bottom.
00:45:05.269 --> 00:45:08.264 It says that it has translation issue right now, but says
00:45:08.264 --> 00:45:10.949 caching it will use this usually say cache counter.
00:45:11.479 --> 00:45:14.349 If you click that, it will bust all of the caches.
00:45:14.519 --> 00:45:17.111 This is a great trick to teach your clients if they are having
00:45:17.111 --> 00:45:19.704 trouble with indexing products and having them not show on the
00:45:19.704 --> 00:45:19.909 site.
00:45:19.979 --> 00:45:22.189 This will ensure that that is not an issue.
00:45:22.949 --> 00:45:24.509 Ohh I didn't even know about that.
00:45:24.519 --> 00:45:24.979 That's new.
00:45:24.859 --> 00:45:26.299 Yes, it's lovely.
00:45:25.289 --> 00:45:26.239 Is the new guy?
00:45:26.649 --> 00:45:27.479 Yeah, this is.
00:45:27.409 --> 00:45:31.346 By default, the cache is set to expire every two hours, so it
00:45:27.489 --> 00:45:29.789 Uh 20232.
00:45:31.346 --> 00:45:35.156 would be like 2 hours before it would expire, and so people
00:45:35.156 --> 00:45:37.759 don't think the changes working usually.
00:45:38.129 --> 00:45:40.989 So that's that's a good suggestion making that's I do
00:45:39.029 --> 00:45:41.729 You get a lot of UAT feedback there.
00:45:40.989 --> 00:45:42.419 that exact same thing. Yep.
00:45:43.089 --> 00:45:43.689 Is that right?
00:45:43.699 --> 00:45:46.369 Now that you've found that out on today, alright.
00:45:47.329 --> 00:45:49.884 I probably not the first time, but it's the most recent time
00:45:49.884 --> 00:45:50.889 I've had to use it, yes.
00:45:54.799 --> 00:46:00.676 So after those steps you can now see is digital download is a uh
00:46:00.676 --> 00:46:03.569 tab on our product details page.
00:46:03.899 --> 00:46:08.104 So if a client wishes to add additional tabs to their product
00:46:08.104 --> 00:46:12.105 details page, they can generate the attributes and use the
00:46:12.105 --> 00:46:12.579 toggle.
00:46:17.529 --> 00:46:22.616 Toggle here of is product detail tab to have that information
00:46:22.616 --> 00:46:27.620 display and let me turn this off before I forget and it's up
00:46:27.620 --> 00:46:31.229 there and Ron is not happy that it's there.
00:46:36.629 --> 00:46:37.089 All right.
00:46:42.639 --> 00:46:46.610 We also have the option for predefined attributes within
00:46:46.610 --> 00:46:50.999 CEF, so if you have an attribute for your products that you're
00:46:50.999 --> 00:46:55.389 using frequently and you want it to have a predefined value so
00:46:55.389 --> 00:46:59.290 your administrators do not create the wrong value for a
00:46:59.290 --> 00:47:01.519 product, you have the option to.
00:47:04.079 --> 00:47:07.789 You have the option to, uh.
00:47:08.559 --> 00:47:09.209 Add the.
00:47:13.909 --> 00:47:16.399 Add the predefined values to your.
00:47:19.519 --> 00:47:19.979 Umm.
00:47:20.859 --> 00:47:22.769 Attribute and let me just save that.
00:47:22.779 --> 00:47:26.861 OK, so if you turn on is predefined, yes you have the
00:47:26.861 --> 00:47:29.129 option to save the value here.
00:47:29.339 --> 00:47:35.107 So if you have a yes or no, uh option for an attribute is this
00:47:35.107 --> 00:47:35.839 product.
00:47:35.889 --> 00:47:38.139 Uh digital download is this product?
00:47:38.149 --> 00:47:41.109 Uh blue is this product red?
00:47:41.119 --> 00:47:41.889 Yes or no.
00:47:41.899 --> 00:47:43.139 You can save your values.
00:47:45.369 --> 00:47:49.409 And then that will be a value on the attribute.
00:47:49.749 --> 00:47:56.154 So if I go back to my attribute list here and I find my test
00:47:56.154 --> 00:47:57.309 attributes.
00:48:01.049 --> 00:48:05.779 You can see that the predefined option is now selected.
00:48:05.789 --> 00:48:07.529 You can see that it's also hidden.
00:48:10.729 --> 00:48:13.789 And OK, what am I missing?
00:48:29.939 --> 00:48:36.882 And each time the attributes UM is assigned to the product, uh,
00:48:36.882 --> 00:48:43.717 the predetermined value of yes will be used and let me go back
00:48:43.717 --> 00:48:47.839 and add another predetermined option.
00:48:48.309 --> 00:48:49.119 I'm on the wrong one.
00:48:51.009 --> 00:48:52.569 Let's see test.
00:48:56.619 --> 00:49:00.471 So if I want to add a second option of no, I can add that
00:49:00.471 --> 00:49:01.799 option here as well.
00:49:10.429 --> 00:49:16.319 And within my test attribute, I'll now have the predetermined
00:49:16.319 --> 00:49:18.219 values of yes or no.
00:49:18.789 --> 00:49:25.039 So within the catalog, if we go back to our attributes.
00:49:27.199 --> 00:49:32.653 And I, uh selected my test attribute for example with the
00:49:32.653 --> 00:49:35.849 predetermined value of yes or no.
00:49:35.859 --> 00:49:42.266 That would be my only options as a selectable attribute on the
00:49:42.266 --> 00:49:43.079 product.
00:49:49.579 --> 00:49:52.369 Alright, so let me delete this.
00:49:54.889 --> 00:49:57.049 So any questions about attributes?
00:50:03.339 --> 00:50:03.579 Nope.
00:50:05.809 --> 00:50:11.316 Alright, so moving back to the catalog, uh products, categories
00:50:11.316 --> 00:50:16.736 and attributes are gonna be the most common functionality used
00:50:16.736 --> 00:50:19.059 by client within SEF admin.
00:50:19.409 --> 00:50:23.982 Along with creating users and accounts, so back to the
00:50:23.982 --> 00:50:27.639 catalog, we'll now take a look at checkout.
00:50:27.689 --> 00:50:32.813 So within checkout we have some different capabilities for the
00:50:32.813 --> 00:50:33.219 user.
00:50:33.689 --> 00:50:39.257 We have what we call target shipping, which allows for the
00:50:39.257 --> 00:50:44.825 user to select a different shipping location for different
00:50:44.825 --> 00:50:48.599 products within the within their order.
00:50:48.609 --> 00:50:52.898 So you can see I have uh drop down and I guess you can't see
00:50:52.898 --> 00:50:56.836 the drop down, but there's different addresses that are
00:50:56.836 --> 00:51:01.054 currently within my address book that allow me to select my
00:51:01.054 --> 00:51:02.179 desired address.
00:51:02.449 --> 00:51:07.293 So if I have this iPhone needs to go to my grandma at 300 N
00:51:07.293 --> 00:51:12.460 Lamar St and I need this, this book shipped to my house, then I
00:51:12.460 --> 00:51:16.819 can select those different shipped to locations here.
00:51:16.829 --> 00:51:21.351 At this step, additionally, if I have just a single address
00:51:21.351 --> 00:51:26.099 within my address book, but I need to add another to ship this
00:51:26.099 --> 00:51:30.771 product to the user can quickly add a new address here and it
00:51:30.771 --> 00:51:33.559 will be saved to their address book.
00:51:35.159 --> 00:51:36.769 I'm going to interrupt again.
00:51:36.879 --> 00:51:40.209 This is another great place that has tripped us up recently.
00:51:40.219 --> 00:51:43.205 We've had a fair number of clients that did not realize
00:51:43.205 --> 00:51:46.030 until late on in the process that target shipping is
00:51:46.030 --> 00:51:47.309 something that's offers.
00:51:47.579 --> 00:51:51.053 So just always making sure that you're talking about this with
00:51:51.053 --> 00:51:51.769 your clients.
00:51:51.859 --> 00:51:54.909 A Shelton and discovery, making sure he's really making sure
00:51:54.909 --> 00:51:57.959 they see this rather than just tuning out while he's talking
00:51:57.959 --> 00:51:58.409 about it.
00:51:58.479 --> 00:52:01.539 But for us to as PMS just making sure that we're like, OK, so you
00:52:01.539 --> 00:52:03.439 know, how does this work in your system?
00:52:03.449 --> 00:52:04.609 Where is this mapping?
00:52:04.699 --> 00:52:06.885 How are you guys handling multiple shipping addresses
00:52:06.885 --> 00:52:09.475 early on in the projects, we can get ahead of them calling that
00:52:09.475 --> 00:52:10.689 out three weeks before launch.
00:52:13.319 --> 00:52:15.869 Saying be quiet now.
00:52:15.519 --> 00:52:15.989 Yes.
00:52:15.999 --> 00:52:17.559 Thank you, Mickey. Perfect.
00:52:17.289 --> 00:52:20.733 As and on that same thought, though, with that, because this
00:52:20.733 --> 00:52:24.291 is kind of what sets us apart from the Shopify's and the likes
00:52:24.291 --> 00:52:27.791 of those and definitely we're much more like be to be focused
00:52:25.909 --> 00:52:27.209 So that's what I like to hear.
00:52:27.791 --> 00:52:31.066 right, you know like you're sure you'll see both kinds of
00:52:31.066 --> 00:52:34.623 clients, the ones who do just want like I just want them to be
00:52:34.623 --> 00:52:35.639 able to check out.
00:52:36.739 --> 00:52:38.029 It's like, yeah, we get that.
00:52:38.039 --> 00:52:40.159 But this is something that makes us a little different.
00:52:40.169 --> 00:52:42.369 And you know, bring up on your customers.
00:52:42.379 --> 00:52:45.079 This might be something that's really advantageous for them.
00:52:46.159 --> 00:52:48.839 And so that is out of the box the split ship.
00:52:50.779 --> 00:52:53.929 Yes, entirely out of the box.
00:52:55.049 --> 00:52:55.209 It's.
00:52:57.769 --> 00:53:01.839 And then as you can see here, we have our quantity selectors.
00:53:01.889 --> 00:53:04.339 Are these meant to be turned off as are?
00:53:04.349 --> 00:53:05.279 Is that a bug?
00:53:05.289 --> 00:53:06.859 Call for the demo site.
00:53:10.339 --> 00:53:11.189 Which do you talk about?
00:53:11.689 --> 00:53:13.059 The quantity selectors.
00:53:14.309 --> 00:53:17.459 Oh well, you have to split it first.
00:53:20.069 --> 00:53:22.906 Yet to place the plus button version, do you have to have
00:53:22.906 --> 00:53:24.079 another line item first?
00:53:24.649 --> 00:53:25.849 Ah, OK.
00:53:25.199 --> 00:53:26.789 Then you can start.
00:53:26.839 --> 00:53:27.189 Yeah.
00:53:27.199 --> 00:53:29.319 Breaking it out into into two, there you go.
00:53:30.289 --> 00:53:30.899 Gotcha.
00:53:30.939 --> 00:53:35.953 So you can't modify your actual total number here from your
00:53:35.399 --> 00:53:36.989 No, that's just your cart total.
00:53:35.953 --> 00:53:37.039 card. Gotcha.
00:53:36.999 --> 00:53:39.530 If there's only if you're only shipping it to one place, that's
00:53:39.530 --> 00:53:41.784 just the total that's in your cart, and you can't really
00:53:41.784 --> 00:53:42.179 modify it.
00:53:42.189 --> 00:53:45.237 Those quantity selectors only work if you're shipping to
00:53:45.237 --> 00:53:47.269 multiple addresses for one line item.
00:53:48.069 --> 00:53:48.469 Gotcha.
00:53:50.489 --> 00:53:53.079 We are all learning today me as well.
00:53:53.189 --> 00:53:53.789 Thank you, Kyle.
00:53:54.309 --> 00:53:55.919 Umm, alright, So what?
00:53:55.929 --> 00:53:59.780 You make your shipping selections, then we would
00:53:59.780 --> 00:54:04.259 proceed to our shipping rate quotes section of checkout.
00:54:04.349 --> 00:54:08.753 This is where the shipping provider integration would be
00:54:08.753 --> 00:54:13.003 utilized, or if a client is using a flat rate shipping
00:54:13.003 --> 00:54:17.562 method, we would display the products as you see here they
00:54:17.562 --> 00:54:21.579 are, uh broken up based on their ship to locations.
00:54:22.199 --> 00:54:25.772 So you can see this ones going to one address and then my
00:54:25.772 --> 00:54:28.359 iPhones are going to a different address.
00:54:28.599 --> 00:54:33.157 So I'm returned rates for this product to this address and then
00:54:33.157 --> 00:54:36.789 this separate product go into a different address.
00:54:37.089 --> 00:54:41.534 I would also be returned the rights to ship here as well,
00:54:41.534 --> 00:54:45.596 even with flat rate if I'm shipping to two different
00:54:45.596 --> 00:54:50.041 locations, I would be charged the flat rate value for the
00:54:50.041 --> 00:54:53.259 different addresses that I'm shipping to.
00:54:53.569 --> 00:54:58.243 So if for example we were using flat rate, it might just say you
00:54:58.243 --> 00:55:02.773 know standard shipping flat rate shipping whatever wording the
00:55:02.773 --> 00:55:07.303 client wants to go with and we would have our value displaying
00:55:07.303 --> 00:55:11.402 as well once you make your selection, you can see in the
00:55:11.402 --> 00:55:15.501 top right here in my order summary that my shipping rate
00:55:15.501 --> 00:55:18.089 has updated based on my selections.
00:55:19.869 --> 00:55:25.178 If I increase my speed and up my price, it will update here as
00:55:25.178 --> 00:55:25.599 well.
00:55:26.169 --> 00:55:32.054 One thing that we also can do, it would be a customization but
00:55:32.054 --> 00:55:37.285 with shipping provider integrations we can control what
00:55:37.285 --> 00:55:39.059 rates are returned.
00:55:39.449 --> 00:55:43.409 If you're familiar with Nat, then you know that for their
00:55:43.409 --> 00:55:47.504 shipping provider integration, we're only returning certain
00:55:47.504 --> 00:55:49.279 shipping provider options.
00:55:50.129 --> 00:55:54.747 So if a client only wanted UPS ground or UPS second day air, we
00:55:54.747 --> 00:55:59.149 could restrict what's returned from the shipping provider to
00:55:59.149 --> 00:56:03.622 only be those two values here and those would be the only two
00:56:03.622 --> 00:56:07.879 values that are available to the customer during checkout.
00:56:12.319 --> 00:56:15.189 So next step is going to be payment.
00:56:15.519 --> 00:56:19.958 So this is something that is very important to ensure that we
00:56:19.958 --> 00:56:24.038 have the information from the client about the different
00:56:24.038 --> 00:56:28.620 payment methods that are gonna be available on the site as well
00:56:28.620 --> 00:56:32.772 as the different scenarios to which these payment methods
00:56:32.772 --> 00:56:35.349 would be available to the customer.
00:56:36.759 --> 00:56:40.877 For example, we may have different account types such as
00:56:40.877 --> 00:56:44.560 B to B&B to CB to C customers may only receive
00:56:44.560 --> 00:56:49.328 credit card payment options that check out, while B to B may have
00:56:49.328 --> 00:56:52.289 the option for invoices and credit card.
00:56:53.039 --> 00:56:58.215 ACH is something that we do offer out of the box, but it is
00:56:58.215 --> 00:57:03.649 important to to note that if the client is wishing to use ACH,
00:57:03.649 --> 00:57:09.083 that that is something that we are aware of to ensure that ACH
00:57:09.083 --> 00:57:11.239 is functioning correctly.
00:57:13.069 --> 00:57:17.512 So with the different out of the box options that you see here,
00:57:17.512 --> 00:57:21.955 ACH credit card invoicing quote me the first three options, ACH
00:57:21.955 --> 00:57:25.842 credit card and invoice would allow you to complete the
00:57:25.842 --> 00:57:28.549 checkout process and place your order.
00:57:28.979 --> 00:57:33.274 The fourth option of quote me, what it does is essentially
00:57:33.274 --> 00:57:37.786 takes the line items that you currently have in your cart and
00:57:37.786 --> 00:57:42.372 you've proceeded to check out with and we'll convert them to a
00:57:42.372 --> 00:57:44.919 quote rather than an actual order.
00:57:44.989 --> 00:57:49.770 So once that an order is converted to a quote, it will be
00:57:49.770 --> 00:57:53.479 submitted to SEV as a quote and not a order.
00:57:54.049 --> 00:57:57.829 So we'll take a look at the quote process and just a moment.
00:57:59.729 --> 00:58:05.689 So with our payment methods, we have ACH, credit card and
00:58:05.689 --> 00:58:12.162 invoice and ACH is not giving me the option to select my saved
00:58:12.162 --> 00:58:15.039 ache payments for my wallet.
00:58:15.109 --> 00:58:21.724 But if we switch to credit card, you can see we have our default
00:58:21.724 --> 00:58:24.369 payment method displaying.
00:58:24.379 --> 00:58:29.891 Here I do have the option to change to a new payment method
00:58:29.891 --> 00:58:35.220 from my wallet as well as adding a new credit card within
00:58:35.220 --> 00:58:40.916 checkout itself and the CVV is required each time at checkout
00:58:40.916 --> 00:58:46.979 and ordered to process the order and process the payment with the
00:58:46.979 --> 00:58:47.989 CEF wallet.
00:58:48.079 --> 00:58:53.756 We do not store full credit card numbers or information with the
00:58:53.756 --> 00:58:58.909 payment provider being used for the project on first time.
00:59:00.179 --> 00:59:02.709 Uh entry of the payment method.
00:59:02.899 --> 00:59:06.017 We passed the payment information to the payment
00:59:06.017 --> 00:59:06.589 provider.
00:59:06.859 --> 00:59:11.033 The payment provider would then return a token for the payment
00:59:11.033 --> 00:59:15.141 method and we would store that token within self and use that
00:59:15.141 --> 00:59:16.929 to process future payments.
00:59:17.209 --> 00:59:21.614 So if a client asks about security around credit card
00:59:21.614 --> 00:59:26.427 information and stuff, we are not storing full credit card
00:59:26.427 --> 00:59:27.079 details.
00:59:27.089 --> 00:59:31.291 We are using the token provided by the payment provider to
00:59:31.291 --> 00:59:34.139 securely store credit card information.
00:59:39.279 --> 00:59:43.759 Invoices so and voices are another way to pay.
00:59:44.929 --> 00:59:49.967 So if a customer uh chooses to pay via invoice out of box, we
00:59:49.967 --> 00:59:52.079 require a PO number field.
00:59:52.089 --> 00:59:56.355 Here some clients will ask for this to be an optional field or
00:59:56.355 --> 00:59:57.709 be removed entirely.
00:59:58.169 --> 01:00:03.878 But if a invoice payment option is used during checkout upon
01:00:03.878 --> 01:00:09.774 checkout completion, we would generate the sales order as well
01:00:09.774 --> 01:00:12.769 as the invoice for the customer.
01:00:13.099 --> 01:00:19.066 The invoice would be created with an outstanding balance and
01:00:19.066 --> 01:00:25.326 would be required to be paid by the customer based on the terms
01:00:25.326 --> 01:00:31.489 and agreements with the company or with the client with credit
01:00:31.489 --> 01:00:37.945 card payments upon check out, we create these cells order as well
01:00:37.945 --> 01:00:41.759 as an invoice with the status of paid.
01:00:41.829 --> 01:00:47.245 So if you submit an order, we create an invoice that's already
01:00:47.245 --> 01:00:52.059 been paid because we are capturing funds at the time of
01:00:52.059 --> 01:00:56.959 checkout using the credit card on file for the customer.
01:00:59.859 --> 01:01:05.198 Any questions about any of that and we'll take a look at the uh
01:01:05.198 --> 01:01:06.449 quotes process.
01:01:11.149 --> 01:01:11.599 None for me.
01:01:13.769 --> 01:01:14.499 Perfect.
01:01:14.589 --> 01:01:22.134 Alright, so with quotes quotes I'm sure you are familiar with
01:01:22.134 --> 01:01:22.499 us.
01:01:22.509 --> 01:01:27.634 I won't talk about it like you have no idea what a quote is,
01:01:27.634 --> 01:01:32.675 but similar to checkout we have the option to, uh, have our
01:01:32.675 --> 01:01:34.019 target shipping.
01:01:34.169 --> 01:01:34.799 Uh.
01:01:35.049 --> 01:01:39.281 Use our shipping rate quotes through the provider or through
01:01:39.281 --> 01:01:40.599 flat rate shipping.
01:01:40.609 --> 01:01:44.833 That's been configured for the project so as I proceed there my
01:01:44.833 --> 01:01:45.889 quote check out.
01:01:45.899 --> 01:01:51.369 It operates very similar to normal checkout, just without
01:01:51.369 --> 01:01:54.009 the need for a payment step.
01:01:55.959 --> 01:01:57.949 So once you submit your quotes.
01:02:01.919 --> 01:02:05.598 You'll get a notification for your master quote number and
01:02:05.598 --> 01:02:06.969 your sub quote number.
01:02:07.399 --> 01:02:10.877 So we'll come over to Seth and take a look at this new lease
01:02:10.877 --> 01:02:11.789 submitted quote.
01:02:22.739 --> 01:02:27.694 So as you can see I have my order linite our product line
01:02:27.694 --> 01:02:32.819 item from my quote displaying here and at the bottom of the
01:02:32.819 --> 01:02:38.115 page we have our quote actions button which is how the client
01:02:38.115 --> 01:02:43.326 admin would essentially progress the quote through the quote
01:02:43.326 --> 01:02:44.009 process.
01:02:44.059 --> 01:02:47.959 So you can see this is begin processing of our quote.
01:02:52.909 --> 01:02:57.811 Once the quote has entered the processing status, then the next
01:02:57.811 --> 01:03:01.869 status it'll be available is the ready for approval.
01:03:04.389 --> 01:03:10.495 Once you mark it as ready for approval, I as a customer that's
01:03:10.495 --> 01:03:16.213 submitted the quote can return to my user dashboard and my
01:03:16.213 --> 01:03:17.569 quote section.
01:03:18.059 --> 01:03:21.636 And as you can see my most recent quote now has the status
01:03:21.636 --> 01:03:22.969 of ready for approval.
01:03:23.519 --> 01:03:28.103 I can then navigate to the quote details page, review the quote
01:03:28.103 --> 01:03:32.329 that's been submitted by the company I am purchasing from.
01:03:32.339 --> 01:03:37.501 If I like the quote and I want to continue with my order, then
01:03:37.501 --> 01:03:40.369 I can use the approve button here.
01:03:41.159 --> 01:03:42.889 Once I approve my quotes.
01:03:46.419 --> 01:03:50.029 Then an invoice will be generated for the quote and I
01:03:50.029 --> 01:03:52.769 can either click OK, stay on the screen.
01:03:52.779 --> 01:03:57.749 Now I'm on or I can go directly to the newly generated invoice
01:03:57.749 --> 01:04:02.009 for my quotes once I'm at the invoice payment screen.
01:04:02.019 --> 01:04:07.609 Here I can then make a payment against my outstanding invoice.
01:04:07.659 --> 01:04:11.904 I have the option to select a credit card that I have within
01:04:11.904 --> 01:04:12.599 my wallet.
01:04:13.219 --> 01:04:18.257 Umm, a call out here that if you have a client that wants to do
01:04:18.257 --> 01:04:23.137 ACH payments for invoices, that is something that is going to
01:04:23.137 --> 01:04:27.702 require additional time to configure as an option for the
01:04:27.702 --> 01:04:29.669 customer paying invoices.
01:04:30.379 --> 01:04:36.289 You do have the option to pay EA full or partial invoice payment.
01:04:36.349 --> 01:04:42.198 So if I want to pay $300.00 against my $931 outstanding
01:04:42.198 --> 01:04:46.479 balance, we do offer that functionality.
01:04:46.569 --> 01:04:46.799 Really.
01:04:46.929 --> 01:04:47.139 Uh.
01:04:48.499 --> 01:04:53.636 And then additionally with invoices, if I come back to my
01:04:53.636 --> 01:04:59.394 invoices here I have the option to pay against multiple invoices
01:04:59.394 --> 01:05:01.519 or bulk invoice payment.
01:05:01.589 --> 01:05:05.857 So with this it pulls my outstanding invoices on my
01:05:05.857 --> 01:05:10.371 account and then we'll prepopulate with the full value
01:05:10.371 --> 01:05:12.669 of the outstanding invoices.
01:05:12.749 --> 01:05:18.061 Uh at the top of the page here, similar to paying and individual
01:05:18.061 --> 01:05:23.454 invoice, I can also customize my bulk payments to be partial if I
01:05:23.454 --> 01:05:28.193 want to pay just a certain amount against the outstanding
01:05:28.193 --> 01:05:32.687 total I have that option to do that in bulk as well as
01:05:32.687 --> 01:05:33.749 individually.
01:05:38.679 --> 01:05:43.391 Once you pay an invoice, uh, you'll see we have our status
01:05:43.391 --> 01:05:44.429 here of paid.
01:05:44.939 --> 01:05:49.398 There's no longer an outstanding balance and then additionally,
01:05:49.398 --> 01:05:53.369 we have our other statuses of unpaid and partially paid.
01:05:53.679 --> 01:05:57.144 So as you pay against an invoice, your balance due will
01:05:57.144 --> 01:06:01.104 decrease based on the number of payments that you are based on,
01:06:01.104 --> 01:06:04.630 the amount that you've paid against the invoice and will
01:06:04.630 --> 01:06:08.404 continue to update until you have fully paid the outstanding
01:06:08.404 --> 01:06:08.899 invoice.
01:06:15.409 --> 01:06:18.089 Any questions about quotes or invoices?
01:06:21.619 --> 01:06:22.009 Nada.
01:06:24.119 --> 01:06:29.898 Alright, so while we're talking about invoices and orders, I did
01:06:29.898 --> 01:06:32.209 want to go and talk about.
01:06:36.519 --> 01:06:42.498 The sales group are master and sub orders so this is something
01:06:42.498 --> 01:06:48.667 that confuses clients sometimes and call call on you to give the
01:06:48.667 --> 01:06:51.039 explanation for this one.
01:06:52.999 --> 01:06:54.879 If you're here, yeah.
01:06:53.489 --> 01:06:54.179 The sales groups.
01:06:55.699 --> 01:06:56.209 Yeah.
01:06:56.219 --> 01:07:00.518 So the sales groups are essentially a container that
01:07:00.518 --> 01:07:05.628 allows you to follow the stream of transactions or the streams
01:07:05.628 --> 01:07:10.169 that records that are created for a particular customer
01:07:10.169 --> 01:07:10.899 scenario.
01:07:10.909 --> 01:07:15.969 Like I ordered 100 widgets or I get a quote for 100 widgets.
01:07:15.979 --> 01:07:19.663 I can see the quote to the order to the invoice and then
01:07:19.663 --> 01:07:21.149 potentially the return.
01:07:21.159 --> 01:07:25.000 If I do return anything so a sales group is essentially a
01:07:25.000 --> 01:07:28.509 container that relates all of those things together.
01:07:28.899 --> 01:07:32.732 So you can see here you have the master order, which is what the
01:07:32.732 --> 01:07:34.619 customer placed during checkout.
01:07:34.899 --> 01:07:41.533 So let's say I got 50 shoes, but I sent 20 to Shelton and I sent
01:07:41.533 --> 01:07:42.859 30 to myself.
01:07:43.389 --> 01:07:45.569 So the master order would show all 50.
01:07:46.459 --> 01:07:48.509 The suborder there would be 2.
01:07:48.639 --> 01:07:52.215 There would be one for 20 that goes to Shelton and there would
01:07:52.215 --> 01:07:53.009 be one for 30.
01:07:53.019 --> 01:07:53.849 That goes to me.
01:07:53.859 --> 01:07:57.078 So there would be 2 suborders per shipping addresses that I
01:07:57.078 --> 01:07:57.989 put on the order.
01:07:59.159 --> 01:07:59.779 Umm.
01:08:00.169 --> 01:08:02.859 And then of course, the invoice that's generated for those.
01:08:02.869 --> 01:08:06.550 Typically it's just for the entire order, unless the client
01:08:06.550 --> 01:08:10.476 specifically asks to customize it to where the invoices are sub
01:08:10.476 --> 01:08:11.519 ordered specific.
01:08:11.589 --> 01:08:15.808 But typically the invoice is for the master order, just as a call
01:08:15.808 --> 01:08:19.324 out there, and those are typically synced back in from
01:08:19.324 --> 01:08:21.049 whatever ERP they're using.
01:08:21.879 --> 01:08:23.469 Umm but yeah quotes.
01:08:23.479 --> 01:08:29.946 And I think if you go over to you, that would be relationships
01:08:29.946 --> 01:08:30.459 here.
01:08:32.839 --> 01:08:36.903 Besides just those, because I know there's associations over
01:08:36.903 --> 01:08:40.900 there, if you click on the associations tab, it'll tell you
01:08:40.900 --> 01:08:41.699 the invoice.
01:08:43.299 --> 01:08:46.818 Umm, I don't know why that invoice wouldn't be showing up
01:08:46.818 --> 01:08:50.337 in the sales group tab, cause when you're doing the sales
01:08:50.337 --> 01:08:54.099 group says the master and sub order but I didn't see anywhere
01:08:54.099 --> 01:08:55.919 that it would say the invoice.
01:08:58.309 --> 01:09:01.059 That might be a question for Eric.
01:09:04.289 --> 01:09:07.435 It's technically you should have a quote if it if it originated
01:09:07.435 --> 01:09:10.679 from a quote then you would have the master order and sub orders.
01:09:10.689 --> 01:09:13.964 If it was split and then you would have the invoice that's
01:09:13.964 --> 01:09:15.129 associated with that.
01:09:19.289 --> 01:09:22.407 On one sales group page where you can see everything that's
01:09:22.407 --> 01:09:23.809 related to the sales group.
01:09:24.789 --> 01:09:25.499 So that's interesting.
01:09:26.979 --> 01:09:29.514 I don't know why it's not showing the invoices there, but
01:09:29.514 --> 01:09:30.999 does that make sense to everyone?
01:09:31.009 --> 01:09:31.509 Of what?
01:09:32.069 --> 01:09:34.099 I guess conceptually ACL's group is.
01:09:34.109 --> 01:09:36.989 Is there's already questions on that?
01:09:37.619 --> 01:09:39.529 Yes, makes sense to me.
01:09:41.249 --> 01:09:44.894 The wording is a little confusing for sure, but yeah,
01:09:44.894 --> 01:09:46.109 for the most part.
01:09:46.449 --> 01:09:49.581 It might be easier, Shelton, if you go to the store front and
01:09:49.581 --> 01:09:51.349 just go to the order details page.
01:09:52.319 --> 01:09:53.229 Yeah.
01:09:53.319 --> 01:09:57.788 So that essentially there if you go to any one of those orders
01:09:57.788 --> 01:10:02.328 could see up at the top where it says sales group #240 and that
01:10:02.328 --> 01:10:06.513 sales group is going to tie together that quote that order
01:10:06.513 --> 01:10:07.719 and that invoice.
01:10:10.529 --> 01:10:10.739 OK.
01:10:15.489 --> 01:10:18.106 Yeah, it's kind of hard, I guess conceptualizing it, if you're
01:10:18.106 --> 01:10:20.307 just looking at it from the admin, it's kind of more
01:10:20.307 --> 01:10:20.639 helpful.
01:10:20.649 --> 01:10:23.159 I think if you look at it from the order details perspective.
01:10:30.979 --> 01:10:31.529 Awesome.
01:10:31.539 --> 01:10:32.249 Thanks girl.
01:10:32.439 --> 01:10:32.809 Too.
01:10:32.819 --> 01:10:34.099 Any no questions there?
01:10:32.889 --> 01:10:33.479 Yeah, of course.
01:10:36.859 --> 01:10:37.009 No.
01:10:37.119 --> 01:10:37.949 Perfect.
01:10:38.019 --> 01:10:43.449 Alright, so will round out with the diff.
01:10:43.949 --> 01:10:47.712 Excuse me, the different tabs that are available within the
01:10:47.712 --> 01:10:49.279 outer box user dashboard.
01:10:49.509 --> 01:10:53.646 So starting with the my dashboard is kind of a landing
01:10:53.646 --> 01:10:58.234 page that gives you a quick overview of your current orders,
01:10:58.234 --> 01:11:02.746 invoices and quotes and allows you to quickly navigate to a
01:11:02.746 --> 01:11:07.710 specific order, invoice or quote line item as well as view all uh
01:11:07.710 --> 01:11:11.997 so you can use the dashboard here to quickly get to your
01:11:11.997 --> 01:11:16.811 orders, invoices and quotes or find a specific line item as you
01:11:16.811 --> 01:11:18.089 place new orders.
01:11:18.819 --> 01:11:22.369 Invoices are generated, are quotes are created.
01:11:22.519 --> 01:11:28.084 This list will automatically update to be the most recent
01:11:28.084 --> 01:11:28.659 items.
01:11:28.709 --> 01:11:32.479 Uh, that you have placed in order for or not?
01:11:32.489 --> 01:11:34.079 I don't excuse most recent orders.
01:11:34.089 --> 01:11:35.099 Invoices or quotes.
01:11:36.449 --> 01:11:40.346 Next we have our account settings which is going to be my
01:11:40.346 --> 01:11:43.839 profile, account, profile, address book and wallet.
01:11:44.229 --> 01:11:49.211 So you're my profile information here is going to be your user
01:11:49.211 --> 01:11:50.159 information.
01:11:50.669 --> 01:11:54.690 So this is the information associated to your user which is
01:11:54.690 --> 01:11:56.499 associated to your account.
01:11:56.549 --> 01:12:00.704 So this is where you would manage your user specific
01:12:00.704 --> 01:12:05.563 information such as name, phone, uh, email and the ability to
01:12:05.563 --> 01:12:07.209 change your password.
01:12:09.339 --> 01:12:12.851 Next is the account profile settings which is going to be
01:12:12.851 --> 01:12:14.909 the account specific information.
01:12:15.519 --> 01:12:19.589 So with a client, if they have, you know, account specific
01:12:19.589 --> 01:12:23.934 information within their ERP and we sync that information over
01:12:23.934 --> 01:12:26.899 that is where this information would live.
01:12:26.909 --> 01:12:31.768 And then the associated users of an account as I log in
01:12:31.768 --> 01:12:37.060 underneath my user, I would see my user specific information
01:12:37.060 --> 01:12:39.749 here and then the address book.
01:12:39.759 --> 01:12:43.039 This is where you will manage your address information.
01:12:44.289 --> 01:12:48.112 As you can see, I have my currently existing addresses and
01:12:48.112 --> 01:12:52.000 I have the ability to edit those, delete them, or add a new
01:12:52.000 --> 01:12:56.018 address, and then at the top here you see we have our default
01:12:56.018 --> 01:13:00.100 billing and shipping based on the address records I have I can
01:13:00.100 --> 01:13:01.849 quickly change these to be.
01:13:06.049 --> 01:13:11.381 New address values as I add new addresses in and the next we
01:13:11.381 --> 01:13:12.779 have our wallet.
01:13:12.869 --> 01:13:17.719 This is where you will manage your payment information.
01:13:18.509 --> 01:13:24.345 A good call out here about the wallet, something that we had an
01:13:24.345 --> 01:13:29.907 interesting time discussing with Nat is going to be the user
01:13:29.907 --> 01:13:33.919 specific or user exclusivity of the wallet.
01:13:33.929 --> 01:13:39.631 So as a user underneath an account, my wallet information
01:13:39.631 --> 01:13:43.169 is going to be specific to my user.
01:13:43.679 --> 01:13:48.397 Our address book here is going to be shared across all
01:13:48.397 --> 01:13:49.169 accounts.
01:13:49.179 --> 01:13:51.369 Are all users underneath an account?
01:13:51.699 --> 01:13:55.760 Same thing with orders and voices and quotes, but the
01:13:55.760 --> 01:13:59.069 wallet itself is going to be user specific.
01:13:59.079 --> 01:14:03.579 So if I have a corporation and I have a single credit card that I
01:14:03.579 --> 01:14:08.010 like for all of my users to use when placing orders, that credit
01:14:08.010 --> 01:14:12.169 card would have to be entered by each user specifically into
01:14:12.169 --> 01:14:14.759 their CEF wallet in order to be used.
01:14:15.669 --> 01:14:16.819 Any questions about that?
01:14:23.199 --> 01:14:23.729 Not for me.
01:14:25.349 --> 01:14:25.749 Perfect.
01:14:28.259 --> 01:14:33.117 Next is gonna be wish list so the wish list operates very
01:14:33.117 --> 01:14:35.629 similar to the favorites list.
01:14:36.099 --> 01:14:39.979 It essentially is a running list of items from the storefront.
01:14:41.379 --> 01:14:46.524 As I find products that I may want to purchase later or save
01:14:46.524 --> 01:14:51.669 for later to quickly get to, I can add them to my wish list.
01:14:51.769 --> 01:14:56.451 Uh wish list is not a segregated list like shopping list that
01:14:56.451 --> 01:14:58.339 we'll get to in a second.
01:14:58.769 --> 01:15:02.632 It essentially is a single list that adds you add products to
01:15:02.632 --> 01:15:02.819 it.
01:15:02.929 --> 01:15:07.096 As you can see, it is just a single list that continues to
01:15:07.096 --> 01:15:07.449 grow.
01:15:08.349 --> 01:15:13.201 Uh favorites list operates, you know, essentially the same way,
01:15:13.201 --> 01:15:16.309 just with a different naming convention.
01:15:17.759 --> 01:15:22.500 Shopping list, however, allow you to create a specific list to
01:15:22.500 --> 01:15:23.929 assign products to.
01:15:24.359 --> 01:15:28.451 So you can see I have my laptop shopping lists so well as a
01:15:28.451 --> 01:15:32.612 generator in it, but if I was, you know, purchasing a lot of
01:15:32.612 --> 01:15:37.113 laptops frequently or purchasing a certain set of products on the
01:15:37.113 --> 01:15:41.409 storefront, I could add these products to a shopping list that
01:15:41.409 --> 01:15:44.820 I create within the user dashboard and have these
01:15:44.820 --> 01:15:47.479 separated from by other shopping list.
01:15:48.029 --> 01:15:48.269 Uh.
01:15:49.309 --> 01:15:53.139 Different from favorites list and Wish list where the products
01:15:53.139 --> 01:15:57.029 we combined these are separated based on the shopping list that
01:15:57.029 --> 01:15:58.609 I assigned the product to.
01:16:00.329 --> 01:16:03.909 So if I go back to the storefront and I want to add
01:16:03.909 --> 01:16:07.696 some pencils to one of my shopping lists, I can add to
01:16:07.696 --> 01:16:08.659 shopping list.
01:16:08.669 --> 01:16:12.866 Here my currently created shopping lists are available as
01:16:12.866 --> 01:16:14.819 an option in the drop down.
01:16:15.289 --> 01:16:19.369 Then I also have the ability to create a new shopping list to
01:16:19.369 --> 01:16:21.409 assign this product to as well.
01:16:26.839 --> 01:16:27.929 My favorite way to shop.
01:16:26.989 --> 01:16:27.209 And.
01:16:30.929 --> 01:16:34.789 And then the last tab is gonna be our in stock alerts.
01:16:36.609 --> 01:16:40.519 So this use for this tab is as it sounds.
01:16:40.629 --> 01:16:44.583 If I have a product that you know is currently out of stock
01:16:44.583 --> 01:16:48.603 on the storefront and I would like to know when that product
01:16:48.603 --> 01:16:52.754 is back in stock, I can select that product, add it to my list
01:16:52.754 --> 01:16:57.103 here, and once the product comes back in stock, I will receive an
01:16:57.103 --> 01:17:01.452 email notification notify me the products back in stock and I can
01:17:01.452 --> 01:17:03.099 now go order the product.
01:17:05.699 --> 01:17:10.162 In stock alerts, shopping lists, favorite list and wish list are
01:17:10.162 --> 01:17:14.349 all configurable out of the box functionality that we offer.
01:17:14.659 --> 01:17:18.814 If the client does not want to include this, similar to
01:17:18.814 --> 01:17:23.562 reviews, it's something that is very easily configurable within
01:17:23.562 --> 01:17:24.229 the site.
01:17:24.339 --> 01:17:28.515 It takes very minimal time to implement, but it does take a
01:17:28.515 --> 01:17:32.692 little bit of time for us to go in there and turn off these
01:17:32.692 --> 01:17:36.798 different tabs within the user dashboard and functionality
01:17:36.798 --> 01:17:38.329 within the storefront.
01:17:38.339 --> 01:17:39.619 For these different tabs.
01:17:44.069 --> 01:17:47.289 Alright, so any questions about the user dashboard or anything?
01:17:47.659 --> 01:17:50.179 Uh, anyone wants to revisit?
01:17:53.929 --> 01:17:59.355 Any regular pain points that we run into or things we additional
01:17:59.355 --> 01:18:01.859 gotchas we should be aware of?
01:18:05.239 --> 01:18:08.339 Or user dashboard specifically or just anything.
01:18:08.849 --> 01:18:11.819 Let's focus on user task for the dash specifically.
01:18:12.459 --> 01:18:13.049 Gotcha.
01:18:13.599 --> 01:18:14.259 Perfect.
01:18:14.379 --> 01:18:20.017 So one area that is going to be something that clients either
01:18:20.017 --> 01:18:25.928 struggle with internally or want some guidance on is going to be
01:18:25.928 --> 01:18:31.566 modifying the user dashboard information account profile, uh,
01:18:31.566 --> 01:18:36.931 account specific information, user specific information or
01:18:36.931 --> 01:18:42.296 addresses within CEF and how that relates to their current
01:18:42.296 --> 01:18:42.659 ERP.
01:18:43.399 --> 01:18:48.599 So different scenarios with this is a client may request that
01:18:48.599 --> 01:18:54.134 when we sync in this information from their ERP, it is uneditable
01:18:54.134 --> 01:18:56.649 within the CEF user dashboard.
01:18:57.099 --> 01:19:03.156 Another scenario is they allow for free flowing changes between
01:19:03.156 --> 01:19:04.859 CEF and their ERP.
01:19:05.039 --> 01:19:09.812 So if once my accounts created when their ERP we sync that
01:19:09.812 --> 01:19:14.504 information in and then I come in and I update my address
01:19:14.504 --> 01:19:19.601 information or update my user or account information, we would
01:19:19.601 --> 01:19:24.698 then sync that back to the ERP and update the account and user
01:19:24.698 --> 01:19:25.749 record there.
01:19:25.869 --> 01:19:31.569 Another option that we've done in the past is a update form.
01:19:32.239 --> 01:19:36.946 So if I needed to update my information, there would be an
01:19:36.946 --> 01:19:42.211 option to update information and essentially we would display the
01:19:42.211 --> 01:19:47.077 current fields for a user or for account settings that would
01:19:47.077 --> 01:19:51.864 enter in that information we would capture that and then we
01:19:51.864 --> 01:19:56.889 would pass that information to the client through an email and
01:19:56.889 --> 01:20:00.479 they would update that information manually.
01:20:01.109 --> 01:20:04.805 That's typically the most expensive route to go is that
01:20:04.805 --> 01:20:09.095 update form where we capture the information and then pass it to
01:20:09.095 --> 01:20:11.669 the client to update within their ERP.
01:20:13.319 --> 01:20:18.190 And the fourth option is just strictly a message that says if
01:20:18.190 --> 01:20:22.432 you need to change your settings, you know contact us
01:20:22.432 --> 01:20:24.789 and we'll update your account.
01:20:24.829 --> 01:20:29.318 So that's something that can be kind of a pain point is
01:20:29.318 --> 01:20:33.888 determining how we're gonna handle information synced to
01:20:33.888 --> 01:20:38.938 inform an ERP for accounts users and addresses as something if
01:20:38.938 --> 01:20:44.069 it's going to be editable within CEF and how we're gonna handle
01:20:44.069 --> 01:20:44.469 that.
01:20:44.479 --> 01:20:48.404 Because sometimes with the integrations they may not
01:20:48.404 --> 01:20:53.068 account for that within sales because the client does not tell
01:20:53.068 --> 01:20:57.141 them, you know we need a bidirectional account sync or
01:20:57.141 --> 01:21:01.805 user sync and we end up having to add that in at a later date,
01:21:01.805 --> 01:21:04.989 which increases the budget of the project.
01:21:05.279 --> 01:21:11.340 So I would say that's probably one of the larger, I guess, uh
01:21:11.340 --> 01:21:17.499 pain points at least personally that I've dealt with with some
01:21:17.499 --> 01:21:23.755 projects of you know, how are we gonna handle that account user
01:21:23.755 --> 01:21:28.349 and address updates for umm CEF versus an ERP.
01:21:30.919 --> 01:21:33.579 Additionally with invoices.
01:21:35.789 --> 01:21:40.893 In some scenarios, the client may not want invoices to be
01:21:40.893 --> 01:21:42.829 generated within self.
01:21:42.839 --> 01:21:45.749 We would get them strictly from their ERP.
01:21:46.539 --> 01:21:49.279 This can, you know, lead to some issues.
01:21:49.709 --> 01:21:54.076 Uh, with the sink and ensuring that invoices are being synced
01:21:54.076 --> 01:21:58.725 incorrectly as well as providing the correct status updates based
01:21:58.725 --> 01:22:02.739 on changes made to invoices within self back to the ERP.
01:22:05.899 --> 01:22:08.109 That's another area. Quotes.
01:22:08.539 --> 01:22:13.564 Quotes are something that some ERP's do not support, so if a
01:22:13.564 --> 01:22:18.424 client wishes to use quotes and their ERP does not support
01:22:18.424 --> 01:22:23.532 quotes, there may need to be additional customizations within
01:22:23.532 --> 01:22:28.803 the ERP or quotes would have to be handled manually or strictly
01:22:28.803 --> 01:22:33.169 through CEF and then relayed to the ERP as an order.
01:22:33.179 --> 01:22:33.459 Order.
01:22:34.699 --> 01:22:39.142 If the quote is converted to an order within CEF, or the quote
01:22:39.142 --> 01:22:42.809 could be entered manually into the ERP as in order.
01:22:43.279 --> 01:22:47.309 So I would say a lot of the times any issues with the user
01:22:47.309 --> 01:22:51.475 dashboard is just going to be around integrating information
01:22:51.475 --> 01:22:52.499 from an ERP or.
01:22:56.009 --> 01:23:00.031 I've I've probably would say that's really the only thing
01:23:00.031 --> 01:23:04.053 modifying account fields and user fields to display a new
01:23:04.053 --> 01:23:04.399 data.
01:23:04.749 --> 01:23:08.724 That's relatively easy, and then it just kind of falls back again
01:23:08.724 --> 01:23:10.169 on populating that data.
01:23:11.469 --> 01:23:11.859 Uh.
01:23:11.869 --> 01:23:15.797 From an ERP, if we are doing an integration, but if we were
01:23:15.797 --> 01:23:20.118 handling everything through self we can update you know different
01:23:20.118 --> 01:23:24.439 information fields to display on these settings and that would be
01:23:24.439 --> 01:23:25.879 relatively easy to do.
01:23:26.089 --> 01:23:29.763 So I would say probably just integrations typically cause the
01:23:29.763 --> 01:23:30.059 most.
01:23:32.549 --> 01:23:37.398 Headache with the user dashboard and then additionally you know
01:23:37.398 --> 01:23:41.414 if a client's gonna require a new tab to display new
01:23:41.414 --> 01:23:45.809 functionality or new fields entirely compared to what the
01:23:45.809 --> 01:23:48.839 out of the box user dashboard tabs are.
01:23:49.289 --> 01:23:52.982 That does increase the complexity of the project
01:23:52.982 --> 01:23:53.509 itself.
01:23:55.629 --> 01:24:00.417 Any other things you could think of, Kyle that would be user
01:24:00.289 --> 01:24:00.619 Uh.
01:24:00.417 --> 01:24:01.829 dashboard related?
01:24:03.569 --> 01:24:05.409 Umm, we're going.
01:24:05.419 --> 01:24:05.939 I can think of.
01:24:09.529 --> 01:24:14.750 Making anything that you can think of that might be another
01:24:14.750 --> 01:24:17.099 user dashboard paint point.
01:24:19.089 --> 01:24:22.381 Just to be aware that a lot of times clients want to hide, you
01:24:22.381 --> 01:24:23.269 know, some of it.
01:24:23.279 --> 01:24:26.969 So just making sure they want all the things they have.
01:24:29.159 --> 01:24:29.859 Other than that, no.
01:24:36.319 --> 01:24:37.909 Perfect, alright.
01:24:37.979 --> 01:24:39.089 Uh, any more questions?
01:24:39.099 --> 01:24:44.456 Cassie, anything specific that you want to talk about anymore
01:24:44.456 --> 01:24:49.640 specific areas that you're concerned about on the left side
01:24:49.640 --> 01:24:51.109 with pain points?
01:24:52.579 --> 01:24:57.374 About image uploads, what what happens when those don't work in
01:24:57.374 --> 01:25:00.819 the sense of what we heard from a UI earlier?
01:25:02.149 --> 01:25:07.259 So that I believe was an app setting issue.
01:25:07.679 --> 01:25:12.867 According to Brendan Lyon, and he has said that he has fixed
01:25:07.869 --> 01:25:08.049 Now.
01:25:12.867 --> 01:25:17.969 it, so that seemed to just be some, uh, internal SEF issue.
01:25:18.399 --> 01:25:22.799 Nothing to do with the actual images themselves so.
01:25:23.039 --> 01:25:23.259 Cool.
01:25:27.039 --> 01:25:30.968 So it is I guess, worth noting that some clients don't choose
01:25:27.379 --> 01:25:27.969 I was asked.
01:25:30.968 --> 01:25:34.834 to actually upload their own images and some choose to store
01:25:34.834 --> 01:25:38.699 them elsewhere and just have us refer to the link where that
01:25:38.049 --> 01:25:38.499 Umm.
01:25:38.699 --> 01:25:39.459 photo lives.
01:25:39.569 --> 01:25:42.205 I guess that's something to be aware of that that is something
01:25:42.205 --> 01:25:43.669 that can be done and sometimes is.
01:25:44.269 --> 01:25:44.599 Hmm.
01:25:46.349 --> 01:25:48.779 There are better with best practice.
01:25:46.599 --> 01:25:46.739 Yes.
01:25:48.789 --> 01:25:50.779 I mean that does one work better?
01:25:50.189 --> 01:25:55.796 Best best practice for like a bulk upload for lots of photos
01:25:55.796 --> 01:26:01.219 is to get the file name of the image on that upload sheet.
01:26:01.449 --> 01:26:03.359 For products, have you seen that yet, Kathy?
01:26:04.589 --> 01:26:05.469 I don't think so.
01:26:05.479 --> 01:26:07.939 I haven't seen that like the bulk upload happened yet.
01:26:06.589 --> 01:26:08.219 It's it's just a simple.
01:26:08.229 --> 01:26:13.852 Yeah, just a simple excel sheet with headers that just say like
01:26:10.849 --> 01:26:11.069 Yeah.
01:26:13.852 --> 01:26:17.629 you know one column 4 umm title, whatever.
01:26:17.639 --> 01:26:20.809 All, all, all the stuff, and you could even create new stuff.
01:26:19.709 --> 01:26:20.139 OK.
01:26:20.819 --> 01:26:23.749 So you can create new attributes on there or whatever you want.
01:26:23.919 --> 01:26:24.909 Really simple.
01:26:25.299 --> 01:26:29.693 So in there, the best bet is to just put the file name of the
01:26:29.693 --> 01:26:31.819 images that you want you know.
01:26:31.889 --> 01:26:34.299 But you know Cassie, pick one.
01:26:34.429 --> 01:26:39.997 Youknowwhatever.jpg and they just named them all that way to
01:26:39.997 --> 01:26:41.639 their specificity.
01:26:42.029 --> 01:26:46.929 And then essentially just send us the images and we can do like
01:26:46.929 --> 01:26:48.689 a bulk dump of them in.
01:26:50.839 --> 01:26:54.446 In the database, just like a fancy transfer, big files or
01:26:54.446 --> 01:26:55.689 something like that.
01:26:56.739 --> 01:26:56.929 Like.
01:26:59.369 --> 01:27:01.519 Because uploading each one just takes a long time.
01:26:59.689 --> 01:26:59.839 And.
01:27:01.869 --> 01:27:02.209 Yeah.
01:27:04.769 --> 01:27:08.707 And then this is the product importer that was mentioned
01:27:05.299 --> 01:27:05.639 Umm.
01:27:08.707 --> 01:27:09.259 earlier.
01:27:09.729 --> 01:27:15.089 So the product importer can be customized to fit, you know,
01:27:15.089 --> 01:27:17.769 different client requirements.
01:27:17.779 --> 01:27:23.455 And Brendan Lyon has done some great work with updating the
01:27:23.455 --> 01:27:29.698 product importer and I'm sure he would be glad to give you a tour
01:27:29.698 --> 01:27:31.589 of his his new work.
01:27:31.599 --> 01:27:36.256 But with the product import sheets, as you can see, we have
01:27:36.256 --> 01:27:40.059 our different product information areas that the
01:27:40.059 --> 01:27:44.948 customers can fill out, uh, if they need to and import uh, you
01:27:44.948 --> 01:27:49.294 know, bulk amount of products rather than creating them
01:27:49.294 --> 01:27:54.028 individually, they can use this sheet here to enter in their
01:27:54.028 --> 01:27:58.607 product information and then import this directly into CEF
01:27:58.607 --> 01:28:02.254 and it will generate the products based on the
01:28:02.254 --> 01:28:05.979 information that was provided by the client so.
01:28:11.619 --> 01:28:13.999 That is a quick view of that.
01:28:14.069 --> 01:28:19.429 Uh, obviously not a ton of information, but yeah, so.
01:28:19.569 --> 01:28:20.659 No, that was very helpful.
01:28:20.669 --> 01:28:21.229 Thank you, Shelton.
01:28:22.099 --> 01:28:22.909 Indeed.
01:28:23.059 --> 01:28:23.639 Thank you, Shelton.
01:28:23.489 --> 01:28:24.029 Indeed.
01:28:26.379 --> 01:28:26.679 Kudos.
01:28:28.199 --> 01:28:28.329 And.
01:28:28.239 --> 01:28:34.462 And then next time we do this, we can talk about uh, price
01:28:34.462 --> 01:28:38.259 rules and discounts, the fun stuff.
01:28:37.469 --> 01:28:37.859 Yay.
01:28:41.949 --> 01:28:42.969 Yay.
01:28:44.259 --> 01:28:45.449 Face grills on.
01:28:46.539 --> 01:28:47.599 Have a great weekend, everybody.
01:28:47.429 --> 01:28:47.889 Right.
01:28:47.969 --> 01:28:49.059 Yes, Greg, weekend.
01:28:48.579 --> 01:28:49.109 You too.
01:28:49.069 --> 01:28:52.414 Make sure you do time logs before you sign off and Chris,
01:28:49.119 --> 01:28:49.769 Thanks everyone.
01:28:49.209 --> 01:28:51.279 Very well time logs.
01:28:52.414 --> 01:28:55.990 if you are actually there, can we grab you for one second and
01:28:55.990 --> 01:28:58.239 invoice notes time, log invoice notes?
01:28:59.699 --> 01:29:01.899 Everybody who is not Chris, get out of here.
01:28:59.769 --> 01:29:00.129 So bye bye.
01:29:00.299 --> 01:29:00.669 Project.
01:29:04.129 --> 01:29:04.589 And me?
01:29:12.689 --> 01:29:14.739 Not entirely sure Chris's actually here.
01:29:14.749 --> 01:29:15.959 Cassie, I'm sorry.
01:29:15.799 --> 01:29:16.919 I don't think he is.
01:29:16.069 --> 01:29:19.160 You might, I think he's probably in one of the development
01:29:16.959 --> 01:29:17.859 That's that's OK.
01:29:19.160 --> 01:29:22.250 meetings or something else at the same time, and he's left
01:29:21.329 --> 01:29:26.449 Umm, he's always double meeting it up like Chris.
01:29:22.250 --> 01:29:22.669 earring.
01:29:26.459 --> 01:29:26.819 Are you there?
01:29:27.929 --> 01:29:28.359 Deed.
01:29:28.369 --> 01:29:28.899 It's so true.
01:29:28.379 --> 01:29:29.009 No, that's cool.
01:29:30.669 --> 01:29:34.232 Should I just let them know that we're preparing that information
01:29:34.232 --> 01:29:35.419 for them by next week?
01:29:34.319 --> 01:29:36.369 Yes, yes.
01:29:35.479 --> 01:29:36.579 OK, that works.
01:29:36.459 --> 01:29:40.162 And then my recommendation and Chris Deers can burn all they
01:29:40.162 --> 01:29:44.108 like, as I say it is loop Sydney in to the conversation and just
01:29:42.609 --> 01:29:43.729 Yeah. OK.
01:29:44.108 --> 01:29:47.629 have a ping with you know you can even include me to her.
01:29:47.719 --> 01:29:51.189 You, me, Chris, and just say hey, like, who's doing this?
01:29:51.199 --> 01:29:52.929 I wanna get this to them and you know.
01:29:53.569 --> 01:29:54.699 Yeah, correct.
01:29:55.729 --> 01:29:56.529 Can do.
01:29:56.219 --> 01:29:57.929 First of alright.
01:29:56.859 --> 01:29:57.679 Appreciate it.
01:29:58.059 --> 01:29:58.619 Thank you, ma'am.
01:29:58.629 --> 01:29:59.729 Have a wonderful weekend.
01:29:58.629 --> 01:30:00.279 Have a great weekend and I will see you.
01:30:00.489 --> 01:30:03.549 Yeah, I see you next week, right?
01:30:02.079 --> 01:30:02.649 Yep, bye.