Forum Discussion
Business Central - Blocking External Operations Until Previous Operation Quality
Hello Team,
We are evaluating the Quality Management process in Microsoft Dynamics 365 Business Central for a Release Production scenario.
Our requirement is to control the production workflow in such a way that an External Operation (Subcontracting Operation) cannot be processed or posted unless the previous operation's quality inspection has been completed and approved.
Business Requirement
- Production consists of multiple routing operations.
- Quality inspection is required after specific operations.
- If an inspection result is pending, failed, or not approved, the next operation (especially an external/subcontracting operation) should not be allowed to proceed.
- The system should enforce this control automatically to prevent production from moving to the next stage without quality clearance.
Questions
- Does standard Business Central provide any functionality to block the posting or execution of a subsequent routing operation until the previous operation's quality inspection is completed?
- If using a Quality Management add-on, how is this scenario typically handled?
- Is there a standard quality status (Released, Accepted, Rejected, Hold, etc.) that can be linked with routing operation progression?
- Can the system prevent an External Operation from being posted when the previous operation's inspection order is still open?
- Has anyone implemented similar process controls in Business Central, and what approach was used (standard functionality, workflow, or customization)?
Any guidance, best practices, or recommendations would be greatly appreciated.
2 Replies
Your requirement is to stop the next subcontracting operation until the preceding operation’s inspection is approved. Microsoft’s Quality Management extension provides production-output inspection generation and inventory/transaction blocking, but those capabilities alone do not establish that every subsequent routing operation is gated.
Inspection status and result are separate. A PASS result can still belong to an Open inspection; Finished is a separate state. Microsoft documents “Allow finished only,” result-based transaction restrictions, and workflows that block lots on inspection creation and unblock them on passing completion.
In a sandbox, configure the production inspection rule and test the exact subcontracting posting path with open, failed and finished-passed inspections. Include purchase receipts and production journals used in your process. If the next operation can proceed, have your partner implement or select an extension that validates the predecessor inspection at those posting points. Third-party quality statuses and enforcement depend on that add-on’s documented behavior.
Microsoft Dynamics 365 Business Central does not natively enforce a “hard stop” that blocks subcontracting/external operations until the previous routing operation quality inspection is approved. However, the built‑in Quality Management extension (introduced in 2026 release wave 1) provides workflows, lot blocking, and inspection status controls that can be configured to achieve this requirement. For stricter enforcement, organizations typically combine standard workflows with customization or third‑party add‑ons.
https://learn.microsoft.com/en-us/dynamics365/business-central/qms-lot-blocking-unblocking
