What we do
Tools
Industries
Department
How we workLet's talk →
Home/Dynamics 365/Dynamics 365 Supply Chain Management Modules
Microsoft Dynamics 365

Dynamics 365 Supply Chain Management: What Each Area Does, and Where Your Partners Come In

Supply Chain Management is the half of Microsoft's finance and operations apps that runs physical goods: inventory, warehouses, purchasing, planning, production and transport. Here is what each area covers, how it shares one set of records with Dynamics 365 Finance, and where data from suppliers, 3PLs and floor devices still has to be brought in.

Supply Chain Management in short

What it is: the Dynamics 365 app for inventory, warehouse management, procurement, master planning, manufacturing and transportation, built on the same platform as Dynamics 365 Finance.

Who runs it: distributors, manufacturers and retailers with several warehouses or plants, usually alongside Finance in one environment.

What it doesn't do by itself: read a supplier's EDI, a 3PL's warehouse system or a conveyor controller. Those arrive through integration, one partner at a time.

The areas inside Supply Chain Management

Area What it handles Where outside data usually meets it
Inventory management On-hand stock, reservations, transfer orders, batch and serial tracking, and quality orders. Stock held at a 3PL or a marketplace warehouse only counts once someone posts it. The Inventory Visibility add-in can take in outside sources, but each one still needs a feed.
Warehouse management Locations, waves, pick and put-away work, cycle counts, and the Warehouse Management mobile app on handheld devices. Conveyors, sorters, voice picking and print-and-apply stations usually speak their own protocol, not D365's.
Master planning Planned purchase, transfer and production orders from demand, stock and lead times, calculated by Planning Optimization. Demand forecasting sits alongside it. Plans are only as good as the lead times and the sales forecast. If those live in a spreadsheet, the plan inherits its age.
Procurement and sourcing Purchase requisitions, purchase orders, vendor agreements, and a vendor collaboration portal for confirmations. Larger suppliers won't use your portal. They send order acknowledgements and ship notices as EDI instead.
Production control Bills of materials, routes, and production orders for discrete, process and lean manufacturing. Machine counts and scrap from a shop-floor MES are often re-entered at shift end.
Transportation management Loads, routes, carrier rates and freight reconciliation. Live tracking and label data stay in each carrier's system unless something pulls them in.

How Supply Chain Management and Finance share one set of records

When Finance and Supply Chain Management run in the same environment, they aren't two systems that sync. They're two apps over one database. A product receipt updates stock and posts its value to the ledger in the same step, and a vendor invoice is matched against the purchase order and receipt before it reaches accounts payable. That's also why people still call the pair F&O; our Finance and Operations page untangles the names and compares it with Business Central.

So nearly all integration work on Supply Chain Management faces outward. Dynamics 365 Sales and Field Service reach it through dual-write. Everything else comes through data entities: OData for record-by-record reads and writes, the data management framework for recurring file imports and exports, and business events to push changes out. The Dynamics 365 API and Dynamics 365 integration pages go through those routes in detail.

Where goods move but Dynamics 365 hears about it late

Each of these looks fine in a demo, because demos don't include your trading partners.

Every supplier sends EDI a little differently

How you'll know: Ship notices (856) and order acknowledgements (855) arrive, and a buyer types the quantities and dates into the purchase order by hand.

Fix: Map each trading partner's documents to the right D365 data entities once, through an EDI layer, and send exceptions to a queue someone owns. A new partner is then a mapping job, not a new process.

The 3PL runs its own warehouse system

How you'll know: Releases go out by email or a portal, and shipments come back as a nightly CSV, so stock and order status in D365 trail reality by a day.

Fix: Send released orders to the 3PL as they're released, and post its pick, pack and ship confirmations back to the sales order and inventory as they happen. See our 3PL warehouse software page for the 3PL's side of this.

Floor hardware that the mobile app doesn't drive

How you'll know: Handhelds run the Warehouse Management mobile app, but the sorter, scale or label printer line has its own controller, and somebody reconciles counts afterwards.

Fix: A small service between the controller and D365 that turns each scan or weight into the matching warehouse transaction, and flags the ones it can't place.

Orders from a store D365 has never heard of

How you'll know: Web store or marketplace orders are exported, cleaned in Excel and imported in a batch, so promised stock gets sold twice.

Fix: Create the sales orders through OData as they come in, and send stock levels back to the store on a short schedule. Our inventory automation page covers the stock side.

Integration questions to settle before go-live

Ask these during the implementation, while the partner is still configuring data entities.

  • Which trading partners send EDI, and which documents does each one send?

    The count of partners times documents is the real size of the EDI work. Most projects underestimate it by asking only about purchase orders.

  • Which data entity does each inbound document land in?

    Agreeing this early stops two teams building different routes for the same ship notice.

  • Who works the error queue, and how fast?

    A failed import that nobody sees is worse than a manual one. Somebody needs to own rejected documents daily.

  • Does each feed need to be live, or is a batch fine?

    Stock and shipments usually need minutes. Price lists and lead times can run nightly through the data management framework.

  • Which devices run the mobile app, and which run something else?

    Anything outside the mobile app needs its own bridge, and that's easier to plan before racking and conveyors are wired.

Questions people ask

What does Dynamics 365 Supply Chain Management cover?

Inventory management, warehouse management, procurement, master planning and demand forecasting, production control for discrete, process and lean manufacturing, and transportation management. It's built on the same platform as Dynamics 365 Finance.

Does Dynamics 365 support EDI with suppliers?

Yes, through an EDI layer that translates each partner's documents into Supply Chain Management's data entities. That layer is usually an add-on or middleware rather than part of the core app, and every trading partner needs its own mapping, because no two send exactly the same format.

Can Dynamics 365 integrate with a third-party warehouse management system?

Yes. Some 3PL and WMS vendors maintain a Dynamics connector. Where they don't, the link is built against D365's data entities: released orders out, and picks, shipments and receipts back in, ideally as each one happens.

Is Supply Chain Management part of Finance and Operations, or a separate product?

Both, in a way. It's licensed as its own app, but it belongs to the finance and operations family and usually runs in the same environment as Dynamics 365 Finance, sharing one database. Supply Chain Management handles goods; Finance handles the ledger, payables and receivables.

Does the Warehouse Management mobile app run on our existing scanners?

It runs on Windows, Android and iOS devices, so many rugged Android handhelds can use it. Fixed hardware such as sorters, scales and print-and-apply lines is a different matter and usually needs its own integration.

How do we report on Supply Chain Management data together with other systems?

Export the D365 tables to a reporting store and combine them there with the 3PL, carrier or store data. Our Dynamics 365 reporting page covers the options, and n-frames builds the feeds that bring the outside sources in on a schedule.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.