How to Define Pre-Shipment Functional Tests for Industrial Equipment

A pre-shipment functional test should answer a limited but important question: does the identified equipment perform the agreed factory-test functions under the agreed test conditions? To make that answer usable, convert each required function into an observable acceptance criterion, agree the procedure before the test date, and require documented closure of every failed or incomplete item before shipment release. A successful factory test does not automatically prove performance in the final process or installation.

Separate functional testing from inspection and site-performance acceptance

A functional test checks whether equipment carries out defined actions or control responses. Depending on the equipment, this may include motor rotation, actuator travel, pump start and stop, alarm response, interlock operation, communications signals, valve sequencing, leak-tightness, or operation through an agreed automatic cycle.

The required scope comes from the purchase order and its technical attachments: the specification, datasheet, approved drawings, bill of materials, control narrative, cause-and-effect chart, electrical schematics, fluid-power diagrams, software documentation, and inspection and test plan (ITP). These documents should establish what the supplier is required to demonstrate and what the buyer is entitled to review or witness.

Do not treat several related activities as interchangeable:

• Pre-shipment functional testing demonstrates specified functions using an agreed procedure and acceptance criteria.
• Pre-shipment inspection commonly addresses equipment identity, completeness, visible condition, documentation, accessories, preservation, packing, and dispatch readiness.
• Factory acceptance testing (FAT) is a contractual term whose scope varies. It may include functional testing, performance checks, product trials, or buyer witnessing, but none of these should be assumed without an agreed procedure.
• Site acceptance testing (SAT) or commissioning evaluates functions that depend on the actual installation, site utilities, connected systems, process media, operating procedures, or final controls integration.

Supplier-published guidance on food-processing equipment similarly distinguishes a factory acceptance event from a dispatch-focused pre-shipment inspection, while noting that the activities can overlap when the contract combines them. That distinction is useful, but it is not a universal definition of FAT. The controlling definition is the one in your agreement and approved test documents. See the supplier’s FAT and pre-shipment inspection discussion for an example of this distinction.

A no-load demonstration also has limits. A conveyor may run without showing whether it can move the specified load. A pump may rotate without demonstrating its required duty point. A control panel may energize without proving correct response to all field signals. The test should therefore state exactly what is being demonstrated, what is not being demonstrated, and which conditions must be deferred to site acceptance.

Turn specified functions into observable acceptance criteria

The practical core of pre-shipment functional testing is a test matrix. It links each agreed requirement to a test action, a stated acceptance boundary, and evidence that a reviewer can examine later.

Avoid criteria such as “machine operates correctly” or “system is fully functional.” They conceal the test method and leave room for disagreement. Replace them with a statement that identifies the condition, action, expected result, observation method, and record.

A usable test-matrix structure is:

For example, an interlock criterion can be defined without inventing a universal time limit: “With the guard-open input active, issue the agreed start command. The driven equipment shall not start, and the control interface shall indicate the guard-open condition. Record the input state, command, output state, and alarm or status indication.” The approved electrical drawings and controls narrative should define the relevant input and expected response.

For a pressure or vacuum hold test, the procedure should identify the tested boundary, test medium, stabilization method, starting condition, hold period, permitted pressure change, instrument range, and recording method. A supplier example for process equipment describes recording pressure at the beginning and end of a defined hold period. That is a useful record pattern, not a universal pressure, duration, or allowable-loss requirement. The required values must come from the equipment design, applicable requirements, and contract.

Use the manufacturer’s instructions to prevent an acceptance test from becoming an improper operating event. Instructions may limit energization time, rotation direction, permitted test media, allowable pressure, temporary hose connections, lubrication requirements, guarding arrangements, or sequence of operation. If the proposed factory setup cannot represent the specified duty, record the limitation rather than treating an easier substitute test as equivalent.

Define observation when a number is not appropriate

Not every function requires a numerical tolerance. Some acceptance points are inherently discrete: an emergency-stop circuit de-energizes outputs; a valve fails to its defined position; an alarm appears on the human-machine interface; a door switch prevents motion.

