Dynamics 365 Transportation Management - Simply Explained

1
00:00:00,000 --> 00:00:04,200
Hello and welcome to another episode of Microsoft Knowledge Nuggets here on M365FM.

2
00:00:04,200 --> 00:00:05,840
I'm your host, Mirko Peters.

3
00:00:05,840 --> 00:00:09,600
Today's topic is one that almost everyone who works with supply chains has heard of,

4
00:00:09,600 --> 00:00:11,360
but few people truly understand.

5
00:00:11,360 --> 00:00:13,720
Dynamics 365 Transportation Management.

6
00:00:13,720 --> 00:00:14,400
Here's the problem.

7
00:00:14,400 --> 00:00:18,560
A customer places an order, stocks sits in the warehouse, a carrier needs a pick-up time,

8
00:00:18,560 --> 00:00:22,520
the customer expects delivery, and later a freight bill lands on someone's desk.

9
00:00:22,520 --> 00:00:25,360
For years, those steps lived in separate spreadsheets, phone calls,

10
00:00:25,360 --> 00:00:28,840
rate sheets, and handoffs between teams out, and that creates gaps.

11
00:00:28,840 --> 00:00:31,720
The warehouse might prepare goods before transport has a plan.

12
00:00:31,720 --> 00:00:34,600
Finance might see a bill without knowing what anyone agreed to pay.

13
00:00:34,600 --> 00:00:36,720
So what exactly is transportation management?

14
00:00:36,720 --> 00:00:41,840
In plain English, it's the transportation desk inside Dynamics 365 Supply Chain Management.

15
00:00:41,840 --> 00:00:44,720
It connects warehouse doors, vendors, customers, and carriers.

16
00:00:44,720 --> 00:00:48,480
Will plan loads, choose routes and rates, ship goods, and check freight charges?

17
00:00:48,480 --> 00:00:52,280
By the end of this episode, you'll see how all these pieces fit together to make your work

18
00:00:52,280 --> 00:00:55,880
life easier.

19
00:00:55,880 --> 00:00:58,760
Why transportation management exists?

20
00:00:58,760 --> 00:01:00,880
Let's start with the basic truth.

21
00:01:00,880 --> 00:01:04,280
Physical goods don't move just because a sales order exists on the screen.

22
00:01:04,280 --> 00:01:07,960
They need a truck, a trailer, a container, or another way to travel.

23
00:01:07,960 --> 00:01:11,600
Someone needs to know where the goods start, where they need to arrive, how much space

24
00:01:11,600 --> 00:01:14,640
they take up, when they need to leave, and what the trip should cost.

25
00:01:14,640 --> 00:01:18,000
Now when you picture one box going to one customer, it sounds simple.

26
00:01:18,000 --> 00:01:22,000
But a real company might send many orders from the same warehouse on the same day, receive

27
00:01:22,000 --> 00:01:26,760
goods from several vendors and move stock between its own sites at the same time.

28
00:01:26,760 --> 00:01:30,480
Each movement has people, dates, space, and money attached to it.

29
00:01:30,480 --> 00:01:33,840
Without a shared system, each team sees only its own piece.

30
00:01:33,840 --> 00:01:35,520
Sales sees the customer order.

31
00:01:35,520 --> 00:01:39,880
Purchasing sees the vendor order, warehouse staff see the items they need to pick, pack,

32
00:01:39,880 --> 00:01:41,200
receive, or put away.

33
00:01:41,200 --> 00:01:44,920
The transport team sees a list of things that must move often after everyone else has

34
00:01:44,920 --> 00:01:45,920
already done their part.

35
00:01:45,920 --> 00:01:47,680
That's where delays and confusion start.

36
00:01:47,680 --> 00:01:49,080
Here's a concrete example.

37
00:01:49,080 --> 00:01:52,560
Imagine a warehouse has 10 customer orders ready for the same city.

38
00:01:52,560 --> 00:01:56,320
If nobody connects those orders before booking transport, the company might arrange several

39
00:01:56,320 --> 00:02:00,160
partly filled trips, or the carrier might arrive before the warehouse knows which goods belong

40
00:02:00,160 --> 00:02:01,160
on the vehicle.

41
00:02:01,160 --> 00:02:03,280
The goods are ready, but the movement isn't planned.

42
00:02:03,280 --> 00:02:07,880
So transportation management gives that movement a place inside Dynamics 365 Supply Chain

43
00:02:07,880 --> 00:02:08,880
Management.

44
00:02:08,880 --> 00:02:12,440
It's not a separate consumer shipping app where you type in a tracking number and watch

45
00:02:12,440 --> 00:02:14,440
a parcel move across a map.

46
00:02:14,440 --> 00:02:18,040
Instead, it works with the business records already inside the connected platform, and

