Warehouse Pick Substitution Approval Accuracy

Select the original order line and compare its requested SKU with the proposed alternative, because an approved substitute for one model or revision may not fit another configuration. Treat the system's substitute list as a candidate source, not universal permission, since product engineering and customer terms can impose different gates before the warehouse changes an order.

Oracle documents substitute-item use during pick release for transfer orders, but system configuration is not blanket permission to change a customer order. Check the alternative's size, rating, expiry, certification and intended use, because a visually similar part can create a safety or warranty problem that a barcode match will not detect.

Separate technical suitability from commercial permission, since even a fitting part may change price, delivery promise or contract terms and require an authorised customer decision. A warehouse supervisor's technical sign-off is not necessarily customer consent, so when the alternate changes the promised arrival or commercial amount, bring the decision to the authorised customer or commercial owner as required.

Use the current approved-list revision and effective date, because a component superseded last month should not be selected from an obsolete screen or printed sheet, and preserve the revision used at pick time since a replacement approved after dispatch cannot make the earlier physical pick correct retroactively. Compare actual quantities in a common unit and check pack contents and shelf life, as one carton of the alternate can contain a different number of usable pieces than one carton of the original.

Check that alternative stock is actually available and released for shipment, since an engineering-approved SKU that is on quality hold cannot solve the current shortage. Record the authoriser, approval scope and time before release, because a backdated signature documents a later review but does not make an earlier unapproved dispatch accurate.

For manual emergency picks, link the event to the original order and retain who approved each gate, so a reason code entered afterwards remains distinguishable from timely authorisation, and keep reversals and manual changes in the audit history. A change back to the original SKU before dispatch should not inflate the denominator of completed substitutions.

At pick or pack, verify the physical variant and lot, since a correct approval with a different item in the box is still an error under an actual-dispatch measure, and lot and serial records should follow the actual item delivered. If a customer refuses the offer, keep the original order line under the authorised short, cancellation or back-order process rather than recording a completed substitute merely because one was proposed.

State which substitution events are eligible, as a proposed alternative that never shipped may belong in the offer history while the actual-dispatch rate counts the completed pick against required approvals. Where no alternate meets specification, escalate instead of forcing a replacement to hit the service target, and for regulated or safety-critical goods retain the qualified product owner's documented judgment, because the quality gate matters more than this operational percentage.

Show unauthorised dispatches separately from substitutions that were correctly proposed and refused, since a single accuracy rate cannot explain whether the failure was product fit, consent or packing. Capture why the original item was unavailable and review complaints, returns and recurring shortages beside this rate, because frequent substitutions for one SKU can reveal a planning or supplier problem, and a returned substitute should be inspected for fit, quantity or customer expectation without changing the historical approval timestamp.