What should an importer specify for a smart App air fryer?
Specify the user action, required connection, appliance response and evidence for each proposed App feature. A Wi-Fi version being available does not confirm remote start, voice control, a particular App or support for every phone. Keep essential, optional and excluded functions separate in the quotation.
A useful smart air fryer brief describes what the buyer wants a person to do with a phone, what the appliance remains responsible for, and who will support that experience. “App control” alone leaves too much room for different quotations.
Yaoyuan has confirmed that a smart App version with Wi-Fi connectivity is available for each of the 22 added models, P535–P556. Use that availability to open a version-specific discussion. The feature brief below turns a request into decisions that can be quoted, demonstrated and approved.
Start with one buyer use case
Describe a situation, not a feature slogan: who uses the phone, where they are, what information or action they need, and what they do if the connection is unavailable. “See whether the cooking cycle has finished while elsewhere in the home” is a clearer proposed use case than “full smart control.” It still needs a supplier response about feasibility.
Mark each request as essential, optional or excluded. If the buyer only needs readable on-appliance settings, ask for a standard catalog version alongside the connected quotation. If phone interaction serves a specific customer need, define that interaction before adding it to packaging. The existing digital and manual controls guide covers the basic panel choice; this brief covers the connected experience.
Keep the model baseline separate from App functions
JD-02A, Catalog P535, is listed at 8.5 L and 1700 W, with a 0–30 minute timer and an 80–200 °C range. Its original picture shows two rotary controls and a windowed drawer. JD-02B, Catalog P536, shares the printed capacity and power, but has a digital upper panel, a 0–60 minute timer, a 70–200 °C range and eight listed preset menus.
These are facts about the printed catalog configurations, not an approved connected sample. A digital display does not prove Wi-Fi capability, and the available App version does not establish that its settings match either pictured panel. Put the exact model and requested version at the top of the brief, then obtain the connected control specification.
Separate monitoring, setting changes and heating commands
Use one row for each proposed phone action. The examples below are buyer questions, not a list of supported functions. Ask the supplier to complete the dependency, appliance behavior and evidence columns before agreeing any sales wording.
| Phone action | Network dependency | Appliance authority | Required evidence | Release promise |
|---|---|---|---|---|
| Monitor cooking status | Specify local or Internet access and stale-data indication. | Reading status does not authorize a change. | Demonstrate visible states and update delay. | Name only the states demonstrated. |
| Change time or temperature | Define when a command can reach the appliance. | Define permitted ranges, confirmation and panel priority. | Show accepted and rejected changes on the approved sample. | State when adjustments are available. |
| Initiate heating | Propose explicit connection and eligibility conditions. | Qualified engineering review must define authorization, rejection and local stop behavior. | Review the control specification and controlled demonstration. | Exclude unless separately approved for this order. |
| Receive a completion notice | Identify Internet, account and phone-permission dependencies. | A notice is not confirmation that someone attended the appliance. | Demonstrate delivery and unavailable-service behavior. | Describe the notice without promising uninterrupted delivery. |
A command shown as “sent” on a phone is different from one accepted by the appliance. Ask how the user sees the difference. Carry the agreed behavior into the separate pairing and offline sample-acceptance plan; do not use the feature brief as a substitute for testing.
Example: a deliberately limited connected brief
The following is a hypothetical buyer request, not a JD-02B specification or a supplier commitment:
Model direction: JD-02B / P536, connected version. Planned quantity: 1,000 PCS. Destination country, plug and voltage: buyer to specify. Proposed essential use case: view cooking progress from a phone. Optional: a completion notice. Excluded from this brief: initiating heating from the phone. Please identify the actual App, supported phones and operating systems, connection requirements, and whether the proposed functions can be supplied.
Request a response against each line: available as quoted, requires a different configuration, unavailable, or needs clarification. Record the demonstration and document needed to close each open point. If the essential use case cannot be supported, reconsider the connected option instead of replacing it with a vague “smart” claim.
Name the responsible parties before approving the claim
NIST IR 8425 treats consumer IoT as a product that can include the device, supporting software and backend services. That broader scope helps frame responsibility; it is not certification of these air fryers.
For each proposed feature, identify the appliance, App-distribution, service-operation and buyer-support contacts. Ask who receives a fault report involving both the phone and appliance. Handle post-approval version changes through the component-change approval process; keep software-support periods and lifecycle terms in the separate support specification and applicable connected-product security review, not in a feature label.
A private-label appliance does not automatically include a custom App, buyer-owned software or an App-store account. Separate branding deliverables from software ownership and operating responsibilities. Use the App account and device-handover guide to assign the return and replacement journey.
Send a feature brief that keeps both versions identifiable
Attach the selected model, connected or standard version, feature matrix and unresolved questions to the private quotation request. Add quantity, country, plug, voltage, packing, OEM requirements and destination port. Use the exact model page to select the correct version-specific RFQ. Yaoyuan supplies factory-direct wholesale orders; MOQ starts from 1000 PCS.
Buyer questions
Does a Wi-Fi version mean every phone action is available?
No. Connectivity availability and function scope are separate decisions. Ask for the actual App and a written response to each requested action.
Can the brief include remote start or voice control?
It can identify them as questions, but neither is confirmed for this range. Keep them out of product promises unless the exact order version is reviewed and approved.
What should a buyer do before paying for custom App work?
First confirm whether custom development is offered. Then define deliverables, ownership, operating costs and support responsibilities separately from the appliance branding order.
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 your required phone experience and the functions that remain unconfirmed. For a specific model, use its connected-version request so the model and catalog ID stay with the inquiry.
Yaoyuan Electric supplies factory direct, wholesale only. MOQ starts from 1000 PCS. Retail and one-piece orders are not accepted.