47
00:02:18,040 --> 00:02:20,320
order creates the need for goods to move.

48
00:02:20,320 --> 00:02:22,200
Warehouse work prepares the goods.

49
00:02:22,200 --> 00:02:25,280
Transportation management plans, how those goods travel between locations.

50
00:02:25,280 --> 00:02:28,240
Think of it like the transportation desk in an office building.

51
00:02:28,240 --> 00:02:31,000
The sales team brings a customer request to the desk.

52
00:02:31,000 --> 00:02:34,600
Purchasing brings news that a vendor will send goods in, the warehouse brings the actual

53
00:02:34,600 --> 00:02:36,160
stock and the loading doors.

54
00:02:36,160 --> 00:02:39,960
The transportation desk connects those requests to the company's transport plan.

55
00:02:39,960 --> 00:02:41,320
There are two main directions.

56
00:02:41,320 --> 00:02:44,400
Inbound transportation means goods travel into your business.

57
00:02:44,400 --> 00:02:47,880
You've ordered items from a vendor, and those items need to reach your warehouse.

58
00:02:47,880 --> 00:02:51,160
Sometimes the vendor controls that trip, sometimes your company arranges it, either way

59
00:02:51,160 --> 00:02:54,680
you need a clear plan for getting the goods to the right place and receiving them when

60
00:02:54,680 --> 00:02:55,680
they arrive.

61
00:02:55,680 --> 00:02:58,760
Outbound transportation means goods travel out of your business.

62
00:02:58,760 --> 00:03:03,400
A customer has ordered products, the warehouse prepares them, and a carrier or company vehicle

63
00:03:03,400 --> 00:03:04,800
takes them to the customer.

64
00:03:04,800 --> 00:03:07,640
Both flows deal with movement, but the starting point differs.

65
00:03:07,640 --> 00:03:09,880
Inbound starts with a purchase order and a vendor.

66
00:03:09,880 --> 00:03:12,280
Outbound starts with a sales order and a customer.

67
00:03:12,280 --> 00:03:14,760
There's also a third type that beginners often miss.

68
00:03:14,760 --> 00:03:15,760
Transfer orders.

69
00:03:15,760 --> 00:03:19,360
Transfer order moves stock between your own company locations.

70
00:03:19,360 --> 00:03:22,440
Maybe one warehouse has too much stock and another warehouse needs it.

71
00:03:22,440 --> 00:03:26,320
No customer purchase is involved, but the physical goods still need transport.

72
00:03:26,320 --> 00:03:31,040
In Dynamics 365 Transportation Management, transfer orders belong to the outbound scenario

73
00:03:31,040 --> 00:03:33,240
and can be planned alongside sales orders.

74
00:03:33,240 --> 00:03:35,160
That makes sense when you picture the loading dock.

75
00:03:35,160 --> 00:03:39,720
Oh, whether a pallet travels to a paying customer or to another company warehouse, somebody

76
00:03:39,720 --> 00:03:44,840
still needs to arrange the vehicle, reserve space, and send it out from the same door.

77
00:03:44,840 --> 00:03:48,960
So this connected approach replaces the old chain of separate lists and phone calls

78
00:03:48,960 --> 00:03:50,440
with shared information.

79
00:03:50,440 --> 00:03:54,480
The order tells the system what needs to move, the warehouse prepares the items.

80
00:03:54,480 --> 00:03:57,240
Transportation management turns that need into a transport plan.

81
00:03:57,240 --> 00:04:01,400
Once goods need to move, the system first needs a workable shipping plan.

82
00:04:01,400 --> 00:04:02,400
Planning the load.

83
00:04:02,400 --> 00:04:06,840
Today's knowledge nugget is about something every logistics team needs, but often explains

84
00:04:06,840 --> 00:04:08,360
differently.

85
00:04:08,360 --> 00:04:09,840
Planning a load.

86
00:04:09,840 --> 00:04:13,520
You can start planning transportation from either orders or shipments, or myicopeters

87
00:04:13,520 --> 00:04:16,600
from M365, FM, and let me clear up a myth right away.

88
00:04:16,600 --> 00:04:18,320
A shipping plan doesn't start from scratch.

89
00:04:18,320 --> 00:04:20,000
It starts from records you already have.

90
00:04:20,000 --> 00:04:22,040
A sales order holds what a customer bought.

91
00:04:22,040 --> 00:04:26,240
A purchase order lists, what a vendor needs to send, a shipment groups, those items into

92
00:04:26,240 --> 00:04:29,640
a more focused shipping record, ready to be combined with others.

93
00:04:29,640 --> 00:04:31,440
So which starting point should you use?

94
00:04:31,440 --> 00:04:33,040
That depends on how your company works.

95
00:04:33,040 --> 00:04:36,200
Some teams plan early, looking directly at order lines.

