SD Picking and PGI Part 5: Architecting Picking and PGI for Scale

📌 KEY POINTS
✅ Warehouse execution model per site (lean, embedded EWM, decentral EWM) drives how picking and PGI work and who owns them.
✅ Shipping points, storage locations and HU management must be designed together.
✅ PGI timing links logistics to finance: revenue, COGS and billing cut-offs at month-end.
✅ Inventory accuracy needs confirmation discipline, reversal rules and monitoring.
⚠️ A design where PGI happens "whenever someone remembers" breaks month-end revenue recognition.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–4 covered the process and integration. This part is the architect view.

━━━━━━━━━━━━━━━━━━━━
▶ 1. EXECUTION MODEL PER SITE

• Small sites: lean picking in the delivery.
• High-volume sites: EWM with waves, RF, packing, loading.
• Decentral EWM for independence/performance; embedded for simplicity.

━━━━━━━━━━━━━━━━━━━━
▶ 2. STRUCTURE ALIGNMENT

• Shipping points ↔ dispatch areas; storage locations ↔ EWM warehouses.
• HU management per storage location decided once.

━━━━━━━━━━━━━━━━━━━━
▶ 3. PGI TIMING AND FINANCE

• PGI at loading/truck departure; cut-off rules at month-end.
• Billing runs after PGI jobs; revenue recognition dependencies.

━━━━━━━━━━━━━━━━━━━━
▶ 4. INVENTORY ACCURACY

• Confirmation before PGI, controlled differences, VL09 rules.
• Cycle counting in warehouse; KPIs for differences.

━━━━━━━━━━━━━━━━━━━━
▶ 5. PERFORMANCE, RESILIENCE, GOVERNANCE

• Mass PGI windows, parallelization, lock tuning.
• Monitoring and alerting for failed PGI.
• Enhancement register and change control.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Classify sites and choose execution models.
2. Align shipping points, storage locations and HU decisions.
3. Define PGI timing and month-end cut-offs with finance.
4. Set accuracy KPIs and monitoring.

✅ CHECKPOINT: month-end closes with all shipped goods goods-issued and billed, and inventory differences within tolerance.

A manufacturer's month-end revenue fluctuated because trucks left on the 31st but PGI was posted on the 2nd, after dispatch clerks returned. Finance reversed accruals every month. The architect moved PGI to loading completion in EWM for the main DCs and to a scheduled job for smaller sites, with a monitored cut-off. Revenue timing stabilized and month-end adjustments disappeared.

• Same execution model for all sites regardless of volume.
• PGI timing disconnected from physical shipment.
• HU decisions per storage location made inconsistently.
• No monitoring of picked-not-issued deliveries.
• No month-end cut-off plan.

• Choose execution model per site profile.
• Align structure (shipping points, storage locations, HUs).
• Tie PGI to physical events.
• Agree cut-offs with finance.
• Monitor accuracy and failures.

Questions: "How would you design picking and PGI for multiple sites?", "Why does PGI timing matter for finance?", "How do you ensure inventory accuracy?"
Strong answer: execution model per site (lean/EWM embedded/decentral), aligned structures and HU management, PGI at physical shipment with month-end cut-offs, accuracy controls (confirmation, reversals, counting), performance and monitoring.