►
From YouTube: MSI Open Demo. July 7, 2017
Description
Magento 2 Multi Source (Stock) Inventory open demo
A
There
are
three
main
tracks:
source
management,
shipping
sources,
algorithm
selection
and
the
refactoring
and
integration
of
the
new
inventory
solution
with
the
current
catalog
checkout
and
sales
processes
which
happen
in
magenta
are
going
to
be
implemented,
and
we
already
have
several
stories
which
are
implemented
and
the
over
boo
request,
which
we
handled
and
merged
into
all
develop
branches.
So
everybody
could
could
come
to
this
page
and
see
the
current
progress,
so
that
will
have
to
help
with
new
contributors
to
see
the
current
state
of
the
project.
A
Also,
that
will
help
to
understand
that
was
going
to
be
implemented
at
the
final
state
of
the
product
and
actually
a
lot,
but
not
the
news
that
will
help
our
management
to
get
understand
where
we
are
and
whether
the
projects
going
to
to
the
whether
it's
in
a
good
shape
or
in
a
bad
one.
So,
for
now
we
have
pretty
pretty
good
velocity
and
performance,
and
the
urine
is
a
current
week.
A
B
B
B
B
B
B
B
B
B
B
B
B
B
B
A
Okay
sink
the
Thoreau
wall
stood
regarding
this
presentation,
so
we'll
ever
had
a
ground
process
which
isn't
part
in
the
background.
That's
why
it
was
the
row
like
the
magenta
was
working
not
so
fast
lecture
that
it
was
a
development
mission
with
the
background
process.
That
was
actually
the
main
reason
the
performance
issue
also
another.
Another
thing
is
that
you
can
see
here.
A
You
can
see
here
we
have
two
independent
stories,
so
the
prorack
assignment
per
each
source
in
admin
UI
was
demonstrated
by
valerie.
So
it's
actually
where
you
can
go
to
the
product
page
and
assign
different
sources
to
the
specified
product,
but
also
we
have
another
story
which
is
supposed
to
assign
products
on
the
specify
source
page,
so
that
would
be
independent
UI.
So
it's
pretty
similar
to
what
we
have
with
the
with
the
category
on
the
prod.
A
So
phenomena
could
be
assigned
to
a
category
both
from
the
product
page
as
well
as
from
the
category
page
and
on
the
category
page.
For
example,
you
will
open
the
grid
with
the
products,
so
this
would
be
pretty
similar
to
assigning
products
to
the
sources,
because
so
now,
actually
during
the
implementation
of
the
story,
we
start
with
respect
with
the
several
issues
with
our
UI
components,
because
the
component
which
you
just
saw
on
the
demo,
doesn't
support.
Actually,
then.
A
The
course
all
would
say
so
Lord
impartially
the
data
of
the
collection.
So
for
now
it's
loads
the
cool
data
and
we
can
use
it
for
the
product
page
because
it's
probably
there
would
not
be
too
many
sources
like
more
than
several
hundreds.
But
if
we,
if
you
will
consider
the
vice
versa,
so
the
assigning
products
on
the
source,
it
would
be
possible
to
have
quite
water
products.
We
just
store
it
in
some
particular
source.
A
So
it's
not
recommended
to
use
CCI
components
of
in
purposes
because,
for
example,
heaven
like
many
like
many
thousands
of
products
storing
on
some
particular
source,
we
will
probably
overload
our
our
performance
and
get
the
performance
degradation,
because
currently
a
component
will
just
load
all
of
that
all
of
the
sources
and
we'll
just
make
it
pagination
locally
on
the
level
of
the
jealous
creep,
but
actually
that
would
not
affect
your
Ajax
request
and
load
in
beta.
So
actually
all
the
data
would
below
the
default.
That's
why?
A
A
A
C
Currently
only
some
problem
interface
and
some
API
implementation,
but
but
not
yet
specific
implementation
or
some
test
only
a
trough
for
the
api
path,
and
here
I'm
working
on
it.
But
yeah
I
do
first,
the
one
of
the
poorest
from
UK
I
finish
this
and
then
I,
give
due
to
real
I
think
it
was
two
requests
as.
C
C
For
the
basic
implementation,
with
some
basic
tasks,
it
will
be
enough
I
think,
but
if
we
need
more
functionality
or
some
advanced
functionality,
it's
I
think
I
make
only
a
dislocating
implementation
and
decide
this
human
body
is
finished.
Then
we
can
some
some
top
define
what
for
more
advanced
medications,
yeah.
A
A
A
A
And
three
days
ago,
so
I
believe
a
letter
will
updates
this
pool
crest
but
the
demo
and
yes,
you
can
look
through
the
code
changes
and
see
see
all
the
specific
books
working
with
with
a
UI
component.
So
it's
pretty
interesting
because
we
actually
start
with
several
issues
and
seek
them
and
some
some
implementation
work
reconsidered
during
the
during
the
work.
So
it
could
be
interesting.
Actually
that
would
be
useful
to
deliver
this
cottage.
C
A
A
A
C
A
So
let
me
read
the
equations
and
equation.
It
is
how
we
are
going
to
integrate
our
MSI
solution
with
the
one
biggest
which
already
exists
on
the
market
and
which,
like
which
is
a
part
of
Magento,
go
so
now.
We
are,
we
here
actually
weekly
meetings
with
the
uncommon
presentative
and
we
discuss
how
that
so,
it's
going
to
be
integrated
with
a
comb.
A
Would
be
solution
which
could
fit
for
basic
needs
for
basic
merchants,
but
if
notions
has
some
particular
requirements
regarding,
for
example,
performance
requirements
or
or
if
the
amount
of
stops
is
really
huge,
like
maybe
hundreds
or
thousands
stops,
and
we
need
to
proceed
with
some
operation
very
quickly
or
with
additional
with
very
high
accuracy.
So,
for
example,
one
of
the
part
of
the
project
which
is
called
shipping
and
source
selection
algorithm.
A
So
we
need
to
choose
what
what
the
sources
should
be
used
to
fulfill
the
order
and
when
we,
for
example,
several
hundreds
of
the
source
so
amount
of
the
possibilities
of
the
order.
Fulfillment
is
really
huge.
So
probably
what
we'll
provide
in
the
scope
was
a
MSI
solution
would
be
just
basic
sanitation,
so
probably
for
the
merchant
visit.
This
really
high
demands
on
the
high
requirement
for
the
performance
or
the
accuracy,
for
example,
like
the
minimal
shipping
cost
probably
and
come
out.
A
The
reason
would
be
better
than
out
of
the
box
MSI,
and
so
the
M
poem
will
override
and
provide
all
implementation.
So
actually
what
MSI
is
going
to
make?
Actually
MSI
is
going
to
introduce
new
API?
Yes,
tension
points
and
provide
the
basic
implementation,
and
we
consider
the
uncom
is
a
more
sophisticated
solution
which
will
feed
for
the
enterprise
merchant
requirements.
A
So
actually
this
would
be
implementation
for
the
same
extension
points
we
already
established
in
the
scope
of
the
MSI
but
more
sophisticated,
it's
an
impatient
so
yeah.
So
what
here?
We
are
making
the
more
generic
architecture
with
more
generic
and
the
custom
extension
points,
but
uncom
will
provide
more
sophisticated
for
most
of
the
decade,
implementation
for
the
source
selection
algorithm
for
the
made
before
indication
process.
A
So
yes,
that's
actually
the
difference
between
the
community
reason
and
the
Enterprise
Edition,
and
actually
that's
that's
how
we
make
it
usually
because,
like
if
some
feature
is
introduced
by
Enterprise
Edition-
and
we
already
have
they
pretty
similar
feature
in
the
community
difference,
we
will
just
enhance
it
in
a
Enterprise
one,
so
make
it
more
scalable
make
it
more
make
it
performance
better
in
Enterprise,
Edition,
so
function
right.
There
may
be
more
configurable.
A
Okay,
so
is
there
now
any
other
question?
Probably
we
will
be
finishing
this
mission
and,
of
course
you
can
use
for
any
queries,
our
open,
this
open,
fracture
or
Pinkney
oval
era,
or
anybody
from
the
community
engineering
team
and
we'll
leave
the
capital
system
and
for
now
thank
you
for
participation
and
see
you
next
week
on
the
next
weekly
weekly
status
meeting,
bye,
guys,
bye.