96
00:04:36,200 --> 00:04:39,680
Other teams create shipments first, then decide what travels together.

97
00:04:39,680 --> 00:04:41,320
Both parts lead to the same question.

98
00:04:41,320 --> 00:04:42,800
What should go on the same vehicle?

99
00:04:42,800 --> 00:04:44,120
Here's the simplest definition.

100
00:04:44,120 --> 00:04:47,560
A load is the digital record for a planned movement of goods.

101
00:04:47,560 --> 00:04:51,720
You can picture it as one truck, one trailer, one container, or one collection of shipments

102
00:04:51,720 --> 00:04:52,920
that travel together.

103
00:04:52,920 --> 00:04:57,120
It gives you one place to see which goods belong together before physical work starts.

104
00:04:57,120 --> 00:04:58,920
Now here's something many people get wrong.

105
00:04:58,920 --> 00:05:01,760
A load doesn't mean every item fits inside one physical box.

106
00:05:01,760 --> 00:05:04,720
It means the system groups goods around one transport plan.

107
00:05:04,720 --> 00:05:06,680
Several customer shipments may share one truck.

108
00:05:06,680 --> 00:05:09,240
A large order might fill a whole trailer by itself.

109
00:05:09,240 --> 00:05:12,200
A container arriving from a vendor can also become a load.

110
00:05:12,200 --> 00:05:14,040
Even before your warehouse receives the goods.

111
00:05:14,040 --> 00:05:17,000
The point is to stop treating each order as its own trip.

112
00:05:17,000 --> 00:05:20,600
Imagine a distributor has six customer orders ready for Friday delivery.

113
00:05:20,600 --> 00:05:24,080
All six sit in the same area, and each order fills only part of a truck.

114
00:05:24,080 --> 00:05:28,640
Sending six half empty vehicles, wastes, space, and creates six separate transport jobs.

115
00:05:28,640 --> 00:05:31,360
The team can instead group compatible shipments into one load.

116
00:05:31,360 --> 00:05:34,120
Compatible means they can reasonably travel together.

117
00:05:34,120 --> 00:05:37,880
They leave from the same warehouse, need to go around the same time, fit within vehicle

118
00:05:37,880 --> 00:05:39,960
limits, and follow your shipping rules.

119
00:05:39,960 --> 00:05:43,240
The system helps bring those records together instead of relying on someone to spot the

120
00:05:43,240 --> 00:05:44,480
pattern in a spreadsheet.

121
00:05:44,480 --> 00:05:46,040
That group now has a shared plan.

122
00:05:46,040 --> 00:05:48,160
A warehouse sees what belongs on the load.

123
00:05:48,160 --> 00:05:50,880
The transport planner sees the total space and wait.

124
00:05:50,880 --> 00:05:54,360
People don't need to rebuild the same list in emails, notes, or a separate file.

125
00:05:54,360 --> 00:05:55,600
But here's the thing.

126
00:05:55,600 --> 00:05:58,160
Grouping goods isn't just about putting more items together.

127
00:05:58,160 --> 00:06:02,520
A truck has limits, wait, floor space, height, a container has its own rules.

128
00:06:02,520 --> 00:06:06,600
If the system groups goods without checking those limits, the load may look fine on screen,

129
00:06:06,600 --> 00:06:08,240
but fail at the loading dock.

130
00:06:08,240 --> 00:06:11,360
Dynamics 365 uses load templates to help avoid that.

131
00:06:11,360 --> 00:06:16,000
Think of a load template as a reusable set of limits for a type of vehicle or container.

132
00:06:16,000 --> 00:06:19,600
Create one for a small delivery truck, another for a larger trailer, another for a shipping

133
00:06:19,600 --> 00:06:20,600
container.

134
00:06:20,600 --> 00:06:24,840
Each template holds limits for weight, volume, height, and other rules your company needs.

135
00:06:24,840 --> 00:06:27,640
The template gives the load a shape before you start filling it.

136
00:06:27,640 --> 00:06:31,360
So if a shipment weighs too much or takes up too much room, the planner sees it doesn't

137
00:06:31,360 --> 00:06:32,520
belong on that load.

138
00:06:32,520 --> 00:06:36,000
The answer might be a second vehicle, a different template, or a different grouping of

139
00:06:36,000 --> 00:06:37,000
shipments.

140
00:06:37,000 --> 00:06:40,320
The software doesn't lift pallets, but it does give your team a clearer plan before

141
00:06:40,320 --> 00:06:41,920
physical work begins.

142
00:06:41,920 --> 00:06:45,840
One built-in approach is called volume-based load building.

143
00:06:45,840 --> 00:06:47,920
That sounds more technical than it needs to.

144
00:06:47,920 --> 00:06:52,400
It means the system uses the maximum height and weight from your load template when building

