Dynamics 365 Supply Chain Management is an Operations application that licenses on the Operations base rate and shares the base plus attach model with Finance, Commerce, and Project Operations. What makes Supply Chain distinct is the shop floor: a large population of shift workers, warehouse operators, and production staff who touch a narrow set of transactions on shared terminals. Microsoft offers a device license precisely for this scenario, where named user licensing would force a full or Activity seat onto every worker across every shift. The most common error is assigning named user licenses to shift workers who should be on shared device licenses. The second is putting full Operations seats on warehouse and inquiry users who belong on the Activity tier. The third is unlicensed multiplexing through the manufacturing execution and warehouse integrations that read and write Supply Chain data. Supply Chain is where device licensing and tier discipline change the math, and the shop floor is the largest lever.
Supply Chain prices at the Operations base rate with the same restricted tiers as Finance, plus a device licensing option that is decisive on the shop floor. The named user versus device decision and the tier mix drive the bill.
The full Supply Chain license carries the complete warehouse, manufacturing, and planning surface at the Operations base rate. The Activity license covers users who only execute defined operational tasks. The Team Members license sits lowest for light read and write. The device license covers shared terminals where many workers across shifts touch the same station.
A user who needs Supply Chain alongside Finance or another Operations application pays one full Operations base and attaches the rest at a reduced rate. The device option breaks the named user assumption for the shop floor, where the same physical station serves dozens of workers across three shifts and a per worker named license would multiply the count needlessly.
Supply Chain produces three expensive waste patterns. The dominant one is named user licensing for shop floor workers who belong on device licenses. The second is full Operations seats on light warehouse users. The third is unlicensed multiplexing through the execution and warehouse integrations.
Every shift worker who scans a pallet gets a named Operations license because the device option was never configured. Across three shifts and a large floor, the named user count balloons far beyond the number of physical stations. Licensing the shared terminals as devices instead collapses that count to the station footprint and is the single biggest Supply Chain saving.
Warehouse supervisors who only run inquiries and approvals, and planners who only read, get the full Operations seat at the base rate. The Activity tier exists for exactly this defined task work. At the Operations base price the gap is large, and a population of light users on full seats compounds across the operation.
Manufacturing execution systems, warehouse robotics, and barcode middleware read and write Supply Chain data through service accounts. Microsoft counts the human users and devices behind those integrations, not the service account. Organizations routinely under license this indirect access, and it is a primary finding in Operations audits.
The Supply Chain bill responds to three levers. Device licensing collapses the shop floor count. Tier rationalization moves light users to Activity. Multiplexing remediation licenses the integrations before an audit prices the gap.
The decisive Supply Chain move is licensing shared shop floor and warehouse terminals as devices rather than assigning a named seat to every worker. The count drops from the worker headcount across all shifts to the number of physical stations. Telemetry on station usage confirms the device footprint, and the saving recurs for the life of the agreement.
The device baseline then feeds the EA renewal where the Operations lines are negotiated against the true station and seat count rather than the inflated named user roster.
Inquiry users, planners, and approvers who only execute defined tasks move to the Activity tier, capturing the gap against the Operations base rate. The decision follows the usage telemetry, not the org chart.
The execution systems, robotics middleware, and warehouse integrations get mapped to the users and devices behind them so the indirect access is licensed correctly before an audit prices the multiplexing punitively.
Supply Chain negotiates inside the Operations envelope. The device ratio and the Operations base rate are the leverage points, and the buyer who arrives with a device verified floor and a closed multiplexing gap holds the strong position.
Supply Chain and Finance share the base plus attach model, so the Operations applications negotiate as one envelope. A buyer who brings the device baseline, the rationalized tier mix, and the reconciled attach counts negotiates the Operations base rate and the device ratio from the true requirement. Splitting the family forfeits the combined leverage Microsoft would otherwise have to concede.
The renewal is the moment to reset the shop floor from named user licensing to the device baseline and to close any multiplexing gap on the buyer's terms. A buyer who arrives with the station count and the usage evidence negotiates from the real footprint. Carrying the inflated named user roster forward anchors the deal on the most over counted population in the estate.
The Supply Chain engagement is a device and tier diagnostic, an attach and multiplexing reconciliation, and the integration of the clean baseline into the Operations negotiation. The output is a Supply Chain line priced at the stations and seats the operation actually runs.
We map the shop floor and warehouse against physical stations to establish the device footprint, pull usage telemetry to right size the office tiers, and quantify the multiplexing through the execution and warehouse integrations. The output is a defensible device baseline, a right sized tier mix, and a closed indirect access gap.
We convert the shop floor to device licensing, move light office users to Activity, remediate the multiplexing, and fold the clean baseline into the Operations negotiation. We secure the Operations base rate and device ratio and lock multi year price protection. The output is a Supply Chain position priced at the true footprint and defensible through the term.
The Dynamics 365 Supply Chain diagnostic maps the shop floor to physical stations, converts it to device licensing, moves light office users to the Activity tier, closes the multiplexing exposure, and brings the clean baseline into the Operations negotiation. The result is a Supply Chain line priced at the stations the operation actually runs.