Usefulware PO Match ยท Shopify review reference 142783

Native Shopify purchase orders, real receiving evidence

This recording uses the actual hosted app and synthetic records created in a fresh Shopify Dev shop. These are native Shopify purchase orders, not the app's optional Demo examples.

2 min 41 sec continuous window capture at 2 fps. English captions added; browser toolbar removed. No audio or substituted screenshots. Shopify Admin is localized; the captions explain the receiving steps.

What the recording proves

  1. #PO2 orders 10 units at USD 8.00. Native receiving shows 8 accepted, 1 rejected and 1 pending.
  2. An original PDF is stored privately. Invoice fields are manually entered and confirmed, with an explicit native purchase-line mapping. No OCR is performed.
  3. The confirmed invoice bills 10 units at USD 8.50. The first comparison shows USD 21.00 potential exposure and creates a case.
  4. Shopify Admin accepts the last pending unit. Sync now reads 9 accepted, 1 rejected and 0 pending. The previous case becomes historical.
  5. The same confirmed invoice version is compared again: USD 8.50 quantity exposure + USD 4.50 price exposure = USD 13.00.

Potential exposure requires merchant review of delivery timing and agreed terms. It is not recovered savings or a recommendation to pay. The app sends no supplier email or payment.

Repeat this test in the installed review shop

Download the synthetic reviewer test kit โ€” native PO setup instructions, PDF, valid CSV, negative-quantity CSV and SHA-256 checksums.

In Shopify Admin, use Products โ†’ Purchase orders, an inventory-tracked product and native receiving. Open the app in that same shop, verify Connected Shopify shop and click Sync now. The kit explains each expected result.

Customer sales orders, draft sales orders and another app's private POs are different records. If Shopify returns no native POs, the app says so explicitly. Optional labelled Demo examples do not establish data synchronization. No real purchase, customer store or payment is needed for this test.

All test documents are synthetic and non-payable, without real contact or payment information. If the generated PO number differs from the example, select your actual native PO and adapt the CSV reference. Leave the extra valid CSV import as a draft to avoid duplicate invoice confirmation.