# Averon private beta — tester guide

Version 11 · 17 September 2026

Use fictional personal/business details. Purchases are simulated or Stripe test only; no goods, real charges or payouts. ChatGPT sign-in remains required. Only operator-approved emails can use application pages, even with a purchase link.

## Access walkthrough — operator and tester together

1. Operator opens /test, signs in and adds the tester's ChatGPT email. No invitation email is sent. Share the beta URL yourself.
2. Tester opens https://joinaveron.com/test in their own browser and signs in. Record whether the merchant workspace opens.
3. An account that has not been approved must see the access-denied explanation. Opening /merchant/ or an existing purchase link must not grant access.
4. Operator removes the approved tester. Their next API/page request must be rejected. Returning focus to the portal rechecks access. Content already delivered cannot be recalled from a person's browser.
5. Restore access if further testing is wanted. Existing workspace and purchase records should remain. Removal does not disconnect a store, cancel purchases or revoke a private receipt token; it restricts account access.

## Complete simulator journey

1. Open Merchant workspace. Complete test merchant setup and create a stocked product with explicit variant, price, shipping, tax and refund terms.
2. Open its purchase link as an approved tester. Choose Buy now, confirm the exact total and simulate a successful full contribution. Check the receipt and exactly one ready order in the merchant workspace.
3. Start a separate Fund together purchase. Contributor A supplies part of the total. Check that no ready order exists yet. Share with approved contributor B, who supplies the remaining balance. Confirm exactly one order for this purchase.
4. Refresh/retry the completed contribution; totals and order count must not increase.
5. Create a third purchase, contribute partly and cancel through merchant tools. Verify a pending refund first. Confirm the simulated refund and check the receipt, refund total and absence of a ready order. Retrying the confirmation must not increase the refund.
6. Submit feedback at /test: steps, expected/actual result, device/browser and time. Never include passwords, card data, secret pairing codes or private receipt links. Operator checks feedback appears once.

A simulator result is not proof of Stripe card checkout or WooCommerce behavior. Stripe standalone purchases retain existing operator restrictions. Do not use live cards.

## WooCommerce walkthrough

Follow /integrations/woocommerce-setup.md on a merchant-owned public HTTPS staging store. An authorized administrator installs and pairs plugin 0.9.0; configure supported EUR, stock, quantity-one and base-region tax/shipping. Disable external fulfilment automation. Select stocked simple products or explicit variations.

Repeat direct and shared journeys with Stripe test checkout. Check the pending stock reservation before contributions; only successful full verified funding may confirm the same native order. Test expiry, cancellation, refund accounting, duplicate events, changed stock/price, disconnect and reconnect/retry. Record native order ID, non-secret errors and observed results. Do not treat fixture checks as live-store evidence.

Current limits: target up to €100, fixed shipping, test payments, no real fulfilment or payouts. Payment verification currently depends on return/manual checks; background Stripe completion webhooks are pending.