►
From YouTube: Magento MSI Open Demo. December 16, 2017
Description
Magento MSI presentation during #MageConf hackathon
- Synchronization with Lecagy CatalogInventory Shown
- Integration MSI with checkout
- Introducing limitation for Default Stock, from now it can have the only Default Source Assigned
- How Product Editing form UI should be changed to MSI more natural and to prevent introducing inconsistencies between Single and Multi-stock systems
A
Now
we're
now
we
just
finished
the
contribution
day
in
the
magenta
Keefe
office
before
the
main
scone,
and
you
know
you
can
sled.
There
are
a
lot
of
people
in
this
in
this
room
who
attended
that
that
meeting
and
would
like
to
see
how
it's
actually
happening
and
sorry
we
have
some
mess
and
I
did
not
prepare
agenda
in
advance.
So
who
would
like
to
make
a
contribution?
Just
can
raise
your
hand
or
just
start
saying
something.
So
we
can.
A
A
B
A
So
we
were
me
and
Lars.
We
worked
on
the
integration
to
the
catalog
search
and
we
stuck
in
some
problems
there,
because
we
figure
out
that
we
need
additional
information
and
allowing
irrigated
stock
tables
and
therefore
we
new
ticket
here
we
already
the
crude
task-
is
still
in
progress,
and
this
mutate
is
especially
interesting
for
other
developers.
I
think
it
doesn't
harm
the
customer
or
merchant
experience,
but
it's
interesting
to
know
that
our
information,
whether
a
product
is
in
or
out
of
stock,
is
currently
based
on
this
query.
So
we
asked
whether
aggregated.
A
A
Thank
you,
Adam
just
I,
just
want
to
say
several
words
regarding
regarding
the
update
button,
provided
that
will
actually
help
us
to
support
both
the
catalog
search,
implementation
and
the
category
implementation,
because,
as
you
probably
know,
the
category
view
is
a
is
a
just
particular
case
of
the
catalog
search.
So
we
found
the
drawback
currently
that
we
don't
provide
the
search
and
category
view
functionality
for
the
multi
stock
and
the
Vadim
start
fixing
that
adopting
our
search
functionality
for
the
multi-step.
A
A
B
B
Synchronization
between
okay
and
we
had
is
regarding
the
if
she
wants
to
default
sort
bride
an
earlier.
We
try
to
delete
legacy
stock
item
between
also
that
to
to
falsify
stock
ID,
but
it
looks
like
it
didn't
worked
as
it
should
because
it
produced
some
expected
behavior
at
the
rest
of
the
Magento.
So,
instead
of
that,
we
were
going
to
point
yeah.
Instead
of
deleting
legacy
right,
we
are
going
to
update
their
stock
status
to
to
zero
to
not
available.
So
all
that
we
have
done
is
in
this
plugin.
B
B
It
should
update
probate
so
excitin
to
five
as
well,
but
if
you
try
to
update
quantity
here,
it
will
not
reflect
to
the
legacy
cattle
inventory,
because
now
it's
part
of
the
other
ticket,
which
was
a
which
was
about
disabling
possibility
to
to
change
quantity
on
in
default
source
item
I'm.
Not
sure
who
did
it
that.
A
A
Currently
we
have
that
so
the
initial
year
we
did
not
want
to
overcomplicate
the
UI
interface
for
merchants
could
has
single
stock
inventory,
so
the
UI
should
be
the
same
for
them.
So
we
still
have
the
quantity
field
and
is
in
stock
fields
in
the
prologue
editing
page
in
the
admin
panel,
but
for
example,
and
actually
currently
it
introduced
some
issues.
So
what
what
the
proposal
we
have
for
you
to
consider
is
it?
A
Actually?
We
have
two
proposals,
the
first
one,
first
of
all
that
for
the
food
source
and
for
the
default
store
concept,
we
will
introduce
another
limitation,
so
we
would
not
be
able
to
assign
additional
sources
to
default.
Stop
so
actually
the
food
source
and
default
talk
would
be
would
be
the
sink
which
will
create
for
single
stock
users
and
actually
that
would
be
substitution
of
the
cattle
inventory
functionality
they
had
before.
A
A
A
So
if
there
is
any
other
stock
accept
the
default
store
created,
we
would
just
just
just
remove
the
quantity
and
there
is
in
stock
field
in
the
product
product,
editing
page,
and
there
would
be
this
Creed
underneath
of
the
page,
whereas
it
is
a
possibility
to
set
up
the
fool
and
the
defaults
or
the
full
source
and
any
other
sources
so
because
we
actually
no
need
like
leave.
The
inventory
currently
manipulation
on
the
page
and
in
two
different
energy
different
places.
E
Yeah
I
agree,
so
that's
something
I
should
review
with
Eugene
or
one
of
the
other
designers.
We
either
can
override
it
as
you
described.
So
if
we
have
multiple
stock
than
the
original
field
doesn't
appear,
and
they
only
have
the
grid
or
the
new
section
or
we
can
make
it
so
that,
for
example,
we
gray
out
editing
of
the
default
stock
in
the
new
section.
There's
a
couple
approaches:
I
want
to
check
with
the
designer
for
their
opinion.
Yes,.
A
Yeah,
so
the
disabling,
the
first
field
in
grids
of
the
first
row,
which
is
responsible
for
the
default
source,
is
also
an
option,
but
it
would
be
a
little
bit.
The
user
could
be
little
bit
frustrating
because
to
update
the
data
for
the
default
source.
You
need
to
update
data
in
the
floor
like
editing
forms,
but
if
you
would
like
to
change
the
data
for
the
default
for
the
first
different
source
item,
you
need
to
go
to
another
place
on
the
page.
Yeah.
E
I
understand
it's
not
my
favorite
idea,
because
it
doesn't
meet
very
well
the
use
case
of
stock
transfers.
So
if
I
want
to
move
five
units
from
default
to
source,
a
I
can't
do
that
in
one
section,
I
have
to
do,
you
know,
add
five
to
a
in
the
source
area
and
then
I
have
to
go
up
and
subtract
five
from
the
original
box
and.
F
A
So
we
can,
of
course
we
can
fix
it,
but
it's
still
like
this
behavior
looks
abnormal
from
the
current
from
the
current
from
from
the
point
of
view
how
the
system
works
now,
yes,
actually,
why
we
just
proposing
to
remove
this
possibility
if
you
have
system
to
specify
the
data
for
the
quantities
in
stock
in
the
product?
Ok,.
A
G
We
have
to
apply
this
limitation
because
we
have
a
mechanism
that
keeps
synchronize
quantities
of
legacy
kind
of
inventory,
with
quantities
of
MSI
when
the
merchant
is
only
one
default
standard,
but
what
we
had
to
do
I
was
to
prevent,
prevent
the
ability
to
define
multiple
sources
for
the
default
stock,
because
when
the
merchant
defines
or
entity
in
this
field
and
the
field
the
quantity
field
of
the
product
development
agent,
because
you
know
where
to
sign
this
quantity.
So
what
we
have
done,
thanks
to
the
contribution
of
retardant,
is
today.
G
Yes,
I
mean
this
limitation
API
level,
so
that
I
can
show
you
that
is
reflected
also
in
the
in
panel,
even
if
Moonves
from
Ricardo
will
disable
this
this
this
button
for
the
default
stock.
But
now
for
me,
it's
useful
to
show
you
that
his
limitation
is
apart
if
I
try
to
assign
our
stock
so
another
source
to
the
third
stock
I
generate
here
when
I
start
to
save.
G
G
G
G
It's
green
and
what
actually
she's
hotter
here
and
sign
sources
to
stop
dust?
Are
these
two
cases?
The
church
that
you
can
you
don't
assign
multiple
values
are
very
different
from
the
default
source,
which
is
one
at
the
moment
we
don't
have.
We
have
this
one
ID
and
hard
coded
into
subscribe.
Our
needs
will
change
in
position
in
our
implementation.
We
don't
use
the
hard-coded
one,
but
we
reuse
the
different
stuff
rather
than
the
defense's
provider,
but
the
implementation
of
this
interface
actually
has
one
of
coded
in
the
future,
and
that's
all
from
my
side.
A
D
D
There
is
a
mechanism
that
synchronized
the
old
couple
commentary
and
the
ending
you
could
work
on
venturi
and
there
are
a
few
places
where
you
need
to
get
a
product
school
by
product
idea
and
it
was
project
repository
used
for
it
and
it
is
very
heavy
per
ation.
So
we
had
a
task
to
implement
service
that
will
calculate
this
relation.
So
we've
done
it
yesterday
at
almost
the
Constitution
Day
and
the
other
task
related.
D
C
A
A
E
A
A
little
bit
more
complicated
because
usually
actually
we
close
this
story
when
the
pull
requests
get
to
the
develop
branch
and
but
not
when
it's
just
opened
because
we
still
have
like
we
have
19
pull
requests
and
no
none
of
them
like
going
to
be
merge
because
they
have
some
issues
because
in
some
of
them
the
test
should
be
fixed
in
some
of
them.
We
some
of
them
still
not
been
reviewed
properly.
So
actually
we
closed
the
story
when
the
fool
requested
north
to
the
develop
branch
but
you're
it
make
sense.
A
So
we
performed
this
story
regarding
the
import/export
of
the
product
aware
of
the
product
import,
because
we
already
made
the
minimal
minimal
stuff
for
that.
So
the
product
import
currently
update
the
store's
item
for
the
default
source,
but
not
the
stock
item
and
this
a
key
for
now
also
guy
started
to
work
on
adaptation
of
the
reporting,
so
I
believe
that
story
we're
gonna
be
closed
soon.
Also,
we
guys
here
on
the
edge
comfort
contribution.
They
also
fix
it.
A
The
functionality
of
the
product
alert
so
I
believe
that's
gonna
be
closed
soon,
so
also
regarding,
we
have
is
a
bunch
of
story
regarding
the
integration
of
the
legacy
catalog
inventory
and
the
MSI.
So
the
storage
Scout
adaptation
supposed
to
be
closed
soon
and
we
need
we
will
cross
these
three
story
points
out
of
the
backlog,
so
this
substitute
of
deduction
current
checkout
flow
with
reservation
place
placement
gonna
be
close,
so
we
look
at
the
pull
request
for
it
as
well.
A
We
started
to
work
on
admin
part
and
we
already
added
tab
where
we
supposed
to
describe
all
the
sources
from
which
we
will
make
a
stock
deduction
and
also
started
to
work
on
the
dead
Demi
algorithm.
So
we
started
to
work
on
these
stories
in
progress
and
actually
like
the
dummy
algorithms
also
be
started
being
on
the
development.
A
A
Actually,
like
all
of
this
3-story
is
supposed
to
be
closed
because
we
have
the
pool
request
for
all
of
them
and
actually
the
last
pool
request
been
presented
by
CC
new
shine
bar
tech
today,
so
that
was
probably
the
last
pool
request.
We
needed
to
fill
the
gap
on
legacy
and
the
new
MSI
integration
and
making
sure
that
we
have
the
data
consistent
in
both
of
the
storages.
So
all
of
this
bunch
of
this
restore
is
going
to
be
closed.
A
A
We
have
quite
a
lot
of
quite
a
lot
of
pull
requests
created,
so
we
need
a
little
more
time
for
me
and
Valera
to
process
them,
because
currently
we
have
like
19
pull
requests
opened
and
Atlee
and
we
need
at
least
like
a
few
like
several
days
to
process.
Some
of
them
make
it
delivery
to
the
to
the
to
the
develop
branch,
and
after
that
we
will
align
our
our
page
with
with
with
a
roadmap
so
because
we
definitely
have
a
great
update
and
because,
like
what
of
pull
request,
create
a
lot
of
work
done.