145
00:06:52,400 --> 00:06:53,760
or suggesting a load.

146
00:06:53,760 --> 00:06:57,040
In plain English, it checks whether the goods fit within the limits you set.

147
00:06:57,040 --> 00:06:58,520
Those values aren't locked forever.

148
00:06:58,520 --> 00:07:01,400
A planner can override them when real world needs change.

149
00:07:01,400 --> 00:07:03,200
Maybe a carrier sends a different trailer.

150
00:07:03,200 --> 00:07:04,560
Maybe a trip allows a different height.

151
00:07:04,560 --> 00:07:08,720
The template supplies the normal rule, and the override handles the exception without

152
00:07:08,720 --> 00:07:09,720
rebuilding everything.

153
00:07:09,720 --> 00:07:11,880
Let's return to those six customer orders.

154
00:07:11,880 --> 00:07:14,720
Each alone might take up 15% of a truck.

155
00:07:14,720 --> 00:07:18,200
Plan separately, you could send six mostly empty vehicles.

156
00:07:18,200 --> 00:07:22,400
Grouped into one load, the same orders may fill most of one truck with room left for more.

157
00:07:22,400 --> 00:07:23,400
That's a better use of space.

158
00:07:23,400 --> 00:07:25,480
Now, the same idea works both directions.

159
00:07:25,480 --> 00:07:28,760
For inbound planning, create a load around items coming from a vendor.

160
00:07:28,760 --> 00:07:32,560
The transport plan connects to the expected receipt, so the warehouse knows what's due and

161
00:07:32,560 --> 00:07:33,760
prepares for arrival.

162
00:07:33,760 --> 00:07:37,160
Instead of learning about a delivery only when it appears at the gate, the receiving

163
00:07:37,160 --> 00:07:38,680
team has a planned record.

164
00:07:38,680 --> 00:07:42,480
For outbound planning, select warehouse items that need to leave for customers and

165
00:07:42,480 --> 00:07:43,640
group them into a load.

166
00:07:43,640 --> 00:07:47,640
The warehouse prepares those goods based on the load details, not a disconnected list.

167
00:07:47,640 --> 00:07:53,040
One full load still needs a way to travel, a company to move it and an expected charge.

168
00:07:53,040 --> 00:07:56,000
Roots, carriers and rates.

169
00:07:56,000 --> 00:07:58,560
The load now tells you what needs to travel together.

170
00:07:58,560 --> 00:08:02,560
Next, you need to decide who moves it, which service they use, and what that trip should

171
00:08:02,560 --> 00:08:03,560
cost.

172
00:08:03,560 --> 00:08:05,360
The company that moves your goods is called the carrier.

173
00:08:05,360 --> 00:08:08,920
It can be an outside transport company that collects and delivers your freight.

174
00:08:08,920 --> 00:08:11,920
It can also mean your own fleet if you run your own trucks and drivers.

175
00:08:11,920 --> 00:08:15,560
Either way, the carrier is responsible for the physical trip.

176
00:08:15,560 --> 00:08:19,440
That distinction matters because you still need a plan, even when the truck belongs to you.

177
00:08:19,440 --> 00:08:22,640
With an outside carrier you agree on prices and services ahead of time.

178
00:08:22,640 --> 00:08:26,160
With your own fleet, you may still want the transport charge calculated, especially if

179
00:08:26,160 --> 00:08:28,680
delivery costs appear on customer orders.

180
00:08:28,680 --> 00:08:32,120
Dynamics 365 transportation management supports both situations.

181
00:08:32,120 --> 00:08:33,120
Then there's the route.

182
00:08:33,120 --> 00:08:37,080
A route is the planned path from pick up to destination along with the service choice.

183
00:08:37,080 --> 00:08:38,760
It answers practical questions.

184
00:08:38,760 --> 00:08:40,760
Which warehouse does the carrier collect from?

185
00:08:40,760 --> 00:08:43,160
Which customer or location receives the goods?

186
00:08:43,160 --> 00:08:45,120
Which carrier service handles the trip?

187
00:08:45,120 --> 00:08:48,800
Picture a delivery leaving your main warehouse for a customer across the country.

188
00:08:48,800 --> 00:08:52,400
One route may use standard road freight that costs less but takes longer.

189
00:08:52,400 --> 00:08:55,120
Another may use a faster, more expensive service.

190
00:08:55,120 --> 00:08:57,920
Same starting and ending point, but the transport choice changes.

191
00:08:57,920 --> 00:08:59,920
A rate is the expected charge for that choice.

192
00:08:59,920 --> 00:09:02,480
It's not a random number typed in at the last minute.

193
00:09:02,480 --> 00:09:06,760
Rates come from pricing agreements with carriers, combined with shipment or route details.

194
00:09:06,760 --> 00:09:07,760
Where the goods start?

