The D365 Firming Flaw That Makes On-Time Delivery Impossible

Why D365 Production Orders Stop Trying to Hit Your Customer's Delivery Date

Your planning team is doing everything right. They're running the schedule, watching the dates, flagging orders that are at risk. When an order looks tight, they escalate. Overtime gets approved. The floor works the weekend. The order ships, and it's still late. The customer calls. Nobody saw it coming.

This is not a planning failure. It's not a capacity problem. The team was working as hard as they could toward the wrong date.

What the Planning Team Sees

When a planned production order exists in D365, two dates are visible: the customer's requested delivery date and the realistic delivery date based on actual capacity. If the system determines the order will be late, both dates are visible and the planner can see the gap. They know the customer wanted it by the 15th and the realistic date is the 30th. That visibility matters. It tells the planner where the problem is and gives them a chance to act.

When that planned order is firmed into a production order, something changes. The customer's requested delivery date disappears. It is no longer visible on the production order. The only date the production team has to work with is the delivery date on the production order itself.

That delivery date is the delayed date.

What D365 Is Doing

This is not a data entry error. It is not a missing field that someone forgot to populate. It is a D365 behavior that occurs automatically at the moment of firming.

When a planned order is firmed, D365 populates the production order delivery date with the realistic scheduled date, not the customer's requested date. The customer's requested date, which was visible on the planned order, does not carry forward. It does not appear on the production order. It is not accessible to the production floor team without going back to the original sales order.

From that moment forward, the production order delivery date and the customer's requested delivery date are two different dates, and only one of them is visible to the people responsible for hitting it.

Why This Compounds Over Time

In a make-to-order environment, most production orders are already behind the customer's requested date before they're firmed. Finite capacity scheduling exists precisely because there isn't always enough capacity to meet every requested date. When the system can't backward schedule to the requested date, it forward schedules and produces a realistic date that reflects actual capacity.

That realistic date is what populates the production order delivery date at firming.

So, the team inherits a delivery date that is already late on day one. Every reschedule, every capacity update, every planning optimization run works to protect that date. The system is optimizing toward lateness. Not because anyone made a mistake, but because the date the system is working from was never the customer's date to begin with.

Running extra shifts helps. Expediting helps. But without knowing the customer's actual requested date, the team has no target to measure against and no way to know whether their effort is closing the gap or just reducing it.

The Moment It Becomes Visible

It usually becomes visible in one of two ways.

The first is the customer call. The order ships on the production order delivery date. The team marks it on time. Two days later the customer calls because the part was due three weeks ago. From the production floor's perspective, the order was never late. From the customer's perspective, it was late before it was ever firmed.

The second is the planning meeting. Someone asks for an update on a sales order that the customer is asking about. When they pull up the production order, the delivery date doesn't match what the customer requested. The production order shows a date three weeks later than what the customer was promised. The team has been working toward the wrong target the entire time, and the escalation happens too late to change the outcome.

In both cases the information needed to prevent the miss was available at the planned order stage and lost at firming. The production team never had a chance to respond to the real deadline because the real deadline was never in front of them.

What Makes This Hard to Diagnose

Most teams that experience this pattern attribute it to capacity problems, planning execution, or material availability. Those are the visible symptoms. The root cause,that the production order delivery date was never the customer's requested date, is not visible without knowing where to look.

Implementation partners who set up D365 FSC typically configure the firming process and move on. The behavior described here is not a configuration error. It is how D365 behaves by default when a planned order is firmed under finite capacity scheduling. Identifying it requires someone who has tested firming behavior extensively and understands the relationship between planned order dates, production order dates, and sales order requested dates in a finite capacity environment.

The teams most affected are often the ones working hardest. They are hitting their internal targets and missing customer commitments at the same time, and they cannot reconcile the two because the dates they are working from are not the dates that matter.

Kerry Kennedy is a fractional operations and D365 FSC consultant specializing in finite capacity planning implementations. If your team is consistently missing customer delivery dates despite hitting internal schedule targets, schedule a 30-minute conversation.