The feed form is the first process decision

A request for a “chili sauce line” can hide the most important variable: what arrives at the factory gate. Fresh whole pods, dried whole pods, flakes or powder, and a prepared mash or puree are not interchangeable. They differ in handling, contamination risk, water content, particle structure and preparation equipment.

FAO’s technical manual on small-scale fruit and vegetable processing treats raw-material selection, harvest and post-harvest care as quality factors, and separates preliminary operations from preservation steps because each operation changes what the next machine receives. The feed brief has to match the receiving section, not an idealised material.

Three purchase briefs cover most chili sauce projects: fresh, dried and prepared. “Prepared” can mean blanched, roasted, fermented mash, puree or frozen material. Each needs its own description and a named supplier lot.

Fresh chili: a perishable receiving brief

Fresh pods bring water, soil, field heat and variable maturity into the plant. The brief should state the chili type or cultivar if known, the harvest window, transport time and conditions, whether stems are on or off, the pod condition and whether the lot has already been washed. It should also say whether the line will wash, inspect, destem and cut, or whether some duties are completed upstream.

Washing and sorting are not cosmetic. They remove soil and defective fruit and create a controlled reject stream. FAO’s manual treats water, utensils and surfaces as part of the sanitation operation, so water quality belongs in the equipment review. For a chili line, the washer, inspection conveyor and destemmer form a connected preparation section, so transfer, drainage and reject handling must be quoted together.

Fresh feed also changes the water balance. Pods carry variable moisture, and the recipe may add liquid before or during blending. The blender, pump and kettle must handle the resulting base. One lot cannot define a season, but it can expose whether preparation controls the variation that matters.

Dried chili: define whole, flake or powder

Dried chili is not one feed. Whole pods need inspection, possible size reduction and a decision about hydration. Flakes and powder have different flow behaviour, dust load and wetting characteristics. A dry ingredient should not go directly to a wet colloid mill; it needs a hydration or wet-blending step first. If hydration is selected, the water becomes part of the formulation.

The purchase brief should identify the dried form, declared moisture condition, whether stems and seeds are present, the supplier’s foreign-material controls, packing format and lot traceability. The receiving area needs dust control and separation between dry handling and wet processing; those are layout and equipment requirements, not housekeeping notes.

Rehydration is not dilution. Rehydration brings a dry ingredient to a workable feed and its water is accounted for in the recipe. Dilution adjusts the finished sauce. Confusing the two produces a water balance nobody can reproduce and a grinder feed that changes from batch to batch. The brief should state the water source, addition basis, intended uptake or drainage, and sampling method.

Prepared and fermented feed: write the supply boundary

A supplied mash, puree or roasted chili can remove fresh-pod preparation from the line, but it creates a different boundary. The processor must define what the supplier guarantees and what the sauce line still has to do. Ask for the material form, particle profile, declared ingredients or processing aids, salt and acidity information needed for materials selection, pack format, storage conditions and lot identity. Commercial formula details can stay private.

If the feed is a fermented mash, fermentation is upstream. A finishing line may refine, grind, blend, heat and fill, but it does not include fermentation tanks or validate that process. Roasted chili is likewise a separate scope unless quoted. The equipment list should show where the feed enters and what is excluded.

The hand-off needs a sample. A specification sheet cannot show how the mash pumps, how much air it holds, or whether pieces survive transfer. A small trial on the supplied material is more informative than a description of the feed.

Stems, skins and seeds are a product policy

Chili sauce texture is partly a decision about fractions. Stems are normally removed for food quality, but the equipment question is where and how. Skins and seeds may be retained for body and appearance, or separated for smoothness. State the policy for each fraction rather than leaving it to a mill setting.

Seed and skin removal creates a reject stream and a cleaning duty. Retaining them changes the load on the mill, pump and filler. A chunky product may keep visible fragments; a smooth product may need refining. In either case, sample after filling, because the smallest passage in the line can alter the particle profile.

A supplier’s claim also needs a boundary. A refiner can separate a stream under stated conditions, but it cannot decide whether the product meets the buyer’s texture expectation. That belongs to the product trial and the agreed acceptance method.

Connect the feed brief to the texture trial

The feed brief and texture target should be written together. Fresh, rehydrated and supplied feeds will not behave the same in a cutter, mill, blender or filler. The trial should use the intended feed form and a representative lot, then check the product at the blender, after transfer and in the package.

Do not accept a quotation that substitutes a different feed “for testing” without recording the substitution. A successful run on prepared flakes says little about whole dried pods, and a smooth-sauce trial does not establish a chunky line. The trial report should identify the feed lot, preparation, water basis, texture and package.

The output is a short feed specification for the enquiry: form, lot, preparation, stem, skin and seed policy, water basis and texture target. It need not reveal the commercial recipe.

A purchase brief in one page

A concise feed brief can be assembled before a detailed line layout is requested. It should include:

  • Feed form and supplier lot: fresh whole, dried whole, flakes, powder, mash, puree or roasted.
  • Origin and date: harvest or processing date, transport conditions and received condition.
  • Preparation already completed upstream and the preparation still required in the line.
  • Stem, skin and seed policy, including the intended reject stream.
  • Hydration or dilution basis, with the water source and accounting method.
  • Target texture, particle acceptance method and package format.
  • Output basis, utilities, available space and any existing equipment interfaces.
  • Sample availability and the name of the person who can answer material questions.

A precise feed brief does not guarantee a process, but it removes avoidable assumptions and gives the trial a defined starting point.

Sources and boundaries

These sources support the general process and regulatory context discussed above. They do not establish a machine rating, a validated process for a particular product, or a project result.

  1. FAO Technical manual on small-scale processing of fruits and vegetablesFood and Agriculture Organization of the United Nations

    Raw-material selection, preliminary operations and sanitation context for small-scale fruit and vegetable processing. Historical guidance, not a chili-specific process validation.

  2. UNIDO Small-scale fruit and vegetable processing and productsUnited Nations Industrial Development Organization

    Production-method and quality-assurance context. Does not establish a capacity, yield or equipment guarantee.

Editorial analysis by the chilisauceprocessingline.com team, published 28 October 2026. It is not a process-authority opinion, a project report or a substitute for product-specific trials.