Dynamics 365 Intelligent Order Management - Simply Explained

1
00:00:00,000 --> 00:00:04,080
When a customer clicks buy on your website, the item they want could be sitting in a warehouse,

2
00:00:04,080 --> 00:00:06,760
a store or a cross-town, or with a delivery partner.

3
00:00:06,760 --> 00:00:11,120
All the customer really expects though are two things, a clear promise and a package at their door.

4
00:00:11,120 --> 00:00:14,640
Welcome to another episode of Microsoft Knowledge Nuggets on M365.

5
00:00:14,640 --> 00:00:19,880
FM, I'm Murcopitas and today we're looking at Dynamics 365 Intelligent Order Management in plain English.

6
00:00:19,880 --> 00:00:24,000
We'll follow that order from the checkout click through to the work that actually gets it delivered.

7
00:00:24,000 --> 00:00:27,160
Think of it as the central dispatch desk in a busy office building.

8
00:00:27,160 --> 00:00:29,640
It isn't another online shop and it doesn't pack the box.

9
00:00:29,640 --> 00:00:33,040
It just directs the right people in systems so the work happens in the right place.

10
00:00:33,040 --> 00:00:34,840
Yes, though.

11
00:00:34,840 --> 00:00:37,360
By orders become messy.

12
00:00:37,360 --> 00:00:41,160
Imagine you sell the same headphones through your website, your physical stores,

13
00:00:41,160 --> 00:00:43,480
an online marketplace and a call center.

14
00:00:43,480 --> 00:00:46,160
To the customer, those are all just ways to buy headphones.

15
00:00:46,160 --> 00:00:50,320
But behind the scenes, each channel sends order details into a completely different system.

16
00:00:50,320 --> 00:00:53,480
Your website holds one record, the store point of sale holds another,

17
00:00:53,480 --> 00:00:55,400
a marketplace sends its own format,

18
00:00:55,400 --> 00:00:58,880
and a call center agent creates an order somewhere else entirely.

19
00:00:58,880 --> 00:01:03,360
One simple customer promise gets split into several moving parts that don't talk to each other.

20
00:01:03,360 --> 00:01:05,560
And stock adds another layer of complexity.

21
00:01:05,560 --> 00:01:09,000
The main warehouse might have 20 pairs, a store across town has five,

22
00:01:09,000 --> 00:01:13,320
and another warehouse has stock too, but it's farther away with higher shipping costs.

23
00:01:13,320 --> 00:01:17,400
Some stock is already reserved for other orders, returned items or in-store customers.

24
00:01:17,400 --> 00:01:20,880
So seeing a number beside a product doesn't actually settle the problem.

25
00:01:20,880 --> 00:01:22,720
Then you have to decide how to deliver.

26
00:01:22,720 --> 00:01:25,080
Should the warehouse ship it? Should a store ship it?

27
00:01:25,080 --> 00:01:26,680
Or can the customer collect it locally?

28
00:01:26,680 --> 00:01:30,800
And if someone buys two items and no single location has both, do you split the order into two packages

29
00:01:30,800 --> 00:01:32,800
or wait until everything can ship together?

30
00:01:32,800 --> 00:01:36,760
Every choice affects cost, delivery time, and the promise you gave the customer.

31
00:01:36,760 --> 00:01:40,520
Two decades ago, companies ran these jobs in separate systems with separate teams.

32
00:01:40,520 --> 00:01:41,600
Sales took the order.

33
00:01:41,600 --> 00:01:44,040
Someone checked stock, the warehouse got a request.

34
00:01:44,040 --> 00:01:45,840
A shipping partner got another request,

35
00:01:45,840 --> 00:01:47,440
billing dealt with its own part later.

36
00:01:47,440 --> 00:01:50,480
That worked fine when orders were simple and volumes stayed low.

37
00:01:50,480 --> 00:01:53,520
But here's the thing, when updates move slowly between systems,

38
00:01:53,520 --> 00:01:54,880
people start filling the gaps.

39
00:01:54,880 --> 00:01:59,480
A customer service agent checks one screen, emails a warehouse team, then calls a carrier,

40
00:01:59,480 --> 00:02:04,080
and meanwhile, a product can sell through another channel before the stock update reaches the website.

41
00:02:04,080 --> 00:02:06,400
Now you have an order for something you can't send.

42
00:02:06,400 --> 00:02:09,360
That's how overselling happens, and it's also how delivery choices take too long,

43
00:02:09,360 --> 00:02:11,760
teams keep copying details from one place to another,

44
00:02:11,760 --> 00:02:14,520
and customers get vague updates instead of firm answers.

45
00:02:14,520 --> 00:02:17,240
From the customer's side, none of that complexity matters,

46
00:02:17,240 --> 00:02:20,280
because they just ask one question, where's my order?

47
00:02:20,280 --> 00:02:23,440
What a company really needs is one place that can see the order journey

48
00:02:23,440 --> 00:02:25,440
across all those connected business apps,

49
00:02:25,440 --> 00:02:27,800
while each app keeps doing what it does best.

