►
From YouTube: MSI Open Demo. July 21, 2017
Description
Magento 2 Multi Source (Stock) Inventory open demo
Sources to Stock assignment API (DONE) (S) #PR39
Admin UI for Sources to Stock assignment (DONE) (S) #PR39
Reservation mechanism description and Demo of design how the Order Placement will work with new Inventory mechanism
Event Sourcing description for Order placement
https://github.com/magento-engcom/magento2/wiki/Reservations
A
A
So
for
now,
whichever,
as
you
probably
already
know,
we
have
msi
roadmap
and
it's
pretty
easy
to
to
drag
our
current
state
and
the
updates
we
have
week
by
week.
So
during
this
week
we
we
go
working
on
a
true
stories,
mostly
sources
to
stop
assignment
eight
guys
and
admin,
UI
four
sources
to
stock
assignment.
A
Actually,
along
that
work,
we
decided
to
reconsider
Andrey,
implement
and
a
little
bit
refactor
our
existing
API
for
for
stock
item
and
change
the
change,
the
way
how
we
work
with
the
stock
item
ID.
So
we
decided
that
because
the
stock
item
entity
is
just
a
limp,
we
no
need
to
show
its
ID
at
all
and
because
each
state
and
the
state
of
this
entity
is
represented
by
source
ID
and
the
SQ.
So
we
actually
eliminated
the
awareness
about
stock
item
ID
in
the
system.
A
So
you
can
look
through
the
code
base
and
I
will
update
the
documentation
of
the
api's,
the
current
state
of
the
guys,
because
after
some
conversation,
visual
error
here
we
decided
that
we
introduced
some
are
eight
days
and
some
approaches
which
don't
have
examples
in
our
current
magenta
to
codebase,
and
it
would
be
useful
to
describe
a
why
why
particularly
some
of
these
changes
have
been
made
and
why
these
differ
from
what
the
seven
magenta
to
code
base.
So
we
tried
also
to
make
all
our
changes
to
be
documented
in
the
code.
A
So
we
added
quite
a
lot
of
documentation
and
description
in
the
peach
p-dog
blocks
in
the
PHP
comments
to
all
the
interfaces
we
have
in
the
inventory
API
module.
So
it
would
be
useful
for
you,
when
you're
looking
through
the
interfaces
in
inventory,
API
module
to
get
awareness.
Why
some
particular
decision
of
for
interface
has
been
made.
A
C
D
B
A
You
you
mean,
so
we
don't
have
this
task
in
our
issues,
but
it
was
this
interface
for
this
assignment.
Links
of
sources
to
stocks
was
implemented
in
the
scope
of
this
pull
request.
So
you
was
working
on
this
pull
request
and
Valera
continues
that
work
and
it's
implemented
in
the
scope
of
this
pull
request,
which
is
now
being
presented
by
Valera.
So
this
task
is
onboard
of
the
code
base
which
is
used
for
this
demo.
A
E
On
multi-celled,
it
was
request,
request
from
our
deal
and
also
he
fixed
back
with
shipping
method.
Seventh
on
source,
page
next
say:
evil
we
completed
mobile,
a
fuckton
of
OPI
interfaces.
Now
they
become
again
up
became
more
friendly,
more
DDD
friendly,
but
now
this
could
not
push
that
I
want
to
push
today,
even
in
any
minion.
And
finally,
we
finish
it.
D
D
D
E
A
A
A
A
Yes,
I
added
a
description
of
step
by
step.
She
calls
on
the
reservation
page
so
here
I
describe
the
exit,
the
reservation
entity,
but
more
order
is
needed
yourself.
But
what
is
more
important
here.
I
describe
the
example
of
solve
the
package
out
particular
checkout
happens
when
we
have
several
physical
sources
like
heroes,
source
a
source
be
so
see
an
amount
of
particular
sq
in
our
case
is
q1
by
2025
stem,
so
I
described
the
idea
of
this
top
item.
So
the
stock
item
is
a
visual
aggregation
and
the
stock
item.
A
We
should
be
created
in
the
time
of
the
indexation
process,
so
we
we
need
to
introduce
a
new
type
of
index
which
will
create
the
stock
item
table.
So
it
would
be
new
stock
item
table,
not
the
one
which
is
already
used
for
the
Cadillac
inventory
module,
and
we
need
to
calculate
this
aggregation
like
20,
plus
25,
plus
10,
and
get
55
and,
for
example,
how
we
will
use
this
data.
A
So
for
now
we
don't
have
the
reservation,
that's
why
we
make
it
adoption
like
50
5-0,
and
this
is
more
than
sorted
service.
They
requested
number
by
this
customer.
That's
why
we
will
make
decision
that
we
can
proceed
to
checkout
and
place
the
order.
So
in
our
case,
during
the
or
replacement
time,
this
system
is
agnostic
to
the
fact
from
which
physical
sources
it
want
a
quantity
of
the
sq1
would
be
deducted
afterwards.
So
that's
why
we
don't
use
source
item
interface
during
the
during
the
process
of
order
placement.
A
A
The
index
entity
like,
for
example,
the
same
as
for
the
flat
table,
so
we
can
just
read
data
from
the
set
table,
but
not
writer,
so
the
data
in
a
flat
table
is
a
point
of
changing
user
indexation
process
only
so
this
time
we
just
create
a
reservation
object,
and
it's
very
important
here
to
dimensions
that
the
reservation,
so
it's
just
append
on
the
operation.
So
we
don't
make
any
checks.
We
don't
make
any
balking
operation.
We
don't
make
any
race
conditions
here.
This
way.
A
Actually
one
of
the
points
we
want
to
fix
possible
rate
conditions
which
could
happen
now
Durin's
imagine
to
touch
account
because
for
now
we
are
making
a
transactional
way
of
checking
whether
we
have
enough
quantity
on
particular
stock
item.
But
in
our
case
we
will
just
make
using
the
reservation
management
service.
We'll
just
add
reservation
in
a
particular
quantity.
That's
all
so
we
would
not
get
any
possible
lock
plate
a
mouth
or
deadlock
a
function,
because
we
don't
make
any
additional
checks
to
just
make
a
reservation.
A
That's
all,
and
after
the
first
after
the
first
order,
the
system
has
next-next
stayed.
So
we
have
source
item,
a
source
item,
B
source
eyes
and
see
the
same
quantity
as
before,
like
20
25
and
10,
and
a
quantity
of
the
sq1
on
the
stock
item.
A
is
Q
55,
so
it's
not
changed
yet.
So
we
did
not
process
order
yet
so,
for
example,
the
order
would
be
processed
potentially
through
the
queue
so
and
it's
possible
that
there
would
be
some
light
and
see
after
the
order
has
been
placed
before
the
order
would
be
processed.
A
A
And
now
we
need
to
make
decision
again
whether
we
can
sell
that
quantity
to
this
particular
customer
and
this
actually
we
proceed
with
the
same
steps
as
before,
so
we
need
to
make
to
get
the
quantity
of
the
sq1
on
a
stock
item,
a
which
is
65
and
the
make
deduction
of
a
number
of
existing
reservation
for
the
product
sq1
and
in
our
case
it's
already
sorted.
So
we
just
make
a
65
surkhi
equals
225,
skew
more
than
ten
doesn't
make
a
decision
that
we
can
proceed
to
checkout.
A
A
So,
as
you
can
see
here,
we
don't
use
a
source
item
at
all,
and
the
source
item
would
be
used
during
the
order
processing
time
when
we
need
to
make
a
deduction
on
some
particular
sources
and
for
this
decision
we
need
to
launch
the
algorithm,
which
will
actually
the
duck
which
will
actually
decide
from
which
particular
sources
you
need
to
make
the
deduction.
So
this
would
be
that
will
happen
during
the
time
of
the
order
processing.
A
But
for
now
we
are
describe
them
and
we
are
preparing
all
the
interfaces
which
we
need
for
the
order
placed
in
time.
So
it
should
be
order.
Placement
should
be
as
fast
as
possible.
It
should
be
without
any
possible
organ
operation
as
possible
and
potentially
it
could
be
processed
synchronously
with
all
the
technical
requirements
because
for
the
order
placement.
A
B
C
A
Which
are
managed
here,
like
Valera
mentioned,
like
stock
item
index,
turns
to
fight
the
manager,
something
like
that.
So
we
would
not
have.
We
would
not
have
a
repository
for
stock
item
as
we
have
a
source
item.
So
there
is
no
repository
for
stock
item
because
an
index
entity
and
it's
not
a
reasonable
to
provide
an
API
for
the
the
spoke
item
management.
A
D
A
Topic-
and
the
reservation
also
is
the
next
topic.
We
have
to
implement
all
right.
Okay,
so
I
think
we
need
the
the
index
entity
before
we
have
the
reservation
all
across
the
dependencies
there.
So
I
think
last
is
also
already
assigned
for
for
this
topical.
And
yes,
yes,
so
this
is.
This
is
the
task.
This
is
the
issue
number
48
and
society
all
right,
so
perfect,
I
think,
oh,
if
I
already
write,
you
wrote
you
before
and
I
will
have
on.
A
Sunday
I
think
something
about
six
hours
where
I
can
work
on
this
project,
so
I
think
we
already
make
a
date
with
Lars,
where
we
work
together
on
this
topic,
so
I
think
I
will
join
just
yes
this
this
issue
pretty
interesting.
It's
pretty
big
one,
so
you
can
take
it
and
both
work
on
it.
Yeah
all
right,
if
they're
also
a
concept
term
written
on
below
on
the
wiki
for
for
the
index,
aggregation
and.
A
A
E
A
A
Mci
so
provide
the
gauge
branch.
Okay,
so
red
decided
this
way.
We
will
will
decide
to
visible
error
and
will
provide
you
a
stable
branch
out
to
the
sweet
meeting,
because
we
have
the
latest
interfaces
in
a
Valera
branch.
But
the
branch
for
now
at
the
current
stage
has
a
some
red
test
and
we
will
decide
how
to
fix
that
to
provide
you
branch
whose
latest
interfaces
which
would
be
stable.
Okay,.
A
So
far
not
I
am
like
to
see
the
coat
and
I'm
pretty
I'm.
I
I
think
I
will
be
surprised
what
I
will
see
after
the
new
pool
on
the
code
base.
I
believe
I
believe
yet
because
you
made
quite
a
lot
of
changes,
but
this
would
be
good
surprised,
I,
I,
hope
so
and
make
sure
we
really
excited
to
see
you
back
on
board,
and
so
it's
really
nice.
A
No
thanks,
I
also
happy
to
be
back
the
project
company.
We
don't
have
enough
time
for
this,
but
I'm
looking
forward
and
pretty
sure
I
will
be
surprised
in
a
positive
way.
Yeah
and
also
please
pay
attention,
for
example,
for
the
multiple
operations
save,
because
we
don't
have
such
examples
in
the
magenta
code,
and
this
is
pretty
performance.
A
Efficient,
API
actually
Lars
tweeted
about
that
some
time
ago-
and
this
is
pretty
interesting
because
actually
like
we
had
a
meet
up
yesterday
in
magenta
office,
and
we
had
a
conversation
about
the
flow
like
not
not
enough
performance
of
our
API
so
that
multiple
multiple
save
an
API
will
help
to
to
fix
that
problem.
So
we
already
start
using
this
operations.
This
corpus,
MSI
so
I,
believe
this
would
be
useful
for
designing
your
own
API
making
teacher.
So
this
kind
of
a
good
example
great.
So
it's
a
already
the
newer
or
M.