RETAIL ERP AND POS OPERATIONS TEST PACK Tellency evaluation resources | Reviewed 3 November 2026 https://tellency.com/resources/erp-evaluation-tools Purpose: assess the connection between purchasing, stock, checkout and finance. Illustrative scenarios are proposed acceptance tests, not customer results or assurances that every configuration passes. Use a sandbox and agreed local currency, tax, devices, payment methods and roles. PROJECT / STORE / ENVIRONMENT: TEST OWNER / FINANCE REVIEWER: SOFTWARE VERSION / DEVICE CONFIGURATION: EVIDENCE LOCATION / DATA-HANDLING RULES: For each case record preconditions, expected result, role, observed result, transaction IDs, evidence, reconciliation, status, gap owner and sign-off date. Allowed statuses: PASS / FAIL / CONFIGURATION REQUIRED / INTEGRATION REQUIRED / NOT TESTED. Record missing capabilities rather than treating them as demonstrated. R01 — PARTIAL SUPPLIER RECEIPT Order 100 units. Receive 90, including 2 damaged units. Confirm usable stock, rejected stock treatment, outstanding order quantity and supplier follow-up. Check how the supplier invoice and any credit relate to accepted quantities. Expected: quantities and documents reconcile under the agreed policy. R02 — BRANCH TRANSFER WITH A SHORT RECEIPT Request 20 units from branch A to branch B. Ship 20; receive 19. Check request approval, dispatch, in-transit ownership, receipt and discrepancy. Expected: the missing unit is investigated rather than silently creating stock at both locations or erasing the difference. Record the correction authority. R03 — SALE, DISCOUNT AND STOCK MOVEMENT Sell a stocked item at the agreed price, then test an authorised discount. Record receipt, inventory movement, tax and tender treatment. Repeat an attempt with a role that cannot approve the discount. Expected: totals reconcile and the permitted/rejected actions match the agreed authorisation rules. R04 — RETURN AND REFUND Return one unit against the sale. Confirm receipt reference, refund authority, tender handling and whether stock is resalable, damaged or quarantined. Expected: quantity, tax and financial effects are traceable; an unrelated sale is not silently altered. Validate payment integration requirements separately. R05 — END-OF-DAY RECONCILIATION Use several agreed tender types in the sandbox. Compare recorded sales, returns, refunds, expected cash, physical count and any settlement reports. Expected: differences have an owner and explanation; payment settlement timing is not confused with the checkout sale date. Confirm required exports/reports. R06 — STOCK COUNT VARIANCE System quantity is 100 and physical count is 97. Capture the count and approval. Check whether adjustment is draft or posted and who can authorise it. Expected: the variance, reason, approval and resulting balances are traceable. A count marked complete does not alone establish a posted financial correction. R07 — LOT OR EXPIRY CONTROL, WHERE REQUIRED Receive two lots with different expiry dates. Attempt the agreed prohibited sale or transfer of held/expired stock. Expected: the configured block or warning matches the acceptance criteria and can be demonstrated at the actual terminal. Do not assume a stock report proves checkout enforcement. R08 — OFFLINE / DEVICE / CONNECTIVITY EXPECTATIONS Write down required devices, printers, scanners and payment connections. Test a network interruption only in an agreed environment. Record what remains available, what queues, how resynchronisation occurs and how duplicates are prevented. No offline capability should be assumed without this demonstration. R09 — MULTI-CHANNEL HANDOFF, WHERE IN SCOPE Create an online order, reserve stock, fulfil or cancel it, and inspect POS/ERP records. Expected: the configuration avoids double allocation and exposes the status your staff need. Validate web/mobile, gateways and marketplace links separately; they are not implied by a generic ecommerce module name. CONFIRMED CUSTOMER SCOPE — CONTEXT ONLY Ajwa Cash & Carry: Tellency finance, sales/POS, inventory, procurement, reporting. https://tellency.com/customers/ajwa Bin Saeed: Tellency POS, inventory and procurement. https://tellency.com/customers/bin-saeed These module scopes are confirmed. They do not claim that either customer has performed the illustrative tests above or achieved a measured financial result. DECISION / GAPS / IMPLEMENTATION OWNER / ACCEPTANCE DATE: Reuse: copy and adapt for evaluation. If publishing an adaptation, identify changes and cite the resource page above when useful. No endorsement, payment or reciprocal link is required. Never include confidential customer records.