50
00:02:27,800 --> 00:02:31,200
Sales captures the sale, the warehouse manages picking and packing,

51
00:02:31,200 --> 00:02:33,400
shipping handles delivery, billing handles money,

52
00:02:33,400 --> 00:02:35,440
nobody needs to throw every system away.

53
00:02:35,440 --> 00:02:37,960
What's missing is the coordinator between them are,

54
00:02:37,960 --> 00:02:41,080
a place that can receive an order, see what needs to happen next,

55
00:02:41,080 --> 00:02:44,320
and direct work without relying on a chain of manual handoffs.

56
00:02:44,320 --> 00:02:48,960
That's the problem, Dynamics 365 Intelligent Order Management Addresses.

57
00:02:48,960 --> 00:02:50,680
The plain English definition.

58
00:02:50,680 --> 00:02:54,600
So what exactly is Dynamics 365 Intelligent Order Management?

59
00:02:54,600 --> 00:02:58,760
You, Timur, Mirko Peters, and today we are going to break it down in plain English.

60
00:02:58,760 --> 00:03:00,160
Here's the simplest definition.

61
00:03:00,160 --> 00:03:03,880
It's a cloud app that takes an order and guides it through all the systems.

62
00:03:03,880 --> 00:03:07,440
A company already uses IO from the moment the order arrives

63
00:03:07,440 --> 00:03:09,800
until fulfillment and billing are done.

64
00:03:09,800 --> 00:03:11,440
Think of a busy rail station.

65
00:03:11,440 --> 00:03:13,400
Train's arrived from different directions.

66
00:03:13,400 --> 00:03:14,960
Passengers need different platforms.

67
00:03:14,960 --> 00:03:17,240
Some connections are fast, others have to wait.

68
00:03:17,240 --> 00:03:20,240
Intelligent Order Management works like the station's control room.

69
00:03:20,240 --> 00:03:22,240
It doesn't drive the train or sell the ticket,

70
00:03:22,240 --> 00:03:25,320
but it sees the whole route and tells each system what to do next.

71
00:03:25,320 --> 00:03:28,480
Microsoft built Intelligent Order Management on top of Dataverse.

72
00:03:28,480 --> 00:03:30,320
Dataverse is the shared data foundation

73
00:03:30,320 --> 00:03:33,680
behind many Dynamics 365 and Power Platform apps.

74
00:03:33,680 --> 00:03:36,960
In plain English, it gives business apps one common place

75
00:03:36,960 --> 00:03:39,080
and one common format for storing information.

76
00:03:39,080 --> 00:03:41,600
That means an order doesn't mean something completely different

77
00:03:41,600 --> 00:03:43,160
in every screen and system.

78
00:03:43,160 --> 00:03:44,720
Now that shared foundation helps,

79
00:03:44,720 --> 00:03:49,000
but you don't need to buy every other Dynamics 365 app to use Intelligent Order Management.

80
00:03:49,000 --> 00:03:52,880
A company might run Dynamics 365 Finance or Supply Chain Management.

81
00:03:52,880 --> 00:03:55,080
Another might use a different warehouse system,

82
00:03:55,080 --> 00:03:58,520
a different online store or a shipping service from another vendor.

83
00:03:58,520 --> 00:04:02,040
This app can work with both Microsoft and non-Microsoft Business Apps.

84
00:04:02,040 --> 00:04:03,720
The connection points are called providers.

85
00:04:03,720 --> 00:04:06,160
A provider moves order and fulfillment information

86
00:04:06,160 --> 00:04:08,960
between Intelligent Order Management and another system.

87
00:04:08,960 --> 00:04:11,000
Think of a provider as a translator at the door.

88
00:04:11,000 --> 00:04:12,960
One system sends an order in its own format.

89
00:04:12,960 --> 00:04:14,760
The provider understands that format,

90
00:04:14,760 --> 00:04:17,320
passes the information into Intelligent Order Management,

91
00:04:17,320 --> 00:04:20,960
and can send the next request back out in a format the other system understands.

92
00:04:20,960 --> 00:04:23,080
So the app brings order information together

93
00:04:23,080 --> 00:04:24,920
even when the order started somewhere else.

94
00:04:24,920 --> 00:04:27,400
A customer might buy through an AL Commerce site,

95
00:04:27,400 --> 00:04:30,160
another might place an order through a point of sale system.

96
00:04:30,160 --> 00:04:34,080
A business customer could send an electronic order through a B2B process.

97
00:04:34,080 --> 00:04:37,440
Intelligent Order Management gives the company one place to view those orders

98
00:04:37,440 --> 00:04:39,760
and see where each one sits in fulfillment.

99
00:04:39,760 --> 00:04:41,720
Not every order follows the same path.

100
00:04:41,720 --> 00:04:42,960
One may wait for stock,

101
00:04:42,960 --> 00:04:44,760
another may already sit with a warehouse.

102
00:04:44,760 --> 00:04:47,160
A third might need a billing step after delivery.

103
00:04:47,160 --> 00:04:48,280
The app tracks that state,

104
00:04:48,280 --> 00:04:51,440
so a team sees more than just order received.