195
00:09:07,760 --> 00:09:08,560
Where they go?

196
00:09:08,560 --> 00:09:09,560
The service used.

197
00:09:09,560 --> 00:09:12,440
The amount transported, so a route tells you how goods should move.

198
00:09:12,440 --> 00:09:14,600
A rate tells you what you expect to pay.

199
00:09:14,600 --> 00:09:18,280
Those two ideas belong together because a cheap route may miss your delivery promise, while

200
00:09:18,280 --> 00:09:20,840
speed may cost more than the order supports.

201
00:09:20,840 --> 00:09:22,320
Transport planning isn't just finding a truck.

202
00:09:22,320 --> 00:09:28,080
It's choosing a service that fits your customer commitment and the company's cost rules.

203
00:09:28,080 --> 00:09:30,600
Dynamics 365 includes the rate route workbench.

204
00:09:30,600 --> 00:09:32,880
The name sounds formal but the purpose is simple.

205
00:09:32,880 --> 00:09:37,640
It gives planners a place to compare route and rate choices for a shipment side by side.

206
00:09:37,640 --> 00:09:41,080
Instead of checking one carrier table, then another and comparing in a separate file, you

207
00:09:41,080 --> 00:09:43,680
review the choices connected to that shipping need.

208
00:09:43,680 --> 00:09:45,880
Maybe one option reaches the customer sooner.

209
00:09:45,880 --> 00:09:47,280
Maybe another costs less.

210
00:09:47,280 --> 00:09:51,800
The system doesn't know every customer values speed more than cost, because businesses work

211
00:09:51,800 --> 00:09:52,800
differently.

212
00:09:52,800 --> 00:09:57,120
A customer may have paid for urgent delivery, so the faster route makes sense.

213
00:09:57,120 --> 00:10:00,600
Another accepts longer delivery and the lower charge fits better.

214
00:10:00,600 --> 00:10:02,440
People still make the decision.

215
00:10:02,440 --> 00:10:06,040
Transportation management gives you agreed choices and expected costs, while your business

216
00:10:06,040 --> 00:10:08,040
decides which trade-off works.

217
00:10:08,040 --> 00:10:10,440
Here's what the built-in module actually does.

218
00:10:10,440 --> 00:10:15,080
Rate information comes from rate tables, your company enters and maintains in Dynamics 365.

219
00:10:15,080 --> 00:10:18,920
Think of these tables as stored records of agreed carrier prices and route rules.

220
00:10:18,920 --> 00:10:22,680
If you've negotiated a price for a certain service in lane, that information sits in the

221
00:10:22,680 --> 00:10:24,160
system and supports planning.

222
00:10:24,160 --> 00:10:26,360
That works well when your rates follow known agreements.

223
00:10:26,360 --> 00:10:31,000
For example, work with a few regular carriers, serve familiar routes, and update prices when

224
00:10:31,000 --> 00:10:32,000
contracts change.

225
00:10:32,000 --> 00:10:36,280
Transport planner uses rates already recorded instead of hunting through old emails, but here's

226
00:10:36,280 --> 00:10:38,200
something many people misunderstand.

227
00:10:38,200 --> 00:10:41,920
The built-in module doesn't act like a live shopping site connected to every carrier.

228
00:10:41,920 --> 00:10:45,960
It doesn't automatically pull fresh prices from live feeds and compare across a broad network

229
00:10:45,960 --> 00:10:46,960
in real time.

230
00:10:46,960 --> 00:10:50,560
If your company needs multi-carrier rate shopping, live booking links, or deeper shipment status

231
00:10:50,560 --> 00:10:52,960
updates, you normally connect a third party system.

232
00:10:52,960 --> 00:10:55,160
That's not a failure of transportation management.

233
00:10:55,160 --> 00:10:56,880
It defines its job clearly.

234
00:10:56,880 --> 00:11:01,160
These tools handle structured transport planning, inside supply chain management, using the

235
00:11:01,160 --> 00:11:04,480
carrier, route, and rate information your company maintains.

236
00:11:04,480 --> 00:11:07,240
And it's also not a consumer-pastel tracking website.

237
00:11:07,240 --> 00:11:11,920
You won't use it like a map where you enter one tracking number and watch a vehicle icon

238
00:11:11,920 --> 00:11:13,000
travel down a road.

239
00:11:13,000 --> 00:11:16,960
This module focuses on business transport decisions before and around the shipment, which

240
00:11:16,960 --> 00:11:20,880
goods move together, which carrier handles them, which route applies, what the trip should

241
00:11:20,880 --> 00:11:21,880
cost.

242
00:11:21,880 --> 00:11:26,680
Once your company selects that plan, the warehouse and transport teams need to carry it out.

243
00:11:26,680 --> 00:11:30,720
From warehouse door to customer door, a transport plan only helps when people can actually turn

