Free POS buyer test pack: sample CSVs and a demo scorecard

Get the files

• Download the complete bilingual pack (ZIP)
• Read the English instructions (Markdown)
• Read the Spanish instructions (Markdown)
• Download six sample product variants (CSV)
• Download opening stock by location (CSV)
• Download the expected inventory ledger (CSV)
• Download the synthetic sale and return (CSV)
• Download the blank reconciliation worksheet (CSV)
• Download the demo scorecard (CSV)
• Open the printable English and Spanish scorecard (HTML)
• Download the test configuration record (CSV)
• Read the bilingual column guide (Markdown)
• Download sources and provenance (JSON)
• Download the file integrity manifest (JSON)

Download once, compare the same tasks

The complete ZIP and every individual file are available below, without a contact form. Use the English or Spanish instructions first. The product data includes six variants, leading-zero barcodes, similar names, accented text and one zero-stock combination. Opening quantities are in a separate file for the two test locations.

These files extend our export checklist and POS Review's existing inventory scenario. Keep using the finder and online demo scorecard to organize your requirements; this pack supplies the small dataset and evidence sheets to take into the demonstration.

What the stock test should show

Start the target item with 12 available units at A and zero at B. Order 10 more. Seven arrive: five good and two damaged; three remain undelivered. Sell three, return one in sellable condition, then dispatch and receive four at B. The final target balance is 11 at A and four at B. During transit, the four travelling units must stay out of availability at both stores.

The 15-unit final check is 12 opening + 5 accepted − 3 sold + 1 returned. The transfer changes location. The two damaged units and three still with the supplier are separate quantities to explain. All checkpoints are provided in the expected ledger.

Reconcile the files, not only the screen

A supplemental synthetic sale uses three units at 12.00 USD, a 10% line discount and zero tax only to isolate the arithmetic. Returning one unit at its discounted amount leaves 21.60 in net test sales. The worksheet gives 19 checks for product identities, location stock, record counts, discounts, refunds and net test tender. Observed values and differences are blank for you to fill from the report and independently from its export.

Use one report cutoff and timezone. Preserve original exports and map actual record IDs to the suggested TEST labels. Match the original sale on the return. CSV quotes do not protect leading zeros from spreadsheet auto-conversion: import identifiers as text and compare their exact strings after re-export. The sample is neutral data to map into the provider's current template, not a universal import format.

Keep the demonstration free and the result honest

Use an existing isolated test account or a no-cost provider demo and approved test-tender mode. Do not make a real card charge, buy a plan or send an order to a real supplier for this exercise. If the needed setup is unavailable without spending, leave that requirement pending and record the quote. No provider has passed the pack until you have observed the relevant result.

Record the actual country, plan, version, equipment and role. Mark essential tasks before starting. A missing required result stays unresolved; optional successes do not cancel it. This exercise does not establish fiscal compliance, hardware compatibility, card integration, support performance or offline reliability. Add a focused demonstration when any of those are required.

POSFind, POS Review, FreePOS USA and VoVi share ownership through VOVI POS, INC. Links between them connect related buying resources. They are not independent endorsements.

Files and version

Version 1.0.0 contains English and Spanish instructions, seven CSV files, a printable bilingual scorecard, a column guide, sources and SHA-256 checksums. Keep the original download unchanged and work from a copy. The date is the pack publication date, not a test execution date.