105
00:04:51,440 --> 00:04:53,920
They can see exactly where the order is in its journey.

106
00:04:53,920 --> 00:04:56,160
Here's the part people sometimes miss.

107
00:04:56,160 --> 00:04:59,080
Intelligent Order Management doesn't take over every job.

108
00:04:59,080 --> 00:05:01,720
It doesn't suddenly become the warehouse workers picking screen,

109
00:05:01,720 --> 00:05:03,360
the carriers delivery network,

110
00:05:03,360 --> 00:05:05,320
or the finance team's billing system.

111
00:05:05,320 --> 00:05:07,840
Those connected apps still do their specialist work.

112
00:05:07,840 --> 00:05:10,880
Intelligent Order Management directs the handoffs between them.

113
00:05:10,880 --> 00:05:14,200
It receives the request, checks the route, passes the work along,

114
00:05:14,200 --> 00:05:16,120
and then watches for the next update.

115
00:05:16,120 --> 00:05:17,880
Now let's follow one order through that route,

116
00:05:17,880 --> 00:05:21,880
because the order journey makes the whole idea much easier to see.

117
00:05:21,880 --> 00:05:24,600
The order journey rules that direct the work.

118
00:05:24,600 --> 00:05:28,680
Imagine a customer orders two items from your website late in the afternoon,

119
00:05:28,680 --> 00:05:31,280
and they want both items delivered tomorrow.

120
00:05:31,280 --> 00:05:32,880
The online store captures the order,

121
00:05:32,880 --> 00:05:36,960
"Ow customer name, delivery address, the two order lines, and the delivery choice."

122
00:05:36,960 --> 00:05:39,680
A provider brings that order into Intelligent Order Management

123
00:05:39,680 --> 00:05:41,200
and the order journey can begin.

124
00:05:41,200 --> 00:05:42,880
Before anyone tries to fulfill it,

125
00:05:42,880 --> 00:05:44,400
the system validates the order

126
00:05:44,400 --> 00:05:47,080
to make sure all the information needed for the journey is there

127
00:05:47,080 --> 00:05:49,080
and follows the company's rules.

128
00:05:49,080 --> 00:05:51,520
It checks the order header for customer and delivery details,

129
00:05:51,520 --> 00:05:53,600
it checks each line for product and quantity,

130
00:05:53,600 --> 00:05:56,280
it confirms the address has enough information for delivery,

131
00:05:56,280 --> 00:05:59,280
and it makes sure the order meets the rules for that sales channel.

132
00:05:59,280 --> 00:06:02,360
That first check stops bad information from moving downstream

133
00:06:02,360 --> 00:06:03,880
before it causes problems.

134
00:06:03,880 --> 00:06:06,160
Imagine an order with a missing apartment number.

135
00:06:06,160 --> 00:06:08,400
If it goes straight to a warehouse and then to a carrier,

136
00:06:08,400 --> 00:06:11,720
someone might only spot the problem after a package can't be delivered.

137
00:06:11,720 --> 00:06:14,080
A validation step catches the issue earlier,

138
00:06:14,080 --> 00:06:17,160
while there's still time to contact the customer or hold the order.

139
00:06:17,160 --> 00:06:19,920
The route for this work lives in an orchestration flow.

140
00:06:19,920 --> 00:06:22,120
That phrase sounds technical, but it's simple.

141
00:06:22,120 --> 00:06:24,040
An orchestration flow is a visual map

142
00:06:24,040 --> 00:06:26,760
that tells Intelligent Order Management what should happen

143
00:06:26,760 --> 00:06:30,320
as order information arrives and events come back from connected systems.

144
00:06:30,320 --> 00:06:32,840
You create that map around your own business process.

145
00:06:32,840 --> 00:06:35,480
A basic order flow might start when a new order arrives.

146
00:06:35,480 --> 00:06:37,080
It validates the header and lines,

147
00:06:37,080 --> 00:06:39,240
it sends the order for fulfillment decisions.

148
00:06:39,240 --> 00:06:42,520
After that, it sends the fulfillment order to the right connected system.

149
00:06:42,520 --> 00:06:44,280
Once the work reaches the right stage,

150
00:06:44,280 --> 00:06:46,600
it can send order information to a billing provider.

151
00:06:46,600 --> 00:06:48,040
Each action has a clear job.

152
00:06:48,040 --> 00:06:50,760
Validate order header checks the main order details.

153
00:06:50,760 --> 00:06:54,120
Validate order line checks the individual products and quantities.

154
00:06:54,120 --> 00:06:56,600
Center fulfillment passes the fulfillment order

155
00:06:56,600 --> 00:06:58,720
to the provider that handles that work.

156
00:06:58,720 --> 00:07:01,600
Send to invoice passes order information to the billing provider.

157
00:07:01,600 --> 00:07:04,200
The name sound like labels on a factory control panel,

158
00:07:04,200 --> 00:07:07,120
and that's useful because each label tells you exactly what happens

159
00:07:07,120 --> 00:07:08,520
at that point in the flow,

