Write the SOP around linked order lines, a visible exception decision, authorized parcel contents, and separate carrier-handoff evidence. The procedure should help the next person see what is missing instead of making a checkbox stand in for a decision.
Docsie's public pick, pack, and ship outline separates release holds, picking quantities and exceptions, packing, labeling, and handoff confirmation. This original small-order example uses those workflow distinctions without adopting its filled example, packing rules, or automation claims. Docsie's fulfillment SOP outline
Preserve the order and unit before tracing the work
The fictional order is O01. SKU-N identifies notebooks and SKU-C identifies cards. Both use the unit piece. Actual authorized order references, source locations, reviewer, packing materials, address, and carrier requirements remain TO CONFIRM for real use.
| O01 order line | Ordered pieces | Recorded picked pieces | Short quantity |
|---|---|---|---|
| SKU-N notebooks | 3 | 3 | 0 |
| SKU-C cards | 2 | 1 | 1 |
| Total | 5 | 4 | 1 |
These are supplied illustrative counts, not a real warehouse observation. Keep the ordered and picked quantities in separate fields. Do not change the ordered card quantity to one to make the pick appear complete, substitute another SKU, or update inventory from this review.
Make the short-pick decision a gate
First verify the actual authorized order and its hold status in the maintained workflow. The picker then records the SKU, location reference, unit, and actual count according to the organization's procedure. At the short card pick, stop the release claim and ask the authorized reviewer for a decision.
The baseline state for O01 is Hold: a partial-release decision has not been supplied. A complete review query is:
O01 requires SKU-N three pieces and SKU-C two pieces. The pick record contains SKU-N three and SKU-C one, leaving one card short. Please provide the authorized decision and its reference before parcel contents are released for packing.
This query draft has not been sent. The actual recipient, decision, reference, and response stay blank until they exist. A proposed review option or view switch is not approval.
Keep the partial-pack variant visibly conditional
In a separate original variant, assume decision D01 explicitly authorizes a partial parcel containing three SKU-N notebooks and one SKU-C card, with one card outstanding. That conditional variant demonstrates what the records would need; D01 is not an actual approval in the baseline.
The packer checks only the contents authorized by that decision. Parcel P01 would contain four pieces: three notebooks plus one card. The order still has one card outstanding. Keep packed quantity separate from picked quantity; a pick record alone does not establish what a parcel contains.
Record order ID, order line/SKU, unit, decision reference, parcel ID, and actual packed quantity. A later reconciliation of the outstanding card needs its own evidence rather than silently marking all five pieces complete. One parcel is a package count, not one item piece.
Match the label without inventing carrier receipt
A proposed label record LAB01 identifies P01 and O01. The actual address and service must be supplied and checked in the authorized workflow; the demonstration includes no real customer address and generates no carrier label.
Compare parcel, order, authorized contents, and label/document references before staging. Prepared or staged is not the same as handed off. Handoff record H01 has blank timestamp and carrier acknowledgement in this example, so the result is “Carrier handoff not confirmed.” Do not display shipped, carrier received, or delivered from the existence of LAB01.
When an actual handoff occurs, record the required evidence through the maintained process. The SOP does not purchase a label, contact a carrier, or establish a delivery outcome.
Give each step a record and an unresolved state
The sequence is authorized-order/hold check, pick record, short-pick decision, authorized packing check, parcel-label match, and actual handoff record. For each step, identify the role, input record, check, output evidence, and exception to route. Keep unsupplied locations, approvers, materials, and carrier requirements explicit rather than borrowing rules from a generic template.
The local HTML review shows order-line, exception, and parcel views connected by the same IDs. The baseline Hold and conditional D01 variant must remain distinct. The local review does not integrate with a warehouse system, scan items, write stock records, create a parcel or ship an order.
Copy this prompt for the short-pick SOP packet
Prepare a complete US English warehouse fulfillment SOP review packet with original order-line ledger, short-pick query, blank decision record, conditional parcel-content variant, proposed label reference, blank carrier-handoff record, and expected-state test matrix. All records fictional; no actual order, count, packing or shipment.
Order O01: SKU-N notebook ordered3 pieces, SKU-C card ordered2 pieces. Pick record N3/C1: five ordered, four picked, one card short. Preserve order/SKU/location reference/unit and quantities. No silent substitution, ordered-quantity rewrite or inventory adjustment.
Baseline partial-release decision unknown: Hold. Query authorized reviewer for decision/reference before release. Actual reviewer, recipient, response and D01 authority remain blank. A view click is not approval.
Separate conditional variant only if D01 authorizes partial packing N3/C1 with C1 outstanding. Parcel P01 contains four pieces, not a complete five-piece order; one parcel is not one piece. Keep picked and actual packed counts distinct and match authorized order/decision/contents.
Proposed LAB01 ties P01/O01; actual address/service TO CONFIRM, no real label generation. H01 timestamp/carrier acknowledgement blank: handoff not confirmed, not shipped/delivered. Prepared/staged label or parcel is not carrier receipt.
Steps: verify authorized order/hold; record pick SKU/location/pieces; stop short pick/request decision; pack only authorized contents/check quantities; match parcel/order/label documents; stage and later record actual handoff evidence. Roles, packing materials and carrier requirements must come from actual workflow. No machinery, regulated-goods, safety certification or borrowed packing standards.
Proposed HTML order/exception/parcel views preserve stable IDs, baseline versus conditional variant, ordered/picked/packed/outstanding and blank handoff. Implementation/testing pending. No live WMS, scan integration, label purchase, send or shipping controls. Maintained record system remains authoritative.
Review the quantities and handoff in NOS
NOS can save and render a prepared HTML copy of the linked order, exception, and parcel records. Use it to inspect whether the hold and conditional partial release remain separate after any proposed views are built and tested. Keep actual decisions, packing records, labels, and carrier evidence in the maintained fulfillment workflow.
Finish with the short card and unconfirmed carrier handoff visible beside the exact records, so a prepared parcel never becomes a complete or delivered order by assumption.