Feeder Acceptance Test Guide 2026

A feeder should be accepted against a written test, not a good impression

Feeder projects often drift into trouble because FAT was treated as a quick demo instead of a structured acceptance test. The supplier proves the bowl moves parts, everyone nods, and only later does the customer discover that the feed rate was measured on a half-filled bowl, with hand-picked samples, under easier conditions than the real line will see.

A proper acceptance test stops that. It turns vague promises into measurable conditions: part sample, fill level, duration, orientation yield, controller reserve, and fault behavior. These are simple checks. They just need to be written down before the machine reaches FAT or SAT.

This guide lays out a practical feeder acceptance approach for vibratory bowls, flexible feeders, and integrated systems. It works well alongside our RFQ checklist and validation guide.

Why feeder acceptance often fails in practice

The first reason is undefined test conditions. Buyers ask for 180 ppm, but do not define bowl fill level, sample condition, or duration. The supplier may still act in good faith and test differently than the plant expects.

The second reason is mixing gross movement with usable output. A feeder can move many parts through a bowl track while still delivering fewer good parts at the discharge than the line needs.

The third reason is that FAT and SAT get confused. FAT should prove the machine at the supplier. SAT should prove it again in the customer environment. They are related, but not interchangeable.

What FAT and SAT should each prove

FAT should confirm the equipment concept, output target, orientation yield, and basic fault behavior before shipment. It is the place to catch wrong assumptions while changes are still cheaper.

SAT should confirm that the same feeder performs correctly after transport, installation, plant wiring, and real utility conditions. If the machine depends on a robot or assembly station, SAT should include the true interface behavior.

For larger automation projects, the feeder acceptance should also tie into the machine-level cycle-time plan, not live as a separate checkbox.

A practical acceptance sequence

Most feeder FAT and SAT problems become much easier when the team follows a simple sequence.

1. Freeze the acceptance conditions before FAT. Part sample, output target, bowl fill, and duration should be agreed in writing.
2. Measure good output at the actual discharge. That is the number the line can use.
3. Check controller reserve and fault recovery. A feeder that only works at the edge of its range has no operating margin.
4. Repeat the same logic at SAT. The plant should confirm the machine under real installation conditions.

A short written checklist is usually more valuable than a long verbal explanation after the test goes badly.

What to record during the test

Record the part sample used, fill condition, controller setting, average good-part output, and visible fault types. If the feeder has recipes or PLC integration, record those values too.

If the machine includes related modules such as a hopper, escapement, robot, or vision system, note whether the feeder passed alone or as part of the full cell. That distinction matters later.

Where the customer expects cleanroom, cosmetic, or ESD performance, add those checks directly to FAT instead of assuming they will be covered informally.

Buyer checklist before FAT or SAT

A good acceptance test usually depends on simple preparation from both sides.

• Bring or send real production samples. Test quality depends on the part condition.
• Write down the output definition. Good parts at discharge is usually the safest standard.
• Include fill level and test duration. Short easy tests hide the real problems.
• Define the full-cell interfaces. Robot, PLC, and hopper behavior should not be left vague.

Huben Automation supports feeder FAT and SAT around measurable plant conditions rather than broad promises. If you want help structuring an acceptance plan, send us the project scope and target metrics.