160
00:07:08,520 --> 00:07:11,560
but a real business often needs more than one straight line.

161
00:07:11,560 --> 00:07:14,120
Maybe orders from the website follow one path,

162
00:07:14,120 --> 00:07:16,160
while business customers follow another.

163
00:07:16,160 --> 00:07:18,200
Maybe one type of product needs a special approval.

164
00:07:18,200 --> 00:07:21,200
Maybe an order can move forward only if the first steps succeeds.

165
00:07:21,200 --> 00:07:24,240
Intelligent Order Management includes conditions for that kind of choice.

166
00:07:24,240 --> 00:07:26,840
A condition creates a yes path and a no path.

167
00:07:26,840 --> 00:07:28,320
If the earlier action succeeds,

168
00:07:28,320 --> 00:07:30,640
the order can continue through the yes path.

169
00:07:30,640 --> 00:07:33,640
If it fails, the flow can direct the order to a different path.

170
00:07:33,640 --> 00:07:35,680
That doesn't fix every problem by itself,

171
00:07:35,680 --> 00:07:37,680
but it gives the process a planned response

172
00:07:37,680 --> 00:07:40,760
instead of leaving a team to discover an error by chance.

173
00:07:40,760 --> 00:07:42,160
There are also splitters.

174
00:07:42,160 --> 00:07:45,560
A splitter sends the flow into more than one path based on rules you define.

175
00:07:45,560 --> 00:07:48,960
You might use one when orders from separate sources need different checks

176
00:07:48,960 --> 00:07:51,520
or when different parts of the work need different routes.

177
00:07:51,520 --> 00:07:53,480
Some split paths can come back together later,

178
00:07:53,480 --> 00:07:55,240
while others continue on their own.

179
00:07:55,240 --> 00:07:58,080
Custom actions cover the jobs unique to a business.

180
00:07:58,080 --> 00:08:00,360
Perhaps the company has its own manufacturing system

181
00:08:00,360 --> 00:08:03,080
or a partner system that isn't covered by a standard action.

182
00:08:03,080 --> 00:08:05,760
A custom action can connect that step into the order flow,

183
00:08:05,760 --> 00:08:07,480
so the route still shows the full process

184
00:08:07,480 --> 00:08:09,880
instead of hiding one part in emails or manual work.

185
00:08:09,880 --> 00:08:11,520
Let's return to our two item order.

186
00:08:11,520 --> 00:08:13,120
The system receives it from the website

187
00:08:13,120 --> 00:08:15,960
and checks the customer details, address and product lines.

188
00:08:15,960 --> 00:08:18,720
The order then reaches the fulfillment decision step.

189
00:08:18,720 --> 00:08:20,800
If both items can follow the same route,

190
00:08:20,800 --> 00:08:24,160
the flow can send the fulfillment request onward as one unit.

191
00:08:24,160 --> 00:08:26,440
If the company's rules require a different outcome,

192
00:08:26,440 --> 00:08:27,760
the order can take another path.

193
00:08:27,760 --> 00:08:30,480
Maybe the two items need separate fulfillment requests.

194
00:08:30,480 --> 00:08:32,480
Maybe the order needs a different delivery choice.

195
00:08:32,480 --> 00:08:33,520
The flow doesn't guess.

196
00:08:33,520 --> 00:08:35,360
It follows the rules, the business created

197
00:08:35,360 --> 00:08:37,840
and the events that connected systems return.

198
00:08:37,840 --> 00:08:39,040
That last part matters.

199
00:08:39,040 --> 00:08:41,200
Intelligent order management can direct work,

200
00:08:41,200 --> 00:08:44,280
but the connected systems report back as work moves forward.

201
00:08:44,280 --> 00:08:46,720
A fulfillment provider can receive the request.

202
00:08:46,720 --> 00:08:49,360
A billing provider can receive the order details.

203
00:08:49,360 --> 00:08:52,240
Those events keep the order journey moving through the flow,

204
00:08:52,240 --> 00:08:54,800
so the app isn't one giant replacement system.

205
00:08:54,800 --> 00:08:57,080
It's a set of rules that connect specialists

206
00:08:57,080 --> 00:08:59,680
giving each system the work it needs at the right time.

207
00:08:59,680 --> 00:09:01,360
The online store captures the order.

208
00:09:01,360 --> 00:09:03,160
The fulfillment system handles fulfillment.

209
00:09:03,160 --> 00:09:05,000
The billing system handles billing.

210
00:09:05,000 --> 00:09:07,040
Intelligent order management manages the route

211
00:09:07,040 --> 00:09:08,040
between those jobs.

212
00:09:08,040 --> 00:09:10,080
People responsible for the order process

213
00:09:10,080 --> 00:09:12,240
can design these flows directly in the app.

214
00:09:12,240 --> 00:09:14,920
They don't need to write every path as traditional code

215
00:09:14,920 --> 00:09:17,240
and they don't need to ask an IT administrator

216
00:09:17,240 --> 00:09:19,000
to change every business rule.

217
00:09:19,000 --> 00:09:20,520
That gives the supply chain team a way

