2026-05-11 09-01-51

Jun 01, 2026 17:13 · 1:04:16 · English · Whisper Turbo · 8 స్పీకర్లు
ఈ సరికొత్త కాలం అయిపొయినది. శాశ్వత నిల్వ కోసం ఉన్నతీకరించు →
లాగ్మెట్ సూచికComment
చూపుట మాత్రమే
0:14
S… Speaker 2 (2026-05-11 09-01-51)
Good morning.
0:15
S… Speaker 3 (2026-05-11 09-01-51)
Good morning.
0:17
S… Speaker 2 (2026-05-11 09-01-51)
Did someone invite
0:21
S… Speaker 1 (2026-05-11 09-01-51)
Kurt?
0:21
S… Speaker 4 (2026-05-11 09-01-51)
Remind him
0:25
S… Speaker 2 (2026-05-11 09-01-51)
or ask him if he can join?
0:27
S… Speaker 4 (2026-05-11 09-01-51)
I think
0:32
S… Speaker 1 (2026-05-11 09-01-51)
Jonathan has dropped the call.
0:35
S… Speaker 2 (2026-05-11 09-01-51)
We don't have Jonathan on this call.
0:39
S… Speaker 4 (2026-05-11 09-01-51)
Oh,
0:41
S… Speaker 2 (2026-05-11 09-01-51)
you mean he asked Kurt?
0:42
S… Speaker 1 (2026-05-11 09-01-51)
Yeah.
0:44
S… Speaker 4 (2026-05-11 09-01-51)
Who
0:50
S… Speaker 1 (2026-05-11 09-01-51)
has joined?
0:50
S… Speaker 1 (2026-05-11 09-01-51)
Jonathan was joining the call,
0:54
S… Speaker 1 (2026-05-11 09-01-51)
but I think he dropped off.
0:56
S… Speaker 4 (2026-05-11 09-01-51)
Just ask him.
1:09
S… Speaker 1 (2026-05-11 09-01-51)
Yeah.
1:10
S… Speaker 4 (2026-05-11 09-01-51)
I mean,
1:13
S… Speaker 2 (2026-05-11 09-01-51)
I'm asking Kurt.
1:23
S… Speaker 1 (2026-05-11 09-01-51)
So that new keys need to be discussed with
1:27
S… Speaker 2 (2026-05-11 09-01-51)
Kurt? It's not so much the keys.
1:30
S… Speaker 4 (2026-05-11 09-01-51)
Just
1:42
S… Speaker 2 (2026-05-11 09-01-51)
asking Kurt if he can join.
1:43
S… Speaker 2 (2026-05-11 09-01-51)
We need a solution.
1:47
S… Speaker 2 (2026-05-11 09-01-51)
So here's the problem.
1:48
S… Speaker 2 (2026-05-11 09-01-51)
The new stores
1:53
S… Speaker 2 (2026-05-11 09-01-51)
have the same site ID.
1:56
S… Speaker 2 (2026-05-11 09-01-51)
They have a different global store ID.
2:00
S… Speaker 2 (2026-05-11 09-01-51)
But Kurt builds the ticket ID using
2:05
S… Speaker 2 (2026-05-11 09-01-51)
the mutable site ID 232,
2:08
S… Speaker 2 (2026-05-11 09-01-51)
for example, for one of the stores that's having this problem.
2:11
S… Speaker 2 (2026-05-11 09-01-51)
And so since that store is still numbered 232,
2:15
S… Speaker 2 (2026-05-11 09-01-51)
we will still have ticket IDs colliding even if we switch
2:19
S… Speaker 1 (2026-05-11 09-01-51)
stores.
2:19
S… Speaker 2 (2026-05-11 09-01-51)
Even if we switch to the correct store with the new
2:24
S… Speaker 2 (2026-05-11 09-01-51)
global store ID,
2:25
S… Speaker 2 (2026-05-11 09-01-51)
and I give you a...
2:27
S… Speaker 2 (2026-05-11 09-01-51)
API key for that store,
2:29
S… Speaker 2 (2026-05-11 09-01-51)
I'm still going to wind up with ticket IDs overlapping with the other store.
2:33
S… Speaker 2 (2026-05-11 09-01-51)
So I just wanted to make sure that was
2:37
S… Speaker 2 (2026-05-11 09-01-51)
resolved before we went down this road expecting it to fix the problem.
2:40
S… Speaker 2 (2026-05-11 09-01-51)
It won't.
2:41
S… Speaker 2 (2026-05-11 09-01-51)
But the other thing that could fix the problem is if
2:45
S… Speaker 2 (2026-05-11 09-01-51)
we change the ticket ID sequencing number to start
2:49
S… Speaker 2 (2026-05-11 09-01-51)
beyond where the other ones are.
2:52
S… Speaker 2 (2026-05-11 09-01-51)
I'm assuming there will be no new transactions located to the other
2:56
S… Speaker 2 (2026-05-11 09-01-51)
older store,
2:57
S… Speaker 2 (2026-05-11 09-01-51)
and I think it's already dead,
3:00
S… Speaker 2 (2026-05-11 09-01-51)
right? Then we won't have to worry about them colliding in the future.
3:03
S… Speaker 1 (2026-05-11 09-01-51)
So what
3:07
S… Speaker 1 (2026-05-11 09-01-51)
I understand,
3:08
S… Speaker 1 (2026-05-11 09-01-51)
currently,
3:10
S… Speaker 1 (2026-05-11 09-01-51)
if we're changing to the new store,
3:13
S… Speaker 1 (2026-05-11 09-01-51)
but the ticket ID will start generating again the same number on
3:17
S… Speaker 1 (2026-05-11 09-01-51)
the new store.
3:19
S… Speaker 2 (2026-05-11 09-01-51)
That is correct,
3:20
S… Speaker 2 (2026-05-11 09-01-51)
unless we've advanced the number past the highest number we've ever
3:24
S… Speaker 2 (2026-05-11 09-01-51)
seen so far.
3:25
S… Speaker 3 (2026-05-11 09-01-51)
Yes.
3:26
S… Speaker 4 (2026-05-11 09-01-51)
But
3:32
S… Speaker 2 (2026-05-11 09-01-51)
I wanted to make sure that if Kurt was going to simply
3:36
S… Speaker 2 (2026-05-11 09-01-51)
change the formulation for the ticket ID,
3:38
S… Speaker 2 (2026-05-11 09-01-51)
then in theory we wouldn't have to do that.
3:40
S… Speaker 2 (2026-05-11 09-01-51)
But it would still make the new stores anyway.
3:42
S… Speaker 2 (2026-05-11 09-01-51)
And the next thing is I can't just make keys for the new stores
3:46
S… Speaker 2 (2026-05-11 09-01-51)
because I don't actually have those new stores.
3:50
S… Speaker 2 (2026-05-11 09-01-51)
What I guess I'm going to do rather than burdening you guys with sending me the details for the stores is
3:54
S… Speaker 2 (2026-05-11 09-01-51)
just copy the details from the previous stores and
3:58
S… Speaker 2 (2026-05-11 09-01-51)
rename them to new or rename the other ones to old or something,
4:01
S… Speaker 2 (2026-05-11 09-01-51)
which I think is what you guys did internally anyway.
4:13
S… Speaker 1 (2026-05-11 09-01-51)
pushing the data from here to get the store data to you or like you
4:18
S… Speaker 1 (2026-05-11 09-01-51)
are always making the copy of that store at your end?
4:21
S… Speaker 2 (2026-05-11 09-01-51)
I don't see that store so I'm guessing I'm not getting a push of the
4:25
S… Speaker 2 (2026-05-11 09-01-51)
locations to me.
4:28
S… Speaker 2 (2026-05-11 09-01-51)
for Dunn Brothers,
4:29
S… Speaker 1 (2026-05-11 09-01-51)
perhaps?
4:30
S… Speaker 2 (2026-05-11 09-01-51)
And I think we decided not to do that because we've never tested it.
4:33
S… Speaker 3 (2026-05-11 09-01-51)
Dunn Brothers doesn't have SSO enabled because we wanted to
4:37
S… Speaker 3 (2026-05-11 09-01-51)
do it with Willard first to ensure that it wasn't a positive issue,
4:40
S… Speaker 3 (2026-05-11 09-01-51)
which was good because we found issues with the
4:48
S… Speaker 3 (2026-05-11 09-01-51)
user points.
4:54
S… Speaker 3 (2026-05-11 09-01-51)
yeah so that's why it's not there so you haven't gotten any new um
5:00
S… Speaker 3 (2026-05-11 09-01-51)
You haven't gotten any new stores
5:04
S… Speaker 3 (2026-05-11 09-01-51)
from Don Brothers.
5:06
S… Speaker 2 (2026-05-11 09-01-51)
Right.
5:07
S… Speaker 1 (2026-05-11 09-01-51)
So I'll just make the four stores.
5:09
S… Speaker 1 (2026-05-11 09-01-51)
I'm presuming they have the same names as before.
5:12
S… Speaker 1 (2026-05-11 09-01-51)
I have to make keys and attach them to something,
5:15
S… Speaker 1 (2026-05-11 09-01-51)
and currently I don't have something to attach them to.
5:21
S… Speaker 1 (2026-05-11 09-01-51)
So they will have new location IDs on our side because much like you
5:25
S… Speaker 1 (2026-05-11 09-01-51)
guys, ours are immutable as well.
5:26
S… Speaker 1 (2026-05-11 09-01-51)
I'm not going to recycle them.
5:28
S… Speaker 1 (2026-05-11 09-01-51)
Then I will make new keys that point to those.
5:30
S… Speaker 1 (2026-05-11 09-01-51)
They will have the new global store IDs.
5:34
S… Speaker 1 (2026-05-11 09-01-51)
But unless we do something with the tickets,
5:36
S… Speaker 1 (2026-05-11 09-01-51)
they'll still overlap.
5:37
S… Speaker 2 (2026-05-11 09-01-51)
I mean,
5:40
S… Speaker 1 (2026-05-11 09-01-51)
I'll make them after this call,
5:41
S… Speaker 1 (2026-05-11 09-01-51)
but just to make sure everyone's aware that that alone is not going to solve the problem.
5:46
S… Speaker 1 (2026-05-11 09-01-51)
We have to do one of two things.
5:47
S… Speaker 1 (2026-05-11 09-01-51)
Kirk has to change how the ticket IDs are computed or
5:51
S… Speaker 1 (2026-05-11 09-01-51)
you guys have to advance the ticket IDs past the highest number we've
5:55
S… Speaker 1 (2026-05-11 09-01-51)
seen so far.
5:56
S… Speaker 2 (2026-05-11 09-01-51)
But
6:04
S… Speaker 1 (2026-05-11 09-01-51)
I was hoping Kirk could join and give us a response.
6:06
S… Speaker 1 (2026-05-11 09-01-51)
But if he's not going to join,
6:07
S… Speaker 1 (2026-05-11 09-01-51)
then I guess, Jonathan,
6:09
S… Speaker 1 (2026-05-11 09-01-51)
you'll need to decide what you want us to do.
6:11
S… Speaker 2 (2026-05-11 09-01-51)
I mean,
6:14
S… Speaker 3 (2026-05-11 09-01-51)
there's two parts to this.
6:15
S… Speaker 3 (2026-05-11 09-01-51)
First things first is for this store,
6:16
S… Speaker 3 (2026-05-11 09-01-51)
we have to...
6:18
S… Speaker 3 (2026-05-11 09-01-51)
solve the issue right now,
6:19
S… Speaker 3 (2026-05-11 09-01-51)
which is,
6:20
S… Speaker 2 (2026-05-11 09-01-51)
gosh,
6:21
S… Speaker 3 (2026-05-11 09-01-51)
I don't know how much it takes to advance the ticket ID.
6:25
S… Speaker 3 (2026-05-11 09-01-51)
So please find out.
6:27
S… Speaker 3 (2026-05-11 09-01-51)
And the second thing is Kurt has to make this change no matter what.
6:30
S… Speaker 3 (2026-05-11 09-01-51)
So because you can't have this issue occur again in the future,
6:34
S… Speaker 3 (2026-05-11 09-01-51)
it cannot be tied to any sort of mutable.
6:36
S… Speaker 3 (2026-05-11 09-01-51)
It cannot be tied to the user enterable field.
6:39
S… Speaker 3 (2026-05-11 09-01-51)
As long as the global org ID and the
6:43
S… Speaker 3 (2026-05-11 09-01-51)
global org ID will always be the same.
6:45
S… Speaker 3 (2026-05-11 09-01-51)
The enterprise ID will always be the same.
6:48
S… Speaker 3 (2026-05-11 09-01-51)
Sorry,
6:49
S… Speaker 3 (2026-05-11 09-01-51)
the store ID.
6:50
S… Speaker 3 (2026-05-11 09-01-51)
should never be the same,
6:51
S… Speaker 3 (2026-05-11 09-01-51)
but we currently are able to make the same.
6:54
S… Speaker 3 (2026-05-11 09-01-51)
And then the order ID is just a counter,
6:57
S… Speaker 3 (2026-05-11 09-01-51)
basically.
6:58
S… Speaker 1 (2026-05-11 09-01-51)
So you're saying,
7:01
S… Speaker 1 (2026-05-11 09-01-51)
yeah, the global store ID should never change and it's never going to be,
7:04
S… Speaker 1 (2026-05-11 09-01-51)
and it's not per global org ID,
7:07
S… Speaker 1 (2026-05-11 09-01-51)
right?
7:07
S… Speaker 1 (2026-05-11 09-01-51)
Your global store ID is unique across your universe?
7:10
S… Speaker 2 (2026-05-11 09-01-51)
Correct.
7:11
S… Speaker 2 (2026-05-11 09-01-51)
Yeah,
7:13
S… Speaker 1 (2026-05-11 09-01-51)
then it's the right thing to use for sure.
7:15
S… Speaker 2 (2026-05-11 09-01-51)
Yeah,
7:16
S… Speaker 3 (2026-05-11 09-01-51)
so current needs to make that change.
7:17
S… Speaker 3 (2026-05-11 09-01-51)
And then on top of that,
7:19
S… Speaker 3 (2026-05-11 09-01-51)
we should have business dating to it.
7:24
S… Speaker 1 (2026-05-11 09-01-51)
Yeah, that part,
7:25
S… Speaker 1 (2026-05-11 09-01-51)
I mean,
7:26
S… Speaker 1 (2026-05-11 09-01-51)
there should be some sequencing,
7:27
S… Speaker 1 (2026-05-11 09-01-51)
whether you want to use epoch or whatever,
7:30
S… Speaker 1 (2026-05-11 09-01-51)
because obviously you'll have multiple orders per day.
7:32
S… Speaker 1 (2026-05-11 09-01-51)
So you can include whatever you need in it beyond that.
7:36
S… Speaker 1 (2026-05-11 09-01-51)
Yes, agreed.
7:37
S… Speaker 1 (2026-05-11 09-01-51)
Something to ensure it's unique.
7:39
S… Speaker 1 (2026-05-11 09-01-51)
A critical part of it was to
7:43
S… Speaker 1 (2026-05-11 09-01-51)
make it non -guessable,
7:44
S… Speaker 1 (2026-05-11 09-01-51)
which Kirk and I discussed this,
7:46
S… Speaker 1 (2026-05-11 09-01-51)
you know.
7:47
S… Speaker 1 (2026-05-11 09-01-51)
Years ago when we first started and added ticket ID in the first place,
7:51
S… Speaker 1 (2026-05-11 09-01-51)
the presumption was it was going to be unique because I think he thought
7:55
S… Speaker 1 (2026-05-11 09-01-51)
the site ID would be unique enough across the universe,
8:00
S… Speaker 1 (2026-05-11 09-01-51)
but clearly it's not.
8:01
S… Speaker 1 (2026-05-11 09-01-51)
And then the sequencing of the elements in the ticket ID was so that the
8:05
S… Speaker 1 (2026-05-11 09-01-51)
sequence number wasn't the last thing,
8:06
S… Speaker 1 (2026-05-11 09-01-51)
so they were non -guessable.
8:08
S… Speaker 1 (2026-05-11 09-01-51)
You couldn't predict what the next one would be easily.
8:10
S… Speaker 2 (2026-05-11 09-01-51)
I mean,
8:11
S… Speaker 1 (2026-05-11 09-01-51)
it's still...
8:13
S… Speaker 1 (2026-05-11 09-01-51)
Somewhat easy to predict,
8:14
S… Speaker 1 (2026-05-11 09-01-51)
but it's at least not impossible.
8:15
S… Speaker 1 (2026-05-11 09-01-51)
So it needs to maintain all of that non -predictability,
8:19
S… Speaker 1 (2026-05-11 09-01-51)
non -sequential,
8:21
S… Speaker 1 (2026-05-11 09-01-51)
but immutable and globally
8:25
S… Speaker 1 (2026-05-11 09-01-51)
unique, however you can accomplish that.
8:28
S… Speaker 2 (2026-05-11 09-01-51)
All
8:33
S… Speaker 1 (2026-05-11 09-01-51)
right, so I'm going to make the four new locations
8:37
S… Speaker 1 (2026-05-11 09-01-51)
on my side with the four provided new global store IDs.
8:41
S… Speaker 1 (2026-05-11 09-01-51)
I will make keys assigned to those global store IDs.
8:47
S… Speaker 1 (2026-05-11 09-01-51)
I will copy the existing location definition.
8:52
S… Speaker 1 (2026-05-11 09-01-51)
And by that,
8:53
S… Speaker 1 (2026-05-11 09-01-51)
I mean not the data,
8:55
S… Speaker 1 (2026-05-11 09-01-51)
but just the name of the locations,
8:59
S… Speaker 1 (2026-05-11 09-01-51)
basically.
8:59
S… Speaker 1 (2026-05-11 09-01-51)
That's the only thing I really need.
9:01
S… Speaker 1 (2026-05-11 09-01-51)
I guess maybe I'll
9:05
S… Speaker 1 (2026-05-11 09-01-51)
rename the old ones to old,
9:06
S… Speaker 1 (2026-05-11 09-01-51)
and the new ones to new.
9:08
S… Speaker 3 (2026-05-11 09-01-51)
Just the dash old at the end of them.
9:10
S… Speaker 1 (2026-05-11 09-01-51)
Dash old at the old ones.
9:12
S… Speaker 1 (2026-05-11 09-01-51)
And yeah, these will just be the same name as the previous ones.
9:15
S… Speaker 1 (2026-05-11 09-01-51)
I'll copy the names.
9:18
S… Speaker 1 (2026-05-11 09-01-51)
And then I'll run around in the database and give you a number far
9:23
S… Speaker 1 (2026-05-11 09-01-51)
enough in advance.
9:23
S… Speaker 1 (2026-05-11 09-01-51)
So because we're doing hundreds of orders a day,
9:25
S… Speaker 1 (2026-05-11 09-01-51)
I'll need to give you a,
9:26
S… Speaker 1 (2026-05-11 09-01-51)
I mean, I can give you a current number,
9:28
S… Speaker 1 (2026-05-11 09-01-51)
which will update it the minute I send it to you.
9:30
S… Speaker 1 (2026-05-11 09-01-51)
But for those four stores,
9:34
S… Speaker 1 (2026-05-11 09-01-51)
what would be the old ones of those four stores?
9:38
S… Speaker 2 (2026-05-11 09-01-51)
Yeah.
9:46
S… Speaker 4 (2026-05-11 09-01-51)
Once you provide the key,
9:47
S… Speaker 4 (2026-05-11 09-01-51)
I think we can update that key on it today.
9:50
S… Speaker 4 (2026-05-11 09-01-51)
Right, Jonathan?
9:51
S… Speaker 2 (2026-05-11 09-01-51)
If you can.
9:54
S… Speaker 4 (2026-05-11 09-01-51)
Can you just
9:58
S… Speaker 4 (2026-05-11 09-01-51)
ask Mark?
10:00
S… Speaker 3 (2026-05-11 09-01-51)
if you can push it or overnight if there is no
10:04
S… Speaker 3 (2026-05-11 09-01-51)
other changes.
10:04
S… Speaker 2 (2026-05-11 09-01-51)
All
10:09
S… Speaker 1 (2026-05-11 09-01-51)
right, could you ask the highest part of market what?
10:12
S… Speaker 3 (2026-05-11 09-01-51)
If we can push that new
10:17
S… Speaker 3 (2026-05-11 09-01-51)
four stores with the keys,
10:19
S… Speaker 3 (2026-05-11 09-01-51)
if any other change is not made.
10:21
S… Speaker 2 (2026-05-11 09-01-51)
Okay,
10:25
S… Speaker 1 (2026-05-11 09-01-51)
back to Mark.
10:26
S… Speaker 2 (2026-05-11 09-01-51)
Jonathan,
10:36
S… Speaker 4 (2026-05-11 09-01-51)
do you have the breakdown of the ticket ID?
10:39
S… Speaker 2 (2026-05-11 09-01-51)
Oh,
10:42
S… Speaker 1 (2026-05-11 09-01-51)
I have one, I guess.
10:43
S… Speaker 1 (2026-05-11 09-01-51)
I don't remember exactly what it takes.
10:47
S… Speaker 4 (2026-05-11 09-01-51)
I wanted to make sure that my assumptions were correct.
10:50
S… Speaker 4 (2026-05-11 09-01-51)
I was trying to find the original email from Kurt from way back
10:54
S… Speaker 4 (2026-05-11 09-01-51)
in the day, but I can't figure out what to call it.
10:57
S… Speaker 2 (2026-05-11 09-01-51)
Okay,
10:58
S… Speaker 2 (2026-05-11 09-01-51)
I'll
11:15
S… Speaker 1 (2026-05-11 09-01-51)
find it.
11:16
S… Speaker 2 (2026-05-11 09-01-51)
Well,
11:21
S… Speaker 4 (2026-05-11 09-01-51)
I guess that's settled that for now.
11:23
S… Speaker 4 (2026-05-11 09-01-51)
I'll make the things,
11:24
S… Speaker 4 (2026-05-11 09-01-51)
I'll make the keys,
11:24
S… Speaker 4 (2026-05-11 09-01-51)
I'll make the locations,
11:25
S… Speaker 4 (2026-05-11 09-01-51)
and I'll give you the numbers.
11:34
S… Speaker 1 (2026-05-11 09-01-51)
yes i think we need to discuss one ticket which is regarding
11:38
S… Speaker 1 (2026-05-11 09-01-51)
when user order the item when user had the item
11:42
S… Speaker 1 (2026-05-11 09-01-51)
in a cart and applies the offer and if they
11:46
S… Speaker 1 (2026-05-11 09-01-51)
make any customization the office i think you need to
11:50
S… Speaker 1 (2026-05-11 09-01-51)
discuss that with jonathan right
11:54
S… Speaker 1 (2026-05-11 09-01-51)
Yeah.
11:55
S… Speaker 3 (2026-05-11 09-01-51)
So Jonathan,
11:56
S… Speaker 3 (2026-05-11 09-01-51)
that part that need to handle if any
12:01
S… Speaker 3 (2026-05-11 09-01-51)
changes made on the cart or if cart has been removed or
12:05
S… Speaker 3 (2026-05-11 09-01-51)
user just navigate back from the cart,
12:08
S… Speaker 3 (2026-05-11 09-01-51)
then we need to remove that discount from the cart.
12:11
S… Speaker 3 (2026-05-11 09-01-51)
So a few solutions we had discussed with Layton.
12:15
S… Speaker 3 (2026-05-11 09-01-51)
If you remember Layton,
12:16
S… Speaker 3 (2026-05-11 09-01-51)
we have discussed that we can make the API to call like it
12:21
S… Speaker 3 (2026-05-11 09-01-51)
will remove the
12:24
S… Speaker 3 (2026-05-11 09-01-51)
discount if it is not get used for
12:28
S… Speaker 1 (2026-05-11 09-01-51)
some time.
12:29
S… Speaker 3 (2026-05-11 09-01-51)
So we can add that API
12:33
S… Speaker 3 (2026-05-11 09-01-51)
to just.
12:33
S… Speaker 4 (2026-05-11 09-01-51)
So you want on redeem or something
12:38
S… Speaker 4 (2026-05-11 09-01-51)
along those lines,
12:38
S… Speaker 4 (2026-05-11 09-01-51)
right? I think we have redeem,
12:39
S… Speaker 4 (2026-05-11 09-01-51)
but we don't have on redeem.
12:40
S… Speaker 2 (2026-05-11 09-01-51)
Yeah.
12:42
S… Speaker 2 (2026-05-11 09-01-51)
Yeah,
12:44
S… Speaker 4 (2026-05-11 09-01-51)
we can do that.
12:45
S… Speaker 4 (2026-05-11 09-01-51)
Let me see if I have,
12:46
S… Speaker 4 (2026-05-11 09-01-51)
where is the,
12:47
S… Speaker 4 (2026-05-11 09-01-51)
just look at the APIs.
12:49
S… Speaker 2 (2026-05-11 09-01-51)
So
13:11
S… Speaker 4 (2026-05-11 09-01-51)
we do have void a reward.
13:13
S… Speaker 4 (2026-05-11 09-01-51)
Would that not work?
13:17
S… Speaker 4 (2026-05-11 09-01-51)
I mean, I guess I would need to change the implementation.
13:19
S… Speaker 4 (2026-05-11 09-01-51)
Currently, the redeem,
13:20
S… Speaker 4 (2026-05-11 09-01-51)
the unredeem,
13:22
S… Speaker 4 (2026-05-11 09-01-51)
or the delete of a redeem,
13:24
S… Speaker 2 (2026-05-11 09-01-51)
resumes for
13:30
S… Speaker 1 (2026-05-11 09-01-51)
some reason.
13:31
S… Speaker 4 (2026-05-11 09-01-51)
What's that?
13:33
S… Speaker 1 (2026-05-11 09-01-51)
Yeah,
13:34
S… Speaker 1 (2026-05-11 09-01-51)
if you're okay to push things to those stores.
13:38
S… Speaker 2 (2026-05-11 09-01-51)
Okay.
13:40
S… Speaker 2 (2026-05-11 09-01-51)
But go ahead,
13:43
S… Speaker 4 (2026-05-11 09-01-51)
Nathan. There is a unredeem call.
13:59
S… Speaker 4 (2026-05-11 09-01-51)
I'm just curious if we can't use this one or if it needs some backend changes.
14:03
S… Speaker 4 (2026-05-11 09-01-51)
I'm not sure what assumptions it makes about the state of the order.
14:07
S… Speaker 4 (2026-05-11 09-01-51)
I guess I don't need to make a new one.
14:12
S… Speaker 1 (2026-05-11 09-01-51)
Let me kind of sit here.
14:14
S… Speaker 1 (2026-05-11 09-01-51)
So, Yash,
14:15
S… Speaker 1 (2026-05-11 09-01-51)
what I had asked was that when you have
14:19
S… Speaker 1 (2026-05-11 09-01-51)
a loyalty order,
14:20
S… Speaker 1 (2026-05-11 09-01-51)
okay, or when you have an order in old plum ordering,
14:22
S… Speaker 1 (2026-05-11 09-01-51)
and you navigate to the cart,
14:24
S… Speaker 2 (2026-05-11 09-01-51)
okay,
14:25
S… Speaker 1 (2026-05-11 09-01-51)
and you apply an offer,
14:27
S… Speaker 1 (2026-05-11 09-01-51)
right?
14:28
S… Speaker 1 (2026-05-11 09-01-51)
When you navigate away from the cart,
14:30
S… Speaker 1 (2026-05-11 09-01-51)
I want the offer to be voided.
14:35
S… Speaker 1 (2026-05-11 09-01-51)
which is what Leighton is saying you would do.
14:37
S… Speaker 1 (2026-05-11 09-01-51)
That would fulfill our needs.
14:38
S… Speaker 1 (2026-05-11 09-01-51)
The reason I want the offer to be voided is because that will trigger Leighton to provide
14:42
S… Speaker 1 (2026-05-11 09-01-51)
the offer back to the end user and it will make it available in their
14:46
S… Speaker 1 (2026-05-11 09-01-51)
list of available offers again immediately.
14:51
S… Speaker 1 (2026-05-11 09-01-51)
Right.
14:51
S… Speaker 1 (2026-05-11 09-01-51)
We have all this other stuff in place just
14:56
S… Speaker 1 (2026-05-11 09-01-51)
in case it's not.
14:57
S… Speaker 1 (2026-05-11 09-01-51)
However,
14:57
S… Speaker 1 (2026-05-11 09-01-51)
the issue we have...
15:00
S… Speaker 2 (2026-05-11 09-01-51)
finding is that users will add an off to their cart and
15:04
S… Speaker 2 (2026-05-11 09-01-51)
then they will go leave it and do other things to the cart.
15:06
S… Speaker 2 (2026-05-11 09-01-51)
So they will leave it,
15:07
S… Speaker 2 (2026-05-11 09-01-51)
go by changes,
15:08
S… Speaker 2 (2026-05-11 09-01-51)
change store,
15:09
S… Speaker 2 (2026-05-11 09-01-51)
whatever,
15:10
S… Speaker 2 (2026-05-11 09-01-51)
change cart,
15:12
S… Speaker 2 (2026-05-11 09-01-51)
and they will try to go apply it again and they can't.
15:14
S… Speaker 2 (2026-05-11 09-01-51)
So for instance,
15:16
S… Speaker 2 (2026-05-11 09-01-51)
user opens the store.
15:18
S… Speaker 2 (2026-05-11 09-01-51)
creates an order with a with a coffee on it applies a a discount to
15:22
S… Speaker 2 (2026-05-11 09-01-51)
make the coffee free okay then they notice wait a minute i
15:27
S… Speaker 2 (2026-05-11 09-01-51)
don't want this for this store i want it for this other store or hey i
15:31
S… Speaker 2 (2026-05-11 09-01-51)
want to make a change so they go they leave the cart entirely they
15:35
S… Speaker 2 (2026-05-11 09-01-51)
go change a store and then they go and and uh
15:40
S… Speaker 2 (2026-05-11 09-01-51)
try to place the coffee again then they try to go place their uh
15:45
S… Speaker 2 (2026-05-11 09-01-51)
the discount again.
15:46
S… Speaker 2 (2026-05-11 09-01-51)
And they can't because they no longer have that lowest reward on their account because it's been used.
15:51
S… Speaker 2 (2026-05-11 09-01-51)
And it's still pending usage.
15:56
S… Speaker 3 (2026-05-11 09-01-51)
Yeah, but as there will be multiple
16:00
S… Speaker 3 (2026-05-11 09-01-51)
sessions and multiple devices available on
16:04
S… Speaker 3 (2026-05-11 09-01-51)
the ordering side,
16:05
S… Speaker 3 (2026-05-11 09-01-51)
that's why I want to make this
16:09
S… Speaker 3 (2026-05-11 09-01-51)
call at the loyalty end.
16:10
S… Speaker 3 (2026-05-11 09-01-51)
Because if we applied on this one store with one
16:14
S… Speaker 3 (2026-05-11 09-01-51)
session on one device,
16:16
S… Speaker 3 (2026-05-11 09-01-51)
but if I don't move into the...
16:21
S… Speaker 3 (2026-05-11 09-01-51)
other store or if i'm still on my cart
16:25
S… Speaker 3 (2026-05-11 09-01-51)
is created with that applied reward and then i i
16:29
S… Speaker 3 (2026-05-11 09-01-51)
won't able to see that offer if i use the another
16:33
S… Speaker 3 (2026-05-11 09-01-51)
device and see the offer list
16:38
S… Speaker 3 (2026-05-11 09-01-51)
So that's why I came up
16:42
S… Speaker 3 (2026-05-11 09-01-51)
with one solution to like if it is applied on one device
16:46
S… Speaker 3 (2026-05-11 09-01-51)
then we can like,
16:48
S… Speaker 3 (2026-05-11 09-01-51)
like Leighton will mark that as a reserve
16:52
S… Speaker 3 (2026-05-11 09-01-51)
on the other device.
16:53
S… Speaker 3 (2026-05-11 09-01-51)
That will be shown but with the message that
16:58
S… Speaker 3 (2026-05-11 09-01-51)
it cannot be used as used into the other card or
17:02
S… Speaker 1 (2026-05-11 09-01-51)
device.
17:03
S… Speaker 3 (2026-05-11 09-01-51)
So if user do the payment,
17:06
S… Speaker 3 (2026-05-11 09-01-51)
then it will be moved to the consume state,
17:09
S… Speaker 3 (2026-05-11 09-01-51)
that reward,
17:09
S… Speaker 3 (2026-05-11 09-01-51)
then it will not show on the other devices as well.
17:12
S… Speaker 3 (2026-05-11 09-01-51)
But if user leaves the card or it will not be used
17:16
S… Speaker 3 (2026-05-11 09-01-51)
for some time,
17:17
S… Speaker 3 (2026-05-11 09-01-51)
then it will become available to other devices.
17:20
S… Speaker 2 (2026-05-11 09-01-51)
Here's the thing.
17:22
S… Speaker 2 (2026-05-11 09-01-51)
Up until one,
17:25
S… Speaker 2 (2026-05-11 09-01-51)
two, three.
17:27
S… Speaker 2 (2026-05-11 09-01-51)
Step three,
17:27
S… Speaker 2 (2026-05-11 09-01-51)
we have all that.
17:29
S… Speaker 2 (2026-05-11 09-01-51)
When a loyalty offer is selected on a
17:33
S… Speaker 2 (2026-05-11 09-01-51)
device, it's temporarily reserved.
17:35
S… Speaker 2 (2026-05-11 09-01-51)
Layton does not consume it.
17:37
S… Speaker 2 (2026-05-11 09-01-51)
He just marks it as pending.
17:38
S… Speaker 2 (2026-05-11 09-01-51)
When an offer is marked as
17:43
S… Speaker 2 (2026-05-11 09-01-51)
pending, no one else can use it.
17:44
S… Speaker 2 (2026-05-11 09-01-51)
To the end user,
17:46
S… Speaker 2 (2026-05-11 09-01-51)
it's considered used.
17:47
S… Speaker 2 (2026-05-11 09-01-51)
Because to us,
17:49
S… Speaker 2 (2026-05-11 09-01-51)
it is used.
17:50
S… Speaker 2 (2026-05-11 09-01-51)
It's pending.
17:51
S… Speaker 2 (2026-05-11 09-01-51)
We're waiting for it to be confirmed.
17:52
S… Speaker 2 (2026-05-11 09-01-51)
When Layton actually receives a confirmation because he receives the closed order,
17:57
S… Speaker 2 (2026-05-11 09-01-51)
and he sees the reward is applied in closed order,
17:59
S… Speaker 2 (2026-05-11 09-01-51)
he does consume the offer.
18:00
S… Speaker 2 (2026-05-11 09-01-51)
The thing is here is that when a user leaves a checkout,
18:04
S… Speaker 2 (2026-05-11 09-01-51)
this is what I'm asking you.
18:06
S… Speaker 2 (2026-05-11 09-01-51)
I'm asking you to do the unredeemed call to make it available again.
18:10
S… Speaker 2 (2026-05-11 09-01-51)
You have to tell Layton that they're leaving the carts so that
18:15
S… Speaker 2 (2026-05-11 09-01-51)
way Layton can mark it as available again for the end user.
18:18
S… Speaker 2 (2026-05-11 09-01-51)
Layton has no control over this.
18:20
S… Speaker 2 (2026-05-11 09-01-51)
This is not an action from his end.
18:21
S… Speaker 2 (2026-05-11 09-01-51)
This is an action from the plum ordering end because this is where the action is occurring.
18:28
S… Speaker 2 (2026-05-11 09-01-51)
So that's what I'm asking you.
18:30
S… Speaker 1 (2026-05-11 09-01-51)
What I wanted to point out was
18:34
S… Speaker 1 (2026-05-11 09-01-51)
when I last tested this,
18:36
S… Speaker 1 (2026-05-11 09-01-51)
just to add more chaos,
18:38
S… Speaker 1 (2026-05-11 09-01-51)
if that's appropriate.
18:40
S… Speaker 1 (2026-05-11 09-01-51)
When I last evaluated this issue,
18:43
S… Speaker 1 (2026-05-11 09-01-51)
I was getting a redeem call for a check that wasn't
18:48
S… Speaker 1 (2026-05-11 09-01-51)
closed.
18:50
S… Speaker 1 (2026-05-11 09-01-51)
Now, in the current code,
18:51
S… Speaker 1 (2026-05-11 09-01-51)
that redeem call redeems it because I just presume you guys know what you're doing.
18:55
S… Speaker 1 (2026-05-11 09-01-51)
If you call me to redeem it,
18:57
S… Speaker 1 (2026-05-11 09-01-51)
I actually consume it.
18:58
S… Speaker 1 (2026-05-11 09-01-51)
And so the only way to unconsume it is to unredeem it.
19:01
S… Speaker 1 (2026-05-11 09-01-51)
If, in fact,
19:02
S… Speaker 1 (2026-05-11 09-01-51)
you had simply linked it,
19:03
S… Speaker 1 (2026-05-11 09-01-51)
it would have simply disappeared based on what Jonathan was saying.
19:07
S… Speaker 1 (2026-05-11 09-01-51)
If I keep it in a pending state,
19:09
S… Speaker 1 (2026-05-11 09-01-51)
I never hear from that order.
19:10
S… Speaker 1 (2026-05-11 09-01-51)
When we go through order reconciliation at some point,
19:13
S… Speaker 1 (2026-05-11 09-01-51)
I will throw it away.
19:14
S… Speaker 1 (2026-05-11 09-01-51)
Or you could call unredeem.
19:18
S… Speaker 1 (2026-05-11 09-01-51)
But I was surprised to find a redeem call called for rewards
19:23
S… Speaker 1 (2026-05-11 09-01-51)
that were simply associated with an order,
19:26
S… Speaker 1 (2026-05-11 09-01-51)
and that order hadn't been closed yet.
19:28
S… Speaker 1 (2026-05-11 09-01-51)
Because that wasn't sort of the way it was originally designed.
19:32
S… Speaker 1 (2026-05-11 09-01-51)
Redeem should actually only have been called when the check was settled,
19:36
S… Speaker 1 (2026-05-11 09-01-51)
in which case the offer is truly consumed at that point.
19:40
S… Speaker 1 (2026-05-11 09-01-51)
Calling on redeem at this point would unconsume it,
19:43
S… Speaker 1 (2026-05-11 09-01-51)
which I guess is fine in the current flow,
19:45
S… Speaker 1 (2026-05-11 09-01-51)
but I just wanted to...
19:47
S… Speaker 1 (2026-05-11 09-01-51)
point out that that wasn't the intent behind the original redeem call but
19:51
S… Speaker 1 (2026-05-11 09-01-51)
now it seems like it gets called all the time just when you associate an order
19:55
S… Speaker 1 (2026-05-11 09-01-51)
an offer with a check even before you've checked out
20:00
S… Speaker 3 (2026-05-11 09-01-51)
Okay,
20:01
S… Speaker 1 (2026-05-11 09-01-51)
so we can do like on this case,
20:04
S… Speaker 1 (2026-05-11 09-01-51)
we can make a handler to unredeem if it
20:08
S… Speaker 1 (2026-05-11 09-01-51)
is applied for like more than five or 10 minutes,
20:11
S… Speaker 1 (2026-05-11 09-01-51)
but no action has been made.
20:14
S… Speaker 1 (2026-05-11 09-01-51)
But this,
20:16
S… Speaker 1 (2026-05-11 09-01-51)
when it is pending or reserved,
20:18
S… Speaker 1 (2026-05-11 09-01-51)
currently it is not showing if I'm
20:22
S… Speaker 1 (2026-05-11 09-01-51)
using the another device and...
20:25
S… Speaker 2 (2026-05-11 09-01-51)
That is correct.
20:26
S… Speaker 2 (2026-05-11 09-01-51)
Part of it is because you called it...
20:28
S… Speaker 2 (2026-05-11 09-01-51)
You call the redeem call.
20:30
S… Speaker 2 (2026-05-11 09-01-51)
Right now,
20:30
S… Speaker 2 (2026-05-11 09-01-51)
that's what I was getting at.
20:31
S… Speaker 2 (2026-05-11 09-01-51)
Right now, it calls the redeem call,
20:32
S… Speaker 2 (2026-05-11 09-01-51)
which consumes it.
20:33
S… Speaker 2 (2026-05-11 09-01-51)
It subtracts it from your account.
20:35
S… Speaker 2 (2026-05-11 09-01-51)
It takes the money out of your voucher.
20:38
S… Speaker 2 (2026-05-11 09-01-51)
When you call redeem currently,
20:40
S… Speaker 2 (2026-05-11 09-01-51)
it is redeemed because that's what the API call does.
20:44
S… Speaker 2 (2026-05-11 09-01-51)
If you were simply to have associated,
20:46
S… Speaker 2 (2026-05-11 09-01-51)
then maybe I could make
20:50
S… Speaker 2 (2026-05-11 09-01-51)
some exception to show the offer still available.
20:55
S… Speaker 2 (2026-05-11 09-01-51)
I'm curious what other apps do.
20:57
S… Speaker 2 (2026-05-11 09-01-51)
If I go to the website and associate,
20:58
S… Speaker 2 (2026-05-11 09-01-51)
add an offer to some check for Chipotle and then go to my mobile
21:03
S… Speaker 2 (2026-05-11 09-01-51)
app, can I still attach it in a cart in there?
21:05
S… Speaker 2 (2026-05-11 09-01-51)
I think Jonathan's point is valid in that
21:09
S… Speaker 2 (2026-05-11 09-01-51)
you would expect to not see it again if you had two carts open.
21:13
S… Speaker 2 (2026-05-11 09-01-51)
I guess we should decide if that's the
21:17
S… Speaker 2 (2026-05-11 09-01-51)
functionality we want to have the offer still available if I have two carts open
21:21
S… Speaker 2 (2026-05-11 09-01-51)
on two different devices.
21:24
S… Speaker 1 (2026-05-11 09-01-51)
Jonathan, can't we show that offer to another device as well,
21:28
S… Speaker 1 (2026-05-11 09-01-51)
but with the message that it is already consumed on other
21:32
S… Speaker 1 (2026-05-11 09-01-51)
lists?
21:33
S… Speaker 3 (2026-05-11 09-01-51)
I
21:39
S… Speaker 4 (2026-05-11 09-01-51)
don't think that's worth it.
21:39
S… Speaker 4 (2026-05-11 09-01-51)
I don't think that's...
21:41
S… Speaker 3 (2026-05-11 09-01-51)
I think
21:51
S… Speaker 2 (2026-05-11 09-01-51)
if I log into my same account on a different device,
21:53
S… Speaker 2 (2026-05-11 09-01-51)
I get the same card.
21:54
S… Speaker 4 (2026-05-11 09-01-51)
So the case where that would occur,
21:57
S… Speaker 4 (2026-05-11 09-01-51)
Yash,
21:58
S… Speaker 4 (2026-05-11 09-01-51)
is where you have a person using two different devices at the same time.
22:02
S… Speaker 1 (2026-05-11 09-01-51)
Yeah, right.
22:05
S… Speaker 4 (2026-05-11 09-01-51)
So if they use different devices at the same time,
22:07
S… Speaker 4 (2026-05-11 09-01-51)
then they would have to do the assumption that I have it open here,
22:11
S… Speaker 4 (2026-05-11 09-01-51)
and I've used it,
22:11
S… Speaker 4 (2026-05-11 09-01-51)
and I have it open here,
22:12
S… Speaker 4 (2026-05-11 09-01-51)
I can't use it.
22:14
S… Speaker 2 (2026-05-11 09-01-51)
That's what you have now.
22:17
S… Speaker 3 (2026-05-11 09-01-51)
Yeah.
22:18
S… Speaker 4 (2026-05-11 09-01-51)
So that's fine.
22:22
S… Speaker 1 (2026-05-11 09-01-51)
Just to make sure we
22:26
S… Speaker 1 (2026-05-11 09-01-51)
can show that to the other devices as well,
22:29
S… Speaker 1 (2026-05-11 09-01-51)
so that they shouldn't worry about that has been consumed.
22:33
S… Speaker 1 (2026-05-11 09-01-51)
So we can just show the software message that it is already in
22:37
S… Speaker 1 (2026-05-11 09-01-51)
use.
22:38
S… Speaker 4 (2026-05-11 09-01-51)
I think we're worrying about something that might not happen.
22:42
S… Speaker 4 (2026-05-11 09-01-51)
That might not be an issue.
22:44
S… Speaker 4 (2026-05-11 09-01-51)
That's the problem I think right
22:48
S… Speaker 4 (2026-05-11 09-01-51)
now. That's worrying about something that might not be an issue or may not be required,
22:57
S… Speaker 4 (2026-05-11 09-01-51)
I guess.
22:58
S… Speaker 4 (2026-05-11 09-01-51)
What I'm really asking for...
23:02
S… Speaker 1 (2026-05-11 09-01-51)
Yeah, that thing you can cover with making a
23:06
S… Speaker 1 (2026-05-11 09-01-51)
handler to unredame the reward if it is not in use for some
23:10
S… Speaker 1 (2026-05-11 09-01-51)
time. But I just want to,
23:15
S… Speaker 1 (2026-05-11 09-01-51)
if we can cover this case as well to show the reward to
23:19
S… Speaker 1 (2026-05-11 09-01-51)
other places so that it won't be in future,
23:22
S… Speaker 1 (2026-05-11 09-01-51)
if the user is using the login at two places,
23:26
S… Speaker 1 (2026-05-11 09-01-51)
then it won't be.
23:27
S… Speaker 4 (2026-05-11 09-01-51)
What I'm trying to tell you is that I don't think that's required.
23:33
S… Speaker 4 (2026-05-11 09-01-51)
It's worrying about an edge case that is an edge case,
23:35
S… Speaker 4 (2026-05-11 09-01-51)
sure, but I don't think an edge case that is ultimately needed to
23:40
S… Speaker 4 (2026-05-11 09-01-51)
be covered at this current point in time.
23:41
S… Speaker 1 (2026-05-11 09-01-51)
I do
23:45
S… Speaker 2 (2026-05-11 09-01-51)
agree that we have two different issues,
23:48
S… Speaker 2 (2026-05-11 09-01-51)
right? One is the abandoned carts and to fix the on redeem.
23:51
S… Speaker 2 (2026-05-11 09-01-51)
There is an API call already there,
23:53
S… Speaker 2 (2026-05-11 09-01-51)
so you should try it.
23:54
S… Speaker 2 (2026-05-11 09-01-51)
Call the delete version of the redeem call and see if that doesn't
23:58
S… Speaker 2 (2026-05-11 09-01-51)
solve your problem.
23:59
S… Speaker 2 (2026-05-11 09-01-51)
If it doesn't,
24:00
S… Speaker 2 (2026-05-11 09-01-51)
then we can talk about potential modifications to how that call works.
24:04
S… Speaker 2 (2026-05-11 09-01-51)
I didn't check the logs to see if anybody has ever called it,
24:08
S… Speaker 2 (2026-05-11 09-01-51)
but it's there.
24:11
S… Speaker 2 (2026-05-11 09-01-51)
It was specced by Kurt in the initial go
24:15
S… Speaker 2 (2026-05-11 09-01-51)
-around, so I'm presuming it works,
24:17
S… Speaker 2 (2026-05-11 09-01-51)
but I don't know.
24:17
S… Speaker 2 (2026-05-11 09-01-51)
And then again,
24:19
S… Speaker 2 (2026-05-11 09-01-51)
the second one is whether or not we want to allow reuse in
24:23
S… Speaker 2 (2026-05-11 09-01-51)
shopping carts and what messaging we should have.
24:25
S… Speaker 2 (2026-05-11 09-01-51)
I agree that that's...
24:28
S… Speaker 2 (2026-05-11 09-01-51)
I would call it a nice -to -have or a feature enhancement or whatever.
24:31
S… Speaker 2 (2026-05-11 09-01-51)
The way it currently works now is,
24:33
S… Speaker 2 (2026-05-11 09-01-51)
I think,

ఈ అపోహింగ్‌ను (స్వయంలేని పద గుర్తింపు) సంప్రదాయం (ఆఫ్యుటికల్ ప్రసంగ గుర్తింపు) రూపొందించారు. దోషములు వుండు. ఫార్మేట్‌ను సంక్లిష్టమైన ఆడియోకు వ్యతిరేకంగా నిర్ధారించండి. AI విధానము

❤️ ప్రేమ STT.ai? మీ స్నేహితులకు చెప్పండి!
సారాంశం
ఈ పిక్సెస్ యొక్క యాక్సెస్‌బిలిటి సంగ్రహం ఉద్భవించుటకు కాంక్వెరర్‌ను నొక్కుము.
పరిగణనలోకి...
ఈ రిపోర్టు గురించి AI ను అడుగుము
ఈ అస్థికల పేటిక గురించి ఏమైనా అడగండి —⁠ ఏ.
మరొకరు రాసుకోండి