Segregate the affected material.
Identify quantity, pack units, location, reason, time, and responsible reviewer without implying a specific warehouse system.
SENESA / GALANGALPT SENESA GLOBAL SOLUSIRequest process evidence DRIED GALANGAL · PROCESS-CONTROL FRAMEWORK
From incoming material to the released pack, the buyer should be able to see what happened, which controls applied, what evidence represents the lot, and where an exception changed the route.
01 · MATERIAL-TO-PACK ROUTE
Each stage shows the buyer decision, minimum control questions, and the record expected from the confirmed supply route.
Record the supplier or source reference, arrival date, product state, quantity, packaging condition, visible contamination, and the initial accept, hold, or reject decision.
For a fresh-material route, define washing water, contact surfaces, cleaning sequence, drainage, and cross-contamination controls. If material enters already dried or cleaned, record the actual incoming condition instead of implying a wash step.
Dried slices need a buyer-defined cut and distribution. Whole or chunk material may follow a different size-reduction route or omit slicing. Record line clearance, equipment condition, batch start and end, and format segregation.
Record the confirmed drying method, load identity, start and end, process observations, and deviations. Product acceptance uses the buyer-approved moisture or water-activity target and named test method, not a universal time or temperature published here.
Inspect the agreed sample for format distribution, appearance, defect categories, foreign matter, and other buyer controls. Screens, magnets, metal detectors, or similar controls are recorded only when the confirmed line actually uses them.
Check the approved packaging instruction, liner or inner-pack requirement, net weight, closure, label, lot marks, pack count, and pallet plan. Materials and weights remain buyer- and route-defined until written approval.
Reconcile accepted quantity, packed units, retained samples, inspection results, analytical reports, treatment status, deviations, and destination documents. Record who released, held, or rejected the lot and when.
02 · CONTROL RECORD MATRIX
Document names below are a framework. Final records, owners, retention, language, and availability must match the confirmed operator and buyer agreement.
| Stage | Control question | Record relationship | Decision status |
|---|---|---|---|
| Receiving | What arrived, from whom, when, how much, and in what condition? | Inbound record + initial lot code | Accept / hold / reject |
| Washing / cleaning | Does the step apply, and which hygiene controls were used? | Cleaning log or documented N.A. reason | Continue / correct / hold |
| Cutting | Which format instruction and segregation rule were applied? | Format batch + line-clearance record | Continue / rework / hold |
| Drying | Which load, method, observations, and product tests represent the batch? | Drying log + named test result | Pass / retest / hold |
| Sorting | Which sample, categories, limits, and foreign-matter controls were reviewed? | Inspection worksheet | Accept / rework / hold |
| Packing | Which pack instruction, weight, closure, label, and count were released? | Pack / mark release record | Release / correct / hold |
| Lot release | Do quantities, records, samples, reports, and exceptions reconcile? | Approved lot dossier | Release / reject / concession |
03 · LOT TRACKING
The final system may use a different code, but the buyer file should retain the connections below.
Source reference · process or packing date · unique sequence · format code
Supplier or source identity and the incoming material record.
The confirmed route, dates, format changes, and process records.
Inspection samples, retained samples, reports, and their represented material.
Pack count, weight, label, pallet, and lot marks linked to the released batch.
Buyer order, quantity, destination, documents, exceptions, and release decision.
04 · LOT DOSSIER
A commercial lot file should explain what entered, what changed, what was held or lost, what was packed, and which evidence supports release.
SENESA enquiry and order reference
Source / supplier and incoming-lot reference
Confirmed processing and packing location
Product format and approved specification revision
Incoming, processed, held, reworked, rejected, and packed quantities
Step dates, record IDs, and accountable reviewers
Sample, inspection, and laboratory report relationships
Treatment status and evidence when applicable
Packaging units, lot marks, pallet, and loading relationship
Deviation, concession, release, and retention status
Actual categories, units, tolerances, and reconciliation method must be approved for the confirmed process route.
05 · HOLD + DEVIATION LOGIC
Exceptions must not disappear between processing, testing, packing, and quotation.
Identify quantity, pack units, location, reason, time, and responsible reviewer without implying a specific warehouse system.
Review cause, represented lot, specification impact, evidence, reinspection or retest need, and destination implications.
Release, rework, retest, buyer concession, return, rejection, or another supported decision must keep its approver and lot relationship.
06 · PROCESS QUESTIONS
No. It is a control framework for the supply route. The actual supplier, processing site, packing site, equipment, process sequence, and records must be confirmed for the proposed order before they become commercial claims.
Not necessarily. The incoming material state, cleaning need, cut step, drying event, sorting controls, and packing may differ. The applicable route is written for the selected format and current lot.
SRC-YYYYMMDD-###-FMT is a design example: source reference, process or packing date, unique sequence, and format code. The final format must reflect the confirmed operator and record system.
That outcome requires a verified record chain from incoming material through processing, samples, reports, packing, and shipment allocation. The exact traceability evidence and pack-level granularity are agreed and confirmed for the order.
BUILD THE ORDER FILE
Share format, application, destination, process restrictions, required traceability depth, sample plan, test scope, packing, and document expectations.