For these cases, define who observes the action, where the observation occurs, which indication is checked, and how the result is captured. A video may help demonstrate sequence or motion, but it should not replace a record of instrument readings where measurements are required. Likewise, a supplier declaration that a test was completed is not the same as objective evidence of the configuration, condition, and result.

Agree the test setup, instruments, and responsibilities before the factory test

A late test procedure creates avoidable disputes. The supplier may prepare for a no-load demonstration while the buyer expects a loaded cycle. A buyer may expect a witness point that the supplier treats as a document-review point. Agreeing the procedure before the factory test gives both parties time to resolve these differences while changes are still practical.

The approved procedure or ITP should define:

• equipment identity, model, serial number or tag number, and approved configuration;
• drawing, software, parameter, and procedure revisions to be used;
• test media, utility supplies, loading method, temporary fixtures, and simulation devices;
• required guarding, isolation arrangements, pressure controls, electrical protections, and emergency-stop arrangements;
• instruments, their identification numbers, required range and accuracy, and available calibration or verification records;
• sequence of tests, hold points, witness points, and test notification period;
• parties permitted to witness, record results, and authorize decisions;
• handling of interrupted tests, abnormal results, and retests; and
• records and approvals required before shipment release.

Measuring equipment must be suitable for the acceptance decision being made. If a pressure-change limit is the acceptance criterion, a gauge with an unsuitable range or unreadable scale may not provide meaningful evidence. If timing is important, the timing method must be identified. A supplier quality document may require calibrated or verified acceptance instruments, but its terms do not automatically govern another purchase. Use it only as a prompt to define the necessary measurement capability and request supporting records where your contract requires them.

Request the instrument identification and available calibration or verification status before or during the test review. The required calibration interval, traceability route, and accuracy are application-specific and may be governed by the contract, industry rules, or the buyer’s quality system. Do not assume that a certificate alone proves an instrument is appropriate for a particular measurement.

Remote witnessing can be useful when travel is impractical, particularly for observing sequence, panel indications, equipment identity, and review of electronic records. Its adequacy depends on what must be seen and measured. Camera position, lighting, sound, network reliability, visibility of instrument displays, file retention, and control over recorded footage all affect evidentiary value. For high-risk measurements or complex assemblies, remote video may not provide the same confidence as physical witnessing. Decide the witnessing method before testing, not after a disputed result.

Define records that demonstrate a passed test

A reviewable test record allows a person who was not present to determine what equipment was tested, under which conditions, and whether each criterion passed. The record should be prepared against the approved procedure and test matrix, not reconstructed from memory after dispatch.

For each completed test, request records that identify:

• equipment name, model, serial number, tag number, and configuration;
• relevant drawing, bill of materials, software, parameter-set, and procedure revisions;
• test date, location, participants, and their roles;
• test conditions, including utilities, media, loading, ambient conditions when relevant, and temporary connections;
• instrument identification, range, and associated calibration or verification evidence when required;
• raw readings, calculated values, observed states, and acceptance decision for each criterion;
• photographs, video, screenshots, or data logs where they add traceable evidence;
• deviations, incomplete steps, retests, and final disposition status; and
• signatures or controlled electronic approvals from authorized parties.

Use traceable identifiers consistently. A signed report is less useful if it refers only to a generic model name while the actual unit, installed options, software version, or control panel revision cannot be identified. This is especially important where multiple similar units are built or where a late engineering change affects the tested configuration.

Document control matters as much as test execution. Specify the required language, file format, naming convention, approval method, and submission timing if these are important to the buyer. If records will be reviewed remotely, require legible scans or native data files where relevant; photographs of a handwritten sheet may be inadequate for critical readings.

Control failures, deviations, and retests before shipment release

A failed criterion, omitted test step, damaged component, incorrect configuration, or departure from the approved procedure should be visible in the record. It should not disappear into an informal promise to “fix it before delivery.”

