Control must link dispatch, intended service and physical return, distinguishing completed items, surplus and material still held by the partner.
Index
An external operation may return parts in multiple batches and generate leftovers; closing everything on final receipt hides intermediate differences.
The rule that changes the scope
Control must link dispatch, intended service and physical return, distinguishing completed items, surplus and material still held by the partner.
An ERP may manage movements; a custom module supports operation-level tracking and returns split across deliveries.
The partner can return unused material alongside processed parts. Those movements need different review categories even when arriving in one vehicle. The application should allow discrepancy investigation without blocking the physical return record. Also distinguish administrative closure from technical acceptance: receiving material does not mean the processing service was accepted. Tax or accounting documents, when involved, require separately scoped integrations and professional assessment rather than assumptions within this operational module.
Specify operational deliverables
- Connect each dispatch with its external operation and originating production order.
- Separate returned quantities by condition and required production continuation.
- Keep the balance under the partner's responsibility after every partial return.
Test the exception before acceptance
In a hypothetical scenario, a partner returns some finished parts and surplus; the order must explain remaining material without declaring the whole operation finished.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring a partially returned dispatch and the check used to reconcile supplied material.