Compare every proposal against one controlled application brief so price differences can be traced to equipment, interfaces, evidence and support rather than assumptions.
Use the same product, packaging, dose range, output definition, utilities, site boundary and acceptance method for every supplier. Mark each item as included, excluded, buyer-supplied or still to be confirmed.
| Scope area | Questions to compare | Evidence to request |
|---|---|---|
| Core process | Which pouch route, dosing method and seal process are included? | Equipment list, format range and product assumptions. |
| Product and pack feed | How are product and pouches or film supplied and replenished? | Interface drawing and responsibility schedule. |
| Quality controls | Are coding, verification, checkweighing, inspection and rejection included? | Device specification, tracking sequence and reject challenge. |
| Line integration | Which conveyors, guarding interfaces, signals and downstream handovers are included? | Layout, sequence description and control-interface schedule. |
| Delivery and acceptance | What trials, FAT, site work, training, documents and spares are included? | Test protocol, deliverables and exclusions. |
A lower price is not a like-for-like saving when the line boundary or acceptance evidence is different.
Issue one application brief and compare every response in a common scope matrix. Check the same product, pouch, dose, good-pack output, quality controls, utilities, layout, trials, installation and support assumptions.
Resolve every blank or qualification before using total price as the decision.
Potential exclusions include product feed, change parts, pouches or film, coding, inspection, reject equipment, conveyors, guarding interfaces, extraction, utilities, site installation, training, trials, documentation and spare parts. The actual exclusion list is supplier-specific.
Ask for a written responsibility schedule rather than assuming these items are included.
Tie performance to a named product, packaging specification, format, line configuration, good-pack definition and test method. State the run stages, acceptable rejects, quality checks and evidence that will be retained.
A cycle-rate statement without these conditions is not a complete acceptance definition.
Compare installation scope, commissioning, operator and maintenance training, manuals, drawings, software backups, recipe records, spare-parts information, warranty terms stated by the supplier and the support route. Include any site or remote evidence needed to diagnose faults.
Only treat an item as included when it is written into the proposal or agreed schedule.
An option can be useful, but it should not be counted as part of the production solution until its price, interface and acceptance effect are understood. Likewise, a buyer-supplied item needs a defined connection point and responsible party.
Use the specification checklist, trial guide and aftercare page alongside the quotation.
Lancing can identify inclusions, exclusions and evidence against the real product and pouch requirement.
