0
00:00:08.500 --> 00:00:12.200
Well, hello everyone Welcome to our podcast a
1
00:00:11.200 --> 00:00:14.800
podcast about the world of ux UI
2
00:00:14.800 --> 00:00:18.200
design and much much more. I'm Diana
3
00:00:17.200 --> 00:00:21.100
your host for this episode today joining
4
00:00:20.100 --> 00:00:23.800
me is Carlos viceno. Hi Carlos.
5
00:00:23.800 --> 00:00:27.700
How are you? Hi, Deanna. How are you? I'm good.
6
00:00:27.700 --> 00:00:30.500
I'm glad to be here and talk
7
00:00:30.500 --> 00:00:34.000
to you about UI ux and much more.
8
00:00:33.200 --> 00:00:36.400
Excellent. So Carlos is
9
00:00:36.400 --> 00:00:38.400
our project manager at cool agency.
10
00:00:39.100 --> 00:00:42.100
We'll know that one of the many tasks of a project
11
00:00:42.100 --> 00:00:45.800
manager is to bridge the gap between the client and
12
00:00:45.800 --> 00:00:46.400
the team.
13
00:00:47.100 --> 00:00:50.100
I want to talk a little bit about our Motel.
14
00:00:51.800 --> 00:00:53.200
Look for a new angle.
15
00:00:54.200 --> 00:00:58.000
Under this motor, we always face challenges that
16
00:00:57.300 --> 00:01:01.000
have mastered that we have mastered and
17
00:01:00.200 --> 00:01:03.400
that have made us grow as a
18
00:01:03.400 --> 00:01:03.600
team.
19
00:01:04.500 --> 00:01:07.700
Every time there is a challenge to overcome. We
20
00:01:07.700 --> 00:01:10.100
actually look for a new angle.
21
00:01:11.600 --> 00:01:14.200
Um, that's cool. We specialize in a variety
22
00:01:14.200 --> 00:01:17.300
of services such as UI ux design
23
00:01:17.300 --> 00:01:20.700
CMS automations and software.
24
00:01:21.400 --> 00:01:24.500
However from time to time we have clients
25
00:01:24.500 --> 00:01:26.500
with a very specific need.
26
00:01:27.500 --> 00:01:30.400
Then we have to look for new angles as I
27
00:01:30.400 --> 00:01:33.800
mentioned before and even develop applications that
28
00:01:33.800 --> 00:01:35.400
meet the needs of the client.
29
00:01:36.400 --> 00:01:39.200
So this is the case of one of the clients that we had
30
00:01:39.200 --> 00:01:43.800
recently where we had to synchronize inventories
31
00:01:42.800 --> 00:01:45.500
for their food business.
32
00:01:46.400 --> 00:01:51.400
So Carlos, my first question is regarding what
33
00:01:49.400 --> 00:01:52.500
the client actually
34
00:01:52.500 --> 00:01:52.900
does.
35
00:01:53.700 --> 00:01:56.700
So, can you tell me a little bit more about this
36
00:01:56.700 --> 00:01:57.900
particular client?
37
00:01:59.200 --> 00:02:02.800
Of course happy to tell you about it. So this
38
00:02:02.800 --> 00:02:05.900
client specifically it's producer and
39
00:02:05.900 --> 00:02:08.500
distributor of superfoods. They
40
00:02:08.500 --> 00:02:11.200
produce them. So you
41
00:02:11.200 --> 00:02:14.300
just mentioned and they pretty much
42
00:02:14.300 --> 00:02:17.300
have their main distribution point
43
00:02:17.300 --> 00:02:20.400
it's their Bigcommerce websites.
44
00:02:20.400 --> 00:02:23.800
In this case. They use this specific e-commerce platform.
45
00:02:24.700 --> 00:02:27.900
tells their wholesale and Retail websites
46
00:02:27.900 --> 00:02:28.400
and
47
00:02:29.500 --> 00:02:30.300
they wanted to
48
00:02:31.100 --> 00:02:34.300
integrate their two websites
49
00:02:34.300 --> 00:02:35.900
with their inventory.
50
00:02:36.800 --> 00:02:39.600
Specifically and that's how everything
51
00:02:39.600 --> 00:02:43.700
that started for us in terms of creating this
52
00:02:43.700 --> 00:02:46.700
new application or custom application
53
00:02:46.700 --> 00:02:49.300
for them. I understand. So would you say that was the
54
00:02:49.300 --> 00:02:51.500
most important aspect of this project?
55
00:02:53.100 --> 00:02:56.900
Yeah, the most important aspect was synchronicity basically
56
00:02:56.900 --> 00:03:01.200
been able to have this some
57
00:02:59.200 --> 00:03:02.700
kind of triangle to
58
00:03:02.700 --> 00:03:05.800
come somehow and it's the
59
00:03:05.800 --> 00:03:08.600
whole show website the retail website
60
00:03:08.600 --> 00:03:12.600
and their inventory and those three
61
00:03:12.600 --> 00:03:14.700
aspects aspects are very important because
62
00:03:16.600 --> 00:03:20.800
During inventory. They use it for not only.
63
00:03:22.900 --> 00:03:25.100
have managed their
64
00:03:25.100 --> 00:03:28.600
inventory of their final products,
65
00:03:28.600 --> 00:03:29.700
but also the
66
00:03:30.500 --> 00:03:33.300
They produce their as I
67
00:03:33.300 --> 00:03:36.800
mentioned, they produce their own superfoods. So the whole production change
68
00:03:36.800 --> 00:03:40.100
it's there on their
69
00:03:39.100 --> 00:03:43.300
inventory. So whenever they produce new units of
70
00:03:42.300 --> 00:03:45.600
this items of this
71
00:03:45.600 --> 00:03:45.800
product.
72
00:03:46.500 --> 00:03:51.600
It's supposed to synchronize with their Bigcommerce
73
00:03:50.600 --> 00:03:53.500
websites, and that's very
74
00:03:53.500 --> 00:03:53.800
key.
75
00:03:54.800 --> 00:03:58.600
Because again to do
76
00:03:58.600 --> 00:04:01.400
it manually a specifically in this case
77
00:04:01.400 --> 00:04:03.700
when they have very vast.
78
00:04:05.100 --> 00:04:08.600
Variety of of catalog of different products.
79
00:04:08.600 --> 00:04:11.100
It's key for them to to able to
80
00:04:11.100 --> 00:04:14.900
automate part of the process and to
81
00:04:14.900 --> 00:04:17.400
do it this way save them
82
00:04:17.400 --> 00:04:18.100
a lot of time.
83
00:04:19.100 --> 00:04:22.300
And actually helps in the
84
00:04:22.300 --> 00:04:25.100
lobby in that regard also, they wanted
85
00:04:25.100 --> 00:04:28.400
to synchronize the create.
86
00:04:30.100 --> 00:04:33.500
Invoices invoices whenever they create that
87
00:04:33.500 --> 00:04:36.700
they had got a new order on either their whole wholesale or
88
00:04:36.700 --> 00:04:37.700
retail website.
89
00:04:38.500 --> 00:04:38.700
and
90
00:04:39.700 --> 00:04:41.200
they used to do it manually.
91
00:04:42.200 --> 00:04:45.900
Quote unquote manually exploring the information from becomers and
92
00:04:45.900 --> 00:04:49.600
uploading it to dear and
93
00:04:49.600 --> 00:04:52.400
now it's with this integration of having the
94
00:04:52.400 --> 00:04:55.800
synchronicity between both platforms bigcomers.
95
00:04:56.400 --> 00:04:59.600
And dear that's not necessary. It's automated.
96
00:04:59.600 --> 00:05:03.000
So whenever someone orders a
97
00:05:02.600 --> 00:05:05.600
place and press places on the order on
98
00:05:05.600 --> 00:05:08.200
either the wholesale or the retail website
99
00:05:08.200 --> 00:05:12.200
after medically. It's added to
100
00:05:12.200 --> 00:05:14.100
their sales on.
101
00:05:15.200 --> 00:05:18.700
on their inventory and that all obviously also
102
00:05:18.700 --> 00:05:22.400
affects the inventory there
103
00:05:21.400 --> 00:05:23.100
and
104
00:05:24.400 --> 00:05:28.400
Yeah, I think that's pretty much sums up what the
105
00:05:27.400 --> 00:05:31.300
process was or what are client
106
00:05:30.300 --> 00:05:33.000
asked for and what we worked on.
107
00:05:33.800 --> 00:05:34.700
absolutely, this is
108
00:05:35.300 --> 00:05:39.300
Going to be very important for those who don't know, but can
109
00:05:38.300 --> 00:05:41.500
you tell me a little bit about the difference
110
00:05:41.500 --> 00:05:44.000
between deer inventory and big Commerce?
111
00:05:44.800 --> 00:05:47.600
Of course both well dear inventory
112
00:05:47.600 --> 00:05:50.600
set platform a third party app that allows
113
00:05:50.600 --> 00:05:53.700
users to be able to work on
114
00:05:53.700 --> 00:05:56.500
to be able to manage their
115
00:05:56.500 --> 00:05:59.500
inventory. Mostly that's the main focus. It's a
116
00:05:59.500 --> 00:06:03.400
very comprehensive comprehensive app with a
117
00:06:03.400 --> 00:06:07.100
lot of Integrations available for it and very robust
118
00:06:06.100 --> 00:06:09.600
or while documented API.
119
00:06:10.300 --> 00:06:11.300
so
120
00:06:12.400 --> 00:06:15.400
From deer in that regard. There's a
121
00:06:15.400 --> 00:06:18.300
lot that you can do and you can integrate with because of that.
122
00:06:19.500 --> 00:06:22.400
but the difference between that or managing the
123
00:06:22.400 --> 00:06:25.500
inventory and big Commerce becomers is
124
00:06:25.500 --> 00:06:28.500
a newcomers platform that allows you to host your
125
00:06:28.500 --> 00:06:31.500
website your e-commerce website
126
00:06:31.500 --> 00:06:35.700
and pretty much do whatever
127
00:06:34.700 --> 00:06:38.700
Ecommerce does allows
128
00:06:37.700 --> 00:06:38.700
you to
129
00:06:39.400 --> 00:06:43.200
a place your products there showcase
130
00:06:42.200 --> 00:06:47.200
your products allow people to buy them
131
00:06:47.200 --> 00:06:51.000
online using a different
132
00:06:50.200 --> 00:06:54.100
kinds of payment platforms or payment gateways
133
00:06:53.100 --> 00:06:54.300
like
134
00:06:56.400 --> 00:06:59.800
credit cards or PayPal or Apple
135
00:06:59.800 --> 00:07:02.400
pay Google pay here and else
136
00:07:03.100 --> 00:07:03.400
and
137
00:07:05.300 --> 00:07:08.900
Pretty much. That's the difference. It's an e-comerce platform Bigcommerce
138
00:07:08.900 --> 00:07:11.500
is an e-commerce platform and the inventory
139
00:07:11.500 --> 00:07:14.100
is a nap that allows you to
140
00:07:14.100 --> 00:07:15.200
manage your inventory.
141
00:07:16.800 --> 00:07:20.400
Very nice. Let's talk about another member
142
00:07:20.400 --> 00:07:23.900
of the team that worked
143
00:07:23.900 --> 00:07:26.700
on this project Carlos who
144
00:07:26.700 --> 00:07:28.800
developed the application for the client.
145
00:07:29.700 --> 00:07:32.700
The application was developed by
146
00:07:32.700 --> 00:07:35.500
Maria from beginning to end.
147
00:07:35.500 --> 00:07:38.800
She is a great season
148
00:07:38.800 --> 00:07:42.800
our full stack developer. She's amazing and she
149
00:07:41.800 --> 00:07:45.600
has a lot a
150
00:07:44.600 --> 00:07:48.200
lot of different projects and
151
00:07:47.200 --> 00:07:51.100
in her resume that has
152
00:07:50.100 --> 00:07:53.200
worked for she has worked for
153
00:07:53.200 --> 00:07:57.000
us in different projects for almost three
154
00:07:56.600 --> 00:07:59.800
years now over three
155
00:07:59.800 --> 00:08:02.500
years now and it's been
156
00:08:02.500 --> 00:08:05.500
great to to be able to have her on our team
157
00:08:05.500 --> 00:08:07.700
and she's very
158
00:08:10.300 --> 00:08:14.200
are not only responsible but also very
159
00:08:13.200 --> 00:08:17.800
efficient and effective gravel
160
00:08:16.800 --> 00:08:21.500
Communications and it's always
161
00:08:21.500 --> 00:08:24.700
a pleasure to work with her in any part any project
162
00:08:24.700 --> 00:08:26.600
that we have it in store.
163
00:08:27.400 --> 00:08:31.000
Absolutely. She has done a great job Indeed
164
00:08:30.600 --> 00:08:34.600
Carlos. What is a API
165
00:08:33.600 --> 00:08:36.800
for integration between the big Commerce
166
00:08:36.800 --> 00:08:38.600
and the deer inventory platforms?
167
00:08:39.700 --> 00:08:42.800
So we had to create an API to be
168
00:08:42.800 --> 00:08:46.200
able to manage this integration. It's completely
169
00:08:45.200 --> 00:08:48.400
custom but I'll obviously
170
00:08:48.400 --> 00:08:51.800
uses it calls to
171
00:08:51.800 --> 00:08:54.600
tears and becomers apis.
172
00:08:54.600 --> 00:08:57.600
Both of them are very well documented
173
00:08:57.600 --> 00:09:00.300
and that's super helpful. Whenever you
174
00:09:00.300 --> 00:09:03.500
have any kind of API integration. It's
175
00:09:03.500 --> 00:09:06.700
key for us to be able to have the
176
00:09:06.700 --> 00:09:09.500
recommendation available and some platforms
177
00:09:09.500 --> 00:09:12.200
do it better than others. But in this case both of
178
00:09:12.200 --> 00:09:16.500
them big Commerce and your inventory have great. It's
179
00:09:15.500 --> 00:09:18.500
available very easy
180
00:09:18.500 --> 00:09:19.300
to
181
00:09:20.500 --> 00:09:24.700
to get this information and yeah, but
182
00:09:23.700 --> 00:09:26.300
we didn't really have
183
00:09:26.300 --> 00:09:29.800
any questions in regards to how something
184
00:09:29.800 --> 00:09:30.800
work with and you have to
185
00:09:31.700 --> 00:09:34.900
contact support of any of the platforms or
186
00:09:34.900 --> 00:09:38.300
anything. We had everything our disposal
187
00:09:37.300 --> 00:09:40.700
in this case at Maria's disposal
188
00:09:40.700 --> 00:09:43.700
for for her to to test the how
189
00:09:43.700 --> 00:09:46.200
the apis work and begin with the work and
190
00:09:47.200 --> 00:09:50.200
At the moment no complaints in that
191
00:09:50.200 --> 00:09:53.700
regard. Oh awesome. You know that it doesn't
192
00:09:53.700 --> 00:09:56.700
really matter. What field you are working in.
193
00:09:57.700 --> 00:10:01.700
Working on something new facing challenges
194
00:10:01.700 --> 00:10:06.100
new challenges and overcoming them. It's necessary
195
00:10:05.100 --> 00:10:08.300
because it makes you better
196
00:10:08.300 --> 00:10:11.700
and it actually enrich you not only as a
197
00:10:11.700 --> 00:10:14.400
person not only as a member of a team
198
00:10:14.400 --> 00:10:17.400
but also as a whole unit as an agency,
199
00:10:17.400 --> 00:10:20.500
so my last question for you would be how do
200
00:10:20.500 --> 00:10:23.900
you think the experience enriched us as an
201
00:10:23.900 --> 00:10:24.600
agency overall?
202
00:10:26.100 --> 00:10:29.400
There was an interesting Tech Challenge to work with
203
00:10:29.400 --> 00:10:32.900
this specific integration because it
204
00:10:32.900 --> 00:10:36.500
has special requirements one of
205
00:10:36.500 --> 00:10:39.600
them that I didn't talk about earlier. I forgot
206
00:10:39.600 --> 00:10:42.400
to mention but I'm going to talk about it. Now. It's that
207
00:10:43.900 --> 00:10:47.800
our clients needed to have some kind of cushion of
208
00:10:46.800 --> 00:10:50.400
inventory like I
209
00:10:49.400 --> 00:10:52.100
mentioned before that these three.
210
00:10:53.100 --> 00:10:54.600
key aspects or
211
00:10:56.200 --> 00:10:58.000
how do I call them?
212
00:11:00.700 --> 00:11:01.500
well
213
00:11:02.900 --> 00:11:05.000
this specific elements
214
00:11:05.800 --> 00:11:08.200
Are the e-commerce?
215
00:11:08.900 --> 00:11:11.500
Wholesale e-commerce their retail e-commerce
216
00:11:11.500 --> 00:11:15.600
and tier inventory. These are supposed to be in sync.
217
00:11:16.100 --> 00:11:19.200
And part of that obviously is
218
00:11:19.200 --> 00:11:22.500
because they want everything
219
00:11:22.500 --> 00:11:25.500
to work as a unit like if
220
00:11:25.500 --> 00:11:28.300
someone buys something from the wholesale.
221
00:11:29.800 --> 00:11:33.100
Website then it's supposed to also affect
222
00:11:32.100 --> 00:11:36.000
the retail website
223
00:11:35.300 --> 00:11:38.200
as well because they have the root
224
00:11:38.200 --> 00:11:41.500
of everything the where the warehouse where
225
00:11:41.500 --> 00:11:44.500
they inventory is. It's the same for both websites for
226
00:11:44.500 --> 00:11:46.100
the wholesale or the retail.
227
00:11:46.600 --> 00:11:49.200
So before he had to be done
228
00:11:49.200 --> 00:11:52.300
manually to have it some kind of synchronizing and
229
00:11:52.300 --> 00:11:53.000
now it's automatic.
230
00:11:53.900 --> 00:11:57.100
But also it's very important that whenever they
231
00:11:56.100 --> 00:12:00.200
create a new products or yeah,
232
00:11:59.200 --> 00:12:02.300
whenever they create a new products and it's part
233
00:12:02.300 --> 00:12:05.300
of their website or they their inventory.
234
00:12:05.300 --> 00:12:08.700
It's also available on their website without they having
235
00:12:08.700 --> 00:12:13.000
to do that manually because they have a very a fast
236
00:12:12.500 --> 00:12:15.700
inventory or different kinds
237
00:12:15.700 --> 00:12:17.500
of products in their catalog.
238
00:12:18.300 --> 00:12:23.000
With that said they want to have a cushion for their inventory
239
00:12:22.600 --> 00:12:25.300
because you never know whenever you
240
00:12:25.300 --> 00:12:28.400
have any kind of damage product or anything
241
00:12:28.400 --> 00:12:30.600
like that and you don't want to oversell.
242
00:12:31.300 --> 00:12:35.400
In that regard and then having an unsatisfied unsatisfied
243
00:12:34.400 --> 00:12:37.800
client exactly Customer because they
244
00:12:37.800 --> 00:12:39.500
receive something that wasn't.
245
00:12:41.100 --> 00:12:45.200
a working or or it wasn't high quality
246
00:12:44.200 --> 00:12:47.500
or the quality they expected
247
00:12:47.500 --> 00:12:50.500
or they had to get a refund because
248
00:12:50.500 --> 00:12:53.500
they weren't enough units in
249
00:12:53.500 --> 00:12:54.500
their inventory to
250
00:12:55.400 --> 00:12:59.100
to satisfy this demand and they always
251
00:12:58.100 --> 00:13:02.300
wanted to have a cushion. So whenever something the
252
00:13:01.300 --> 00:13:04.700
synchronized on their same
253
00:13:04.700 --> 00:13:05.000
inventory.
254
00:13:05.800 --> 00:13:08.300
From dear inventory to the big
255
00:13:08.300 --> 00:13:11.800
Commerce websites, they have less units. They
256
00:13:11.800 --> 00:13:14.700
have a cushion. So the they
257
00:13:14.700 --> 00:13:17.600
always show less units in their inventory and on
258
00:13:17.600 --> 00:13:20.900
bigcomers compared to what they have on deer to
259
00:13:20.900 --> 00:13:24.000
make sure that they have this kind of cushion for
260
00:13:23.500 --> 00:13:27.500
whenever try to know not oursel.
261
00:13:28.300 --> 00:13:31.400
And have to refund clients or have unsatisfied clients
262
00:13:31.400 --> 00:13:32.500
or customers.
263
00:13:34.500 --> 00:13:37.600
So that's something that that was very important. And so each
264
00:13:37.600 --> 00:13:40.600
of the requirements going back to to your question. I
265
00:13:40.600 --> 00:13:43.100
didn't forget about it each of
266
00:13:43.100 --> 00:13:47.200
the personalized and requirements that
267
00:13:47.200 --> 00:13:51.100
we have for the project. It was a challenge itself because we
268
00:13:50.100 --> 00:13:53.500
have to make something custom to
269
00:13:53.500 --> 00:13:57.200
satisfy the needs of the client and you seem
270
00:13:56.200 --> 00:13:59.400
to platforms that we were familiar with
271
00:13:59.400 --> 00:14:02.600
but what we were familiar with Bigcommerce not
272
00:14:02.600 --> 00:14:03.800
with deer until then.
273
00:14:04.500 --> 00:14:09.100
And we have to get from here race with this platform and get
274
00:14:07.100 --> 00:14:10.600
as I
275
00:14:10.600 --> 00:14:14.200
mentioned before we were lucky enough that the API documentation
276
00:14:13.200 --> 00:14:16.500
was pretty clear and available. Yeah
277
00:14:16.500 --> 00:14:17.000
for us.
278
00:14:17.800 --> 00:14:20.400
but it was a challenge itself because
279
00:14:20.400 --> 00:14:23.200
it was like making sure that
280
00:14:25.200 --> 00:14:28.200
What is in paper the theory of
281
00:14:28.200 --> 00:14:31.200
the API recommendation, it actually worked that way
282
00:14:31.200 --> 00:14:34.400
and the custom API that we created
283
00:14:34.400 --> 00:14:38.000
worse works as declining expected
284
00:14:37.200 --> 00:14:40.500
and that they were completely satisfied with
285
00:14:40.500 --> 00:14:44.700
the results at the end of the day. That's was our main
286
00:14:43.700 --> 00:14:46.500
Challenge and I'm Maria
287
00:14:46.500 --> 00:14:46.900
accomplish it.
288
00:14:48.400 --> 00:14:51.500
And she did great in the application
289
00:14:51.500 --> 00:14:53.800
works amazingly. Yeah and
290
00:14:55.100 --> 00:14:58.100
Yeah, and it's something something else that I
291
00:14:58.100 --> 00:15:03.800
wanted to mention. It's that obviously there are options like
292
00:15:02.800 --> 00:15:05.200
just having
293
00:15:05.200 --> 00:15:08.300
a software like Parabola or third party like
294
00:15:08.300 --> 00:15:11.400
Parabola or zapier or make which
295
00:15:11.400 --> 00:15:13.100
was integromat in the past.
296
00:15:15.100 --> 00:15:18.300
But in this case for the specifics that the
297
00:15:18.300 --> 00:15:21.400
client or the specific requirements that the client
298
00:15:21.400 --> 00:15:21.600
had
299
00:15:23.300 --> 00:15:27.000
It was key that it was something custom and there are other advantages
300
00:15:26.200 --> 00:15:29.300
to having something custom. Obviously there's
301
00:15:29.300 --> 00:15:32.800
a little bit more of time in terms of my maintenance
302
00:15:32.800 --> 00:15:34.800
because you don't don't depend on
303
00:15:35.600 --> 00:15:38.400
On a third party to to maintain everything
304
00:15:38.400 --> 00:15:39.500
exactly absolutely.
305
00:15:40.300 --> 00:15:42.700
But there's definitely more control over it.
306
00:15:44.700 --> 00:15:48.200
How everything works it's it's you
307
00:15:47.200 --> 00:15:50.100
can scale it up. If you
308
00:15:50.100 --> 00:15:53.900
want to if you want this app or
309
00:15:53.900 --> 00:15:57.100
specific custom application to grow in the future make
310
00:15:56.100 --> 00:15:59.400
it to other scenes or synchronize it
311
00:15:59.400 --> 00:16:02.500
with other platforms or anything like that. It's easier
312
00:16:02.500 --> 00:16:07.600
to do so now that there's some kind of base or
313
00:16:07.600 --> 00:16:08.200
or
314
00:16:10.900 --> 00:16:13.500
Yeah, I don't know how to call it. There's like.
315
00:16:16.200 --> 00:16:20.400
The the base of the app or destruct the
316
00:16:20.400 --> 00:16:22.100
base of the structure of the habits there.
317
00:16:22.800 --> 00:16:23.000
and
318
00:16:24.300 --> 00:16:27.300
that's that's very important and you can scale it
319
00:16:27.300 --> 00:16:30.300
up you the foundations of the other foundation of the
320
00:16:30.300 --> 00:16:33.500
app. Yeah. Sorry. Yeah, the foundations of that are
321
00:16:33.500 --> 00:16:36.700
there the structure of that is there and
322
00:16:36.700 --> 00:16:39.200
you can scale up in the future if you
323
00:16:39.200 --> 00:16:42.600
want to and you pretty much have complete control
324
00:16:42.600 --> 00:16:45.400
over it. It's you don't have to pay us.
325
00:16:46.900 --> 00:16:50.000
Monthly subscription that for some of these third-party absolutes
326
00:16:49.200 --> 00:16:52.500
it can get pretty expensive especially if
327
00:16:52.500 --> 00:16:56.000
you have something like this which is process as
328
00:16:55.200 --> 00:16:58.200
a process of the process with every single
329
00:16:58.200 --> 00:17:01.200
sale that you make whenever you
330
00:17:01.200 --> 00:17:02.400
update the inventory.
331
00:17:03.200 --> 00:17:06.500
There's several times especially if you have a lot
332
00:17:06.500 --> 00:17:09.600
of traffic on your website and well a
333
00:17:09.600 --> 00:17:12.900
bunch of sales a day. It can get pretty expensive
334
00:17:12.900 --> 00:17:15.300
whenever you are paying for a
335
00:17:15.300 --> 00:17:18.300
subscription or to zapier or make or something
336
00:17:18.300 --> 00:17:18.700
like that.
337
00:17:19.500 --> 00:17:22.600
In this case, you're paying for a server, obviously where the
338
00:17:22.600 --> 00:17:25.700
app is hosted but it's way
339
00:17:25.700 --> 00:17:28.400
less expensive like a 10th of what
340
00:17:28.400 --> 00:17:30.300
you will be paying more or less on.
341
00:17:31.100 --> 00:17:34.500
On zapier or any of the other apps
342
00:17:34.500 --> 00:17:37.400
which by the way are really useful and we use
343
00:17:37.400 --> 00:17:40.600
them all the time, but for specific cases
344
00:17:40.600 --> 00:17:43.200
like this one, it was required for
345
00:17:43.200 --> 00:17:47.200
us to have a custom application. Yeah,
346
00:17:46.200 --> 00:17:49.200
and it's only beneficial for the client to
347
00:17:49.200 --> 00:17:52.200
to find ways not to pay.
348
00:17:55.200 --> 00:17:58.200
Oh not too over overflow your budget.
349
00:17:58.200 --> 00:18:01.400
Okay not to spend more than you are expected
350
00:18:01.400 --> 00:18:05.100
to spend in your initial
351
00:18:04.100 --> 00:18:08.300
or your annual budget for
352
00:18:08.300 --> 00:18:11.300
example Carlos. Thank
353
00:18:11.300 --> 00:18:14.600
you very much for joining me in this conversation. I
354
00:18:14.600 --> 00:18:17.500
really hope to talk to you again in the foreseeable future
355
00:18:17.500 --> 00:18:20.100
talking to you as always
356
00:18:20.100 --> 00:18:23.500
wonderful. So that's it for today everybody. Thank
357
00:18:23.500 --> 00:18:26.500
you so much for listening to us and being part
358
00:18:26.500 --> 00:18:29.900
of these experience. So I will see you next time.
359
00:18:29.900 --> 00:18:32.700
Okay. Bye. Bye.
360
00:18:33.300 --> 00:18:33.700
up
.gif)