244
00:11:30,720 --> 00:11:32,000
it into a real shipment.

245
00:11:32,000 --> 00:11:35,720
For an outbound order, the flow usually starts when a customer buys something.

246
00:11:35,720 --> 00:11:38,800
The sales order tells the business what the customer wants, where it needs to go, and

247
00:11:38,800 --> 00:11:39,880
when it should arrive.

248
00:11:39,880 --> 00:11:43,640
That order becomes a shipment, and the shipment joins a planned load with other goods traveling

249
00:11:43,640 --> 00:11:44,640
on the same trip.

250
00:11:44,640 --> 00:11:46,040
Then the warehouse takes over.

251
00:11:46,040 --> 00:11:50,080
Workers pick the items from storage, pack them, and bring them to the right loading area.

252
00:11:50,080 --> 00:11:53,760
Because the shipment belongs to a load, the team can see which goods need to leave together,

253
00:11:53,760 --> 00:11:55,400
and which carrier will collect them.

254
00:11:55,400 --> 00:11:59,200
When the vehicle arrives, the goods move from the warehouse to the carrier, and the carrier

255
00:11:59,200 --> 00:12:00,680
takes them to the customer.

256
00:12:00,680 --> 00:12:02,880
Every step connects to the same movement record.

257
00:12:02,880 --> 00:12:04,760
That sounds ordinary, but imagine the old way.

258
00:12:04,760 --> 00:12:06,640
A picker might work from a printed order.

259
00:12:06,640 --> 00:12:10,480
A transport planner might hold a separate list, and someone at the loading door might search

260
00:12:10,480 --> 00:12:13,840
through emails to check which carrier should take which pallets.

261
00:12:13,840 --> 00:12:16,880
If one detail changed, everybody needed the updated version.

262
00:12:16,880 --> 00:12:19,920
With transportation management, the load gives the teams a shared record out.

263
00:12:19,920 --> 00:12:23,320
The warehouse can see the items connected to the load, the transport planner can see the

264
00:12:23,320 --> 00:12:27,160
shipment details, and the person arranging the pick up can see the planned carrier and

265
00:12:27,160 --> 00:12:28,760
service.

266
00:12:28,760 --> 00:12:32,760
Instead of passing around several paper lists, people work from information linked to the

267
00:12:32,760 --> 00:12:34,480
same order and shipment.

268
00:12:34,480 --> 00:12:35,640
Here's a simple example.

269
00:12:35,640 --> 00:12:39,400
A warehouse has orders for several customers in the same delivery area.

270
00:12:39,400 --> 00:12:43,760
One customer ordered cartons of cleaning supplies, another ordered paper products, and a third

271
00:12:43,760 --> 00:12:45,480
ordered a small batch of equipment.

272
00:12:45,480 --> 00:12:48,560
Each order needs picking and packing, but the transport team doesn't have to treat them

273
00:12:48,560 --> 00:12:49,880
as completely separate trips.

274
00:12:49,880 --> 00:12:51,880
They assign the shipments to one planned load.

275
00:12:51,880 --> 00:12:56,400
Warehouse staff pick each order, pack it correctly, and prepare it for the loading area.

276
00:12:56,400 --> 00:12:59,480
The load record tells them that all those shipments travel together.

277
00:12:59,480 --> 00:13:03,240
When the carrier arrives, the team hands over the goods for one planned movement instead

278
00:13:03,240 --> 00:13:06,680
of trying to match loose pallets to a driver at the last minute.

279
00:13:06,680 --> 00:13:09,000
The customer still receives their own order.

280
00:13:09,000 --> 00:13:12,880
Behind the scenes, though, the business planned that delivery as part of a larger movement,

281
00:13:12,880 --> 00:13:16,560
that link helps the warehouse work with the transport team instead of working ahead of

282
00:13:16,560 --> 00:13:19,440
it or waiting for instructions that arrive too late.

283
00:13:19,440 --> 00:13:23,560
Inbound transportation follows the same connected idea, just in the other direction.

284
00:13:23,560 --> 00:13:27,080
A purchase order tells you that your company expects goods from a vendor.

285
00:13:27,080 --> 00:13:30,760
When your business arranges the transport, a planned inbound load connects the incoming

286
00:13:30,760 --> 00:13:33,720
items to the trip before the goods reach the warehouse.

287
00:13:33,720 --> 00:13:37,480
The vendor sends the shipment, the carrier brings it to your site, and the warehouse receives

288
00:13:37,480 --> 00:13:38,480
it.

289
00:13:38,480 --> 00:13:40,760
Receiving staff can prepare because they know what should arrive.

290
00:13:40,760 --> 00:13:43,960
They can check the planned load against the goods that turn up at the dock, oh, much

