Warehouse Workflow Lab

Warehouse vendor comparison worksheet

Published by Voodoo Robotics · workflows.voodoorobotics.com

Person responsible for this worksheetDateVersion

Requirement control

What to do: Give every need a Requirement ID and mark it required, preferred, or a future idea.

This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.

Vendor response

What to do: Use the Requirement ID to connect every vendor answer to the same need.

This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.

Requirement IDGive the requirement a unique number.

Vendor / solutionEnter the supplier and exact product or service being evaluated.

Native / configured / customNative needs no change; configured uses settings; custom requires new software or hardware work.

Evidence referenceName the photo, report, scan, system record, or observation that proves the answer.

LimitationWrite one specific fact, concern, or item still needing proof.

DependencyState what must be completed first.

Exception pathDescribe how the vendor solution keeps work identified and recoverable when this requirement fails.

Commercial and lifecycle

What to do: Compare one-time and recurring cost plus who is responsible.

HardwareInclude the amount, whether it is one-time or recurring, and what is covered.Example: $3,000/year including supportSoftware / licenseEnter the one-time and recurring software charges, included users or devices, and renewal basis.Example: $18,000/year for 40 devices, updates, and supportIntegrationEnter the one-time and recurring connection cost and what work is included.Example: $24,000 one time for WMS task and confirmation messagesInstallationInclude the amount, whether it is one-time or recurring, and what is covered.Example: $3,000/year including supportSupport / replacementInclude the amount, whether it is one-time or recurring, and what is covered.Example: $3,000/year including supportTrainingInclude the amount, whether it is one-time or recurring, and what is covered.Example: $3,000/year including supportExpansionState the cost and practical work needed to add more users, devices, zones, or sites.Example: $850 per added device plus one day of configurationExit / data portabilityState how the warehouse retrieves its data and continues work when the contract ends.Example: Nightly CSV export of tasks, confirmations, users, and configuration

Scoring

What to do: Use the Requirement ID so each score connects to the original need and proof.

This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.

Requirement IDGive the requirement a unique number.

CriterionName the single requirement or quality being scored in this row.

WeightEnter this criterion’s share of the total importance. All criterion weights should add to 100%.

Vendor scoreScore 0–5: 0 cannot meet it, 1 is an unproved claim, 3 is demonstrated, and 5 clearly exceeds the need.

Evidence qualityChoose the strongest proof actually supplied for this score.

Risk adjustmentEnter 0 when proof is strong or subtract up to 5 score points for unproved claims or major dependencies.

Weighted resultMultiply the weight percentage by the adjusted vendor score. Example: 20% × (4 − 1) = 0.60.