218
00:09:20,520 --> 00:09:22,400
to model the process they actually need.

219
00:09:22,400 --> 00:09:23,960
Still, those changes need care.

220
00:09:23,960 --> 00:09:26,000
An orchestration flow stays unpublished

221
00:09:26,000 --> 00:09:27,600
while you're building and testing it.

222
00:09:27,600 --> 00:09:30,680
During that stage, incoming data doesn't run through the flow.

223
00:09:30,680 --> 00:09:32,800
Once you publish it, the flow and its actions

224
00:09:32,800 --> 00:09:34,800
run when data enters the system.

225
00:09:34,800 --> 00:09:37,800
After publishing, you can't edit that published flow directly.

226
00:09:37,800 --> 00:09:39,240
If the business needs a change,

227
00:09:39,240 --> 00:09:41,120
the team can stop the published flow,

228
00:09:41,120 --> 00:09:43,080
which returns it to an unpublished state.

229
00:09:43,080 --> 00:09:45,080
They can edit the flow, then publish the new version

230
00:09:45,080 --> 00:09:46,040
when it's ready.

231
00:09:46,040 --> 00:09:48,160
That setup pushes teams to test the route

232
00:09:48,160 --> 00:09:50,000
before live orders travel through it.

233
00:09:50,000 --> 00:09:53,000
A route only works if it knows what stock is actually available.

234
00:09:53,000 --> 00:09:55,000
That takes us to the live inventory information

235
00:09:55,000 --> 00:09:56,640
behind each fulfillment decision.

236
00:09:56,640 --> 00:09:59,160
Inventory visibility.

237
00:09:59,160 --> 00:10:01,560
Seeing what you can actually sell.

238
00:10:01,560 --> 00:10:03,000
Here's a plain English truth.

239
00:10:03,000 --> 00:10:05,720
You can't fulfill an order if you don't know you have the stock.

240
00:10:05,720 --> 00:10:08,480
Sounds obvious, but stock can hide in a warehouse, a store,

241
00:10:08,480 --> 00:10:11,040
a partner location, or across different legal entities

242
00:10:11,040 --> 00:10:12,080
inside the same company.

243
00:10:12,080 --> 00:10:13,960
When each location keeps its own count,

244
00:10:13,960 --> 00:10:15,600
you can't answer the basic question.

245
00:10:15,600 --> 00:10:17,520
What can I promise this customer right now?

246
00:10:17,520 --> 00:10:19,800
Inventory visibility gives intelligent order management

247
00:10:19,800 --> 00:10:22,360
a live view of all that stock across your supply network.

248
00:10:22,360 --> 00:10:24,920
Think of it like a stock board in a distribution center.

249
00:10:24,920 --> 00:10:27,520
Instead of calling every shelf and asking someone to check,

250
00:10:27,520 --> 00:10:29,400
the order process looks at one shared view

251
00:10:29,400 --> 00:10:31,080
that all your systems feed into.

252
00:10:31,080 --> 00:10:33,480
Now, just because an item shows up as stock somewhere

253
00:10:33,480 --> 00:10:35,600
doesn't mean it can fulfill every order.

254
00:10:35,600 --> 00:10:38,040
A product might sit in a warehouse but already be reserved

255
00:10:38,040 --> 00:10:40,840
or it sits in a store that can sell locally but can't ship

256
00:10:40,840 --> 00:10:43,080
or it's simply too far away to meet the delivery promise

257
00:10:43,080 --> 00:10:44,360
the customer selected.

258
00:10:44,360 --> 00:10:47,200
There's a big difference between stock that exists somewhere

259
00:10:47,200 --> 00:10:49,520
and stock that can fulfill this order right now.

260
00:10:49,520 --> 00:10:51,520
Imagine a customer bought a jacket online

261
00:10:51,520 --> 00:10:52,840
and wants it tomorrow.

262
00:10:52,840 --> 00:10:54,600
Your main warehouse has none left.

263
00:10:54,600 --> 00:10:56,800
Without current inventory data, your website

264
00:10:56,800 --> 00:10:59,240
might still accept the order based on an old number

265
00:10:59,240 --> 00:11:01,200
and the warehouse then gets a request for something

266
00:11:01,200 --> 00:11:03,120
it can't send, leaving the customer

267
00:11:03,120 --> 00:11:04,640
to find out after checkout.

268
00:11:04,640 --> 00:11:07,200
That creates work for everyone with connected inventory

269
00:11:07,200 --> 00:11:08,040
information.

270
00:11:08,040 --> 00:11:10,480
Intelligent order management sees that the main warehouse

271
00:11:10,480 --> 00:11:13,520
has no jacket for this order but a nearby store does.

272
00:11:13,520 --> 00:11:15,920
If that store supports shipping, it can fulfill the order.

273
00:11:15,920 --> 00:11:17,280
If the customer chose collection,

274
00:11:17,280 --> 00:11:19,480
that same store becomes the pickup location.

275
00:11:19,480 --> 00:11:21,920
The decision starts with a better view of stock.