Classify the issue and assign a written disposition. Common paths are:

• Rework to the original requirement: Correct the equipment without changing the specified requirement, then repeat the affected test as needed.
• Retest: Repeat all or part of a test after correction, with the retest result linked to the original failure.
• Concession, waiver, or deviation approval: The buyer accepts a stated departure from the original requirement under defined conditions. This should be written, controlled, and approved by authorized parties.
• Deferral to site acceptance: A test cannot be completed at the supplier’s facility because required site conditions are unavailable. The remaining scope, owner, method, schedule, and shipment risk must be explicit.

Whether buyer written approval is required for a concession depends on the governing agreement. One supplier’s quality terms state that use-as-is, repair, deviation, waiver, or departure from specified requirements requires buyer approval before shipment. That is an example of contractual risk control, not a universal legal rule. Your purchase order, quality agreement, and nonconformance process should identify who has authority to accept the departure.

If root-cause analysis or corrective action is required, state this in the contract or quality plan. Do not automatically demand an extensive investigation for every minor documentation error, but do not close a recurring or safety-relevant failure with a vague statement either. The response should match the operational, safety, schedule, and replacement risk of the nonconformity.

Shipment with open items is a risk-allocation decision. Before agreeing to it, identify the remaining issue, affected functions, interim controls, responsible owner, due date, required site action, commercial consequences if relevant, and the person authorized to accept the risk. A punch-list item is not closed simply because it has been entered on a list.

Use a shipment-release checklist without overstating what the test proves

Shipment release should combine functional-test status with dispatch readiness. A completed functional test does not confirm that loose accessories were packed, corrosion protection was applied, documents were included, or transport restraints were fitted. Conversely, a satisfactory packing inspection does not demonstrate functional operation.

Before authorizing dispatch, verify the following as applicable to the contract:

• Required functional tests have passed, or each exception has an approved written disposition.
• The final report identifies the actual equipment, configuration, and relevant document revisions.
• Test records include required readings, logs, approvals, and instrument evidence.
• Retest results are linked to the original nonconformance or incomplete step.
• Open items have owners, due dates, interim controls, and written risk acceptance where shipment is permitted.
• Equipment identification, accessories, manuals, spare parts, and certificates match the packing list and purchase order.
• Preservation, protective covers, transport restraints, lifting information, and packaging meet the agreed dispatch requirements.
• Site-acceptance or commissioning activities are identified for functions that could not be demonstrated under factory conditions.

Release equipment only when the required factory-test scope is passed or formally dispositioned, the records identify what was actually tested, and the authorized parties understand the remaining site risks. Treat the result as evidence of the agreed factory-test functions—not as proof of long-term reliability, regulatory compliance, final process capacity, or performance with the installed utilities and process conditions unless those exact conditions were tested and documented.

Frequently asked questions

What is the difference between a pre-shipment functional test and a factory acceptance test?

A pre-shipment functional test is a defined test of specified equipment functions before dispatch. A factory acceptance test may include that activity, but its exact scope is contractual. It can also include inspections, performance checks, product trials, witness points, or document review when those activities are included in the approved FAT procedure.

What should be included in a pre-shipment functional test procedure?

Include the equipment identity and revision, test scope, configuration, utilities and media, safety controls, test sequence, acceptance criteria, instruments, required records, witness arrangements, deviation process, and approval authority. Link every test point to a requirement source and define what result constitutes pass, fail, or incomplete.

Can a buyer accept equipment with open deviations before shipment?

Potentially, if the contract permits it and an authorized party accepts the specific deviation in writing. The record should state the risk, affected function, interim controls, owner, closure date, and any site work required. An open item should not be treated as accepted merely because it is listed in a report.

Does a successful factory functional test prove site performance?

No. Site performance may depend on installed piping or wiring, utility quality, process media, foundations, connected equipment, controls integration, and operating procedures. A factory test can provide strong evidence for the agreed factory conditions, but site commissioning or site acceptance may still be needed to verify final duty.