291
00:13:43,960 --> 00:13:47,240
clearer than a truck appearing with little warning and someone trying to work out which

292
00:13:47,240 --> 00:13:49,520
purchase order the pallets belong to.

293
00:13:49,520 --> 00:13:51,640
Transfer orders fit this process too.

294
00:13:51,640 --> 00:13:54,800
One company site sends stock out while another company site receives it.

295
00:13:54,800 --> 00:13:58,520
The first warehouse prepares the items and ships them and the second warehouse expects the

296
00:13:58,520 --> 00:14:01,080
same items and receives them into its stock.

297
00:14:01,080 --> 00:14:04,840
No outside customer sits at the end of that trip, but the company still needs a clear hand

298
00:14:04,840 --> 00:14:06,560
off between the two locations.

299
00:14:06,560 --> 00:14:10,600
The load connects the sending and receiving work around one planned movement.

300
00:14:10,600 --> 00:14:13,880
Customer delivery choices also stay connected to the shipping decision.

301
00:14:13,880 --> 00:14:17,840
If a planner chooses a faster carrier service because a customer needs goods quickly, that

302
00:14:17,840 --> 00:14:19,600
choice connects to the shipment.

303
00:14:19,600 --> 00:14:23,480
If the business uses a lower cost service because the delivery date allows it, that choice

304
00:14:23,480 --> 00:14:24,480
connects to it.

305
00:14:24,480 --> 00:14:28,320
People can trace the delivery cost back to the route and carrier choice that created it.

306
00:14:28,320 --> 00:14:32,000
The vehicle may leave the dock and the goods may arrive safely, but the work still isn't

307
00:14:32,000 --> 00:14:33,000
finished.

308
00:14:33,000 --> 00:14:36,840
The carrier sends a freight bill afterward and somebody needs to check it.

309
00:14:36,840 --> 00:14:39,400
Freight costs and reconciliation.

310
00:14:39,400 --> 00:14:42,640
The goods have left the warehouse and the delivery may even be complete.

311
00:14:42,640 --> 00:14:43,960
Then the carrier invoice arrives.

312
00:14:43,960 --> 00:14:47,720
That invoice needs checking because the amount on the bill should connect back to the transport

313
00:14:47,720 --> 00:14:53,280
choice the company planned earlier, a/o, including the carrier, route, service, load details and

314
00:14:53,280 --> 00:14:55,120
expected freight charge.

315
00:14:55,120 --> 00:14:59,480
During planning, Dynamics 365 can calculate and expect a transport charge from the company's

316
00:14:59,480 --> 00:15:00,480
rate information.

317
00:15:00,480 --> 00:15:04,680
That expected amount gives the business a starting point before the carrier asks for payment.

318
00:15:04,680 --> 00:15:07,160
Later the carrier sends its freight invoice.

319
00:15:07,160 --> 00:15:11,120
Freight reconciliation means comparing that invoice with the rate and shipment details already

320
00:15:11,120 --> 00:15:12,360
recorded in the system.

321
00:15:12,360 --> 00:15:15,720
In plain English, the company checks whether the carrier charged what the company expected

322
00:15:15,720 --> 00:15:17,520
for the service that actually moved the goods.

323
00:15:17,520 --> 00:15:20,320
Imagine the plan showed a charge of $500.

324
00:15:20,320 --> 00:15:24,160
The carrier invoice also shows $500 and the shipment details match.

325
00:15:24,160 --> 00:15:27,680
That bill has a clear path through the checking process because the planned record and the

326
00:15:27,680 --> 00:15:28,880
invoice agree.

327
00:15:28,880 --> 00:15:30,960
But invoices don't always match the plan.

328
00:15:30,960 --> 00:15:34,640
Maybe the rate table was wrong, maybe the carrier billed for a different service, or maybe

329
00:15:34,640 --> 00:15:38,440
the load changed after planning and a charge needs an explanation.

330
00:15:38,440 --> 00:15:42,280
Without a connected record, finance may only see an invoice number and an amount, then spend

331
00:15:42,280 --> 00:15:45,400
time asking the warehouse and transport team what happened.

332
00:15:45,400 --> 00:15:48,680
Our management keeps the transport decision connected to that check.

333
00:15:48,680 --> 00:15:52,920
Rules can compare the carrier invoice with the expected amount and plan shipment information.

334
00:15:52,920 --> 00:15:57,080
When the details fit within the company's accepted rules, the invoice can move forward.

335
00:15:57,080 --> 00:16:01,040
When the details don't fit, the system sends the difference for someone to review.

336
00:16:01,040 --> 00:16:04,000
That means people don't approve every freight charge blindly.

337
00:16:04,000 --> 00:16:08,440
A transport planner may need to confirm that the carrier used a different service, or someone

338
00:16:08,440 --> 00:16:11,720
in finance may need to ask why an extra charge appeared.

