►
Description
Agenda:
1. Mass Inventory migration (from Source to Source)
2. Stock and Source configuration. Discussion of Design document https://github.com/magento-engcom/msi/wiki/Stock-and-Source-Configuration-design with Anton Kril
A
Our
scope
of
our
backlog
for
my
mouth
stone,
we
still
have
several
open
question,
and
especially
there
are.
There
are
plenty
of
open
questions
regarding
the
technical
implementation
of
the
stories
currently
located
in
our
mouth,
stone,
backlog
and
and
I
propose
to
finalize
the
decision.
Regarding
the
regarding
the
feature
we
already
started
to
discuss
so
much
inventory
action.
C
A
Cool,
so
we
already
had
this
short
chat
with
mark
regarding
proposed
changes
as
base
based
on
on
the
meeting
we
had
with
contributors.
It
was
decided
to
apply
some
changes
to
the
initial
look
and
feel,
and
the
initial
you
can
feel
actually
implies.
Three
different
operations
assigned
to
source
unassigned
from
source
and
transfer
inventory
and
the
main
idea
behind
the
assigned
to
source
operation
is
to
create
empty
out
of
stock
source
items
with
zero
quantity.
A
Chair
to
drop
on
a
sign
now
to
drop
assigned
to
for
separation
because
from
from
perspective
of
Ricarda
and
FedEx
it
was
they
consider
that
the
separation
is
useless,
because
energy
merchants
still
need
to
make
some
action
for
to
provide
some
data
or
make
an
ex-player
expert
and
the
consequent
import
to
fill
the
source
items
with
data.
But,
as
I
understand
mark
mark
has
some
concerns.
A
D
C
D
C
A
A
We
are
still
keeping
it
in
data
briefs,
but
we
just
notify
the
quantity
in
the
initial
source
ID.
So,
for
example,
if
we
are
moving
the
the
stock
from
the
default
force
to
force
a
after
as
a
result
of
operation,
we
will
create
the
source
item
for
the
source,
a
for
for
the
corresponding
product
and
we'll
move
all
the
other
quantity
which
is
currently
exist
on
a
default
source
item.
But
along
with
that,
when
the
operation
is
finished,
we
will
still
have
the
source
item
for
the
default
source.
A
But
this
item
would
have
quantity
quantity,
zero.
So
we
can
consider
this,
for
example,
whether
we
need
to
keep
the
initial
source
item
or
not
not
as
a
dedicated
operation
here,
but
as
a
property
of
the
transfer
operation.
So,
for
example,
we
can
add
the
check
box
for
transfer
inventory
I,
which
says
whether
we
need
to
keep
the
initial
source
item
because
currently
it's
not
possible,
for
example,
to
move
a
partially
inventory
from
one
source
to
another.
So
we
move
inventory
fully
from
from
the
from
the
forth
to
the
destination
source.
A
C
Yeah
so
a
couple
points.
The
first
is
whether
we
unassign
from
the
first
one
I
agree.
We
should
not
unassign
because
it's
a
separate
action,
but
we
want
the
merger
to
decide
if
they
want
on
assignment
for
the
second
one
of
how
we
set
the
quantity.
Are
you
talking
about
the
transfer
inventory
option
or
being
a
scientist
ourselves?
Yep.
A
A
A
From
my
perspective,
the
creation
of
empty
source
item
is
not
and
is
not
a
scenic
business
action,
but
this
is
just
a
part
of
some
just
one
step
on
a
way
of
making
some
business
scenarios,
so
maybe
it
makes
sense
to
provide
like
a
more
high-level
kind
of
coarse-grain.
This
could
be
considered
as
kind
of
coarse-grain
api,
therefore
fine-grain
api,
whereas
there
is
like
a
low-level
api
for
doing
something
so
that
the
level
of
admitting
I
we
should
provide
something
more
high
level
and
like
prevent.
C
The
complete
separation
are
you
referring
to
the
scientist
or
sir
yep
Assunta
yeah?
So,
if
you
think
about
it,
the
way
that
we
have
always
said
yourself
is
that's
two
different
things
were
allowing
member
to
subtract
for
a
source,
so
the
first
students
whether
the
product
is
well
stocked
in
that
location.
We
could
think
that
it
is.
Is
there
a
place
on
the
shelf,
for
this
bug
go
in
the
warehouse?
C
C
For
example,
if
I
open
a
new
warehouse,
I
may
decide,
I
want
a
wide
variety
of
my
products,
some
of
them
the
selection
filters
to
be
available
in
this
warehouse,
but
I
haven't
moved
any
inventory
in
there.
Yet
so
I
can
assign
all
of
you
to
this
source
and
then,
in
a
later
step,
I
can
define
the
quantities
I
want
for
those
products.
There.
A
A
Okay,
okay
I
got
here
planned
I
got
your
point
so,
potentially
the
guys
working
on
this
particular
warehouse.
It
can
get
prepared
that
some
particular
product
types
will
be
delivered
in
the
warehouse,
so
they
can
prepare
some.
They
can
free
some
space
and
get
prepared
for
products
which
would
be
talked
a
little
bit
later.
That's
right!
Okay!
C
C
Unassign
almost
seems
like
the
opposite
of
a
sign.
If
we
don't
feel
like
that,
communicates
next
to
users,
what
will
really
happen?
We
could
change
it
to
something
like
remove
from
source
a
different
action.
It
sounds
that
more
clearly
communicates
the
fact
that
not
only
will
it
be
unassigned
but
calamity
will
be
removed,
or
we
could
have
some
sort
of
copper
confirmation
that
there
has
to
go
through,
but.
A
You
know
like
for
me
kind
of
assignment.
This
is
something
not
more
than
just
a
link.
For
example,
we
have
assignment
product
to
category,
and
this
is
just
a
Lincoln.
For
example,
if
you'll
drop
the
clink,
you
will
still
get
two
entities
product
and
category
and
you
would
not
lose
the
data
sand.
So
there
is
no
possibility
to
lose
sensitive
data
because
actually,
all
the
sensitive
sensitive
data
is
represented
by
product
and
by
category
and
we'll
just
drop
a
linkage.
B
Could
go
either
way.
We
use
a
sign
to
show
that
you're
mapping
and
then
you're
setting
your
product
inventory
amounts.
So
unassign
does
have
that
idea
to
the
merchant
that
they
are
going
to
completely
remove
it
from
that
source.
I,
don't
see
a
problem
with
having
it
as
unassigned
and
then
a
pop-up
that
would
inform
them.
What
will
happen?
Do
they
want
to
continue
this,
or
do
they
rather
want
to
transfer
inventory?
B
C
B
A
A
Yeah,
so
we
will
introduce
from
and
to
and
on
a
from
it
will
be
possible
to
choose
particular
source
from
where
we
we
are
moving
data
because
currently
on
our
product
need
and
we
are
going
to
introduce
at
this
functionality.
The
Prada
grid
is
not
possible
to
filter
by
source,
because
we
have
a
big
beta
in
in
in
a
in
s
south,
representing
on
assigned
to
particular
perfect
its
understand
to
mark
your
key
with
yes,
I
am
okay,
so
looks
like
we
agreed
from
product
perspective
or
mama,
section,
2
and
and.
A
A
A
Yes,
and
along
with
just
to
finalize,
what's
our
decision
regarding
the
transfer
inventory,
whether
it
makes
sense
from
your
perspective
to
it,
for
example,
its
checkbooks
saying
that,
after
the
transfer
inventory,
remove
all
the
source
item
from
the
from
the
source
from
where
we
making
the
from
where
we
making
the
migration?
No.
D
D
A
This
is,
this
is
exactly
what
I
was
proposed
like
a
copy
or
move
it
wasn't
from
why
actually
I
am
proposing,
and
why
I'm,
considering
that
it
could
be
common
common
business
keys,
because
currently
we
have
some
special
meaning
for
default.
Post
the
old
stock
and
it's
not
possible,
for
example,
to
add
other
sources
to
to
default
stock
accepts
it
default
one.
So
all
the
merchants
who
would
like
to
start
using
the
maltese
malti
sourcing
functionality,
they
actually
need
to
create
a
new
custom
stock
and
actually
they
need
to
migrate.
A
They
need
to
move
all
the
all
the
source
items
currently
assigned
to
default
source
to
newly
created
custom
source
and
for
me
it
looks
like
a
pretty
pretty
common
operation
like
or
like
for
merchants.
Who'd
like
start
to
use
a
messiah
functionality
is
to
create
custom
stock
custom
source
and
make
migration,
maybe
several
custom
sources
and
make
a
migration
from
the
default
source
to
the
two
custom
sources.
A
They
will
still
have
this
item
we,
which
is
hero
on
all
the
product
pages
because,
as
a
result
of
migration
operation,
we
are
not
removing
the
default
source
item
from
the
default
source,
so
they
will
still
have
the
defaults.
Also,
it
could
be
irritated.
Actually
it
would
not.
It
would
not
affect
how
the
system
works,
but
it
could
be
potentially
irritating
for
merchants
that
there
are
a
lot
of
empty
source
items
assigned
to
default
source.
C
C
C
C
A
This
this
great
question
so
in-depth
implementation
details.
We
are
going
to
use
bulk
API,
so
the
ball
TP
is
implemented
in
the
scope
of
in
Magento
Enterprise
Edition.
But
recently
the
bulk
EPS
were
ported
to
magenta.
To
do
to
imagine
tree
so
taking
into
account
that
magenta
MSI
is
going
to
be
a
feature
of
magenta
to
the
three
we
can
use.
We
can
use
a
bulk
API
and
the
IP
protocol
in
the
message
queue
so
we're
going
to
use
bulk
API
as
a
as
a
way
how,
under
the
hood,
will
process
all
this
separation.
A
A
So
on
the
row
of
the
who
module
and
all
the
interfaces
belonging
to
this
module
since
Magento
dude,
three,
and
actually
this
give
us
a
possibility
to
this
Mon
to
the
module,
because
I
reckon
venturi
and
totally
remove
it
from
the
magenta
code
base
since
magenta
2.4.
Actually,
this
is
pretty
common
practice
for
us
how
we
introduce
backwards
incompatible
changes,
so
we
initially,
we
introduced
the
deprecated
tag
for
some
particular
interface,
and
this
deprecated
tag
is
well
as
full
major
Magento
release
and
for
the
net.
A
This
is
actually
what
we
plan
to
do
for
catwalk
inventory
module.
The
actual
is
a
robot
to
do
things
or
three
things
which
prevent
us
to
do.
It
is
for
inventory
configuration
because
currency
on
a
messiah.
We
are
not
own
configuration
persistence
mechanism,
we
just
have
a
dropper,
so
we
provide
the
api
and
our
our
implementation
is
just
a
wrapper
over
the
existing
legacy
stock
item,
implementation
provided
by
catholic
inventory
module,
and
also
we
don't.
A
Currently,
we
don't
provide
support
for
bundle
and
group
products
and
if
it's
more
or
less
clear
how
to
do
support
for
bundle
and
group
products
we
just
need
create.
We
just
need
to
introduce
indexation
for
bundle
and
group
products
regarding
the
configuration.
This
seems
a
little
bit
trickier
because
because
currently
like
what
we
have
now
in
our
existing
Amazon
implementation,
all
the
all
the
configuration
of
inventory
we
consider
that
all
the
configuration
is
applied
on
the
level
of
stock.
A
A
We
can
just
calculate
whether
the
border
is
enable
or
not
so,
for
example,
heaven's
a
source,
a
source,
B
and
sourcing
and
saying
that
recorder
is
enable
for
the
source
B.
We
can
say
that
for
the
stock,
a
for
which
all
these
sources
are
assigned
to,
we
can
say
that
configuration
option
for
back
order
on
a
stock,
a
is
calculated
based
on
values.
A
We
we
have
on
a
source
on
a
source
level,
and
we
can
say
that
if
the
quarter
is
enabled
for
the
one
of
the
sources
it
can
be
enabled
for
for
the
stock
as
well,
especially
if
it's,
if
it's,
if
it's
quantity
like
if,
if
the
threshold
is
zero,
because
if
the
threshold
is
negative,
which
is
also
dedicated,
dedicated
story,
which
we
consider
like
ad
possibility
to
apply
negative
threshold
for
backorder.
This
things
also
get
a
little
bit
tricky,
because
we
also
need
to
provide
some
more
sophisticated
calculation.
Whether
the
corner
is
like
is.
A
A
Light
weight
generated
index
would
which
going
to
be
used
on
a
front-end
to
build
and
to
answer
all
the
possible
questions
raised
from
that
from
the
front
and
side,
and
here
we
like
here,
we
need
to
make
like
two
decisions,
whether
we
don't
have
overlap
in
between
the
configuration
options
we
have
on
the
level
of
source
and
on
the
other
power
stock.
It
somewhere
here.
E
E
A
But
back
to
the
conversation,
so
here
we
need
to
make
two
main
two
main
decisions
as
the
first
one,
and
the
first
decision
was
that
there
is
no.
There
is
no
configuration
options
which
can
be
specified
by
merchants
or
by
admin,
on
the
level
of
source
and
on
the
level
of
stock.
So,
currently
we
making
this
aggregation
and
saying
that,
for
example,
back
orders
is
the
option
which
is
which
can
be
specified
on
the
level
of
source
only
and
it
is
calculated
on
the
level
of
stock
and
opposite
to
eat.
A
For
example,
we
have
a
managed
stock
option,
since
this
is
optional,
we
can
specify
on
the
level
of
stock
only,
and
there
is
no
possibility
to
specify
the
same
option
on
the
level
of
source.
This
is
pretty
important
for
us
from
from
the
process
of
how
we
gonna
build
this
index
and
how
we
gonna
make
all
the
fall
backs,
because
if
we
would
have
some
configuration
options
which
can
be
specified
both
on
the
level
source
and
stock,
that
will
introduce
a
lot
of
unclarity
and
the
additional
sophistication.
So
this
is
one
pretty
important.
A
Pretty
important
decision,
which
should
be
should
be
made
probably
mark.
You
need
to
have
some
time
to
look
through
all
the
options
which
mentioned
in
this
table
and
confirm
that
there
is
no.
There
is
no
inventory
configuration
options
which
can
be
specified
on
the
level
on
the
ball
or
both
level,
source
and
stock
and
another
thing
because
the
another
thing
is
scoping,
because
currently
we
inherited
all
the
scope
system
which
we
currently
have
in
a
in
magenta.
So
we
have
the
global
scope
and
we
have-
and
we
have.
A
Side,
scope,
I,
don't
know
whether
it's
yeah,
we
have
global
scope,
we
have,
there
is
no
possibility,
it's
probably
it's
on
its
own
advanced
inventory,
page,
oh,
no,
that
is
the
Justin.
Yes,
so
we
will
are.
We
are
going
to
introduce,
along
with
global
scope,
we
are
going
to
introduce
this
stock
level
configuration
for
some
of
these
configuration
options
and
probably
we
this
additional
level
of
configuration
like
a
stock
configuration,
do
you
say,
store
level
configuration
or
stock,
so
global
stock
and.
A
A
Item
right,
yeah,
torsos
item
in
this
case,
also,
along
with
that,
as
we
say
that
the
quarter
is
the
configuration
which
can
be
applied
on
the
level
of
source.
For
example,
there
is
a
drop
shipper
and
I
would
like
to
say
that
all
the
products,
all
the
source
items
which
is
acai,
which
are
assigned
to
this
drop
shipper
supposed
to
have
the
backorder
status
by
default.
So
this
is
there
should
be
possible
to
specify
a
backorder
on
a
level
of
source.
So,
for
example,
we
we
should
have
another
another
scope
and
the.
E
E
A
We
we
would
have,
we
would
have
dedicated
Commons
for
each
particular
inventory
configuration
like
in
this
case.
We
have
a
dedicated
comment
for
backorder.
All.
There
is
a
possibility
to
specify
backorder
on
different
on
different
levels
and
because
we,
because
we
also
need
to
keep
contract
and,
for
example,
the
quarter
status,
is
integer.
A
A
Four
times
a
fitting
and
they're
also
probably
four
different
configuration
of
some
of
the
configuration
option.
We
would
not
have
additional
level
of
scope
in
at
all.
It
would
be
just
possible
to
specify
the
configuration
option
on
global
level
or
on
source
all
on
stock
level
and
the
on
source
item
and
stock
item,
because,
for
example
like
in
this
case,
you
can
see
for
the
stock
threshold,
it
can
be
possible
to
specify
configuration
option
on
the
level
of
stock
item
and
on
the
level
of
stock.
Only.
D
E
Makes
sense
for
me
so
I
understand
the
motivation
makes
sense
the
motivation
I'm
just
trying
to
understand
it
might
be
a
good.
It
might
be
a
good
thing
to
ask
on
general
because
some
people
they
don't
like
this
interface
segregation,
where
you
have
to
inject
for
every
small
operation.
You
have
to
inject.
D
A
A
A
This
option
is
specifying
the
level
of
stock
item,
but
we
can
always
make
a
fallback
to
the
four
stock
and
we
can
always
return
the
real
float
value.
But,
along
with
that,
we
can.
We
would
have
a
clean
interface,
but
just
for
the
sake
of
supporting
this,
these
checkboxes,
we
need
to
have
a
return
type
like
new
bubble
or
we
need
to
have.
We
need
to
introduce
the
dedicated
interface,
which
will
proceed
with
the
fallbacks
and
always.
E
D
A
You
know
why
I
don't
like
this
idea,
because
you
will,
you
will
bring
the
internals
actually
into
the
business
logic,
because
this
handler
will
what
it
will
do.
It
will
call,
especially
it
will
call
it
will
call
here
like
for
source
item
if
you'll
get
new,
it
should
go
like
upper
level
and
call
that
method
to
to
build
the
form
correctly.
I.
E
Will
say
if,
if
you
implement
it
in
fourth
and
form
handler,
yes,
it
might
be
breaking
encapsulation,
but
if
you
implement
it
in
a
separate
type,
the
trap
says
for
this
specific
client:
it
will
be
more
closer
it'll
interface,
segregation
to
be
older
or
this
because
for
form
you
need
this
logic
for
other
clients.
You
might
not
need.
A
That's
actually
why
I
even
thought
about
introducing
actually
API
for
UI,
so
we
already
have
admin,
UI
interface,
admin's,
sorry,
humans,
yeah,
but
in
MSI
we
have
admin,
UI
models
there
and
we
can
introduce
API
namespace
there
and
in
the
scope
of
admin,
UI
API.
We
can
introduce
this
interface,
which
will
make
hoback's.
E
C
E
A
A
A
Like
we
don't
have
a
precise
order
like
we
have
some
priorities,
but
taking
into
account
that
we
have
enough
contributors
and
we
were
able
to
spread
the
work
among
among
them
and
taking
into
account
that
two
of
these
six
stories
already
already
started
and
people
have
been
working
on
these
stories.
We
will
try
to
make
them
simultaneously.
At
the
same
time
and
we'll.
A
A
A
A
E
A
E
C
E
E
C
A
So
the
question
I
help
to
you,
I
already
created
in
this
document.
There
is
this
table
where
it
specified
whether
the
configuration
option
is
applicable
on
a
level
of
stock
on
the
level
of
source
and
also
I
had
an
assumption
that
merchants
will
have
an
ability
to
specify
just
on
one
particular
level,
whether
it's
but
not
both
and
another
thing.
We
need
to
decide
well
what
kind
of
scopes.
A
Okay
item
level,
whether
we
need
to
reduce
an
ability
to
buy
it
on
a
stock
level
so
like
like
in
the
in
the
proposal
here
like
the
quarter,
is
possible
to
specify
on
the
level
of
source
item
yeah.
It's
on
another
level
of
source
items,
source
and
global,
and
for
example,
like
say
if
it
is
stock
threshold,
it's
possible
to
special
and
above
stock
item
and
stocks.
A
A
A
A
C
A
C
E
Suggest
there
was
one
one
more
comment
about
general
and
linking
and
linking
of
inventory
from
Magento
current
scope
model
of
scoping
model.
It
would
be
good
to
have
completely
independent
scoping
models
that
can
be
mapped
on
Magento.
So,
if
you
deploy
as
you
there's
no
plan
in
future
is
to
deploy
inventory
as
a
separate
service,
and
ideally
it
should
be.
It
should
be
independent
of
scope
configuration.
So
where,
were
you
were
you
with
issues?
C
A
Have
a
quick
question:
if
you
have
a
time
because
I
thought
about
this,
but
I
have
a
technical
issue,
because
there
is
no
problem
for
us,
for
example,
to
resolve
to
do
what
what
you
just
propose
to
do
like
a
resolve:
MSI
scope
based
on
Magento
scope.
But
actually
that
can
you
can
introduce
some
side
effect.
For
example,
based
on
magenta
website.
A
We
can
resolve
a
stock
and
provide
the
provide
a
way
to
apply
data
on
on
that
stock,
but
actually
taking
into
the
taking
into
account
that
a
stock
could
be
potentially
assigned
to
several
websites.
We
can,
as
a
side
effect,
affect
the
data
configuration
data
belonging
to
another
website.
If
you
will
do
this
resolving
from
website
to
the
stock.
E
A
All
the
discussion
on
the
site-
racket,
public
with
great
okay.
So
probably
we
will
finalize
the
backlog
and
regarding
this
the
configuration
configuration
story,
I
have
a
question
to
you:
mark,
look
look
through
this
table
and
provide
provide
the
different
options
for
scope
for
all
of
this
configuration
option,
whether
it's
gonna
be
and
also
like,
applied
to
source
and
stock.
A
Could
you
please
check
whether
it's
correct
from
your
purse
from
your
point
of
view
or,
if
not
just
just
updated,
I
built
it
on
my
assumption,
whether
it's
supposed
to
be
belong
to
stock,
a
source
and
after
we
finalized
I?
Believe
internal
radio
looks
release
interfaces
and
he
likes
this
option,
so
you
can
do
it.