Commercial Production Guide
Product SOPs: Architecture, Not Hundreds of Documents
A product SOP is the standard procedure with the product-specific parts filled in: how this product is prepared, loaded, dried, verified and packaged. The goal is architecture, not hundreds of one-off documents: one skeleton, one set of rules, and a product page per item that says only what differs.
Category: SOPs
The Architecture
Build product SOPs from the shared skeleton in the SOP guide:
- One master skeleton with the ten standard sections (name, purpose, scope, equipment, materials, procedure, quality checks, corrective actions, records, revision date).
- One product page per product that fills the skeleton and names the product-specific steps.
- Product differences live in preparation, loading, cycle expectations, dryness checks and packaging, not in the document structure.
- The machine manual stays the authority for settings; every product page references, never restates, the manual.
Short Worked Examples
These are structure examples, not full procedures: they show how you would frame the product-specific sections. Fill cycle times, loads and checks from your own measured operation.
How mango slices might structure:
- Preparation: wash, peel, cut to a consistent slice thickness, treat for high sugar if the operation uses a treatment.
- Loading: even, single-layer-ish coverage with space between pieces; the tray load planner tracks per-tray weights.
- Dryness: brittle, non-sticky pieces with no soft center; high sugar means extra care before packaging.
- Packaging: prompt sealing, absorber per spec, label with product, batch and date.
How pet food might structure:
- Preparation: portioning and any cooking per the recipe; ingredient handling and sanitation per the pet-food food-safety guide.
- Loading: consistent depth so drying is even across the tray.
- Dryness: verified per the operation's check; fat content means shorter storage expectations.
- Separation: scheduling and cleaning separation from human-food runs, per the operation's rules.
How prepared meals might structure:
- Preparation: cook, cool and portion per the recipe; record cooling before freezing.
- Loading: mixed ingredients need even distribution so no single dense component holds moisture.
- Dryness: check the densest component, not just the surface.
- Traceability: batch ID ties the meal to its recipe and ingredients; see traceability.
How powders might structure:
- Preparation: purée or slurry at consistent consistency, spread thin for even drying.
- Milling: grind, sieve to target, and handle fines so powder loss is controlled.
- Humidity: mill and package in the driest conditions available; see the powder production guide.
- Packaging: moisture-proof packaging and prompt sealing; powder absorbs humidity fastest of all forms.
Build architecture, not hundreds of documents
Do not write a full SOP from scratch per product. Write the skeleton once, and one page per product that fills the blanks and names the differences. When something changes, the skeleton updates once and every product page follows.
Where product pages live
Product SOPs pair with the operation's batch records and the product development guide: the SOP defines how, the record proves what happened, and the Lab methodology documents how results are measured.
Frequently Asked Questions
How much detail should a product page have?
Only what differs from the skeleton plus the product-specific checks. If a step is identical for every product, it belongs in the master SOP, not repeated on 20 pages.
Do the examples above contain numbers to copy?
No, and they should not. Cycle times, loads, thicknesses and absorber sizes come from your own measured operation and the manufacturer's documentation, not from an example.
Do product SOPs become compliance documents?
Only if your regulatory context requires it. They are working process documents; compliance requirements come from the relevant authorities.
Key Takeaways
- One shared skeleton plus one page per product: document differences, not repeated boilerplate.
- Worked examples (mango, pet food, meals, powders) show how to structure, never numbers to copy.
- Keep the machine manual as the authority and reference it rather than restating it.
Related Guides
Continue through the Commercial Production Center with these related guides.