FIELD ORDER ACCEPTANCE RECORD
Companion: https://yenra.com/wireless-software-for-mobile-field-sales/
Prepared September 8, 2026. Editable test worksheet.

Use an authorized sandbox with test accounts, products and recipients.
Prevent real shipments, stock reservations and customer messages.
Have the mobile app, CRM/ERP integration and supported workflow documented.
Define acceptance criteria and exception owners before testing.

Date/time zone/test owner:
Device, OS, mobile app/version and role:
CRM/ERP versions and integration/configuration reference:
Customer/delivery address/product identifiers and units:
Price list/version/effective date/currency/approval requirements:
Inventory source, snapshot timestamp and reservation policy:
Local order reference and expected server identifier:

For each case record the expected and actual result in EACH system.
Cases: normal order; stale stock; unauthorized discount; address change;
loss of connection around submission; supported retry; supported amendment;
app restart and return to connectivity.

Case, workload and exact interruption point:
Phone state and timestamp:
Server order identifier and timestamp:
Accepted/rejected/pending lines and quantities:
Price and stock exceptions, owner and decision:
Final fulfilment handoff and test confirmation:
Duplicate search and final number of orders for the test reference:
Evidence location, pass/fail/pending, owner and retest:

Fictional example: request 12 cases from a 09:00 snapshot showing 20;
at 10:15 only 8 are accepted for the requested date. The remaining 4
require a visible customer decision under the business's actual rules.
Verify the final accepted quantities and one explainable order result.
Generic offline-recovery guidance and supplier sources are in the guide.