๐Ÿญ Maiyuri Bricks SOP DashboardAll SOPs

๐Ÿท๏ธ SOP 26 โ€” Batch Card / QR / NFC Tagging

SOP Name:         Batch Card / QR / NFC Tagging
Process Code:     BATCH_TAGGING_V1
Version:          V1
Owner:            Factory Supervisor
Applies To:       Factory Supervisor, Stacking Labour
Frequency:        Every production batch
Last Updated:     2026-06-25
Review Frequency: Monthly

1. Purpose

Give every batch a clear identity card so product, quantity, quality and curing status can be traced from mixing to dispatch.

2. Who Is Responsible

3. When To Use This SOP

At the start of every batch, and whenever the batch moves (stacking โ†’ curing โ†’ dispatch).

4. Visual Process Flow

flowchart TD
A[Batch created] --> B[Write batch card]
B --> C[Attach QR/NFC tag if available]
C --> D[Place card with batch island]
D --> E[Update status at each stage]
E --> F[Card retired at dispatch]

5. Batch Card Fields

Batch ID:
Date:
Product (MIB/CIB, 6/8-inch, solid):
Quantity (mini-stacks x 20):
Mix recipe code:
First-20 approval: PASS / HOLD / FAIL
Quality status: Approved / Hold / Reject
Curing start date:
Ready-for-dispatch date:
Dispatched? (date / vehicle):

6. Step-by-Step Visual SOP

  1. Create the Batch ID at production planning (PROD_PLAN_V1).
  2. Write the batch card with the fields above. [PHOTO: Batch card]
  3. Attach a QR/NFC tag if available (links to the Supabase/Docmost batch record).
  4. Place the card visibly in front of the batch island.
  5. Update status at each stage: first-20, QC, curing start, ready date.
  6. Keep the card with the batch through every move.
  7. Retire/file the card at dispatch.

7. Do / Don't

โœ… DoโŒ Don't
Keep one card per batch, always visibleShare one card across mixed batches
Update status at every stageLeave dates/status blank
Match card quantity to actual stacksGuess the quantity

8. Checklist

[ ] Batch ID matches production plan
[ ] All card fields filled
[ ] QR/NFC tag attached (if available)
[ ] Card placed with batch
[ ] Status updated at each stage
[ ] Card retired at dispatch

9. Records To Update

10. Escalation Rule

Inform Ram/Srinivasan if a batch loses its card / identity, or if card quantity does not match physical stock.

11. Common Mistakes

12. 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: /batch
n8n workflow:     wf_batch_tagging_v1
Odoo object:      stock.lot
Approval role:    Factory Supervisor
Supabase table:   production_batches
Status:           Future automation