276
00:11:21,920 --> 00:11:23,760
For a company with several legal entities,

277
00:11:23,760 --> 00:11:26,320
this view covers inventory across all of them.

278
00:11:26,320 --> 00:11:28,440
That matters when you operate in more than one country,

279
00:11:28,440 --> 00:11:30,560
region or business unit and stock doesn't live

280
00:11:30,560 --> 00:11:32,040
under just one set of records.

281
00:11:32,040 --> 00:11:34,360
The order process uses real-time inventory data

282
00:11:34,360 --> 00:11:36,240
as it decides what path to take.

283
00:11:36,240 --> 00:11:38,480
A warehouse, store or other inventory source

284
00:11:38,480 --> 00:11:40,960
still manages its own stock records.

285
00:11:40,960 --> 00:11:43,160
Inventory visibility brings the current numbers

286
00:11:43,160 --> 00:11:45,720
into the wider order process, where the fulfillment rules

287
00:11:45,720 --> 00:11:46,680
can use them.

288
00:11:46,680 --> 00:11:49,200
That helps you avoid promises based on yesterday's data

289
00:11:49,200 --> 00:11:51,880
and gives customer service a clear answer when someone asks

290
00:11:51,880 --> 00:11:54,200
whether an item can still arrive on time.

291
00:11:54,200 --> 00:11:55,600
Instead of searching several systems

292
00:11:55,600 --> 00:11:57,240
and hoping the information matches,

293
00:11:57,240 --> 00:11:58,880
the order team sees the stock position

294
00:11:58,880 --> 00:12:00,440
that drove the fulfillment choice.

295
00:12:00,440 --> 00:12:02,480
Of course, seeing all possible locations

296
00:12:02,480 --> 00:12:03,920
doesn't answer every question.

297
00:12:03,920 --> 00:12:06,120
You might find the item in five locations,

298
00:12:06,120 --> 00:12:09,000
one closest to the customer, another with more stock,

299
00:12:09,000 --> 00:12:11,400
a third that lets you ship both products together,

300
00:12:11,400 --> 00:12:13,160
someone or something still needs to choose.

301
00:12:13,160 --> 00:12:16,080
That job belongs to fulfillment optimization.

302
00:12:16,080 --> 00:12:20,080
Fulfillment.

303
00:12:20,080 --> 00:12:24,840
Optimization choosing the best place to ship from fulfillment.

304
00:12:24,840 --> 00:12:27,360
Optimization compares the possible locations for an order

305
00:12:27,360 --> 00:12:30,200
and selects one based on rules your company sets.

306
00:12:30,200 --> 00:12:33,640
In plain English it answers, where should this order come from?

307
00:12:33,640 --> 00:12:35,440
Best doesn't always mean closest.

308
00:12:35,440 --> 00:12:37,120
The nearest store might have the item,

309
00:12:37,120 --> 00:12:38,920
but shipping from there could cost more.

310
00:12:38,920 --> 00:12:41,440
A warehouse farther away may already have both items ready

311
00:12:41,440 --> 00:12:43,840
to pack together and another location may have stock

312
00:12:43,840 --> 00:12:46,040
but can't meet the delivery date the customer chose.

313
00:12:46,040 --> 00:12:49,080
Every company has to decide what it wants the rules to favor.

314
00:12:49,080 --> 00:12:51,200
Some businesses put delivery speed first.

315
00:12:51,200 --> 00:12:53,200
Others want to keep shipping costs down.

316
00:12:53,200 --> 00:12:55,600
A company may also want to protect store stock for customers

317
00:12:55,600 --> 00:12:58,800
walking in or avoid splitting an order into several packages

318
00:12:58,800 --> 00:13:00,600
unless there's no other choice.

319
00:13:00,600 --> 00:13:03,360
Intelligent order management uses fulfillment strategies

320
00:13:03,360 --> 00:13:04,760
that reflect those choices.

321
00:13:04,760 --> 00:13:07,000
Think of it like choosing a route for a delivery van.

322
00:13:07,000 --> 00:13:08,800
The shortest road may not be the fastest

323
00:13:08,800 --> 00:13:10,400
because there could be traffic, roadwork,

324
00:13:10,400 --> 00:13:11,760
or a stop that takes longer.

325
00:13:11,760 --> 00:13:14,040
In the same way, the nearest building may not give

326
00:13:14,040 --> 00:13:17,720
the best fulfillment result once stock, cost, service promises

327
00:13:17,720 --> 00:13:19,880
and delivery options come into the picture.

328
00:13:19,880 --> 00:13:22,680
Let's go back to the customer who bought two items online.

329
00:13:22,680 --> 00:13:24,840
A store 10 minutes away has the first item.

330
00:13:24,840 --> 00:13:27,520
The warehouse has both items but sits farther away.

331
00:13:27,520 --> 00:13:30,960
If the store ships the first item and the warehouse ships

332
00:13:30,960 --> 00:13:33,240
the second, the customer might get two packages.

333
00:13:33,240 --> 00:13:36,160
That could meet the delivery date, but it also raises shipping costs.

