►
From YouTube: Magento MSI Open Demo. December 7, 2018
Description
Agenda:
Today's agenda:
1. @Alex Lunkov will tell us about MSI feature analysis he did
2. @Ratnesh will share with us his experience of utilizing MSI in POS (point of sale application) based on Magento 2.3
https://webkul.com/blog/introduction-to-magento2-multi-source-inventory/
3. @TheRick will describe technical details about Magento 2.3 commerce with MSI releasing https://www.gamelife.it/
4. @Slava Moskalyuk will show the progress regarding Distance Based algorithm and Google API integration
5. @Tom Erskine will present Automated Test update for a current week
A
Today,
I
asked
a
manager
from
our
partner
and
one
of
the
biggest
country
we
contributing
partner,
probably
is
going
to
be
the
biggest
in
2018
I'm.
Talking
about
a
Twix,
and
today,
I
asked
Alex
to
encode
from
from
Patrick's
company
join
us,
and
he
will
tell
us
a
little
bit
more
while
he's
inside
and
he
is
about
published
article
about
about
the
msi
project
inventory
in
general
and
what
the
what
the
feature
set
alex
personally
and
the
ethics
agency,
considered
to
be
to
be
useful
for
msi.
B
B
So
as
you
as
you
girl,
already
mentioned,
ethics
developers
has
have
greatly
contributed
to
do
the
inside
now
as
available
as
a
core
bundle
extension
for
2.3
and
we
as
a
synthesized
starting
discovering
opportunities
for
our
clients
to
integrate
with
MSI
yeah
I
thought
that
that
would
be
great
to
prepare
like
a
short
overview
of
the
already
available
features.
That
merchants
can
leverage
inside
first
Prince
rain
and
at
the
same
time
we
can
like
try
to
predict
what
could
be
useful
for
our
clients
to
have
in
future
releases
of
the
MSI.
B
B
Early
I
mean
probably
early
but
I
would
say
by
the
end
of
the
next
week,
and
so
yeah
we'll
probably
share
this
article
with
every
merchant
that
we
start
working
on
and
so
by
exploring
these
information
merchants
will
be
able
to
decide
whether
or
not
MSI
is
a
good
fit
for
them.
So
yeah
I
start
with
a
short
overview
of
what
is
actually
the
a
Masonic
us.
B
B
B
We
think
that
store,
pickup
will
definitely
be
huge
and
we
already
have
a
few
requests
from
different
merchants
that
they
would
really
love
to
have
a
store,
pickup
option,
their
stores,
and
that's
that's,
definitely
a
great
opportunity
to
use
MSI
for
that,
because
I
mean
for
us
as
an
aside,
it's
always
better
to
have
as
native
integration
as
possible.
So
we
we
bought
a
group
for
using
MSI
plus
some
customizations,
then
installing,
like
third-party
modules,
that
we
need
to
manage.
B
It
would
be
really
really
great
to
see
more
sales
channels
available
out
of
the
box,
but
also
I
think
that's
a
great
opportunity
for
extension
developers
to
provide
their
modules
to
extend
MSI
functionality
so
yeah,
just
summing
up
here,
I
think
in-store
pickup
is
definitely
one
of
the
most
popular
requests
currently
on
the
market
and
for
b2b
merchants.
The
variety
of
sales
channels
that
they
can
incorporate
out
of
the
box
is
also
it's
also
very
important.
So
yeah,
that's
that's
my
take
on
that,
and
should
you
have
any
questions,
please
feel
free
to
reach
out.
A
We
we
hope
to
see
your
post
as
soon
as
possible,
and
it
was
really
great
to
see
to
see
your
opinion
and
thank
you
very
much
for
our
tweets.
You
did
a
great
job
on
MSI
and
made
the
made
the
ball
rolling
and
the
next
one
today
gonna
be
our
our
guest
from
that
cool
agency.
Who
will
tell
us
a
little
bit
more
about
already
utilized
MSI
and
he'll
leave
this
for
the
point
of
sales
application
and
so.
C
D
C
Previously,
when
there
was
no
msi,
what
pro
we
are
getting
is
at
the
time,
because
there
is
only
single
inventory
for
both
website
and
us.
So
what
exactly
should
we
are
getting?
Is
we
have
to
divide
and
make
some
logic
to
divide
the
inventory
for
us
application
and
website,
because
there
is
only
one
single
inventory
of
each
product
so
in
case
of
offline
mode,
when
the
inventory
that
divided
already
through
POS
application,
there
is
a
case
if,
in
offline
mode.
C
C
C
C
A
E
C
E
C
Mm-Hmm,
if
any,
if
this
is
the
case
of
offline
mode,
then
all
the
inventory
of
a
particular
product
has
already
synced
to
the
offline
data
of
the
browser.
That
means,
if,
let's
say,
Joe's
dough
fill,
has
33
inventory,
then
that
33
inventory
is
for
the
four
only
POS
and
if
in
offline
mode
or
we
have,
we
create
orders
with
all
the
33
inventory.
Then
there
no
issue,
because
no
website
is
going
to
utilize,
that
33
inventory
from
in
from
this
source,
because.
A
I'm,
just
thinking
that
this
is
very
similar
implementation
to
what
we
consider
in
how
the
store
pickup
gonna
be
implement.
It
was
in
store
pickup,
so
the
historical
functionality
implemented
pretty
easily
based
on
they
exist
in
a
Masai
architecture,
but
the
stock
resolve
and
mechanism
supposed
to
be
supposed
to
be
implemented.
A
Many
earlier
so
currently,
a
Masai
has
own
logic
to
to
resolve
the
stock
based
on
the
sales
channel,
but
in
a
in
a
case,
if
you
will
implement
the
store,
pick
up,
the
store
pick
up,
gonna
be
gonna,
be
provided
like
like
a
drop
down
assumption
and
the
actually
customer
will
choose
the
appropriate
stop.
So,
in
this
point
of
sale
terminal,
this
is
actually
pretty
similar,
because
because
currently
you
choose,
you
choose
a
particular
location
and
to
this
particular
location
this
source
is
assigned
to.
A
A
C
Yes
and
we
have
implemented
a
one
of
my
team
member-
have
implemented
this
in
the
dropship
module
actually
I
have
that
to
the
module,
have
almost
the
same
kind
of
flow
that
I
have
followed
in
the
POS
application
and
she's
not
available
here.
So
I
cannot
actually
let
you
know
the
exact
implementation,
but
you
can
have
an
idea
with
this
block
that
she
already
wrote.
A
A
G
G
G
What
I
can
do
actually
is
to
tell
you
what
happened
while
working
with
MSI
and
this
new
project,
because
actually
this
project
started
with
magenta
2.2.
So
actually
there
was
no
MSI,
as
you
probably
know,
and
at
the
very
beginning,
MSI
was
not
requirement
for
this
project
and
if
I
explain
you,
what
kind
of
project
is
this
you
will
probably
say
from
the
very
beginning?
G
Why
are
you
using
am
assign
this
project
as
well,
because
we
don't
have
any
multiple
source,
so
we
just
have
one
single
source,
so
using
MSI
at
very
beginning
can
be
something
strange
for
people,
not
that
or
not
that
doesn't
know
exactly
how
a
missile
works,
but
I.
We
understood
that
we
were
needing
Atmos
I
when
this
customer
asked
us
to
export.
It
was
one
of
the
first
requirement
to
export
all
the
quantity
that
basically,
the
people
were
asking,
so
the
quantity
ordered
that
were
not
shipped.
G
This
was
this
was
one
of
the
first
requests
and
then
they
asked
us.
We
need
to
update
our
stock
depending
on
the
quantity
we
actually
have
in
our
stock
and
not
depending
on
the
quantity
minus
the
quantity
order.
So
if
you
know
how
the
reservation
system
works,
basically
this
this
was
a
requirement
for
this
project.
So
at
the
end
we
decided
to
to
add
MSI.
They
are
not
using.
Of
course,
all
the
MSI
features
as
far
as
now.
G
So
the
main
key
point
was
the
reservation
mechanism
and
without
it
honestly
I
had
no
idea
to
implement
without
messing
or
the
transaction
and
so
on
and
yeah.
But
tomorrow
they
they
know
they
have
MSI
and
they
are
starting
asking
to
trendle
multiple
sources
for
tomorrow,
because
this
customer
basically
is
a
video
game,
distributor
and
I'm
so
happy
to
work
with
this
kind
of
customer
actually
because
I'm
very
geek
from
this
perspective,
and
they
had
the
f
shops
all
around
the
Italian
country.
G
So
they
will
probably
add
some
kind
of
support
to
to
even
see
how
many
products
they
have
been
differential
shops
and
maybe
build
something
more
powerful.
That
now
and
that's
it
and
honestly
was
easier
than
expected
to
be
honest,
because
the
very
beginning,
upgrading
from
a
2.2
project
to
a
2.3
project,
with
a
new
module
like
a
messiah,
was
something
unknown
for
us,
but
at
the
end
was
I
have
to
say
quite
easy
of
course,
easy
always
and
that's
it
I'm
sorry,
because
I
have
no
presentation
but
yeah
I'm.
G
A
E
A
Okay,
so
let's
proceed
Father
and
the
next
one
gonna
be
Slava,
so
we'll
show
you
so
on
a
previous
demo.
Ricardo,
so
Ricardo
actually
is
really
has
a
really
high
velocity
because,
along
with
making
a
magenta
to
the
tree
releases,
he
also
has
a
time
to
make
the
contribution
and
the
week
ago
he
made
the
humiliate
delivery
of
the
first
and
one
of
the
biggest
feature
feature
of
milestone
3,
and
he
demonstrated
the
distance
based
algorithms,
a
working
prototype,
actually
even
more
than
just
a
working
prototype.
A
A
H
Hi
everyone,
let
me
show
Martin
so
during
our
test
of
BR,
the
distance
sources
under
it.
We
face
one
issue
like
several
issues,
but
one
issue
is
described
it
in
the
tickets,
key
on
github
that
when
we
were
creating
a
new
source
and
put
post
code,
it
will
post
code
of
corporate
with
a
city
nearby
to
us
unfortunate
I.
H
H
H
H
H
H
Another
issue
what
we
faced
I
created
ticket
about
it,
it's
that
I
have
problem
and
when
I
said
one
source
in
United,
States
and
another
source
in
Ukraine,
for
example,
and
after
I
place.
The
order
with
Ukrainian
address,
source
selection.
Algorithm
I
had
a
problem
to
count
distance
because
it's
using
rotis
like
driving
or
walking
or
bicycle.
But
it
could
not
count
the
distance
from
united
state
to
Ukraine.
Not
any
of
these
ways,
and
it's
strong
exception.
H
A
That's
why
currently
making
the
like
here,
for
example,
you
see
that
I
have
a
stock
and
there
are
several
several
sources
in
Europe
and
one
in
the
United
States,
and
currently
we
have
actually
the
ship
can
address,
whether
in
Europe
or
in
the
United
States.
The
Google
will
will
give
us
an
error
because
he
can
just
provide
computed
the
distance
between
Europe
and
the
United
States,
using
the
drive
and
bicycling
or
walking
computation
mode.
That's
why
so
countries
we
don't
have
that
precise
answer,
what
to
do
with
this
source?
A
A
G
A
G
G
A
That
it
could
be
crucial
for
some
particular
business,
for
example,
if
it
has
a
pizza
delivery
and
we
just
provide
an
ability
to
deliver
on
on
a
bicycle
on
a
bicycle.
So
all
our
guys
involved
in
the
delivery
you
use
bicycle
to
deliver
pizza
and
for
like
and
Google
and
and
we
choose
like
the
business
choose,
this
calculation
type
like
bicycling
and
Google
just
returned
that
it's
not
possible
to
reach
some
particular
address
by
bicycle
because
it
is
on
the
island
or
I.
Don't
know
what
the
reason
so
there
is.
A
There
is
still
the
possibility
to
get
this
error,
and
maybe
we
no
need
to
make
a
fallback,
because
using
the
fallback
we
can
calculate
the
distance,
but
from
our
delivery
perspective
still
would
be
unreachable
by
for
our
delivery
service.
So
maybe
it
may
have
to
highlight
that
it's
not
possible
to
to
reach
from
from
this
particular
source
to
the
delivery
address
or
make
sense.
E
E
A
E
Shown
there
at
the
top,
because
we
have
to
make
an
assumption
that
the
source
well,
that
they
configured
this
sources
correctly
and
were
able
to
resolve
the
location
of
the
sources
at
the
time
they
set
up
the
sources.
So
when,
if
you
go
to
source
configuration
and
I
edit,
the
details
of
a
source
there,
I
would
expect
to
get
an
error
on
that
screen.
If
I
can't
resolve
a
source
on
this
screen
that
you're
currently
showing
now
I'll,
get
an
error.
If
the
shipping
address
the
destination
has
a
problem,
mm-hmm.
E
Just
think
it
adds
a
lot
so
that
the
UX,
because
assuming
Austin,
gets
set
up
correctly.
It
will
work
for
every
shipment,
though,
that
the
the
time
and
place
to
correctly
set
up
Austin
is
when
the
source
is
being
configured
and
we
should
validate
it
when
we
create
a
source
or
make
changes
to
the
source.
I.
F
Think
also,
an
important
point
is
that
the
Google
API
is
strictly
Maps
and
its
location
to
location.
Can
you
get
there
by
walking
driving
or
bicycle,
but
it's
not
if
it's
shippable,
so
Austin
is
skippable,
but
Google
isn't
set
up
that
way
to
determine
if
it's
shippable.
So
it's
not
really
an
error
of
it
can't
detect
the
distance,
but
it
is
still
shippable,
so
it
would
still
be
good
to
have
there
I
think
I.
E
A
A
A
That
was
the
last
issue
we
we
had
with
with
Google
API
and
also
as
we
yesterday
agreed
on
the
grooming
meeting.
We
decided
to
switch
to
Google
address
components
to
refine
that
query.
So
now
we
provide
the
as
a
dedicated
component,
zip
code
and
country
code,
and
actually
that
was
demonstrated
by
slalom-
and
this
is
all
regarding
Google,
API,
specific
fixes
and
now
following
the
agenda,
we
are
switching
to
Tom
and
Tom
will
will
present
the
update
regarding
the
automated
test
coverage
and
MFDs.
J
So
this
is
just
our
weekly
update
on
quality
and
test.
So
we'll
begin
with
our
manual
testing,
we
have
our
current
test
coverage.
505
tests
and
142
of
those
are
automated
363
of
those
are
manual
only
at
this
point,
however,
all
505
are
run
manually
and
so
that
total
figure
is
how
many
run
fully
for
manual
or
defined
fully
manually.
We
have.
J
This
can
put
a
breakdown
so,
as
you'll
see,
majority
is
within
seals
and
cut
logs
been
a
couple
of
tests
editions
since
last
week,
there's
been
a
couple
more
added
and
we'll
be
over
the
next
week.
So
we
should
see
this
number
of
creeping
up.
The
last
map
full
manual
test
run
big
thanks
to
Slav
and
his
team
for
getting
that
finished
out.
That
was
finished
out
on
the
fifth
and
we
we're
left
with
these
results.
J
So
great
majority
of
passes,
some
issues
with
the
field
skipped
some
blocks,
those
are
being
resolved,
but
all
together
that
was
a
regression
run
for
us
now
moving
the
automation,
then
so
automated
testing.
Currently,
as
we
know,
it's
done
an
MFT
F.
We
have
this
breakdown
coverage,
as
you
seen
from
the
previous
slide,
so
of
those
five
hundred
five
scenarios
that
would
define
142
of
those
are
currently
automated.
That
is
28
percent
of
the
total
and
obviously
looking
to
increase
that
we
are
not
am
prioritizing
a
drive
towards
the
full
505.
J
So
they
were
almost
freebies
that
we
got
in
and
we
haven't
covered
any
s
3s
or
asked
for
s
by
automation,
as
you
hopefully
would
expect
you
in
terms
of
our
component
coverage,
then
so
we
are
following
roughly
the
same
component
coverage
as
the
full
test
and
manual
regression.
Suites
are
so
that's
a
majority
within
catalog
and
seals.
We
do
also
have
a
good
amount
in
configuration
as
well,
which
we've
found
useful
to
automate.
That's
like
the
current
coverage.
J
There
and
finally
I'm
there
will
be
a
component
level
breakdown
of
this
for
next
report,
but
apparently
just
to
show
you
the
latest
run
of
those
MF
TF
tests
at
no
failures
we're
all
happy
to
see.
We
have
18
skipped
MF
TF
tests
currently
and
due
to
various
issues,
a
high
recurrence
that
it
of
those
will
be
unscripted
a
PR
that
is
in
processing
at
the
moment,
so
we're
looking
at
that
number
to
come
down
and
they
won't
clear
the
rest
of
the
skip
tests
as
well.
J
D
We
are
currently
working
with
Tom
on
figuring
out
how
to
do
that
exactly
considering
the
smorgasbord
of
systems
that
we
were
using
internally
and
externally,
but
we
are
going
to
get
there
and
you're
gonna
start
seeing
where
we
are
having
more
most
failures
and
least
failures,
and
what
the
breakdown
of
our
automated
test
runs
per
component
is
analogous
to
how
we're
doing
it
with
a
manual
testing
right
now.
So
that's
all
incoming
as
Tom
said,
correct.
J
A
Yep
so
looks
like
that's
all
for
today.
Thank
you,
guys
for
your
time
and
the
more
to
come
next
week,
of
course,
join
join
our
grooming
session
and
the
10
year
agreement
session,
scheduled
on
Wednesday
I,
will
share
the
invitation
week
in
the
link
endemic
as
a
child
soon
and
I.
Think
you
think
you
very
much
and
have
a
great
weekend.
Thank
you.