A migration test order should cover more than the payment screen
Walk through confirmation, delivery, receipts, access, refunds and mobile checkout before declaring the new shop ready.

You have copied the products, checked the colours and run one successful card payment. The new shop looks ready. Then a buyer asks where their download is, a course member cannot find the login email, or a refund request lands in an inbox you no longer monitor. A migration test order needs to follow the buyer beyond the payment screen. You are testing a chain: checkout, confirmation, delivery, receipt, access, support and what happens when the transaction goes wrong.
Start with a test plan, not a test order
Before you pay, list the customer journeys your shop must support. A single digital download has a shorter path than a hosted course, membership or coaching call. If you sell several formats, choose at least one product from each important path. Include your most popular product, your cheapest product and anything with unusual access rules or delivery files.
- 1Write down the product, price, discount code if relevant, buyer email address and expected delivery.
- 2Choose the device and browser for the test. Include a phone, not just the desktop setup you used to build the shop.
- 3Record the expected messages, files, links, account permissions and calendar details before placing the order.
- 4Place the order and capture what actually happens at each step.
- 5Repeat the test after making changes. A fix to checkout, email or access can affect another part of the journey.
Check confirmation and payment records
After payment, look at both sides of the transaction. The buyer should see a clear confirmation page with the product name, the amount paid and the next action. You should be able to identify the order in your payment records and match it to the right customer and product. Store.fan sends money straight to your own Stripe account, while Stripe's own processing fee still applies. Check that the order appears where you expect it to by reviewing the relevant payment settings before launch.
| Test | What to verify | Failure to look for |
|---|---|---|
| Confirmation page | Product, amount, next step and support route are clear | A blank page, old brand name or instructions for the previous shop |
| Buyer email | It arrives at the address used and contains the right order details | No message, wrong product or a link pointing to the old domain |
| Payment record | The amount, customer and product can be matched | A missing order or an amount that differs from checkout |
| Discounted order | The discount is applied once and the final amount is correct | An expired, reusable or incorrectly calculated code |
Follow delivery and access to the end
For a download, open the delivery link as the buyer would. Download the file, unzip it if needed and inspect the contents. Check that filenames, licences, version notes and support instructions match what you promised. If you sell digital files through store.fan, compare the delivered package with the product description and test its download delivery rather than assuming that an uploaded file is enough.
For a course, membership or community, use a test buyer account where possible. Confirm that the buyer can sign in, sees the correct product and cannot see something they did not buy. Open the first lesson or member area, test any welcome instructions and check that a returning buyer can find the same access again. For a coaching call or webinar, verify the booking or event details, time zone, joining link and any reminder message. The important question is not simply “did access exist?” but “could a buyer find and use it without asking you?”
Test the unhappy paths
- Use an email address with a typo in a controlled test, if your setup allows it, and note how you would resolve the order.
- Try an unsuccessful payment or abandoned checkout and confirm that no product access is granted before payment clears.
- Test an expired or invalid discount code and check that the message explains what happened without exposing internal details.
- Request or simulate a refund according to your process. Check whether access is removed, what the buyer is told and where the refund status is recorded.
- Look at the support route shown in confirmation and delivery messages. Send a test message and make sure it reaches an inbox you actively monitor.
Repeat the journey on mobile
Mobile checkout is a separate test, not a smaller version of desktop checkout. Open the storefront on a phone with the same link a customer will use. Check that product descriptions, buttons, price, fields and payment controls fit on the screen. Complete the order without switching to a laptop. Then open the confirmation and delivery email on the phone and tap every important link.
If you watch sales from your phone, store.fan has an iOS app with instant sale alerts. That can shorten the time between an order and your awareness of it, but it does not replace the buyer-side test. An alert tells you that a sale happened; it does not tell you whether the customer received the file or found the course.
Decide when the shop is ready
Set a pass condition before you run the final test. For each product path, you should be able to answer yes to these questions: did payment complete or fail as expected; did the buyer receive a clear confirmation; did the correct receipt or order email arrive; did delivery work; did access match the purchase; did refund handling follow your stated policy; and did the same journey work on mobile?
Keep the old shop or redirect plan available while you make the change. Update links in your profile, emails, pinned posts and product mentions only after the new destination has passed the checklist. A store.fan storefront gives you a direct place to send those links, while its free plan is link-in-bio only; paid plans start with a 14-day trial. Choose the setup that matches what you need to sell, and do not treat moving the URL as the finish line.
Not necessarily. Test at least one product from each delivery or access type, plus any product with different pricing, discounts, licences or fulfilment rules. Repeat for individual products when their files, permissions or customer promises differ.
A controlled paid order gives you the clearest evidence about payment, records and delivery. If you cannot do that for every path, use the available preview or test process for the remaining products, but mark those checks as less complete and monitor them after launch.
First identify the order, product and email address, then send the correct access or delivery instructions and record the cause. Fix the underlying link, permission or email problem before directing more customers to that path.
Run the full customer journey before you send your next launch link.
Try store.fanTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.



