Automated Produce Handling & Validation

[Shalom-Karr]

Problem Description

Currently, produce orders require a manual or unstructured approach to verification. In our distribution scenarios, we know instantly based on the active event prefix (which comes from the folder name, e.g., P26 vs S26) whether this run includes produce.

Relying on pickers to manually parse the prefix or remember the rules for a specific event can lead to distribution errors (giving produce to someone who shouldn't get it, or forgetting it for someone who should).

Proposed Solution

We need an automated Produce Validation step integrated into the picker workflow that dynamically reacts to the session prefix.

Key Requirements:

1. Prefix Detection (Directory Based):

   • The server currently reads the orderIdPrefix (e.g. P or S) from the folder directory it's running out of.
   • Rule 1: If the prefix starts with S (e.g. S26) -> The system knows NO PRODUCE is required for this event.
   • Rule 2: If the prefix starts with P (e.g. P26) -> The system knows PRODUCE is required for this event.

2. UX Implementation Question (Open for Discussion):

   • How should the picker interact with the produce requirement when running a P event?
   • Option A (Bulk Alert): When they reach the end of the order, a giant alert/checkbox appears saying: "This order requires a Produce Box. Check here to confirm it was loaded." This treats produce as a single, separate physical box they hand over at the end.
   • Option B (Line Item Integration): Produce is dynamically injected into their pick list as individual items (e.g., "1 Bag of Potatoes", "1 Bag of Carrots") that they have to pick and confirm quantity for, just like warehouse items.
   • Recommendation: If produce is pre-boxed outside the warehouse, Option A is vastly superior and faster. If produce is picked item-by-item from bins on the floor, we must go with Option B.

3. UI Enforcement:

   • If the event requires produce (P prefix) and we choose Option A, the picker cannot complete the order without checking the "Produce Loaded" confirmation box on the end-index screen.
   • If the event does not require produce (S prefix), the UI should explicitly state "NO PRODUCE FOR THIS EVENT" or simply hide all produce-related UI to avoid confusing the loading crew.

Acceptance Criteria

• System accurately identifies produce requirements globally based on the leading character of the folder directory prefix.
• Determine and select the workflow (Option A vs Option B) based on floor operations.
• Implement the UI checkpoint so pickers cannot finish a Produce order without confirming handover.
• Hide produce logic or explicitly display "NO PRODUCE" during S prefixed events.