Outbound & Dispatch
Complete Study Guide + Tracker
Factory-Integrated FG Warehouse | ASRS-based | SAP WM
Warehouse Operations Research — Pillar 1 of 4
Outbound & Dispatch — Complete Study Guide + Tracker
This is your all-in-one working document for Pillar 1: Outbound & Dispatch. It consolidates everything covered so far (Process Flow,
Challenges, Exceptions, Task Breakdown, Basic/Intermediate levels) — Advanced/Deep-theory content is intentionally left out for now, as
agreed.
MY TRACKER — Tick off as you complete each stage
Stage 1: Read
Process Flow (table below)
Task Breakdown (all 10 activities)
Challenges & Countermeasures
Exceptions (step-wise)
Basic level (all 10 activities)
Intermediate level (all 10 activities)
Stage 2: Site Walk Test
Observed/recalled an actual dispatch at Dapada and could name each activity as it happened
Could identify which SAP screen/transaction is used at each step
Could spot at least one real exception/deviation from the ideal flow
Stage 3: Confusion List
(Fill this in as you go — bring these back for targeted follow-up questions) - [ ] Term/task I didn’t fully get #1: _______________ - [ ]
Term/task I didn’t fully get #2: _______________ - [ ] Term/task I didn’t fully get #3: _______________
Stage 4: Self-Check
I can explain the Outbound flow start-to-end to someone else without notes
I understand why each step exists (not just what happens)
I’m ready to move to Inbound
1⃣ PROCESS FLOW
Step Activity Responsible Role System/Doc
1 Dispatch plan received (DSD/Depot Logistics Planner SAP VL06O / Sales order
indent)
2 Vehicle placement & gate entry Security/Gate staff Gate pass, vehicle log
3 Loading bay allocation Dispatch Supervisor Yard/bay management sheet
4 Picking confirmation from storage Warehouse Operator/HOPT-BOPT WMS pick list
driver
5 Staging at dispatch dock Loader team Physical staging area
6 Loading into vehicle Loading labor + Supervisor Loading checklist
7 Invoice & delivery challan generation Dispatch Clerk SAP billing doc
8 Vehicle weighment (if applicable) Security/Weighbridge operator Weighbridge slip
9 Gate exit & seal verification Security Gate out register, seal number log
10 POD (Proof of Delivery) tracking Logistics/CFA POD system/TMS
2⃣ TASK BREAKDOWN (Granular Steps per Activity)
1. Dispatch Plan
1. Receive indent/order from Depot/CFA/customer
2. Check stock availability (ATP) in SAP against requested SKUs/quantities
3. Validate indent against dispatch schedule/vehicle capacity for the day
4. Confirm or flag partial fulfillment if stock is insufficient
5. Lock/freeze the dispatch plan for the day (cut-off time applied)
6. Communicate confirmed plan to warehouse team and transporter
2. Vehicle Placement & Gate Entry
1. Transporter notifies expected vehicle arrival time
2. Security verifies vehicle documents (RC, driver license, insurance)
3. Record vehicle number, driver details, and arrival time in gate register
4. Conduct basic vehicle safety/hygiene check (cleanliness, no pest infestation, roadworthiness)
5. Issue gate-in pass/token
6. Direct vehicle to holding/waiting area until bay is free
3. Loading Bay Allocation
1. Check bay availability against yard/bay schedule
2. Match vehicle to bay based on SKU/zone proximity
3. Communicate bay number to vehicle driver and loading team
4. Direct vehicle to assigned bay
5. Log bay occupancy start time
4. Picking Confirmation from Storage
1. System/TR generates picking requirement from confirmed delivery
2. Transfer Order (TO) created and released to ASRS or manual picker
3. ASRS retrieves pallet / operator manually picks from bin
4. Scan barcode to confirm SKU, batch, and quantity match TO
5. Confirm TO in system (LT12/LT13)
6. Flag and resolve any pick discrepancy (wrong batch, damaged pallet) before proceeding
5. Staging at Dispatch Dock
1. Move picked pallets to designated staging lane for the specific vehicle
2. Arrange pallets in loading sequence (multi-drop: last stop first)
3. Cross-check staged quantity against delivery/invoice document
4. Flag and correct any staging discrepancy before loading begins
5. Confirm staging complete and ready for loading
6. Loading into Vehicle
1. Loading team receives loading checklist/sequence
2. Physically load pallets/cases into vehicle per sequence
3. Scan each pallet/case at load point to confirm loaded quantity
4. Verify weight distribution/stacking as per vehicle safety norms
5. Supervisor cross-verifies loaded quantity against staged quantity
6. Close vehicle (tarp/shutter) once loading confirmed complete
7. Invoice & Delivery Challan Generation
1. Confirm final loaded quantity matches delivery document
2. Trigger billing document in SAP post-loading confirmation
3. Generate e-invoice (statutory requirement)
4. Generate e-way bill with correct vehicle number and route details
5. Print and hand over invoice/challan/e-way bill copies to driver
6. File/retain digital copies for record-keeping
8. Vehicle Weighment
1. Direct loaded vehicle to weighbridge
2. Record gross weight (loaded vehicle)
3. System/manual calculation of net weight (gross minus tare)
4. Compare net weight against invoice quantity within tolerance threshold
5. Flag and investigate variance beyond tolerance
6. Issue weighment slip/certificate
9. Gate Exit & Seal Verification
1. Apply security seal to vehicle (container/shutter)
2. Record seal number against invoice/delivery document
3. Photograph or log seal application (if CCTV/photo protocol exists)
4. Security verifies all documents present (invoice, e-way bill, weighment slip) before exit
5. Record gate-out time in register
6. Release vehicle from premises
10. POD Tracking
1. Transporter/driver delivers to depot/customer
2. Depot/customer confirms receipt and signs/acknowledges POD
3. POD document/scan uploaded into TMS or shared with logistics team
4. Logistics team reconciles POD against dispatch record
5. Flag and escalate missing/delayed POD beyond SLA window
6. Close dispatch record once POD confirmed and reconciled
3⃣ CHALLENGES & COUNTERMEASURES
Challenge Root Cause Countermeasure
Vehicle placement delay Poor transporter coordination Advance vehicle indent scheduling, transporter
SLA
Loading bay congestion Multiple vehicles same slot Bay slotting/appointment system
Wrong SKU/quantity loaded Manual picking error Barcode scan confirmation before loading
Invoice-vehicle mismatch Manual data entry System-driven auto invoice generation post-
loading
Overloading/underloading No real-time weight check Mandatory weighbridge check before gate-out
Seal tampering risk No seal audit trail Photo/seal number logging at gate
Peak season dispatch backlog Capacity vs. demand mismatch Multi-shift loading, temporary labor pool
4⃣ EXCEPTIONS (Step-wise)
Step Ideal Process Exception (What Can Go Wrong) How to Overcome
1. Dispatch plan received Indent confirmed in SAP VL06O Last-minute indent Cut-off time for indent changes;
change/cancellation from Depot; system check for stock availability
indent qty > available stock before confirming plan
2. Vehicle placement & gate entry Vehicle arrives as scheduled Vehicle no-show, wrong vehicle type Backup transporter panel; buffer
(capacity mismatch), transporter vehicle on standby during peak
delay season
3. Loading bay allocation Bay assigned per schedule Bay occupied/conflict, multiple Bay reservation system with real-
vehicles for same slot time yard visibility
4. Picking confirmation from storage WMS/TO-driven pick, FEFO followed ASRS breakdown during pick, TO Manual retrieval SOP as fallback;
stuck/not generated, wrong batch TR/TO aging alert; barcode scan
picked mandatory before staging
5. Staging at dispatch dock Picked stock staged correctly Staging area full, mixed SKU/batch Dedicated staging lanes per vehicle;
staged together, staged stock not staging reconciliation check before
matching invoice loading
6. Loading into vehicle Loaded as per invoice quantity Short/excess loading, damage during Loading checklist with dual sign-off;
loading, wrong SKU loaded barcode scan at load point
7. Invoice & delivery challan Auto-generated post-confirmed Invoice generated before actual Sequence lock: invoice only post final
loading loading complete (mismatch), system loading confirmation; manual billing
downtime delaying billing fallback SOP during SAP downtime
8. Vehicle weighment Gross/tare weight checked Weighbridge malfunction, weight Alternate weighbridge tie-up; weight
mismatch vs. invoice (overload/short variance tolerance threshold with
load) escalation
9. Gate exit & seal verification Seal applied & logged, gate-out Seal not applied/tampered, gate CCTV at seal point; mandatory
recorded register not updated, vehicle exits security checklist before gate-out;
without documentation seal number cross-check with invoice
10. POD tracking Delivery confirmed by POD not received (lost in transit TMS/POD tracking system with
depot/customer ambiguity), transit damage/shortage escalation matrix; transit insurance;
claims, delayed POD causing time-bound POD closure SLA
reconciliation issues
Cross-cutting exceptions: - Peak/month-end dispatch surge — volume exceeds daily loading capacity → pre-planned multi-shift
loading, advance staging a day prior - SAP system downtime — halts steps 1, 6, 7 simultaneously → documented manual dispatch
fallback SOP with retrospective system entry - Statutory document failure (e-way bill generation issue) — vehicle held at gate → backup
e-way bill generation access, transporter awareness on portal issues
5⃣ BASIC + INTERMEDIATE LEVELS (Advanced deliberately left out for now)
1. Dispatch Plan
Basic: A dispatch plan starts with an “indent” — a request from a Depot, CFA, or direct customer for specific SKUs and quantities. The
Logistics Planner receives this and checks it against available stock and the day’s dispatch schedule. Intermediate: In SAP, this is
handled through VL06O (List of Outbound Deliveries), which pulls sales orders and converts them into deliveries. The system checks stock
availability (ATP – Available to Promise) before confirming.
2. Vehicle Placement & Gate Entry
Basic: A transporter sends a vehicle matching the required capacity. Security logs the vehicle at the gate — driver details, vehicle
number, and time of arrival. Intermediate: Governed by a Transporter SLA defining vehicle availability. Some plants use a Vehicle
Appointment/Scheduling system so trucks arrive in slots, reducing yard congestion.
3. Loading Bay Allocation
Basic: Once a vehicle is inside, it’s assigned to a specific bay/dock door where loading will happen. Intermediate: A Yard Management
System (or manual yard sheet) matches vehicles to bays based on SKU proximity to storage zone.
4. Picking Confirmation from Storage
Basic: The system (or a person) picks required stock from storage bins, generally following FEFO — older/near-expiry stock goes out first.
Intermediate: A Transfer Requirement (TR) generates from the delivery, converting into a Transfer Order (TO) via LT03, instructing
ASRS/operator exactly which bin to retrieve from. Barcode scan confirms the right pallet/batch.
5. Staging at Dispatch Dock
Basic: Picked stock is moved to a staging area near the dock — a temporary holding zone before loading. Intermediate: Staging lanes
are dedicated per vehicle/route to avoid mixing SKUs. Reconciliation checks compare staged stock against invoice before loading begins.
6. Loading into Vehicle
Basic: Physical loading of stock into the vehicle, following a checklist for quantity and SKU accuracy. Intermediate: Load sequencing
matters — weight distribution, multi-drop trips loaded in reverse delivery order. Barcode scan at loading confirms exact SKU/quantity
match.
7. Invoice & Delivery Challan Generation
Basic: Once loading is done, an invoice/delivery challan is generated — the legal document showing what was dispatched and to whom.
Intermediate: Billing triggers post-delivery confirmation, sequenced so invoicing doesn’t happen before loading is complete. E-invoice
and e-way bill generation happen at this stage.
8. Vehicle Weighment
Basic: The loaded vehicle is weighed (gross weight) and compared against empty weight (tare) to calculate net cargo weight, verifying it
matches the invoice. Intermediate: Weighbridge systems interface with SAP to auto-capture weight, with defined tolerance thresholds
(e.g., ±2%) before flagging a variance.
9. Gate Exit & Seal Verification
Basic: Before the vehicle leaves, a security seal is applied to prevent tampering, and the gate register logs the exit. Intermediate: SOPs
require the seal number to be cross-checked against the invoice/delivery document, often with CCTV coverage at the sealing point.
10. POD Tracking
Basic: Once the vehicle reaches its destination, the depot/customer confirms receipt — this confirmation is the POD. Intermediate: A
Transport Management System (TMS) tracks POD status, with an escalation matrix for delayed or missing PODs (e.g., escalate after 48/72
hours).
✅ Next Step
Once all tracker boxes above are ticked, come back and we’ll build the exact same structure (Tracker + Process Flow + Tasks +
Challenges + Exceptions + Basic/Intermediate) for Inbound & Receiving.