339
00:16:11,720 --> 00:16:14,560
The point isn't to assume every mismatch is wrong, are you?

340
00:16:14,560 --> 00:16:16,920
The point is to notice the mismatch before payment.

341
00:16:16,920 --> 00:16:19,600
This joins operations and finance around the same shipment.

342
00:16:19,600 --> 00:16:23,920
The transport team chooses a carrier and service, that choice creates an expected cost,

343
00:16:23,920 --> 00:16:27,840
the warehouse sends the goods, and finance checks the later invoice against the record of

344
00:16:27,840 --> 00:16:29,800
what the company planned.

345
00:16:29,800 --> 00:16:32,920
Each team sees a different part, but they are looking at connected information.

346
00:16:32,920 --> 00:16:35,640
The built-in process has a clear scope though.

347
00:16:35,640 --> 00:16:39,640
Companies that need large scale, highly automated freight auditing, often add a third-party

348
00:16:39,640 --> 00:16:41,720
transportation management system.

349
00:16:41,720 --> 00:16:45,640
Those tools can bring deeper carrier connections and more automated checking rules.

350
00:16:45,640 --> 00:16:49,800
The built-in module handles the planned cost and reconciliation work inside supply chain

351
00:16:49,800 --> 00:16:54,200
management, while another system can extend that work when the business needs more.

352
00:16:54,200 --> 00:16:58,360
Put all of these building blocks together and the full picture starts to appear, where

353
00:16:58,360 --> 00:17:00,640
it fits and what it doesn't do.

354
00:17:00,640 --> 00:17:02,920
So where does transportation management actually live?

355
00:17:02,920 --> 00:17:07,160
It belongs inside Dynamics 365 supply chain management, running on the finance and operations

356
00:17:07,160 --> 00:17:08,160
apps.

357
00:17:08,160 --> 00:17:09,160
That's its home.

358
00:17:09,160 --> 00:17:13,560
It's a company that needs a structured way to plan inbound deliveries, outbound customer

359
00:17:13,560 --> 00:17:18,960
shipments, stock transfers between companies, all using their own carrier records, rate tables,

360
00:17:18,960 --> 00:17:19,960
and load rules.

361
00:17:19,960 --> 00:17:22,400
Now let's clear up a common point of confusion.

362
00:17:22,400 --> 00:17:23,880
Business central is different.

363
00:17:23,880 --> 00:17:26,920
Business central doesn't include this built-in transportation management module.

364
00:17:26,920 --> 00:17:31,040
If you're on business central and need transport planning, you're looking at a third-party transportation

365
00:17:31,040 --> 00:17:32,040
management system.

366
00:17:32,040 --> 00:17:35,160
That's the boundary, let's also keep the boundary clear on the other side.

367
00:17:35,160 --> 00:17:39,480
A built-in module doesn't replace every carrier portal, live traffic service, or advanced tracking

368
00:17:39,480 --> 00:17:40,480
tool.

369
00:17:40,480 --> 00:17:44,520
When a business needs live rates from many carriers, wider carrier choices, or deeper tracking

370
00:17:44,520 --> 00:17:47,960
after goods leave the dock, it connects a third-party TMS.

371
00:17:47,960 --> 00:17:49,840
Those tools handle the outside activity.

372
00:17:49,840 --> 00:17:51,680
Think back to the office building.

373
00:17:51,680 --> 00:17:54,200
Transportation management is the transportation desk inside that building.

374
00:17:54,200 --> 00:17:57,080
It connects to orders, warehouse work, and finance.

375
00:17:57,080 --> 00:18:00,080
It keeps the company's own transport plan together.

376
00:18:00,080 --> 00:18:02,880
Outside carrier tools may handle activity beyond that desk.

377
00:18:02,880 --> 00:18:04,280
Two different layers working together.

378
00:18:04,280 --> 00:18:07,200
Conclusion.

379
00:18:07,200 --> 00:18:08,800
Next Knowledge Nugget.

380
00:18:08,800 --> 00:18:10,400
Here's the simplest way to think about it.

381
00:18:10,400 --> 00:18:14,040
A transportation management turns business orders into planned movement of goods.

382
00:18:14,040 --> 00:18:17,720
Then it connects that movement to the freight costs the company checks afterwards.

383
00:18:17,720 --> 00:18:19,320
That's the full loop.

384
00:18:19,320 --> 00:18:21,520
Subscribe on your favorite podcast platform.

385
00:18:21,520 --> 00:18:26,440
Share this knowledge nugget with someone learning Dynamics 365, Supply Chain Management.

386
00:18:26,440 --> 00:18:29,520
Then explore our warehouse and inventory episodes next.

387
00:18:29,520 --> 00:18:32,040
Every load still depends on the stock sitting behind the warehouse door.