{"id":5576,"date":"2026-11-19T17:44:39","date_gmt":"2026-11-19T09:44:39","guid":{"rendered":"https:\/\/www.corvelanmag.com\/?p=5576"},"modified":"2026-10-30T14:59:58","modified_gmt":"2026-10-30T06:59:58","slug":"metal-detector-test-failure-product-hold","status":"publish","type":"post","link":"https:\/\/www.corvelanmag.com\/de\/metal-detector-test-failure-product-hold\/","title":{"rendered":"Routinepr\u00fcfung des Metalldetektors fehlgeschlagen: So legen Sie die Entscheidung zur Produktsperrung fest"},"content":{"rendered":"\n<style>\n.corv-hold { color:#1f2937; font:inherit; font-size:17px; line-height:1.75; display:block; float:none; clear:both; overflow-wrap:break-word; }\n.corv-hold * { box-sizing:border-box; }\n.corv-hold .mdh-section,.corv-hold .mdh-intro,.corv-hold .mdh-toc { display:block; float:none; clear:both; margin:0 0 24px; padding:22px; border:1px solid #d1d5db; border-radius:16px; background:#fff; }\n.corv-hold .mdh-section { border-top:4px solid #374151; box-shadow:0 2px 8px rgba(31,41,55,.04); }\n.corv-hold .mdh-intro,.corv-hold .mdh-toc,.corv-hold .mdh-faq { background:#f3f4f6; }\n.corv-hold h2,.corv-hold h3 { color:#1f2937; line-height:1.3; font-weight:700; overflow-wrap:break-word; }\n.corv-hold h2 { font-size:30px; margin:0 0 18px; scroll-margin-top:96px; }\n.corv-hold h3 { font-size:24px; margin:24px 0 12px; }\n.corv-hold p { margin:0 0 16px; }\n.corv-hold p:last-child,.corv-hold ol:last-child,.corv-hold ul:last-child { margin-bottom:0; }\n.corv-hold ol,.corv-hold ul { padding-left:1.45em; margin:12px 0 18px; }\n.corv-hold li { margin:0 0 10px; }\n.corv-hold a { color:#1f2937; text-decoration:underline; text-underline-offset:3px; }\n.corv-hold a:focus-visible { outline:3px solid #374151; outline-offset:4px; }\n.corv-hold .mdh-toc strong { display:block; margin-bottom:10px; }\n.corv-hold .mdh-toc a { white-space:normal; overflow-wrap:anywhere; }\n.corv-hold .mdh-table { display:block; overflow-x:auto; margin:18px 0; }\n.corv-hold table { width:100%; min-width:540px; border-collapse:collapse; background:#fff; font-size:1em; }\n.corv-hold th,.corv-hold td { padding:12px; text-align:left; vertical-align:top; border:1px solid #d1d5db; }\n.corv-hold th { color:#fff; background:#374151; font-weight:700; }\n.corv-hold .mdh-note,.corv-hold .mdh-cta { display:block; background:#f3f4f6; border-left:4px solid #374151; padding:18px; margin:20px 0; }\n.corv-hold .mdh-note h3 { margin-top:0; }\n.corv-hold .mdh-button { display:inline-block; background:#374151; color:#fff; border-radius:8px; padding:12px 18px; text-decoration:none; font-weight:700; }\n.corv-hold .mdh-media { display:block; float:none; clear:both; margin:18px 0 22px; }\n.corv-hold .mdh-media img { display:block; float:none; max-width:100%; height:auto; margin-inline:auto; }\n.corv-hold .mdh-faq h3 { padding-top:18px; border-top:1px solid #d1d5db; }\n@media (max-width:600px) {\n .corv-hold { font-size:16px; }\n .corv-hold .mdh-section,.corv-hold .mdh-intro,.corv-hold .mdh-toc { padding:18px; margin-bottom:18px; border-radius:12px; }\n .corv-hold .mdh-section { border-top-width:3px; }\n .corv-hold h2 { font-size:24px; }\n .corv-hold h3 { font-size:20px; }\n .corv-hold th,.corv-hold td { padding:10px; }\n .corv-hold .mdh-note,.corv-hold .mdh-cta { padding:14px; }\n}\n<\/style>\n<article class=\"corv-hold\">\n<div class=\"mdh-intro\"><p><strong>After a metal detector test failure, put product on hold from the last valid, successful system check through the point when affected product flow was brought under control.<\/strong> Stop further release, identify the affected stock, and keep it segregated while the cause and product disposition are reviewed.<\/p>\n<p>A product hold means the stock cannot be used or shipped until an authorized decision is recorded. It does not mean every pack contains metal. The problem is that the required inspection result is uncertain. <strong>A successful retest may support restarting the line; it does not, by itself, clear the product already on hold.<\/strong><\/p>\n<\/div><nav aria-label=\"Article contents\" class=\"mdh-toc\"><strong>In this article<\/strong><ol><li><a href=\"#first-actions\">What should you do as soon as a routine check fails?<\/a><\/li><li><a href=\"#hold-boundary\">How far back should the product hold go?<\/a><\/li><li><a href=\"#identify-product\">How do you turn a time window into identifiable product?<\/a><\/li><li><a href=\"#failure-type\">Does a reject failure need the same hold as a detection failure?<\/a><\/li><li><a href=\"#restart\">What must pass before production can restart?<\/a><\/li><li><a href=\"#reinspection\">How should held product be re-inspected and released?<\/a><\/li><li><a href=\"#decision-record\">What should the product-hold decision record contain?<\/a><\/li><li><a href=\"#reduce-exposure\">How can the next failure affect less product?<\/a><\/li><li><a href=\"#faq\">Product-hold questions after a failed metal detector check<\/a><\/li><\/ol><\/nav><section class=\"mdh-section\"><h2 id=\"first-actions\">What should you do as soon as a routine check fails?<\/h2>\n<div class=\"mdh-media\"><img loading=\"lazy\" src=\"https:\/\/www.corvelanmag.com\/wp-content\/uploads\/2026\/10\/corvelan-offline-packaged-product-staging-illustration-20261030-v1.webp\" alt=\"Closed cartons and sealed pouches on a separate off-line staging table\" width=\"1200\" height=\"900\" loading=\"lazy\" decoding=\"async\" \/><\/div>\n\n<p><strong>Control the affected product first, then investigate the failure. Do not keep releasing stock while someone repeats the test or adjusts the detector.<\/strong><\/p>\n<ol>\n<li><strong>Stop the affected flow.<\/strong> Use the line&#8217;s safe stop procedure. Prevent more product from passing through an ineffective inspection or reject system. If an approved alternative inspection route is available, keep its output separately identified.<\/li>\n<li><strong>Block product release.<\/strong> Tell production, the warehouse and the person responsible for quality decisions. Block picking and dispatch for potentially affected stock, including finished cases already moved away from the line.<\/li>\n<li><strong>Identify and segregate the stock.<\/strong> Apply hold identification to the physical product and its inventory record. Include loose packs, partly filled cases, pallets, rework and transfers that fall within the affected range.<\/li>\n<li><strong>Preserve the first failure.<\/strong> Record the time, detector identity, product, selected program, test-piece identity and what actually happened. Save available event logs before changing settings.<\/li>\n<li><strong>Start the equipment investigation.<\/strong> Maintenance identifies and corrects the fault; the quality team controls the affected product and its final disposition.<\/li>\n<\/ol>\n<p>Keep the test pack and test piece out of saleable stock. If maintenance requires access to moving or electrical parts, isolate the equipment before that work begins.<\/p>\n<\/section>\n<section class=\"mdh-section\"><h2 id=\"hold-boundary\">How far back should the product hold go?<\/h2>\n<p><strong>Use the last documented check that demonstrated the required detection and line response for the product being inspected. Extend the hold when records cannot establish that boundary reliably.<\/strong> A shift change, new pallet or new lot number does not prove the detector was working.<\/p>\n<h3>What counts as the last successful check?<\/h3>\n<p><strong>A valid check must cover the required detection and product-control response for the actual run.<\/strong> Read the original test record, not just a green \u201cPASS\u201d on a summary. Match the detector, product and program to the run. Then check the required metal types and sizes, test positions, test sequence, and the actual alarm, stop or reject result.<\/p>\n<p>For an automatic reject line, a detection signal alone leaves an important question unanswered: did the challenged pack leave the saleable flow? For a belt-stop system, the required stop and controlled removal must have worked. A test on a previous recipe may not establish performance for a changed product.<\/p>\n<p>The <a href=\"https:\/\/www.mt.com\/dam\/product_organizations\/pi\/Service\/Compliance\/catalogue\/PI_TestSamples_Catalogue_EN.pdf\" rel=\"noopener nofollow\" target=\"_blank\">METTLER TOLEDO testing catalogue, pages 6\u20138<\/a> links testing with the ability to isolate affected product and calls for records of detection, rejection, failures and corrective action.<\/p>\n<h3>When should you widen the hold?<\/h3>\n<p><strong>Widen it whenever uncertain records, changed conditions or mixed stock prevent you from reliably identifying a smaller affected group.<\/strong> Use the following findings to set that scope.<\/p>\n<div class=\"mdh-table\"><table><thead><tr><th scope=\"col\">What you find<\/th><th scope=\"col\">How to define the affected range<\/th><\/tr><\/thead><tbody>\n<tr><td>The previous check is missing or incomplete.<\/td><td>Go back to the most recent point with adequate evidence of effective control. If none can be established, include the run or connected lots that remain uncertain.<\/td><\/tr>\n<tr><td>The product or program changed after that check.<\/td><td>Find the changeover record and the first valid check for the new conditions. Include output whose inspection has not been demonstrated.<\/td><\/tr>\n<tr><td>The line continued after the failure was noticed.<\/td><td>Include product through the actual stop or effective diversion, not just through the failed-test time.<\/td><\/tr>\n<tr><td>Clocks disagree or product waits in a downstream buffer.<\/td><td>Use event sequences, counters and transfer records to map the detector passage to cases. Include uncertain boundary cases.<\/td><\/tr>\n<tr><td>Product was mixed, repacked or returned as rework.<\/td><td>Trace every destination. Include a whole connected container or lot when the affected portion cannot be separated reliably.<\/td><\/tr>\n<tr><td>Some stock has already shipped.<\/td><td>Keep it in the affected-stock list and start the site&#8217;s incident escalation and distribution trace. The quality lead determines the required market or customer action.<\/td><\/tr>\n<\/tbody><\/table><\/div>\n<p><strong>Do not narrow the hold merely because a technician found a fault at a particular time.<\/strong> Any proposed reduction needs evidence that the excluded product had effective control and approval under the site&#8217;s quality procedure.<\/p>\n<\/section>\n<section class=\"mdh-section\"><h2 id=\"identify-product\">How do you turn a time window into identifiable product?<\/h2>\n<p><strong>Map when product crossed the detector to its pack, case, pallet and storage records. Then reconcile the quantity and location of every affected unit.<\/strong> A time range is useful only when warehouse staff can find and block the stock it describes.<\/p>\n<p>Start with detector event times and production counters. Link them to case labels, pallet scans and warehouse movements. Record what each timestamp means: filling time, detector passage, case closing and pallet completion are different events. A full pallet may contain packs from both sides of the boundary.<\/p>\n<div class=\"mdh-note\">\n<h3>A worked example: include the delay before the line stops<\/h3>\n<p>Suppose the last valid check finished at <strong>09:00<\/strong>. A routine check fails at <strong>10:10<\/strong>, but product continues until the line stops at <strong>10:15<\/strong>. Assume production records show a steady 40 packs per minute over that interval, with no downtime or added rework.<\/p>\n<p><strong>75 minutes \u00d7 40 packs\/minute = 3,000 packs.<\/strong> At 12 packs per case, that is <strong>250 case-equivalents<\/strong>. Stopping the calculation at 10:10 would omit 200 packs produced during the five-minute delay.<\/p>\n<p>Use the 3,000-pack figure to cross-check the case and pallet list. Physically hold every case containing affected packs, including partly filled and mixed boundary cases; the number of cases held can therefore exceed 250. Locate any separate loose packs or transfers as well.<\/p>\n<\/div>\n<p>When output varies, use actual counts and run records instead of multiplying by the nameplate rate. Reconcile normal rejects, test packs and rework separately so they are neither omitted nor counted twice. If the records cannot distinguish the boundary, keep the larger identifiable group on hold.<\/p>\n<p>For unpackaged product, use tote, bin or batch genealogy and measured transfer quantities. If affected material entered a shared hopper and mixed with other stock, its original production time alone cannot separate it again.<\/p>\n<\/section>\n<section class=\"mdh-section\"><h2 id=\"failure-type\">Does a reject failure need the same hold as a detection failure?<\/h2>\n<p><strong>Yes, when the failure prevents the required product-control result. Finding the metal is only one part of the job; the system must also keep the affected product out of the accepted flow.<\/strong><\/p>\n<div class=\"mdh-table\"><table><thead><tr><th scope=\"col\">Failed result<\/th><th scope=\"col\">Evidence to examine<\/th><th scope=\"col\">Where the correction starts<\/th><\/tr><\/thead><tbody>\n<tr><td>The required test piece is not detected.<\/td><td>Test-piece identity, product program, position, product condition and detector event record.<\/td><td>Establish whether the test setup, product conditions or detector performance changed.<\/td><\/tr>\n<tr><td>The detector signals, but the challenged pack stays on the line.<\/td><td>The actual pack destination, reject command, actuator movement and available air or power.<\/td><td>Restore the commanded removal and prove it with the product.<\/td><\/tr>\n<tr><td>A neighboring pack is rejected instead.<\/td><td>Pack sensor, belt speed, product spacing and the sequence from detection to rejection.<\/td><td>Correct product tracking and timing; prove removal of the challenged pack.<\/td><\/tr>\n<tr><td>The belt should stop, but the affected product continues downstream.<\/td><td>Stop command, actual stopping position and downstream transfer.<\/td><td>Restore the stop sequence and controlled removal.<\/td><\/tr>\n<tr><td>A required reject-confirmation or other fail-safe function fails.<\/td><td>Sensor state, alarm and interlock events against the specified control sequence.<\/td><td>Restore and test that function as well as detection and rejection.<\/td><\/tr>\n<\/tbody><\/table><\/div>\n<p>These checks guide the investigation; they do not establish a shorter hold by themselves. USDA&#8217;s <a href=\"https:\/\/www.ams.usda.gov\/sites\/default\/files\/media\/QAD%20Instruction%20609%20-%20Metal%20Detection.pdf\" rel=\"noopener nofollow\" target=\"_blank\">QAD Instruction 609, page 2<\/a>, for products covered by its specifications, also treats failure to reject as a reason to retain product back to the last acceptable check.<\/p>\n<p>A wrong test piece or a damaged test pack needs investigation too. Preserve that finding and repeat the correct procedure while the affected stock remains controlled. A later pass should not overwrite the first failure.<\/p>\n<\/section>\n<section class=\"mdh-section\"><h2 id=\"restart\">What must pass before production can restart?<\/h2>\n<p><strong>The corrected system must pass the site&#8217;s required challenge tests under the intended production conditions, and the designated person must authorize restart.<\/strong> Keep the held stock identified while new production starts.<\/p>\n<p>First record what failed and what was changed. For an intermittent problem, reproduce the relevant conditions where safe: normal pack spacing, line speed, product condition and the operating state associated with the failure. One isolated successful pass can miss a recurring timing or product-effect problem.<\/p>\n<p>Then run the complete approved test sequence. Use the required metal types, sizes, positions and repetitions with representative product and packaging. Observe the challenged pack through the actual stop or reject action. Test the relevant fault alarms and interlocks included in the line&#8217;s specified design. Recover every test piece and test pack.<\/p>\n<p>If a recipe, package or control change takes the system outside its established operating conditions, establish that the new setup can meet the required result before routine production. The <a href=\"https:\/\/www.mt.com\/us\/en\/home\/library\/white-papers\/product-inspection\/validation-verification-monitoring.html\" rel=\"noopener nofollow\" target=\"_blank\">METTLER TOLEDO overview of validation, verification and monitoring<\/a> explains why establishing capability and checking ongoing performance serve different purposes.<\/p>\n<p><strong>Record two separate decisions:<\/strong> permission to restart the corrected line, and disposition of the historical stock. The first needs a functioning system. The second also needs an identified product range, an accepted inspection or disposition method, and a completed product record.<\/p>\n<\/section>\n<section class=\"mdh-section\"><h2 id=\"reinspection\">How should held product be re-inspected and released?<\/h2>\n<p><strong>Where re-inspection is the approved disposition, run the entire affected quantity through a system proven suitable for that product and required metal target. Release only the identified stock covered by satisfactory results and an authorized disposition record.<\/strong><\/p>\n<h3>How do you keep re-inspection under control?<\/h3>\n<p><strong>Use an approved route with effective detection and removal, separate stock by inspection status, and account for every unit.<\/strong> Then follow the sequence below.<\/p>\n<ol>\n<li><strong>Define the route and acceptance criteria.<\/strong> Use the repaired detector or another suitable system. Establish performance with the actual product, packaging and presentation; a spare detector&#8217;s display setting is not enough.<\/li>\n<li><strong>Keep the streams separate.<\/strong> Clearly identify stock awaiting inspection, accepted stock and rejects. Arrange handling so no pack can bypass inspection or return unmarked to the waiting stock.<\/li>\n<li><strong>Test the route before use.<\/strong> Challenge detection and the required product-removal response. Run the stock at the speed and spacing for which that result has been established.<\/li>\n<li><strong>Maintain control throughout.<\/strong> Perform the required checks during and at the end of the re-inspection run. If a check fails, put the newly uncertain portion back under hold, using its last valid check and traceability records.<\/li>\n<li><strong>Reconcile the stock and obtain release approval.<\/strong> Account for accepted units, rejects awaiting investigation, disposal and any other controlled destination.<\/li>\n<\/ol>\n<p>Keep genuinely rejected product separate from the broader stock held because the inspection system failed. A pack suspected of containing metal needs investigation and a defined disposition. Do not keep passing it through until it stops alarming and then treat it as acceptable.<\/p>\n<h3>What if re-inspection is not reliable or practical?<\/h3>\n<p><strong>Keep the product on hold while an effective alternative disposition is established.<\/strong> For example, outer packaging may prevent the available system from reaching the required target. A controlled unpacking and re-inspection process may be suitable, but it must also protect product hygiene, identity and handling conditions.<\/p>\n<p>FDA&#8217;s <a href=\"https:\/\/www.fda.gov\/downloads\/Food\/GuidanceRegulation\/UCM252440.pdf\" rel=\"noopener nofollow\" target=\"_blank\">fish and fishery products guidance, Chapter 20, pages 388\u2013389<\/a>, describes holding affected product for suitable detection, diversion or disposal, alongside actions to restore control. It is guidance for that sector. Your quality team selects the applicable disposition under your product-safety plan and customer requirements.<\/p>\n<p>If held food has exceeded its permitted storage or handling conditions, a successful metal inspection does not resolve that separate problem. Include it in the disposition decision.<\/p>\n<\/section>\n<section class=\"mdh-section\"><h2 id=\"decision-record\">What should the product-hold decision record contain?<\/h2>\n<p><strong>Record what is held, why that range was chosen, what happened to every affected quantity, and who approved each decision.<\/strong> Someone taking over the next shift should be able to locate the stock without reconstructing the incident from memory.<\/p>\n<div class=\"mdh-table\"><table><thead><tr><th scope=\"col\">Record<\/th><th scope=\"col\">Details that make the decision usable<\/th><\/tr><\/thead><tbody>\n<tr><td>Failure and control point<\/td><td>Detector ID, product, lot, program, failed test-piece identity, first failure time, observed result and actual stop or diversion time.<\/td><\/tr>\n<tr><td>Hold boundary and evidence<\/td><td>Last valid check and its original record; reasons for extending the range; clock, buffer or mixing uncertainties.<\/td><\/tr>\n<tr><td>Physical scope<\/td><td>Pack or case codes, pallet\/tote IDs, quantities, locations, inventory blocks, transfers and dispatch references.<\/td><\/tr>\n<tr><td>Correction and restart<\/td><td>Fault evidence, changes made, complete challenge results, test-piece recovery, restart approval and time.<\/td><\/tr>\n<tr><td>Product disposition<\/td><td>Re-inspection equipment and method, run checks, accepted quantity, unresolved rejects, disposal and other controlled destinations.<\/td><\/tr>\n<tr><td>Authorization<\/td><td>Names, roles, dates and times for hold, restart and product disposition; supporting record references.<\/td><\/tr>\n<\/tbody><\/table><\/div>\n<p>For each held group, the starting quantity must equal the sum of accepted product, rejects still controlled, disposal and other documented destinations. <strong>A missing quantity remains an open traceability issue.<\/strong> Do not close the incident by changing the starting quantity to match what was found.<\/p>\n<p>For the example above, an initial decision could read: \u201cHold stock containing the 3,000 packs inspected between 09:00 and 10:15. Block the associated case and pallet IDs. Last valid check: 09:00; failed check: 10:10; flow stopped: 10:15. Disposition remains open pending investigation and controlled re-inspection.\u201d Attach the actual stock list and name the person authorizing the hold.<\/p>\n<p>Production provides run details, warehouse staff locate and block stock, maintenance supplies fault and correction evidence, and the designated quality authority approves disposition. For an industrial quality-control application, use the responsible quality role and the agreed product specification; a detector is not automatically a food-safety critical control point.<\/p>\n<\/section>\n<section class=\"mdh-section\"><h2 id=\"reduce-exposure\">How can the next failure affect less product?<\/h2>\n<p><strong>Choose test intervals and stock controls that let you identify and intercept the uncertain output before it leaves your control.<\/strong> Also reduce the delay between a failed check, stopping the flow and blocking dispatch.<\/p>\n<p>Review how quickly product reaches the warehouse or loading area, how much a buffer can mix, and how reliably case codes link back to inspection. A shorter test interval reduces the potential window, but poor records or slow isolation can still leave a large hold. Set the frequency from the site&#8217;s risk assessment and applicable customer requirements rather than borrowing an hourly rule from another factory.<\/p>\n<p>For our <a href=\"https:\/\/www.corvelanmag.com\/products\/ljt-f-conveyor-metal-detector\/\">LJT-F conveyor metal detector<\/a>, product size, detector opening, packaging, speed and the required alarm, stop or reject response belong in the line review. The final hardware and sequence follow the agreed configuration. Build the hold and release procedure around what the installed line actually does.<\/p>\n<p><strong>After a metal detector test failure, the product-hold decision should leave no uncertain stock available for release:<\/strong> define the range, find it, restore effective inspection, and document the disposition separately from restart.<\/p>\n<div class=\"mdh-cta\"><p><strong>Need to review your detector and line response?<\/strong> Send us the detector model, product and packaging, required metal target, failed test result, belt speed, product spacing and required stop or reject action. Use the message field on our contact page; after first contact, send relevant logs or layout details to sales@corvelanmag.com.<\/p><p><a class=\"mdh-button\" href=\"https:\/\/www.corvelanmag.com\/contact-us\/\">Discuss your metal detection setup<\/a><\/p><\/div>\n<\/section>\n<section class=\"mdh-section mdh-faq\" id=\"faq\"><h2>Product-hold questions after a failed metal detector check<\/h2>\n<h3>Can we release the lot if a repeat test passes immediately?<\/h3><p><strong>A repeat pass alone is not enough.<\/strong> Keep the first failure in the record and investigate why the results differ. The designated quality person must assess the affected range and approve its disposition; permission to restart the line is a separate decision.<\/p>\n<h3>Do we need to hold product if only the stainless-steel test fails?<\/h3><p><strong>Yes, if stainless steel is one of the required detection targets.<\/strong> A ferrous test pass does not resolve that failure. Keep the affected product stream on hold while the stainless-steel result and the complete system response are restored and the stock is assessed.<\/p>\n<h3>What if the test piece cannot be found?<\/h3><p><strong>Treat the missing piece as a potential foreign-material incident as well as a failed or incomplete test.<\/strong> Trace the test pack, reject container and downstream product destinations. Keep the potentially affected stock controlled until the piece is recovered or an effective disposition addresses its possible presence.<\/p>\n<h3>Is a sample of the held lot enough for release?<\/h3><p><strong>A few passing packs do not establish that the rest of the uncertain lot was effectively inspected.<\/strong> Where re-inspection is the approved action, cover the entire affected quantity. Any different disposition needs a documented technical basis and authorization under the site&#8217;s quality procedure.<\/p>\n<h3>Must product waiting upstream of the detector be included?<\/h3><p><strong>Product that has not crossed the failed control point and remains reliably separated can stay identified as awaiting inspection.<\/strong> Pass it through the restored, effective system before acceptance. Mixing, rework or exposure to another metal source may require a wider assessment.<\/p>\n<h3>Can a second detector clear the affected product?<\/h3><p><strong>Yes, where its capability has been established for the actual product, packaging and required metal target, its removal response works, and every affected unit takes that controlled route.<\/strong> Record the checks, quantities and authorized disposition. The presence of a downstream detector alone is not sufficient.<\/p>\n<\/section>\n<\/article>\n<script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Can we release the lot if a repeat test passes immediately?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"A repeat pass alone is not enough. Keep the first failure in the record and investigate why the results differ. The designated quality person must assess the affected range and approve its disposition; permission to restart the line is a separate decision.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Do we need to hold product if only the stainless-steel test fails?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes, if stainless steel is one of the required detection targets. A ferrous test pass does not resolve that failure. Keep the affected product stream on hold while the stainless-steel result and the complete system response are restored and the stock is assessed.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What if the test piece cannot be found?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Treat the missing piece as a potential foreign-material incident as well as a failed or incomplete test. Trace the test pack, reject container and downstream product destinations. Keep the potentially affected stock controlled until the piece is recovered or an effective disposition addresses its possible presence.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Is a sample of the held lot enough for release?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"A few passing packs do not establish that the rest of the uncertain lot was effectively inspected. Where re-inspection is the approved action, cover the entire affected quantity. Any different disposition needs a documented technical basis and authorization under the site's quality procedure.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Must product waiting upstream of the detector be included?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Product that has not crossed the failed control point and remains reliably separated can stay identified as awaiting inspection. Pass it through the restored, effective system before acceptance. Mixing, rework or exposure to another metal source may require a wider assessment.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Can a second detector clear the affected product?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes, where its capability has been established for the actual product, packaging and required metal target, its removal response works, and every affected unit takes that controlled route. Record the checks, quantities and authorized disposition. The presence of a downstream detector alone is not sufficient.\"\n      }\n    }\n  ]\n}\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>After a metal detector test failure, put product on hold from the last valid, successful system check through the point when affected product flow was brought under control. Stop further release, identify the affected stock, and keep it segregated while the cause and product disposition are reviewed. A product hold means the stock cannot be [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":5648,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5576","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.corvelanmag.com\/de\/wp-json\/wp\/v2\/posts\/5576","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.corvelanmag.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.corvelanmag.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.corvelanmag.com\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.corvelanmag.com\/de\/wp-json\/wp\/v2\/comments?post=5576"}],"version-history":[{"count":2,"href":"https:\/\/www.corvelanmag.com\/de\/wp-json\/wp\/v2\/posts\/5576\/revisions"}],"predecessor-version":[{"id":5657,"href":"https:\/\/www.corvelanmag.com\/de\/wp-json\/wp\/v2\/posts\/5576\/revisions\/5657"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.corvelanmag.com\/de\/wp-json\/wp\/v2\/media\/5648"}],"wp:attachment":[{"href":"https:\/\/www.corvelanmag.com\/de\/wp-json\/wp\/v2\/media?parent=5576"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.corvelanmag.com\/de\/wp-json\/wp\/v2\/categories?post=5576"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.corvelanmag.com\/de\/wp-json\/wp\/v2\/tags?post=5576"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}