334
00:13:36,160 --> 00:13:38,680
The warehouse may be able to send both items together.

335
00:13:38,680 --> 00:13:40,760
If it can still hit the promised delivery date,

336
00:13:40,760 --> 00:13:43,360
a single package from that location may be the better choice.

337
00:13:43,360 --> 00:13:46,360
The rule can favor fewer shipments and lower shipping costs.

338
00:13:46,360 --> 00:13:49,920
But if tomorrow's delivery matters more than shipping both items together,

339
00:13:49,920 --> 00:13:53,320
the system may choose the store for one item and the warehouse for the other.

340
00:13:53,320 --> 00:13:54,080
That's a split order.

341
00:13:54,080 --> 00:13:56,280
A split order doesn't mean the system failed.

342
00:13:56,280 --> 00:13:58,640
It can be the planned choice when no single location

343
00:13:58,640 --> 00:14:00,840
can fulfill the whole order the right way.

344
00:14:00,840 --> 00:14:02,880
The business decides when splitting makes sense

345
00:14:02,880 --> 00:14:05,040
through the full-filment strategy it sets.

346
00:14:05,040 --> 00:14:07,760
The same thinking supports buy-on-line, ship from store.

347
00:14:07,760 --> 00:14:09,520
A customer places an order on a website,

348
00:14:09,520 --> 00:14:12,640
but a store near them has the right stock and can send it fast.

349
00:14:12,640 --> 00:14:14,640
So that store becomes the fulfillment source,

350
00:14:14,640 --> 00:14:16,480
even though the customer never visited it.

351
00:14:16,480 --> 00:14:19,440
It also supports buy-on-line, collect-in-store.

352
00:14:19,440 --> 00:14:21,560
The system uses stock and location information

353
00:14:21,560 --> 00:14:24,560
to find a store that can fulfill the order for collection

354
00:14:24,560 --> 00:14:26,960
and the customer gets a local pickup choice

355
00:14:26,960 --> 00:14:30,640
while the company directs the order to the right place.

356
00:14:30,640 --> 00:14:34,360
These choices don't have to sit separately inside every sales channel.

357
00:14:34,360 --> 00:14:36,600
Without a shared fulfillment decision process,

358
00:14:36,600 --> 00:14:38,800
a website, marketplace and call center

359
00:14:38,800 --> 00:14:40,920
may each need their own routing rules.

360
00:14:40,920 --> 00:14:43,080
When the business changes its shipping policy

361
00:14:43,080 --> 00:14:45,160
or starts using stores for fulfillment,

362
00:14:45,160 --> 00:14:47,360
teams may need to update several systems.

363
00:14:47,360 --> 00:14:51,280
Fulfillment optimization puts that decision process in one place within the order journey.

364
00:14:51,280 --> 00:14:52,920
The website keeps taking orders,

365
00:14:52,920 --> 00:14:54,440
the marketplace keeps taking orders,

366
00:14:54,440 --> 00:14:56,320
and the store keeps selling products.

367
00:14:56,320 --> 00:14:59,240
But the company can change how it selects a fulfillment location

368
00:14:59,240 --> 00:15:01,400
without rebuilding rules inside every channel,

369
00:15:01,400 --> 00:15:03,240
giving you more control when stock moves,

370
00:15:03,240 --> 00:15:04,720
delivery promises change,

371
00:15:04,720 --> 00:15:07,320
or a new fulfillment option becomes available.

372
00:15:07,320 --> 00:15:10,480
Still, the fulfillment strategy can only compare locations

373
00:15:10,480 --> 00:15:13,400
if the needed information arrives from the systems that own it.

374
00:15:13,400 --> 00:15:16,240
Or does need to come in, stock updates need to arrive,

375
00:15:16,240 --> 00:15:19,720
and fulfillment partners need to receive their work and report progress back.

376
00:15:19,720 --> 00:15:23,000
That connection work depends on providers.

377
00:15:23,000 --> 00:15:26,320
Providers and connections, the doors into the building.

378
00:15:26,320 --> 00:15:28,560
For intelligent order management to do its job,

379
00:15:28,560 --> 00:15:31,240
it needs a reliable way to talk to everything around it.

380
00:15:31,240 --> 00:15:32,760
Providers are what make that happen.

381
00:15:32,760 --> 00:15:35,640
A provider is basically a connection that moves order details

382
00:15:35,640 --> 00:15:39,440
and fulfillment updates between intelligent order management and another system.

383
00:15:39,440 --> 00:15:43,240
Information flows both ways, so nobody has to copy anything by hand.

384
00:15:43,240 --> 00:15:45,160
Picture a building with many delivery doors.

385
00:15:45,160 --> 00:15:47,680
One door receives orders from your online store,

386
00:15:47,680 --> 00:15:49,840
another connects to your inventory system,

387
00:15:49,840 --> 00:15:52,760
a third sense work to a warehouse or a delivery partner.

388
00:15:52,760 --> 00:15:54,280
Each door has a clear purpose

389
00:15:54,280 --> 00:15:57,400
and providers manage the information passing through each one.

