๐Ÿญ Maiyuri Bricks SOP DashboardAll SOPs

๐Ÿšš SOP 13 โ€” Dispatch Planning

SOP Name:         Dispatch Planning
Process Code:     DISPATCH_PLAN_V1
Version:          V1
Owner:            Factory Supervisor
Applies To:       Factory Supervisor, Sales/Admin
Frequency:        Every dispatch
Last Updated:     2026-06-25
Review Frequency: Monthly

1. Purpose

Plan delivery correctly and avoid wrong product, quantity or site delivery.

2. Who Is Responsible

3. When To Use This SOP

Before every dispatch, once stock is approved (READY_DISPATCH_QC_V1).

4. Visual Process Flow

flowchart TD
A[Confirm customer/site] --> B[Confirm product + quantity]
B --> C[Confirm location/access]
C --> D[Confirm vehicle + driver]
D --> E[Fix loading time]
E --> F[Confirm payment/approval]
F --> G[Inform sales/admin]

5. Step-by-Step Visual SOP

  1. Confirm customer/site name.
  2. Confirm product and quantity.
  3. Confirm site location and access.
  4. Confirm vehicle and driver.
  5. Confirm loading time.
  6. Confirm payment/approval status if required.
  7. Inform sales/admin.

6. Do / Don't

โœ… DoโŒ Don't
Confirm site access before sendingSend a large vehicle to a tight site blindly
Match product to the orderLoad whatever stock is nearest
Confirm payment/approval where requiredDispatch on unconfirmed approval

7. Checklist

[ ] Customer confirmed
[ ] Site confirmed
[ ] Product confirmed
[ ] Quantity confirmed
[ ] Vehicle confirmed
[ ] Driver confirmed
[ ] Loading time fixed
[ ] Sales/admin informed

8. Records To Update

9. Escalation Rule

Inform Ram/Srinivasan if vehicle/driver is unavailable, site access is unclear, or payment/approval is pending.

10. Common Mistakes

11. Improvement Suggestion

If you find a better way to do this process, add a comment below or submit an improvement request in the SOP Improvement Register.


Automation Readiness

Telegram command: /dispatch
n8n workflow:     wf_dispatch_plan_v1
Odoo object:      stock.picking / sale.order
Approval role:    Factory Supervisor + Sales
Supabase table:   dispatch_plans
Status:           Future automation