Free, printable resource

Software Trial Scorecard

Use one scorecard per plan to compare the same tasks. Record what passed, which steps needed a workaround, and what the vendor still needs to price.

Adapt the fictional food and brewery exercises to your work. Use made-up recipes, orders, and customer details. Before signing up for a vendor trial, check its limits, payment requirements, and cancellation terms.

This worksheet is free and works in your browser without an account. Need a shortlist? Compare Zoho Inventory, Stocksmith, and Katana for a small U.S. food business.

Your evaluation

Choose three must-haves before testing

Record evidence, not impressions

For every test, record: required result; actual result; status; evidence reference; workaround; plan/add-on needed; unresolved question.

Pass means you observed the required outcome and recorded supporting evidence. Fail means the requirement was not met. Unknown means the evidence does not resolve it. Not tested means you have not run the task. Not needed means the task is outside your stated requirements; it is not a pass.

Food manufacturing practice scenario

This simplified traceability exercise is separate from the proposed 10 kg exercise in the food guide. Do not compare its quantities with that exercise's production yield.

Create fictional ingredient lots ING-A and ING-B, a recipe TEST-RECIPE, finished batch FOOD-001, and fictional customers CUSTOMER-X and CUSTOMER-Y. Use arbitrary test dates and quantities; these are not a real recipe.

On a small screen, swipe the table sideways. With a keyboard, focus it and use the arrow keys.

Fictional food production tasks
TestAction and evidence to record
Receive ingredientsReceive 10 kg under ING-A and 15 kg under ING-B with different expiry dates. Find both balances, supplier references and expiry dates.
Consume two lotsRecord 3 kg from ING-A and 4 kg from ING-B into FOOD-001. Check remaining balances are 7 kg and 11 kg and the batch retains both lot references.
Split dispatchRecord 20 finished units; dispatch 8 to CUSTOMER-X and 5 to CUSTOMER-Y. Identify the 7 remaining units and both dispatch records.
Trace both directionsStarting from ING-A, locate FOOD-001 and both customers. Starting from a dispatched unit's batch, locate ING-A and ING-B. Save or export the evidence.
Expiry and holdAttempt to allocate expired or held test stock. Record whether the system blocks, warns, permits an override, or provides no control. Record who can override.
Recipe and allergen informationChange the test recipe version and a fictional allergen field. Check what historical batches retain, how changes are logged, and where information is only a note rather than a control.

A completed scenario does not establish regulatory compliance. Confirm which records and controls your business needs separately.

Brewery scenario

Create fictional brew BREW-001, ingredient lots MALT-A and HOPS-A, vessels TANK-1 and TANK-2, and package lots CAN-001 and KEG-001. Use a single explicit volume unit: litres.

Fictional brewery tasks
TestAction and evidence to record
Ingredients into brewReceive malt and hops with lot references. Consume test quantities into BREW-001. Check remaining stock and traceability back to both lots.
Transfer and lossRecord 100 L in TANK-1, transfer 95 L to TANK-2 and record 5 L loss. Confirm the system explains the complete 100 L balance without silently creating stock.
Packaging splitPackage 40 L into 80 × 0.5 L cans and 50 L into 5 × 10 L kegs; record 5 L packaging loss. Confirm the 95 L balance and links to BREW-001.
Packaging materialsConsume 80 empty cans and 5 test keg units. Record how stock and costs handle consumable packaging versus returnable containers.
Trace dispatchDispatch part of each package lot to two fictional customers. Find remaining stock, shipments, brew history and original ingredient lots from either direction.
Exceptions and exportsCorrect a test entry, inspect who changed it, and export a brew/packaging report. List any information required for your own tax or reporting process that the export lacks.

This scenario does not validate excise calculations, duty reporting, product quality or regulatory compliance.

Test records

Fill only the tests relevant to your industry. Keep unrun tasks at Not tested; choose Not needed only when the task is outside your stated requirements. Printed blank fields leave room for handwriting.

Receive ingredients

Consume two lots

Split dispatch

Trace both directions

Expiry and hold

Recipe and allergen information

Ingredients into brew

Transfer and loss

Packaging split

Packaging materials

Trace dispatch

Exceptions and exports

Cost and implementation check

Do not record an unknown cost as zero. Ask the vendor to confirm the scope in writing.

Decision record

Decision rule: A must-have in Fail blocks acceptance. Unknown or Not tested requires clarification or a trial; Not needed must be justified before evaluation and does not count as a pass. Record any limitation and decide explicitly whether a workaround meets the requirement.

Back to save controls

Next: model your quoted costs or return to the comparison. Save your answers before leaving.