►
From YouTube: Magento MSI Open Demo. April 13, 2019
Description
Agenda:
- Greetings from todays broadcasting location – *Magento Meetup and Contribution Day in Kyiv* @Alex Lunkov
- Stock Export API @Stepan Furman @Slava Moskalyuk
- Inventory Reservations CLI @Riccardo Ugolini
- New Inventory compatibility for Commerce Edition and B2B extension @daniloempire
- Product page Source Assignment UI improvements @fratob85 @TheRick
- Partial Stock Transfer Web API @bcerban
- Store Pickup track updates @Aleksandr@Maxim Novik
- Upcoming release announcement @iminiailo @ishakhsuvarov
- Quality status by @Tom Erskine
A
Hello
guys
welcome
to
another
weekly
MSA
demo.
Today
we
have
really
lots
of
exciting
updates
and
we
are
hosting
it
from
another
went
this
month.
This
is
a
key
of
contribution
day
and
meetup
organized
by
twigs
and
the
first
first
to
talk
to
you
would
be
Alex.
Who
is
one
of
the
event
organizers?
He
will
introduce
what's
happening
here
and
what's
the
agenda
for
the
following
two
days.
B
B
We
expect
around
70
80
people
and
that's
really
excited
because
exciting,
because
today
we
also
have
Alexander
craft
cook
and
he
will
be
talking
about
his
work
on
msi
in-store
pickup
feature,
which
is
I,
think
really
great
to
hear
both
merchants
and
developers
so
yeah,
that's
one
of
the
talks
were
also
gonna.
Have
three
other
speakers,
including
Victoria
from
ethics.
We're
gonna
tell
us
about
latest
commerce
trends
and
also
eager
we'll
be
talking
on
the
event
and
Vadim
from
tech
division.
B
B
A
Thank
you,
Alex
we're
really
enjoying
the
event
location
for
now
and
I
hope.
The
event
would
be
even
better
okay.
So
now
we
are
going
to
follow
our
agenda
and
due
to
technical
issues,
we'll
skip
this
talk
expert
for
now,
so
I
would
kindly
invite
Ricardo
to
talk
about
inventory
that
reservation
CLI,
which
was
implemented
during
the
last
Meetup
and
contribution
day
in
Perugia,
usually
last
week
to
please
guys
if,
if
you
have
anything
to
share.
C
D
D
C
Okay,
so,
for
example,
in
this
case,
we
out
were
on
one
compensation
problem,
and
this
year
like
come
on,
just
show
us.
We
have
something
going
wrong
in
one
order.
I
cannot
read
exactly
because
it's
quite
small
here
and
it
also
say
what
is
the
product
and
how
much
you
should
be
compensated
to
go
back
to
our
zero
condition.
Okay,
is
that
correct?
Yes,.
D
C
C
D
F
So
just
small
update.
So
currently
we
have
this
tool
which
highlight
all
these
orders
and
all
the
products
which
are
affected
in
the
scope
of
these
orders,
because
quite
interesting,
quite
an
interesting
fact
that
we
not
so
because,
potentially
even
in
this
cup
of
an
order,
we
could
have
some
or
some
excuse
which
we
were
counted
correctly
and
along
with
that.
F
We
could
have
some
sq4,
which
we
don't
have
the
proper
compensated
reservation,
because,
for
example,
because
of
the
partial
shipment
functionality,
so
that
we
usually
place
an
order
and
fully
fulfill
the
order
for
particulars
queue
and
for
all
those
which
are
not
fulfilled.
We,
for
some
reason,
can
have
inconsistent
state
so
that
these
two
will
determine
the
inconsistency
not
just
on
the
level
of
order,
but
on
the
level
of
let's
say
order.
F
Item
and
the
output
of
this
tool
will
provide
us
the
order,
reference,
the
FDU
and
the
quantity
which
is
considered
like,
which
is
not
compensated
so
that
static.
Just
just
an
example.
If
the
initial
like
is
a
initial
order,
been
played
for
10
items
and
the
initial
reservation
created
for
-10
item,
and
then
it
was
a
partial
shipment
and
correspondingly
+5
reservation
for
+5
was
created.
F
So
this
is.
This
is
1/2,
which
was
currently
demonstrated
by
Ricardo
by
both
Ricardo's,
that
we
have
double
Ricardo
power,
and
currently
we
are
working
on
another
tool
which
is
supposed
to
compensate.
So
currently
we
have
a
tool
is
supposed
to
highlight
their
inconsistency
and
another
tool
which
supposed
to
fix
the
inconsistency
and
that
inconsistency
gonna
be
fixed
with
creation
of
compensation
or
reservation.
We
will
introduce
a
new
type
of
reservation.
F
So
you
know
you
know,
reservations
are
created
in
the
scope
of
the
business
event,
so
the
business
event
gonna
be
manual
adjustment
and
the
pretty
interesting
fact
here
that
we
are
not
removing
or
like
we
are
not
removing
existing
reservation.
We
are
just
compensating
them
so
that
potentially,
if
something
went
wrong,
it
means
to
have
a
chance
just
to
see
what
was
compensated
and
may
make
some
additional
adjustment
on
top
of
that.
So
this
is
pretty
safe
way
to
to
fix
him.
F
The
reservation
quantity-
and
this
is
this-
is
another
ticket
and
there
like,
and
we
are
working
on
it
right
now
and
also
recovery
is
involved
in
these
activities.
So
thank
you
guys
for
this
presentation.
This
is
pretty
nice,
pretty
nice
feature,
and
especially
now,
when
we
see
quite
a
lot
of
merchants,
started
to
migrate
on
Magento
to
the
3
that
one,
because
we
especially
see
quite
a
lot
of
migration
and
the
MSI
activity
after
the
magenta
to
the
to
the
one
was
released.
F
A
A
E
E
E
A
Thank
you
very
much.
This
is
really
great
presentation,
especially
when
we
can
see
that
it
really
works
and
I.
Think
if
you
already
have
the
code
for
the
msi
part
feel
free
to
submit
a
pull
requests
targeting
msi
at
the
same
time
we'll
be
processing
them
simultaneously,
so
we'll
be
trying
to
merge
them
as
soon
as
possible.
So
this
feature
is
available
in
the
scope
of
the
next
release.
E
E
A
C
E
A
So
the
next,
the
next
item
on
the
agenda
is
also
really
nice
source
assignment.
You
are
improvements.
The
sauce
assignment
table,
which
all
of
us
have
seen
on
the
product
page
that
grid
had
some
issues.
It
was
not
that
usable
and
Francesco
did
quite
a
lot
of
work
to
rework
that
UI
and
make
it
much
more
usable
and
user-friendly.
So
I
am
now
passing
the
word
to
recall
Francesco,
who,
whoever
is
going
to
present
it
yeah.
C
C
I
think
there
were
three
issues
but
all
related
to
the
source
assignment
that
was
before
his
pull
requests
was
almost
in
this
state,
so
basically
it
was
almost
unusable,
but
or
at
least
quite
ugly,
and
what
it
is
to
rework
passing
to
this
condition
that
you
can
see
from
one
leg
installation.
So
what
he
did
basically
was
to
compress
this
information
by
adding
one
to
tip,
because
before
was
the
fourth
source
and
the
source
code.
C
C
Then
he
also
unified,
notify
and
use
the
fault
column,
because
before
was
yeah
in
two
different
columns.
That
was
quite
space
consuming,
and
now
it
is
just
in
one
single
call.
This
was
quite
tricky
to
do,
and
plus
y
also
removed
the
additional
column
with
unassign
that
was
almost
and
useful
because
we
had
a
quite
tough
explanatory
icon
and
basically,
what
he
managed
to
do
is
to
reduce
the
space
of
the
doors
assignment
and
honestly
make
it
a
slightly
better
than
before,
and
that's
it.
C
A
You
very
much
for
the
presentation.
Actually,
this
all
of
these
items
were
a
part
of
the
bigger
task
which
we
had
on
the
our
issue,
tracker
at
some
points,
and
we
have
extracted
some
items
from
it
and
after
Francesco's
work,
it's
really
nice,
but
we
have
filed
two
more
tasks
related
to
moving
the
buttons
and
hiding
the
source
assignment
table.
That's
all
when
there
are
no
forces,
maybe
Francesca
or
somebody
else
would
like
to
pick
that
up.
A
H
H
F
Preliminary
slava,
are
you
ready
to
present?
Your
part
no
actually
saw
would
be
talking
on
behalf
of
Stepan
woman,
who
is
currently
still
in
a
train
and
he
is
still
reaching
the
vacation
of
meetup.
That's
why
he
is
not
able
to
join
the
meeting
right
from
the
Train.
That's
why
Slava
will
make
presentation
behalf
of.
I
Okay,
so
I
have
reused
profile,
a
small
profile
from
performance.
Kid
and
I
have
created
more
than
1200
products
by
this
profile,
and
the
main
idea
of
this
PR
is
that
we
should
be
able
to
export
stock
data,
and
also
this
export
should
count
aggregated
reservation
place
it
during
the
different
operation,
placing
quarter
shipment
and
so
on,
so
on
so
it
over.
The
duration
have
to
be
counted.
I
I
F
Good,
thank
you,
slalom,
I
believe
the
next
time.
So
this
time
we
was,
we
were
not
prepared,
but
probably
next
time
we
will
demonstrate
the
asynchronous
work
of
this
API
code,
because
potentially
it
can
take
quite
a
long
time
if
we
it
will
be
expert
in
the
stock,
with
a
big
number
of
s
Q's
and
the
looking
at
Alex
Rosen,
who
is
currently
watching
this
presentation,
I
just
try
and
trying
to
foresee
his
next
question.
F
So
we
will
make
a
presentation
for
you
on
during
the
next
Yuma
how
they're
going
to
be
implemented,
asynchronous
export
and
probably
so
here
is
another
question
to
mark
and
I
regarding
this
functionality.
So
as
you
like,
as
the
solid
res
demonstrated
us
here,
we
presume
all
this
reservation
placed
and
we
are
expert
in
stock
taken
into
account
like
what
we
literally
do.
Currently,
we
iterate
all
that
product
and
we
are
explicitly
calling
get
product,
saleable
quantity,
so
like
on
a
small
profile.
F
Currently
we
have
1000
like
12
hundreds
of
product
and
for
each
and
any
of
that
product
we
were
calling
get
products
available,
quantity
so
potentially
on
a
big
profile.
That
could
take
some
like
some
number
of
some
time
and
we
made
some
checks
on
a
medium
profile,
so
a
medium
profile.
It
took
more
than
our
and
potentially
so.
The
time
will
grow,
depending
on
the
opinion
on
the
catalog
size.
So
what
we
thought
that,
potentially
we
can
provide
two
possibilities
of
export.
F
The
first
one
will
will
be
very
precise
and
will
include
all
the
tracer
ation
another
one
could
be
really
quick.
For
example,
if
you
will
just
dump
a
table,
dump
dump
an
index
for
particular
stock,
so
that
would
be
pretty
pretty
much
the
same
as
what
we
are
showing
on
the
catalog
page
or
on
the
search
result
page.
So
we
will
not
will
not
include
reservation,
but
along
with
that,
that
expert
would
be
very,
very
quick.
G
I
think
it
is
a
valuable
option
and
we
definitely
if
we
introduce
the
quick
export.
We
still
need
to
have
the
the
option
to
do
the
what
we
call
the
more
accurate
export
or
the
one
that
takes
into
consideration
all
the
reservations.
So
the
merchant
can't
decide,
but
if
they're
doing
something
like
for
for
sales
channels
where
they
need
to
do
this
export,
it
may
be
more
important
for
them
to
do
it
quickly
and
they
can
handle.
You
know
any
reservations
that
may
be
there
by
adjusting.
G
You
know:
they're
they're,
out
of
stock
quantity
type
things
in
and
on
the
Amazon
side,
so
they
can
manage
those
thresholds
so
that
they
don't
really
need
the
full
detail,
given
that
they
know
how
much
you
know.
Orders
are
typically
in
flight
at
any
given
moment.
I,
don't
know
if
Ryan,
if
you
have
any
thoughts
on
this
I've
asked
Ryan
to
join
as
well,
because
he's
working
on
the
sales
channel
side
to
see
what
he
thought.
K
K
All
right,
cool,
yeah,
I
think
I
think
we
can
work
with
that.
So
we
discussed
when
we
were
talking
about
implementing
MSI,
whether
or
not
we
could
do
this
with
out
of
stock
thresholds
and
stuff
like
that.
There
are
some
limitations
there.
So
there's
a
there's.
Actually
some
latency
brought
into
this
by
Amazon's
reports,
so
we
don't
necessarily
get
totally
on
time.
Stock
coming
back
from
Amazon
would
be
the
only
issue
so
that
could
introduce
the
need
for
higher
and
higher
stock
thresholds.
K
To
the
point
of
you
know,
20
units
or
or
higher
I
guess
obviously
depending
on
on
sales
volume
for
merchants.
But
do
you
know
what
I
guess
is
the
the
performance,
I
guess
limitation
here
we
we
found
a
bunch
of
instances
where
indexers
could
be
sped
up.
Is
there?
Is
there
any
long-term
opportunity
to
to
increase
performance,
or
this
would
be
about
the
speed
for
the
for
the
future
of
the.
F
Different
in
comparison
to
other
data
beyond
exported,
because
since
material
to
the
tree,
the
quantity
became
kind
of
calculate
able
data
so
that
to
get
the
precise,
saleable
quantity
we
always
supposed
to
call
the
service
and
that
service
under
the
hood
make
quite
a
lot
of
calculation.
So
we
aggregate
in
quantity
on
all
that
sources.
We
taken
the
quarter
into
consideration,
minimal
quantity
threshold
and
all
the
trades
eration
already
placed.
F
So
currently
we
have
the
linear
dependency
on
the
catwalk
size
and
the
number
of
product
assigned
to
particular
stock,
so
that
if
we
have
like
like
a
1000th
product
and
we
have
10,000
product,
that
performance
would
be
like
10
times
slower.
Let's
say
it
that
way,
but
along
with
that,
we
will.
We
will
expert
there
the
correct
quantities,
but
potentially,
if
we
will
just
agree
to
like
provide
an
option
to
neglect,
neglect
reservation
and
just
just
make
a
dump
of
the
of
the
dock
table.
K
F
Currently,
we
are
talking
two
parameters.
The
first
parameter
is
the
stock
ID,
so
MSI
for
the
stock
ID
for
MSI
is
the
is
the
entity
which
map
to
the
sales
channel.
So
this
is
pretty
much
or
pretty
much
the
entity
which
would
be
mapped
to
the
Amazon
sales
channel,
for
example,
and
the
second
parameter
is
a
search
criteria.
So
this
is
the
object
which
provide
and
which
provide
a
possibility
to
apply
different
filtration.
F
G
G
H
Yeah,
so
what
we
had
shocked,
but
with
a
partial
transfer
interface,
it's
actually
implemented
and
REST
API.
So
the
idea
is
to
be
able
to
transfer
partial
stock
amounts
from
one
source
to
another.
Currently
we
only
have
full
dog
transfer.
So
if
you
want
to
transfer
from
source
aged
source,
be
the
full
amount
will
be
moved.
H
H
H
H
H
So
let
me
see,
I
had
I,
think
well,
I
ran
it
twice,
so
I
had
90
items
at
default
and
then
something
like
64
house
a
and
then
I
moved
it
and
it
just
moved
validation
fast.
And
then,
if
we
go
back
here,
then
you
see
that
it
was
all
updated.
The
combined
stock
was
updated
as
well.
H
G
F
G
F
But
at
least
now
we
already
have
a
service,
and
currently
we
already
have
several
potential
application
for
this
service,
because
initially
the
idea
for
this
partial
transfer
appeared
when
we
were
discussing
the
in-store
pickup
and
that
if
we
need
to
fulfill
fulfills
the
inventory
on
particular
source,
which
is
used
for
in-store
pickup
and
which
has
a
lack
of
products
powerful
for
particular
order.
Fulfillment
does
that
Bettina
yesterday
propose
to
use
this
partial
transfer
in
the
scope
of
the
in-store
pickup
track
and
yeah.
F
I
A
M
G
F
M
J
My
date
will
be
short
enough:
topic
type
is
being
the
world
lovely,
but
continent.
So
last
week
and
epic,
if
you
about
Beijing
ready
for
pick
up
button
or
not
last
week
this
week
was
point
limors.
There
is
81
comment.
Also
Captain
Obvious
was
involved
in
there.
As
you
can
see,
I
am
NOT,
saying
much.
J
J
There
is
a
case
where
we
have
an
order
place
using
turkey
club,
but
customer
is
still
able
to
ship
the
order
in
the
usual
way.
So
what
the
behavior
should
be
in
this
case,
I
can
suggest
two
ways:
the
first
one.
The
most
simple
is
just
to
write
the
sheep
bottom
in
the
mean
panel
and
the
second
one
is
to
forbid
the
sheep
order
place
using
turkey
table
if
customer
is
not
certified
yet
so
the
only
way
to
keep
the
order
if
the
you,
the
functionality,
implemented.
G
J
G
Discussed
this
on
our
last
grooming
and
it's
important
to
give
the
merchant
still
the
opportunity
to
to
really
do
whatever
they
want,
so
the
normal
flow
for
instance
or
pickup
order
is
the
order
is
placed
the
the
merchant
gets
it
ready
and
then
clicks
they're
ready
for
pickup
button.
The
customer
gets
an
email
they
come
and
collect
it.
That's
the
normal
flow,
but
if,
for
some
reason
you
know
an
in-store
pickup
order
came
in
and
the
merchant
decided
they
needed
to
ship
it.
G
So
maybe
the
customer
called
in
a
business
use
case,
for
this
is
frequently
I
use.
In-Store
pickup,
if
I
travel
so
I
need
something.
I
can't
get
it
in
time
before
I
need
to
leave
from
my
trip.
So
I
do
an
in-store
pickup
of
somewhere
I'm
going.
Maybe
it
gets
to
this
store
late
or
something
and
now
I'm
not
going
to
be
in
a
place.
I
can
get
that
anymore.
So
if
I
call
the
merchants,
maybe
they'll
ship
it
to
me,
we
need
to
let
the
merchants
have
the
ability
to
do
that.
G
J
G
A
That
merchants
would
have
to
change
the
address.
Also
because
currently
for
store,
pickup
would
orders
I
think
we
were
targeting
to
use
the
store,
pickup
shipping
method
and
the
address
of
the
pickup
point.
So
basically,
I
think
on
the
merchant
sides
would
be
one
or
two
additional
actions,
and
should
we
guide
the
merchant
somehow
that
that
should
be
done.
G
We
are
judged.
I
was
thinking
really
quickly
of
ways
we
can
handle.
That
I
mean
if
they
click.
If
it's
an
in-store
pickup
order
and
they
click
ship,
you
know
we
can.
We
can
take
out
the
the
ship
to
address,
because
the
store
would
not
be
useful.
As
an
address
optionally
I
mean
we
could
replace
it
with
the
default
shipping
address
of
the
customer.
G
That's
probably
the
best
idea
and
then
still
give
them
the
ability
to
change
that
if
they
need
to
so
if
they
click
the
ship
button
on
the
order,
that's
in
store
pickup,
it
should
use
as
the
ship
to
address
the
customers
default
shipping
address.
If
they
do
not
have
a
default
shipping
address,
then
that
can
be
empty
and
the
merchants
still
can
change
that
on
the
shipping
page
if
they
need
to.
F
Option
the
customer
can
change
his
mind
and
instead
of
in
store,
pickup
he'll
pay
for
just
general
shipment.
Whether
we
should
support
another
another
case
when
customer
just
order
a
regular
shipment,
but
for
some
reason
he
decided
to
change
his
might
and
prefer
to
go
and
grab
the
order
in
in
any
like
pick
application.
So
that
I
mean
if
the
order
been
placed
with
the
shipment
should
be
shows,
notify
and
the
pickup
location
they'll
just
like
to
consider
order
like
in-store
pickup,
when
it
was
created
like
a
regular
order.
G
G
F
F
Okay,
so
this
is
pretty
much
all
from
from
our
guests
who
made
the
presentation.
There
was
the
last
one,
probably
gonna
be
me,
and
I
will
make
the
unknowns,
a
short
amount
of
the
upcoming
MSI
release.
So
in
a
in
a
week,
or
maybe
in
10
days,
we're
going
to
release
an
aside
version,
one
that
bonded
to
and
in
the
scope
of
this
version,
we
will
release
the
support
of
b2b
so
because,
currently
till
now
that
b2b
could
you
just
default
stock.
F
But
as
you
as
you,
as
you
have
already
seen
during
this
demo,
we
already
incorporated
support
of
quick
order,
and
now
quick
order
can
work
with
with
multi
sources.
Also,
we
have
a
corresponding
things
fixed
for
acquisition
list,
but
that,
along
with
1.1.2
release
of
MSI
will
fully
support
b2b
to
use
all
the
benefits
of
MSI,
also
we're
going
to
release
a
Messiaen
graph
kill.
F
F
Also,
we
will
will
release
the
export
of
stock
data,
so
the
functionality
which
also
was
presented
during
this
during
this
meeting
also,
we
will
will
release
quite
a
big
chunk
of
work,
which
was
created
and
presented
by
recorded
and
passed
on
a
previous
on
a
previous
meeting
where
we
provide
the
asynchronous
synchronization
between
legacy
and
new
inventory
mechanism.
So
this
part
of
work
supposed
to
improve
the
performance
of
products,
evaporation.
F
Also
we
going
to
deliver
some
UI
enhancements,
some
of
this
enhancement
being
present
and
during
this
meeting
as
well,
and
also
we
will
deliver
the
web
api
for
partial
source
source
to
source
transfer.
So
this
functionality
also
been
present
during
this
demo
by
Bettina
and
yeah.
So
this
pretty
much
also
we
have
pretty
oh
and
also
one
with
that
we
fixed
more
than
so
more
than
10
bucks.
So
it's
going
to
be
pretty
big
release
actually
and
then
we
will
be
more
dedicated
on
to
big
features
so
in
store
pickup
and
the
bundled
product
support.
N
N
N
We've
now
fixed
those
in
two
places,
so,
as
you
mentioned
earlier,
with
updated
MF
TF
tests
and
PR
2165
due
to
the
removal
of
the
source
code
column
in
the
product
sources
grid,
so
we're
continuing
to
modify
those
tests
as
we
make
UI
changes,
there
will
be
further
as
we
make
more
of
those
UI
cleanup
tickets
through
and
there
was
some
Travis
on
with
static
failures
on
code
Styles
again,
updates
have
been
made
to
that.
So
we're
back
to
green,
looking
good
for
good
quality
testing.
For
that
one,
one,
two
patch.
N
Beyond
that
we're
looking
at
over
the
last
week,
15
issues
open
for
closed
I'm
focused
on
bug,
so
three
bucks,
one
of
which
is
currently
open.
It's
a
top
ten
bog
right
there
2156
and
you
can
all
look
at
that.
If
anyone
wants
to
pick
it
up
yeah,
but
that's
our
one
major
bug
currently
open
that
was
created
within
the
last
week,
I
will
run
through
automated
there's
been
essentially
no
change
in
automated.
N
These
numbers
are
still
true,
as
of
the
March
22nd
that
hasn't
been
updated
because
automation
hasn't
moved
beyond
fixes
and
no
new
test
just
fixes
the
numbers.
Since
we
completed
that
one
100
regression
has
jumped
from
602
to
625
total.
So
just
since
fencing
the
we've
added
23
4
new
features,
so
there
is
increase
in
test
coverage
as
we
develop.
N
Severity
and
component
are
all
the
sims
before
for
automation,
during
our
focus
in
seals
and
catalog,
primarily
and
in
the
manual
testing
that
is
here.
So
we
see
an
increase
in
the
seals
and
cut
work
numbers
again,
which
is
our
focus,
and
then
this
is
the
manual
test
execution
complete
for
one
100
highlights
there
is
that
and
we
actually
cuted
602
tests
and
a
very
good
pass
rate
as
we
can
see
our
totals
on
the
bottom
16
field,
22
skip
4
block
and
all
of
that
sort
of
an
investigation
and
progress.
N
Closing
some
things
all
right.
Making
test
updates
so
obviously
we
want
that
number
to
be.
You
know
full
pass
and
but
it's
still
a
good
result
and
we're
dealing
with
the
failures
that
came
out
of
it
and
then
we'll
have
updates
as
we
go
forward,
hopefully
bringing
these
numbers
down,
but
that
was
a
very
brief
quality
update
as
per
usual.
This
will
be
in
the
community
weekly
and
any
questions
about
any
of
this
testing
could
come
straight
to
me,
nope
that
was
pretty
fun
I
for
you,
Igor.