A night-light RFQ should not begin with color and packaging. It should begin with the product\u2019s power architecture and target market. A mains plug-in night light, a rechargeable portable light and a replaceable-battery product can require different construction, evidence and acceptance tests.<\/p>\n\n\n\n
Define the architecture first. Then turn broad phrases such as \u201cautomatic sensor\u201d and \u201cmarket compliant\u201d into measurable behavior and traceable documents.<\/p>\n\n\n\n
Use one of the following identities in the RFQ:<\/p>\n\n\n\n
El night-light product families<\/a> category can help buyers review available forms. Do not transfer one model\u2019s plug, sensor, battery or document status to the whole category.<\/p>\n\n\n\n IEC 60598-2-12 addresses particular requirements for mains socket-outlet mounted nightlights. IEC 60598-1 provides general luminaire requirements. Those scopes illustrate why the finished architecture must be identified before the document request is written.<\/p>\n\n\n\n Do not use \u201cEU,\u201d \u201cUS\u201d or another region label as a substitute for a reviewed country list and product architecture.<\/p>\n\n\n\n A plug must fit the intended socket system without unsafe mechanical interference. Review pin dimensions and orientation, product-body clearance, access to adjacent outlets and the effect of rotating or offset designs.<\/p>\n\n\n\n IEC 60884-1 covers household plugs and socket-outlets within its stated scope. The relevant market may use additional or different requirements, so the buyer should obtain a market-specific review rather than infer compliance from appearance.<\/p>\n\n\n\n During sample approval, install the night light in representative socket arrangements. Check whether it blocks adjacent outlets, places controls against the wall, becomes unstable or creates unintended leverage on the socket.<\/p>\n\n\n\n \u201cDusk-to-dawn\u201d is not an acceptance criterion. Specify the states and transitions.<\/p>\n\n\n\n If motion sensing is present, add target path, installation position, ambient condition, hold time and retrigger behavior. Avoid one unqualified distance claim.<\/p>\n\n\n\n State the intended role: orientation light, decorative marker, sleep-area light or another application. Then define the normal output, distribution, color setting and control behavior appropriate to that role.<\/p>\n\n\n\n If the product offers RGB, tunable white, dimming or effects, document how the user selects the mode, whether the last state is remembered and what happens after power restoration.<\/p>\n\n\n\n Do not infer safety or sleep suitability from a warm color name. Keep medical or health claims out of the RFQ unless they have an appropriate evidence path.<\/p>\n\n\n\n Create a document list for the exact product, market and manufacturer. Check:<\/p>\n\n\n\n Packaging marks should be supported by the document package. A logo printed on a carton is not independent proof. Use the broader guide to LED product compliance documents<\/a> for the document-review workflow.<\/p>\n\n\n\n USB charging, emergency operation, replaceable batteries, wireless control or fragrance modules can change the product\u2019s construction and evidence requirements. List every function in the quotation and require revised drawings and documents when the configuration changes.<\/p>\n\n\n\n Do not allow a supplier to add a commercially attractive feature after sample approval without repeating the affected review.<\/p>\n\n\n\n The RFQ should identify retail carton dimensions, protective inserts, included accessories, multilingual instructions, warnings, rating information, barcode placement and master-carton requirements.<\/p>\n\n\n\n Inspect whether the plug pins, diffuser and controls are protected during transport. For plug-in products, the packaging should prevent the product body from loading the pins or damaging visible finishes.<\/p>\n\n\n\n Artwork approval must use controlled files. Record which model, plug and accessory set each artwork version represents.<\/p>\n\n\n\nBuild a market and architecture matrix<\/h2>\n\n\n\n
Campo de decisi\u00f3n<\/th> RFQ entry<\/th> Evidence or sample check<\/th><\/tr><\/thead> Mercado objetivo<\/td> Country or defined market group<\/td> Applicable regulatory\/document review<\/td><\/tr> Power architecture<\/td> Plug-in, corded, rechargeable or replaceable battery<\/td> Product drawing and rating label<\/td><\/tr> Alimentaci\u00f3n<\/td> Voltage, frequency or charging input<\/td> Datasheet and sample measurement<\/td><\/tr> Plug or connector<\/td> Exact configuration and orientation<\/td> Dimensioned drawing and physical sample<\/td><\/tr> Light behavior<\/td> Output state, dimming, color and memory<\/td> Sensor\/control truth table<\/td><\/tr> Included functions<\/td> USB, emergency, fragrance or other feature<\/td> Scope review for every added function<\/td><\/tr> Documentos<\/td> Buyer-approved list linked to model and factory<\/td> Certificates, reports or declarations as applicable<\/td><\/tr> Embalaje<\/td> Label, warnings, instructions and accessories<\/td> Approved artwork and packing sample<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Verify the plug as an interface<\/h2>\n\n\n\n
Convert sensor language into state logic<\/h2>\n\n\n\n
Starting state<\/th> Input or condition<\/th> Expected response<\/th> Registrar<\/th><\/tr><\/thead> Bright ambient<\/td> Light level decreases<\/td> Turn-on threshold and delay<\/td> Measured condition and time<\/td><\/tr> Night mode<\/td> Light level rises<\/td> Turn-off threshold and delay<\/td> Measured condition and time<\/td><\/tr> Near threshold<\/td> Small light fluctuations<\/td> Stable state or defined hysteresis<\/td> Cycling observation<\/td><\/tr> Power interrupted<\/td> Power returns<\/td> Default or remembered state<\/td> Repeated test<\/td><\/tr> Manual override<\/td> User command<\/td> Priority over sensor and reset behavior<\/td> Truth-table result<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Define light behavior separately<\/h2>\n\n\n\n
Request model-specific safety documents<\/h2>\n\n\n\n
\n
Treat extra functions as scope changes<\/h2>\n\n\n\n
Approve packaging as part of the product<\/h2>\n\n\n\n
Run a sample acceptance sequence<\/h2>\n\n\n\n