What should a buyer approve beyond successful Wi-Fi pairing?
Approve the complete journey from using the supplier-identified App and download route to identifying the correct appliance, handling a refused phone permission, recognizing a lost connection and recovering without misleading status. One successful pairing on the supplier's phone does not establish that the intended customer can set up and use the quoted version.
Start with the connected sample, not a similar-looking catalog unit
Yaoyuan's 22-model App and Wi-Fi range spans 5 L, 6.5 L, 8.5 L and 12 L catalog capacities. Each model is available in a connected version. The original pictures and printed parameters describe the catalog configurations, so nominate the App version explicitly when arranging a sample. A familiar panel or the same capacity is not enough to identify the software being evaluated.
For example, KQZX07 / P543 and KQZX08 / P544 are both 6.5 L, 1500 W catalog references. Those shared numbers do not prove identical pairing steps, account behavior or App functions. Record the selected model, sample serial or other unit identifier, control-board and firmware revision, App name and version, phone model, operating-system version and intended sales country. Request missing identifiers before treating observations as repeatable results.
Agree the setup conditions before measuring the experience
Ask for the supported phone platforms, minimum versions, App-store regions, network requirements and pairing instructions for the quoted configuration. Do not assume a Wi-Fi band, Bluetooth-assisted pairing or a guest-network mode from the word "smart." Where a cloud service is involved, distinguish a working local wireless link from internet access and account-service availability.
Choose a small, documented set of buyer-relevant phone and network combinations. Agree how many attempts to observe, what the operator may consult and which outcomes require clarification. A useful record shows the start condition, action, elapsed time, visible message and recovery route. Record measured times rather than inventing a universal acceptable number of seconds.
Treat phone permissions as part of onboarding
For an App using local-network discovery on iPhone or iPad, Apple's local-network privacy guidance explains the access prompt and the ability to change permission later. This does not confirm iPhone or iPad compatibility for a Yaoyuan model.
Android's Wi-Fi permission documentation distinguishes nearby-device permissions from permissions still required by particular APIs and older versions. These platform rules explain why the phone and App versions matter; they do not establish Android compatibility for the quoted air fryer.
On the declared supported platforms, ask the supplier to demonstrate the documented path when a required permission is declined and later restored. Decide whether the message or instructions identify the missing step without asking the user to disable general phone or router security. Keep permission refusal separate from an incorrect network password, an unavailable account service and a device that was never discovered.
Observe distinct connection states
Use the following as a proposed review matrix, with expected outcomes agreed for the exact version before observation. It is not a list of functions already verified on these models. Record "not applicable," "not supplied" or "not confirmed" where a state or feature falls outside the quoted configuration; do not assume that an account, cloud service or pending-request function exists.
Follow the supplied written operating and pairing instructions using the agreed non-heating setup and an authorized operator. Stop and escalate any abnormal behavior. Do not bypass protections, attempt unattended heating or create network loss by interrupting appliance power during cooking.
| Condition | Observe and retain | Buyer decision |
|---|---|---|
| First installation and pairing | Correct publisher and download route, account requirements, device discovery and the identity shown after binding. | Can the intended customer identify the right App and the right appliance using the supplied instructions? |
| Permission declined | Exact message, affected step and documented recovery after permission is restored. | Does support need a platform-specific explanation before the quick-start guide is released? |
| Internet unavailable but local network present | Which displayed information remains current, which actions are unavailable and how the App labels that state. | Are any cloud-dependent features being described as local or offline features? |
| Appliance disconnected from the network | Last-known values, timestamp or stale-state indication, action availability and on-device status under the approved procedure. | Could an old reading be mistaken for the current appliance state? |
| Connection restored | Updated identity and state, clear handling of any pending request and whether a new user action is required. | Does the recovery match the agreed function brief rather than silently implying that an earlier request succeeded? |
| App closed and reopened | Sign-in state, selected appliance and fresh versus retained information. | Is the buyer approving a reproducible customer journey, not only a continuous demonstration session? |
Resolve a stale-status example without overstating the cause
Imagine a buyer sees a remaining-time value on the phone after the sample has lost its network connection. This hypothetical observation does not prove that the appliance is still following that value, that a command was accepted or that heating behavior is unsafe. It establishes a narrower question: what does that screen mean when communication is interrupted?
Ask the supplier to identify the displayed value's source, the expected disconnected indication and the documented recovery. Compare the App and local display within the approved demonstration. If the meaning remains unclear, hold the relevant status claim and quick-start wording; do not replace the observation with "works offline." An App can retain a screen without providing a current reading or offline control.
Turn observations into a specific approval decision
Separate three outcomes: demonstrated as agreed, clarification or correction required, and outside the quoted scope. An unsupported optional function is not automatically a defect, but it must not remain in the accepted marketing promise. Link each issue to the sample and software versions, an observed state and the next responsible reviewer. Retest the affected journey after a correction rather than carrying an old screenshot forward as approval of a new version.
This record supplements the wider air fryer sample approval. It does not replace electrical safety assessment, radio documentation or software-security review. Use the App feature brief to define what should work and the App account and device handover guide to prepare the return and replacement journey.
Buyer questions
Does a successful pairing video prove that the App works in our market?
No. It records one sample, App, phone, account and network combination. Check the intended App-store region, supported phones and customer instructions, then record the agreed combinations on the quoted version.
Does Wi-Fi mean the air fryer needs the internet for all operation?
Not necessarily. Confirm on-device, local-network and cloud-dependent functions separately. The connection label alone does not establish what remains available when internet access is lost.
Can we use one approval for two models with the same capacity?
Only if the supplier documents the relevant shared configuration and the buyer approves that applicability. Equal catalog capacity and wattage do not establish identical App, firmware or pairing behavior.
Connect the App brief to your private quotation
Send the product model, quantity, country, plug type, voltage, packing request, OEM request and destination port. Add the selected App / Wi-Fi version, intended phones and market, proposed observation conditions and unresolved connection questions. Use the exact model page when you are ready to nominate a sample.
Yaoyuan Electric supplies factory direct, wholesale only. MOQ starts from 1000 PCS. Retail and one-piece orders are not accepted.