390
00:15:57,400 --> 00:15:59,760
Microsoft builds some of these connectors themselves.

391
00:15:59,760 --> 00:16:01,880
How they call them first party providers.

392
00:16:01,880 --> 00:16:05,120
They connect intelligent order management with apps like Dynamics 365,

393
00:16:05,120 --> 00:16:07,960
Supply Chain Management, Dynamics 365 Commerce,

394
00:16:07,960 --> 00:16:09,960
or Dynamics 365 Finance.

395
00:16:09,960 --> 00:16:13,600
The inventory and fulfillment services inside intelligent order management

396
00:16:13,600 --> 00:16:16,000
also use these providers to exchange data.

397
00:16:16,000 --> 00:16:18,000
Now, you probably have other systems already.

398
00:16:18,000 --> 00:16:19,800
That's where third party providers come in.

399
00:16:19,800 --> 00:16:21,760
They connect services that Microsoft doesn't build.

400
00:16:21,760 --> 00:16:23,800
Maybe it's your existing e-commerce platform,

401
00:16:23,800 --> 00:16:26,600
a marketplace, a logistics company or a warehouse system.

402
00:16:26,600 --> 00:16:29,160
The point isn't to force you into one set of apps, are you?

403
00:16:29,160 --> 00:16:31,960
It's to let you connect the systems that already fit your business.

404
00:16:31,960 --> 00:16:35,600
Behind the scenes, these providers use power automate connectors.

405
00:16:35,600 --> 00:16:38,760
Power Platform has over 200 pre-built connectors,

406
00:16:38,760 --> 00:16:40,440
so you've got plenty of starting points.

407
00:16:40,440 --> 00:16:44,080
And if none of those fit, you or your partner can build your own provider.

408
00:16:44,080 --> 00:16:46,040
Each connected app still does its own job.

409
00:16:46,040 --> 00:16:48,040
Your online store captures the purchase.

410
00:16:48,040 --> 00:16:49,920
The inventory system tracks stock.

411
00:16:49,920 --> 00:16:52,200
A fulfillment partner packs and delivers the order.

412
00:16:52,200 --> 00:16:54,160
A billing system handles the finances.

413
00:16:54,160 --> 00:16:58,160
Intelligent order management coordinates the messages and next steps between all of them.

414
00:16:58,160 --> 00:16:59,760
Once those systems share updates,

415
00:16:59,760 --> 00:17:02,760
your business can see what's happening across the entire order process.

416
00:17:02,760 --> 00:17:05,760
No more chasing information through separate screens?

417
00:17:05,760 --> 00:17:09,160
Insights and the bigger picture.

418
00:17:09,160 --> 00:17:12,560
That shared information gives you a much clearer picture of your order work.

419
00:17:12,560 --> 00:17:15,560
Intelligent order management includes power BI dashboards

420
00:17:15,560 --> 00:17:18,160
that bring order and fulfillment metrics into one place.

421
00:17:18,160 --> 00:17:20,760
Customer service can find orders that have stopped moving.

422
00:17:20,760 --> 00:17:23,760
Operations can spot blocked routes or fulfillment delays.

423
00:17:23,760 --> 00:17:26,760
And business leaders can look for patterns across the entire process.

424
00:17:26,760 --> 00:17:29,960
Without that view, a delay might seem like an isolated problem.

425
00:17:29,960 --> 00:17:33,960
But when the data is together, your team may notice that many orders slow down

426
00:17:33,960 --> 00:17:35,760
at a specific fulfillment partner.

427
00:17:35,760 --> 00:17:38,960
Or that a certain delivery option creates more exceptions than expected.

428
00:17:38,960 --> 00:17:40,960
The dashboard doesn't fix the issue by itself,

429
00:17:40,960 --> 00:17:43,360
but it helps people know exactly where to look.

430
00:17:43,360 --> 00:17:44,960
Think back to the office building.

431
00:17:44,960 --> 00:17:48,560
Intelligent order management brings together the front desk that receives requests,

432
00:17:48,560 --> 00:17:50,560
the stockboard that shows what's available,

433
00:17:50,560 --> 00:17:53,160
the root planner that chooses a fulfillment location,

434
00:17:53,160 --> 00:17:56,360
and the reporting room where teams can see how everything is moving.

435
00:17:56,360 --> 00:17:59,360
Each part has a different job, but the order connects them all.

436
00:17:59,360 --> 00:18:02,160
Conclusion.

437
00:18:02,160 --> 00:18:04,560
One order, one coordinated journey.

438
00:18:04,560 --> 00:18:06,560
Thanks for joining me for this knowledge nugget.

439
00:18:06,560 --> 00:18:10,760
Intelligent order management maps a single direct root through your entire process,

440
00:18:10,760 --> 00:18:12,560
from initial capture to final billing.

441
00:18:12,560 --> 00:18:15,560
Subscribe on your favorite podcast platform and watch the next episode.

442
00:18:15,560 --> 00:18:18,360
You'll see exactly how Dynamics 365 and Power Platform

443
00:18:18,360 --> 00:18:19,960
handle the work behind the screens.