Quality Orders in D365 Production: Trigger Points, Sampling, and What to Do with Failures
I closed the shop floor execution article with a promise: quality management in production, quality orders, where to trigger them in the flow, and what to do with the material they catch. Here it is, and the thesis up front: the quality module in D365 Supply Chain Management is mostly a trigger table plus discipline. The software part is quick to configure. The expensive mistakes are inspecting in the wrong place and having no agreed plan for what happens when an inspection fails, and neither of those is a parameter.
WHAT A QUALITY ORDER ACTUALLY IS
A quality order is an inspection record: an item, a quantity to sample, a test group containing one or more tests, and a result per test. Tests come in two flavors. Quantitative tests carry a minimum, target, and maximum (a dimension, a torque, a concentration), and the result is a number judged against that window. Qualitative tests carry a test variable with defined outcomes (pass/fail, color match yes/no), and the result is a chosen outcome. The test group bundles the tests with their sequence, instruments, documents, and an acceptable quality level, and validation of the whole order is a pass/fail verdict computed from the individual results.
You can create quality orders manually, and for one-off investigations you will. But the real machinery is automatic generation through quality associations, because an inspection that depends on someone remembering to create it is an inspection that stops happening in week three.
QUALITY ASSOCIATIONS: THE TRIGGER TABLE
A quality association is a rule: for this reference type (purchase, production, route operation, sales, inventory), at this event and execution point (before or after registration, before or after report as finished, at a specific operation), for this item scope (a specific item, an item group, or all items), generate a quality order using this test group and this sampling plan. The collection of these rules is the trigger table, and it deserves the same design respect as location directives get in the warehouse: a small number of deliberate rules beats a sprawl of overlapping ones, and specific rules win over general ones, so keep the general rules few and the exceptions explicit.
WHERE TO TRIGGER IN THE PRODUCTION FLOW
For a manufactured item there are three natural trigger points, and the design question is which combination earns its cost:
• Material receipt (purchase registration). A quality association on the purchase reference type, triggered at registration, stops vendor defects at the door. This is the cheapest place to catch a defect; the material has consumed no capacity yet, and the disposition conversation is with the vendor, not with your own production manager.
• In-process, at a route operation. The route operation reference type generates a quality order when a specific operation reports, before downstream operations add value on top of a defect. The rule of thumb I push hard: inspect where the characteristic is created. If the critical dimension is cut at operation 20, inspect after operation 20, not at the end. Every operation a defect passes through roughly multiplies the cost of scrapping or reworking it.
• Report as finished. A production reference type association at report as finished is the last gate before the item becomes sellable stock. It belongs on items where a final functional check is meaningful, and on anything where a certificate of analysis ships with the goods.
SAMPLING AND BLOCKING: THE TWO DIALS
Each association carries an item sampling definition: a fixed quantity or a percentage of the triggering quantity, and a scope that decides whether one order covers the whole lot or one per batch. Sampling is where inspection cost is set, so put the effort where failure history says it belongs, not uniformly everywhere.
The second dial is blocking. The full blocking flag decides whether the entire triggering quantity is locked until the quality order validates, or only the sample itself. Full blocking at report as finished is the safe default for regulated products and for anything where an escape is expensive, but understand what it does to the warehouse: put-away waits, and if your wave design assumes finished goods are available the moment they hit the location, quality holds will surprise your shipping plan. If you run Advanced WMS with batch-tracked items, look at inventory statuses and batch disposition codes as the blocking mechanism instead, because they integrate cleanly with work creation and let you physically put stock away while keeping it unreservable.
WHEN A QUALITY ORDER FAILS
Validation fails, the quantity is blocked, and now the part nobody configured: what happens next? Decide it before go-live, as a standing rule per failure type, because a blocked pallet with no owner is how quality holds turn into aged inventory.
• Nonconformance first. A nonconformance order names the problem (internal, vendor, customer, or service request), ties it to the item and source, and carries corrections describing what must be done. Even when the physical disposition is obvious, the nonconformance is what turns a failed test into data you can analyze by cause next quarter.
• Rework. Where the defect is repairable, create a rework production order referencing the original batch; the route holds only the repair operations. The labor and material land on the rework order, visibly, instead of hiding inside the original order's actuals.
• Scrap. Where repair is not economic, scrap promptly. Scrap posts into production variances, which is exactly where it should be visible, and ties back to the feedback discipline from the shop floor article: scrap recorded at the operation that caused it is analyzable; scrap dumped at the last operation is just a number.
• Quarantine or vendor return. For undecided cases, move the stock to a quarantine location or warehouse so the decision has a deadline and a place. For failed incoming material, the disposition is a vendor return and a line on the vendor scorecard.
THE ROUTINE THAT MAKES IT WORTH IT
Like job feedback, quality data only pays for itself if someone reads it. The cadence I recommend: a daily look at open quality orders, because an inspection waiting three days is the quality version of the ghost job, blocking stock and hiding a decision. Weekly, failure rates by item and by test: a test that has not failed in a year on a stable process is a candidate for reduced sampling, and a test that fails often is pointing at a vendor, a route step, or a BOM choice that needs fixing rather than detecting. Quality orders are a sensor; the improvement happens upstream of them.
TAKEAWAYS
Build the trigger table deliberately: receipt inspection for vendor risk, operation-level inspection where the critical characteristic is created, a final gate only where it means something. Set sampling by failure history, choose blocking with the warehouse in the room, and decide the failure dispositions (nonconformance, rework, scrap, quarantine) as standing rules before the first pallet gets blocked. The module generates inspections reliably; whether they are the right inspections, in the right place, with a plan for failure, is a design job.
Next time I will look at batch tracking in production: tracking dimension groups, batch attributes, and tracing a defect from a customer complaint back to the exact production order and ingredient batches.
In this series: previous article Shop Floor Execution in D365: Production Floor Execution and Job Feedback Discipline
I closed the shop floor execution article with a promise: quality management in production, quality orders, where to trigger them in the flow, and what to do with the material they catch. Here it is, and the thesis up front: the quality module in D365 Supply Chain Management is mostly a trigger table plus discipline. The software part is quick to configure. The expensive mistakes are inspecting in the wrong place and having no agreed plan for what happens when an inspection fails, and neither of those is a parameter.
WHAT A QUALITY ORDER ACTUALLY IS
A quality order is an inspection record: an item, a quantity to sample, a test group containing one or more tests, and a result per test. Tests come in two flavors. Quantitative tests carry a minimum, target, and maximum (a dimension, a torque, a concentration), and the result is a number judged against that window. Qualitative tests carry a test variable with defined outcomes (pass/fail, color match yes/no), and the result is a chosen outcome. The test group bundles the tests with their sequence, instruments, documents, and an acceptable quality level, and validation of the whole order is a pass/fail verdict computed from the individual results.
You can create quality orders manually, and for one-off investigations you will. But the real machinery is automatic generation through quality associations, because an inspection that depends on someone remembering to create it is an inspection that stops happening in week three.
QUALITY ASSOCIATIONS: THE TRIGGER TABLE
A quality association is a rule: for this reference type (purchase, production, route operation, sales, inventory), at this event and execution point (before or after registration, before or after report as finished, at a specific operation), for this item scope (a specific item, an item group, or all items), generate a quality order using this test group and this sampling plan. The collection of these rules is the trigger table, and it deserves the same design respect as location directives get in the warehouse: a small number of deliberate rules beats a sprawl of overlapping ones, and specific rules win over general ones, so keep the general rules few and the exceptions explicit.
WHERE TO TRIGGER IN THE PRODUCTION FLOW
For a manufactured item there are three natural trigger points, and the design question is which combination earns its cost:
• Material receipt (purchase registration). A quality association on the purchase reference type, triggered at registration, stops vendor defects at the door. This is the cheapest place to catch a defect; the material has consumed no capacity yet, and the disposition conversation is with the vendor, not with your own production manager.
• In-process, at a route operation. The route operation reference type generates a quality order when a specific operation reports, before downstream operations add value on top of a defect. The rule of thumb I push hard: inspect where the characteristic is created. If the critical dimension is cut at operation 20, inspect after operation 20, not at the end. Every operation a defect passes through roughly multiplies the cost of scrapping or reworking it.
• Report as finished. A production reference type association at report as finished is the last gate before the item becomes sellable stock. It belongs on items where a final functional check is meaningful, and on anything where a certificate of analysis ships with the goods.
SAMPLING AND BLOCKING: THE TWO DIALS
Each association carries an item sampling definition: a fixed quantity or a percentage of the triggering quantity, and a scope that decides whether one order covers the whole lot or one per batch. Sampling is where inspection cost is set, so put the effort where failure history says it belongs, not uniformly everywhere.
The second dial is blocking. The full blocking flag decides whether the entire triggering quantity is locked until the quality order validates, or only the sample itself. Full blocking at report as finished is the safe default for regulated products and for anything where an escape is expensive, but understand what it does to the warehouse: put-away waits, and if your wave design assumes finished goods are available the moment they hit the location, quality holds will surprise your shipping plan. If you run Advanced WMS with batch-tracked items, look at inventory statuses and batch disposition codes as the blocking mechanism instead, because they integrate cleanly with work creation and let you physically put stock away while keeping it unreservable.
WHEN A QUALITY ORDER FAILS
Validation fails, the quantity is blocked, and now the part nobody configured: what happens next? Decide it before go-live, as a standing rule per failure type, because a blocked pallet with no owner is how quality holds turn into aged inventory.
• Nonconformance first. A nonconformance order names the problem (internal, vendor, customer, or service request), ties it to the item and source, and carries corrections describing what must be done. Even when the physical disposition is obvious, the nonconformance is what turns a failed test into data you can analyze by cause next quarter.
• Rework. Where the defect is repairable, create a rework production order referencing the original batch; the route holds only the repair operations. The labor and material land on the rework order, visibly, instead of hiding inside the original order's actuals.
• Scrap. Where repair is not economic, scrap promptly. Scrap posts into production variances, which is exactly where it should be visible, and ties back to the feedback discipline from the shop floor article: scrap recorded at the operation that caused it is analyzable; scrap dumped at the last operation is just a number.
• Quarantine or vendor return. For undecided cases, move the stock to a quarantine location or warehouse so the decision has a deadline and a place. For failed incoming material, the disposition is a vendor return and a line on the vendor scorecard.
THE ROUTINE THAT MAKES IT WORTH IT
Like job feedback, quality data only pays for itself if someone reads it. The cadence I recommend: a daily look at open quality orders, because an inspection waiting three days is the quality version of the ghost job, blocking stock and hiding a decision. Weekly, failure rates by item and by test: a test that has not failed in a year on a stable process is a candidate for reduced sampling, and a test that fails often is pointing at a vendor, a route step, or a BOM choice that needs fixing rather than detecting. Quality orders are a sensor; the improvement happens upstream of them.
TAKEAWAYS
Build the trigger table deliberately: receipt inspection for vendor risk, operation-level inspection where the critical characteristic is created, a final gate only where it means something. Set sampling by failure history, choose blocking with the warehouse in the room, and decide the failure dispositions (nonconformance, rework, scrap, quarantine) as standing rules before the first pallet gets blocked. The module generates inspections reliably; whether they are the right inspections, in the right place, with a plan for failure, is a design job.
Next time I will look at batch tracking in production: tracking dimension groups, batch attributes, and tracing a defect from a customer complaint back to the exact production order and ingredient batches.
In this series: previous article Shop Floor Execution in D365: Production Floor Execution and Job Feedback Discipline
No replies yet. Be the first to respond!