►
Description
Discussion of Store Pickup functionality with Multi-Source support
A
A
So
today
we
will
talk
about
the
motive.
Today
we
will
talk
about
the
functionality
of
the
store,
pickup
and
I
will
describe
the
the
proposal
how
the
store
pickup
can
be
implemented
in
the
MVP
functionality,
so
the
MVP
States
for
the
minimal
Viable
Product.
Also,
we
have
several
honored
guests
invited
to
this
meeting
and
one
of
these
guests
Paul
will
demonstrate
how
they
implemented
for
pickup,
and
he
will
share
his
experience
and
insight
regarding
how
it's
better
to
implement
or
how
to
better,
not
to
implement
the
store
pick
up
for
magenta.
A
A
A
A
Laptops
PCs
and
I
will
I
will
be
reading
it
from
from
my
screen.
So
the
main
idea
how
this
topic
up
can
be
implemented
in
the
magenta,
supporting
the
multi-source
inventory.
So
actually,
the
main
idea
that
we
saw
there
how
they
store
pick
up
will
affect
the
means
customer
and
how
it's
going
to
be
implemented
from
the
customer
point
of
view
so
from
the
customer.
A
Actually,
we
don't
interfere
and
we
we
are
not
going
to
affect
the
existing
product
page
and
the
store
pick
up
would
be
added
as
additional
shipping
method
and
when
the
order
is
being
placed
that
the
shipping
step,
we
introduce
an
ability
to
choose
this
to
pick
up
out
of
the
load
shipping
method.
So
currently
you
can
see
how
to
look
like
right
now,
so
it's
implemented
right
now,
so
on
a
ship.
A
Customer
can
can
choose
particular
source
in
the
scope
in
the
scope
was
a
given
stock,
which
should
be
used
to
fulfill
the
order.
Here.
We
want
to
introduce
pretty
important
assumption
that
each
order
should
be
fulfilled
just
from
one
and
only
one,
the
cap
location,
so
we
consider
the
the
pickup
location
as
the
shipping
address,
and
we
want
to
introduce
a
limitation
that
it
shouldn't
be
possible
to
choose
to
specify
a
different
pickup
location
for
different
card
items.
A
So,
for
example,
in
case
of
this
order,
you
can
see
that
there
are
two
different
order
items
or
at
this
time
these
are
cart
items
and
we
would
propose
to
introduce
the
limitation
that
it's
not
possible
to
specify
different
pickup
location
for
different
cart
items
in
the
scope
of
one
order.
Actually,
we
can
we
can
implement
this
functionality,
but
this
one's
around
it
would
be
pretty
pretty
similar
to
the
model
to
the
existing
multi
shaken,
so
how
they
exist.
B
A
For
example,
if
we
will
allow
to
to
to
specify
store,
pickup
based
on
the
card
item
and
the
different
pickup
location,
going
to
be
going
to
be
chosen
for
these
two
cart
items
under
the
hood,
we
will
create
two
different
orders
and
the
service
is
pretty
similar.
How
the
motor
shipment
works.
Potentially
even
we
can
make
an
integration
with
the
multi
chicken
and
consider
that
this
as
a
case
of
the
motor
ship
into
two
different
store
pickup
locations,
but
in
a
minimal
Viable
Product
of.
A
In
a
minimal
Viable
Product
version,
it
is
proposed
to
avoid
integration
with
multi
shipping
and
provide
an
ability
to
choose
a
single
store,
pickup
location
from
let's
say,
a
drop-down
box.
So
how
it's
gonna
look
like.
So
in
a
shipping
method,
we
choose
a
store
pickup
and
after
we
should
restore
pickup.
The
drop-down
box
appears
with
all
possible
pickup
locations,
and
here
you
can
see
that
the
address
shipping
addresses
disappear
because
we
will
use
the
shipping
address
of
the
source.
So
we
will
use
the
source
address
with
a
shipping
address
in
this
case
and.
A
Here,
like
it's
still
an
open
question,
probably
it's
technical,
it's
more
technical
than
functional
one,
whether
we
have
to
add
this
source
selected
for
the
store
pickup
as
an
extension
attribute
for
the
order
created,
or
we
can
just
check
the
check.
The
shipping
address
that
it
matches
to
the
to
the
one
of
the
addresses
of
our
sources
and
based
on
the
address
match.
We
can
decide
that
that
order
was
placed
as
a
store
pickup
order.
So
here
here
is
the
question
which
we
shall
erase
and
currently
I,
don't
know.
A
So
currently,
our
saleable
quantity
is
ten
so
because
we
just
sum
up
all
quantities
altogether
which
give
us
five
plus
four
plus
one,
and
if
customer
has
ordered
eight
items
of
sq1
and
at
the
shipment
step,
he
he
chose
source
a
for
the
store
pickup.
Currently
we
see
that
we
are
not
able
to
fulfill
this
order
because
currently
source
a
contains
that
five
items
so
we
need
to
and
what
the
system
does
in
this
case.
A
So
because
the
initial,
the
initial
vision
of
the
store
pickup
was,
was
to
create
that
correspondent
stocks
for
each
particular
source,
but
that
will
introduce
quite
a
lot
of
indexation
and
that
we
that
could
be
redundant.
That's
why
I
try
to
avoid
it
as
much
as
possible
and
I
wanted
to
reuse
our
existing
indexation
mechanism.
So
in
this
proposal,
I
described
that
we
will
still
make
the
reservation
as
we
do
as
we
do
it
right
now,
so
we
will
place
the
reservation
for
eight
items
of
sq1
on
custom
stock.
A
So,
as
you
know,
we
place
a
massage
support
reservation
on
the
stock
level,
but
not
on
the
source
one,
and
we
don't
want
to
introduce
at
least
this
this
particular
situation.
We
don't
introduce
the
source
level
reservation,
so
that
will
still
create
the
reservation
for
a
custom
stock
which
will
affect
our
saleable
quantity
and
but
in
the
order
object,
we
will
specify
that
this
order
gonna
be
fulfilled
from
that
from
that
from
the
source.
A
A
and
here
merchants
have
to
make
the
internal
transportation
of
three
items
from
source
B
to
source
a
to
fulfill
tzer's
order
and
when
the
required
transportation
would
be
done,
merchants
have
to
initiate
the
the
delivery
of
the
ready
for
pickup
email,
which
will
notify
customers.
That
order
is
ready
for
store
pickup
and
he
can
come
to
this
particular
location
and
grab
the
prepared
items.
A
A
He
should
be
able
to
specify
whether
particular
source
support
historical
functionality
or
not.
So,
for
example,
we
have
the
brick-and-mortar
store
and
brick
a
brick-and-mortar
store
supposed
to
support
the
store,
become
functionality
in
case.
If
you
have
the
warehouse,
maybe
warehouse
should
not
support
the
store
because
functionality
so
that
it
is
proposed
to
introduce
the
kid
extension
in
useful
source
entities
and
the
ability
to
specify
this
attribute
we're
both
admin
panel
or
admin
panel
on
the
source,
editing
page
as
well
as
REST
API,
to
specify
this
attribute
whether
source
is
support
and
a
store.
A
But
along
is
that
we
have
to
notify
merchant
that
some
internal
transportation
need
to
be
done
to
fulfill
the
order,
if,
like
in
the
case,
what
I
described
earlier,
if
you
don't
have
enough
quantity
and
perky
particular
source
to
fulfill
the
order.
So
probably
we
can
introduce
this.
This
check
for
merchant
on
the
shipment
step
and
check
whether
we
have
enough
quantity
to
fulfill
that
order
on
some
internal
transportation
need
to
be
need
to
be
applied
here.
A
B
Thanks
again,
so
until
we
have
any
ability
to
or
have
we
thought
about,
giving
the
merchants
an
option
of
whether
they
want
to
do
that
transfer
not
what
I
mean
is
in
this
example.
If
they
had
to
ordered
eight
of
skew
one
and
they
had
selected
source
a
for
store
pickup
that
we
wouldn't
allow
them
to
complete
it,
because
there's
just
not
enough
there
I
mean
some
merchants
may
not
want
to
have
to
transfer
the
inventory
just
to
be
able
to
fulfill
the
order.
A
The
issue
the
issue
is
that
currently
we
can
see
there
our
stock
at
the
school
and
currently
like
the
stove,
is
determined
for
customer
as
soon
as
he
come
to
the
to
the
to
the
to
the
magenta
web
site.
So
we
check
whether,
like
whether
product
is
accessible
or
not
like
whether
it's
in
stock
out
of
this
particular
store,
and
if
we
will
allow
to
check
voltages
based
on
the
on
the
source
level,
we
will
be
switching
this
go
and
that
will
be
reduced.
A
And,
moreover,
like
we
don't
know
like,
potentially,
we
can
introduce
stocks
/
sources,
but
that
this
this
can
lead
to
the
quantity
inconsistency.
Because
in
this
case
we
will
place
the
reservation
not
on
a
global
stock
like
not
on
a
custom
stock.
But
we
will
place
a
reservation
for
stock,
which
represents
the
source,
a
and
remember
our
previous
discussion
when
why
we
don't
recommend
to
assign
the
same
source
to
different
stocks,
because
the
reservation
could
be
placed
to
one
stock,
and
we
don't
consider
that.
A
B
Now,
I
understand
that
scenario
and
I
understand
how
all
that
works.
I'm
just
thinking
about
this
from
a
merchant
perspective,
because
they
could
get
some
really
ugly
scenarios
or
imagine
they
have
say
three
sources
that
are
all
in
a
stock.
It's
assigned
to
the
one
website
that
they
have
so
somebody
places
in
order
for
three
items
like
they
want
to
get.
You
know
three
t-shirts,
so
it's
in
stock
because
they
have
maybe
one
in
each
source,
so
they're
gonna,
say:
ok,
great
I
want
to
get
it
from
source
a
and
they
complete
their
checkout.
B
Now
the
merchant
has
one
t-shirt
and
a
1
and
B,
and
one
and
C
they
have
to
get
two
shirts
from
B
and
C
to
a
before.
They
can
let
the
customer
know
they
can
come
by
and
pick
them
up
it.
So
that
seems
quite
difficult
or
at
least
that
they
wouldn't
know
they
would
have
that
extra
expense
upfront.
It
would
only
be
after
the
order
came
in.
A
B
A
A
B
Guess
what
I'm
trying
to
understand
is
if
we
create
a
store,
pickup
feature
in
the
way
you've
described
here.
I
would
just
want
to
be
very
clear
on
the
types
of
merchants
use
cases
that
it
covers
on
the
ones
that
it
does
not
because
it
doesn't
have
reservation
at
the
source
level
or
you
know,
selecting
pickup
at
the
source
level.
B
B
That
wouldn't
be
any
better,
because
it's
imagine
it's
the
same
scenario.
Well,
I
have
t-shirt
one
two
three
only
stock
in
one
of
my
sources
but
I
have
three
sources
assigned
to
my
stock.
The
customer
can
really
pick
any
of
those
three
sources
as
their
pickup
location.
Then,
if
they
have
selected
one
wear
shirt.
One
two
three
is
not
in
this
source:
the
merchant
has
to
transfer
it
mm-hmm.
C
Just
a
second
yeah
in
the
cases
where
we
had
this
scenario
we
usually
had,
we
had
a
central
warehouse,
an
actual
store
and
in
practice
we
didn't
ever
get
to
the
situation
that
we
needed
multiple
sources
for
products
to
be
cross,
docked
to
the
USA
to
be
delivered
to
the
to
the
actual
store
by
the
customers,
picking
and
picking
it
up
and
and
all
our
customers
that
implement
this
case.
They
said
it
yet
it's
our
own
risk
that
we
did.
C
B
Yeah
yeah,
thank
you.
I
understand
that
so
I,
just
I
just
want
to
be
clear
on
what
what
it's
capable
of
and
what
it's
not
capable
of
so
then,
when
we
you
know,
are
essentially
describing
the
future
to
merchants.
They
understand
whether
it
will
meet
their
use
cases.
So
the
situation
that
you
described,
where
there's
a
central
warehouse
and
more
likely
than
not
as
orders,
come
in
then
they're
dispatched
from
the
central
warehouse
to
the
place
that
needs
to
be
picked
up,
and
then
the
customer
is
notified
that
it's
available
for
pickup.
D
B
From
a
saleability
perspective,
you
would
just
have
all
the
inventory
of
the
central
warehouse
as
a
part
of
the
stock
and
then
pick
up
from
the
central
warehouse
would
be
disabled,
so
the
inventory
would
be
there,
but
pick
up
would
not
be
allowed.
You
know,
and
it
would
understand
the
quantities
correctly.
C
B
B
B
A
That's
the
topic
I
also
opportu
discuss,
but
this
is
probably
this
app
which
supposed
to
substitute
the
source
selection
algorithm.
So
in
case
merchant
has
to
make
sure
they're
I
enough
quantity
to
the
order
on
the
selected
application
and
the
scene.
That
is
enough.
He
can
just
initiate
the
process
of
this
magnification,
so
I
say.
B
B
The
source
selection
algorithm,
makes
a
proposal,
and
then
you,
when
you
make
shipments,
you
have
to
define
one
source
at
a
time,
so
the
merchant
can
select
the
source
or
actually
the
source
would
be
pre-selected
because
it's
been
selected
by
the
customer,
but
then
we
know
the
inventory
available
in
those
sources
and
so
that
the
merchant
can
go
ahead
and
click.
This
is
available
now,
but
we
can
check
it.
So
we
could,
you
know
we
can
gray
8ao
to
prevent
them
from
clicking
it.
If
there's
not
sufficient
inventory
yeah.
B
With
of
course,
that
this
is
never
fully
I
would
say,
I
was
never
fully
guaranteed,
but
it
is
what
I
meant
by.
That
is
because
we
don't
make
a
reservation
at
the
source
level.
So
when
I
click
that
notification,
the
compensation
reservation
would
happen
right
at
that
moment
so
before
the
customer
gets
there.
But
when
I
tell
them
that's,
when
we
decrement
the
inventory.
B
D
B
Page,
the
other
thing
to
think
about
is
how
we
track,
which
orders
have
or
have
not
been
picked
up,
so
we
decrement
the
actual
quantity
when
we
create
this
shipment,
slash
notification,
whatever
we
call
it
mm-hmm,
but
then
the
customer
hasn't
yet
picked
up
this
items.
So
how
do
we
keep
track
of
that
status
of
whether
they've
picked
them
up
or
not?
B
D
B
I'm,
so
so
right
now
we
actually
don't
do
anything.
For
the
scenario
I
mean
everything
you
described
is
correct.
We
make
the
shipment
decrement
the
inventory
and
that's
at
the
time
of
label
creation
which,
as
you
said,
may
be
different
or
it's
pretty
much
always
different
from
when
it
gets
picked
up
and
scanned
into
the
carrier
system.
B
But
at
that
point,
if
the
package
is
not
deliver,
the
package
is
late
or
anything
like
that.
That's
pretty
much
outside
of
Magento.
It's
going
to
fall
to
a
customer
to
contact
customer
service
and
say
hey
I,
never
got
my
order
at
which
point
the
merchant
can
take
a
variety
of
actions.
You
know
sending
another
refunding
whatever
they
want
to
do,
but
it's
not
hasn't
have
to
be
on
the
original
order.
B
B
The
only
challenge
here-
that's
a
bit
distinct
like
if
I
share
my
regular
orders
and
I
want
to
keep
track
of
you
know
were
they
delivered
where
they
signed
for,
did
they
get
lost
if
they
come,
are
they
coming
back
to
me?
I
can
do
that
through
the
carrier
or
a
a
third
party
ship
station
or
some
other
third
party
software
I
can
see
that
status
for
these.
B
A
C
Think,
in
our
case,
we
it's
up
to
them.
The
we
haven't
actually
implemented
anything
in
Magento
because
because
it's
too
much
of
a
chore
for
every
store
employee
to
actually
register
their
shipment
in
Magento,
so
they
so
they
won't
do
it
anyways
and
because,
when
you
have
to
the
300
physical
stores
and
each
have
ten
employees,
it's
undoable
to
actually
teach
it
and
know
how
to
actually
do
it.
C
So
in
our
case,
they,
the
package
gets
from
the
warehouse
to
the
store
and
and
then
it's
up
to
the
store
to
actually
track
them
and
then
they'll
get
they'll
get
punished
in
some
way.
If
there
follow
the
actual
procedure
to
actually
notify
when
order
needs
to
be
cancelled
and
then
the
central,
the
central
warehouse
watch,
we
cancel
the
order
or
credit
to
order
in
Magento
yeah.
B
And
then
maybe
it's
just
a
how
they
assign
the
responsibility,
because
there
would
be
a
packing
slip
or
shipment
information
most
likely
it
attached
to
that.
So
the
store
employee,
there's
gonna,
have
to
pick
it
and
they
they
keep
it
in
an
area
where
they're
waiting
for
the
customer
to
come,
and
then
it's
just
on
them
to
notice
that
you
know
this
box
has
been
here
for
two
weeks.
The
information
is
on
the
top
of
it
on
that
packs
lift.
So
we
should
get
in
contact.
It's
it's
yeah.
C
Yeah
I
think
we'll
be
at
the
time
we
discuss
it.
Extensively
are
actually
implemented.
Then
came
to
the
conclusion
that
it
would
be
fairly
difficult
to
actually
automate
something
in
this
regard,
and
it's
it's.
The
defaults
will
happen
if
the
cursor,
if
the
store
just
don't
know
it,
don't
knows
what
to
do,
how
to
handle
it,
and
that
is
where
the
problem
lies,
but
because
I
happen
they
have
the
physical
product
that
they
can
see
that
they
have
to
cancel
so
that's
their
status
and
namely,
in
that
sense
right.
A
Yes,
probably
we
have.
We
have
several
question
from
the
UI.
You
UNIX
perspective
whether
we
need
like
whether
we
need
to
introduce
dedicated
step
instead
of
the
source
selection
algorithm,
or
at
least
some
I,
don't
know
like
model
window,
saying
that
currently
it's
not
enough
product
on
the
selected.
How
this
step
should
look
like
how
this
notification
mechanism
should
look
like.
B
A
A
B
But,
for
example,
we
could
have
a
button
in
that
there
instead
of
ship,
says
pickup
and
we
can
have
logic
to
that.
Button
is
displayed
if
it's
a
pickup
order
instead
of
ship
and
then
when
they
click
to
that
page,
they
would
get
taken
to
a
different
screen
and
we
would
create
they
would
have
contained
relevant
information
for
a
pickup
order.
B
A
B
B
B
And
this
the
screen
would
have
something
it
would
have
a
different
layout,
but
similar
to
this,
it
would
just
verify
I,
don't
have
all
the
items
in
the
order,
and
it
would
show
that
there's
sufficient
quantity
for
each
of
those
items
and
then
I
would
click
OK
and
the
customer
is
gonna,
get
an
email
yeah.
So
all
we
should
have
a.
We
should
have
a
a
bcc
option
on
this
email
as
well.
If
it
needs
to
go
to
a
store
manager
or
something
by
source,
it.
C
So
I
have
an
opinion
about
this
and
I.
Don't
know
if
that
solves
the
issue.
So
at
the
current
moment
you
have
the
source
selection
algorithm,
which
will
return
the
quantities
for
certain
exactly
an
example
right
here.
But
but
when
you
select
a
certain
store
for
pickup,
you
are,
you
aren't
actually
selecting
a
source
but
you're,
preferring
a
source
where
the
quantities
needs
to
be
deducted
from,
and
so
in
that
sense
you
only
create
a
preference.
C
It
will
go
in
a
source
selection,
algorithm
and
the
source
selection
algorithm
will
take
the
preference
in
account
and
then
we'll
return
the
quantities.
How
it
sounds
suggestions
you
will
deduct
it
and
then,
if
it
can't
find
the
preferred
solution,
if
just
for
it
we'll
just
return
another
solution
and
would
just
say
life,
for
example
in
this,
in
this
example,
you'll
say
91
or
something,
and
then
you
see
it
in
this
interface,
and
you
actually
know
that
you
have
to
that.
You
have
a
weird
situation,
doesn't
make
sense
so.
B
C
Says
oh,
wait!
Well
and
we'll
show
it.
You
can't
actually
deduct
it
from
the
start
from
the
actual
physical
store
and
then
it'll
just
give
the
second
best
option
it
has
because
you
actually
have
to
do
something
and
I
think
it's
more
of
a
business
issue
that
you
don't
have
the
infantry
available
in
the
store
and
that
you
should
have
more
it's
very
available,
because
if
you
don't
have
it
available,
your
issue
is
in
infantry
management
and
it
isn't
actually
in
the
sales.
You
know.
B
I
think
we
should.
We
should
definitely
prevent
the
merchants
from
sending
an
email
of
customer
until
there's
sufficient
quantity.
But
what
this
page
can
surface
is
the
fact
that
they
don't
have
sufficient
quantity
and
maybe
alternative
sources
where
they
do
have
the
quantity.
Then
they
would
have
to
leave
this
page
and
go
back
and
make
that
inventory.
B
C
C
C
C
This
is
the
shipment
that's
actually
created,
and
then
it
will
be
shipped
to
the
physical
store
and
a
bit,
but
the
I
think
the
yeah.
So
the
track
and
trace
email
has
been
sent
to
the
end
customer
and
we've
created
and
custom
email.
Temp
I
did
watching
mentioned
yeah
yeah.
Your
package
is
currently
underway
to
the
physical
store
and
we
will.
We
will
notify
you
when
it's
delivered
at
the
physical
store
and
then
you
will
get
another
email.
So
in
this
case
we
used
that
for
the
for
the
pickup
and
store
functionality
right
off.
C
C
That's
actually
shipping
from
a
different
source
to
do
physical
store,
and
that
is
so
bio
that
shipment
you
can
actually
track
where
the
product
is
and
when
it
when
that
shipment
is
delivered,
and
you
can
actually
so
in
this
case
you
can
actually
make
the
shipment,
because
you
you
have,
you
have
two
right
hooks
to
actually
trade
in
and
where
else
connector,
API,
connector
or
something
because
you
actually
use
the
shipment
functionality
of
Magento.
In
this
case.
B
Right
well,
we
could
I'm
just
trying
to
think
of
the
steps
involved
here
so
with
what
we
have
an
MSI.
We
could
do
this
it.
What
I
proposed
earlier
of
for
store
pick
of
orders?
We
would
only
show
a
pic
instead
of
ship,
then
that
wouldn't
work,
so
we
would
still
have
we'd
have
to
have
the
ability
to
do
both
either
you
can
send
an
email
to
the
customer,
letting
them
know
that
the
product
is
available
for
pickup,
meaning
you
have
sufficient
quantity
in
the
source.
The
customer
selected.
B
The
other
option
is:
if
there's
not
sufficient
quantity,
the
system
or
magenta
will
prevent
the
merchant
from
sending
that
email,
but
it
would
allow
them
to
create
shipments
one
or
more
shipments,
and
those
shipments
would
be
from
another
source
to
the
source,
the
customer
selected,
and
they
essentially
can
keep
going
through
that
process.
Until
there's
sufficient
quantity
and
the
source
the
customer
wants,
and
then
they
can
send
the
pickup
email
yeah.
C
B
All
we're
doing
there
I
mean
again.
This
is
a
question
for
UX,
but
potentially,
if
we
add
a
pickup
button,
it's
gonna
do
what
I
described
before
it's
gonna
verify.
There's
sufficient
quantity
for
everything
in
the
order,
allow
them
maybe
to
add
a
comment
or
something
and
then
go
ahead
and
click
pickup
and
the
customer
will
get
an
email
that
it's
ready.
B
That
will
only
be
possible
if
there's
sufficient
quantity.
If
there's
not
sufficient
quantity,
they
couldn't
proceed
past
that
screen,
but
they
can
go
back
to
the
regular
order,
page
click
ship
and
generate
shipments.
That
would
move
things
around,
of
course,
that
quantity
would
only
truly
be
moved.
It
would
be
decremented
when
the
shipments
were
made.
It
would
only
be
received
by
somebody
receiving
the
package.
A
A
A
Currently
our
goal
to
get
is
to
compensate
the
world
like
if
you
place
an
issue.
The
reservation
to
compensate
and
the
sum
of
all
reservation
place
in
the
scope
of
one
order
should
be
zero
and
now
because,
for
example,
in
the
in
the
example,
I
provide
the
room
where
we
have
to
make
the
internal
transportation
of
three
item.
We
will
ship
these
three
items
and
after
that
we
have.
The
merchant
can
click
the
pickup
button
and
I.
B
B
Well,
actually,
no,
that's
fine,
that's
correct,
because
that's
not
accounting
for
the
fact
that
the
quantities
going
up
when
it's
received
at
the
source
it
was
sent
to.
So
if
I
need
to
move
three
from
source
B
to
source
a
I,
create
a
shipment
from
source,
B
and
three
are
deducted
or
we
have
a
compensation
reservation
for
three
it
arrives.
The
package
arrives
at
source
a
and
then
someone
has
to
you
know
increment
the
inventory
by
three.
Then
we
then
there's
sufficient
inventory
for
the
pickup
to
happen.
A
By
the
way,
how
the
credit
Mama's
supposed
to
work
in
this
case,
I,
suppose
that
we
should
not
make
that
make
the
return
to
the
source
B
in
case
we
have
the
all
the
products
on
the
source
a
because
we
no
need
this
unnecessary
and
every
delivery.
If,
for
example,
your
customer
reasons
don't
want
to
pick
the
order.
B
A
A
So
we
like,
we
apply
the
source
priority
and
we
make
the
return
to
that
to
the
source
which,
which
has
this
product
allocated
like
source
beans
or
C,
and
return
to
the
to
the
source
with
the
highest
priority.
So
so,
potentially,
if
we
place
an
order-
and
there
are
like
two
items
like
share
and
the
Sun
bottle
of
years,
so
we
prevent
the
situation
when
we
returned
beer
to
the
to
the
source
which
which
holds
just
furniture.
A
B
A
Yeah
yeah,
so
that
was
my
idea:
how
we
should
do
it
in
case
of
the
store
pickup,
but
also
like
in
this
case,
when
we
had
the
internal
internal
transition
from
the
source
B
to
source
eight
types
of
all
that
in
case,
if
the
order
would
be
refunded,
we
no
need
to
get
back
the
three
items
to
the
source
B
from
source
a.
If
we
already
have
this
all
eight
items
allocated
on
the
source,
a
we
can
leave
it.
As
this
happen.
A
A
The
do
we
need
to
like
this
pickup
button
is
going
to
be
just
a
button.
We
checks
that
we
have
enough
products
on
the
selected
source
through
the
order
and
initiate
that
the
Asian
email,
or
should
we
do
anything
else.
I
mean
button,
which
you
click
and
the
notification
that,
like
Saint
merchants,
that
we
notify
customers
that
order
couldn't
be
pickup,
it's
gonna
be
like
it
did.
He
like
it
is
paid
there
I,
don't
know
well.
B
A
B
Say
they
have?
You
know
the
customers
ordered
one
in
the
stores,
a
thousand
in
the
backroom.
Someone
still
has
to
walk
to
the
backroom
pick.
One
of
them
out
and
put
it
in,
like
you
know,
buy
the
pickup
counter.
So
there
is
a
step
there
that
needs
to
take
place
before
they
can.
They
can
let
the
customer
know.
B
B
One
actually
one
other
of
them
sure
they'll
be
more
things
as
we
work
through
the
UX,
but
for
the
we're
allowing
them
to
make
these
internal
shipments
using
our
existing
shipment
mechanism.
But
our
existing
shipment
mechanism
pulls
a
shipping
address,
it
would
take
the
customers
address
and
that's
not
what
the
merchant
wants
to
create.
The
merchant
wants
to
create
a
shipment
between
from
one
source
to
another,
not
to
the
customer.
So.
A
A
B
A
B
A
So
here
we
need
to
describe
it
more
clearly
how
we
want
to
see
this
customization
of
shipment,
because
currently
like
by
default
as
it's
gonna,
be
provided
whole
number
order.
It
items
be
to
Bishop.
So
do
we
need
provide
rest,
the
rest
which
we
don't
have
like
in
this
case
three.
If
the
worker
was
eight,
we
have
five.
So
if
the
store
pickup
should
be
should
be
provided
to,
she
required.
B
B
The
shipment
page
the
same
it
just
changed.
What
is
proposed
by
that
is
we
will.
We
will
propose
shipments
for
things
that
are
below
the
quantity
in
source.
A
in
this
scenario.
It's
when
the
one
I
just
gave
the
200
items.
We
know
we
have
enough
in
source
a
of
199
Ida
miscible
proposer
ships,
zero
of
those,
but.