Keep a smart-home purchase file that matches the actual model
Keep the regional model, quotation, purchase proof and support documents together for a smart-home purchase.
Updated:
Give each purchase a model-specific evidence file
A useful smart-home purchase file connects what you intended to buy, what the seller offered and what arrived. Start with the exact model, regional version and hardware generation, then keep the quotation and purchase proof beside it. For example, Eve's support page separates Australian specifications from other regional entries. Its AU enclosure is listed as 77 mm wide, 77 mm high and 60 mm deep. Preserve those fields with the region and exact model; measurements alone do not identify firmware or compatibility. A saved product name alone can be ambiguous. The archived European plug photograph demonstrates that a visually similar product category can contain materially different regional hardware. It is not evidence for an Australian Eve unit or a substitute for the received model label and instructions.
ACCC warranties guidance ? ACCC price display guidance ? Eve Energy AU entry in global support document ?
Separate the offer from the receipt and the delivery
Save the quotation with its date, seller, quantities, included items and postcode conditions. Keep the final receipt and order confirmation separately so changes remain visible. ACCC price-display guidance addresses total consumer pricing, while your file needs the concrete line items for the actual offer. The unpacked Bridge photo illustrates why instructions, adapters and accessories deserve an explicit included-items record; the pictured European package is not an Australian delivery checklist. If a promised item is missing, preserve the original description and observed delivery contents rather than editing the quote to match what arrived.
Use a complete fictional discrepancy record
Suppose a fictional order lists 2 bulbs, 1 hub and 1 button, while the received parcel contains 2 bulbs and 1 hub. The missing quantity is 1 button, not a vague statement that the package looks incomplete. Record the item description, relevant order line, received contents and date. This example does not determine a legal remedy or explain how a particular seller will resolve a problem. It shows how a precise inventory supports a clearer question. Do not infer compatibility or completeness from the number of boxes, since a starter kit can contain several separately identifiable components.
Keep promises in their own documents
Store warranty terms, the software-support statement, return information and any model-specific compatibility answer separately. ACCC explains that warranties are additional to consumer guarantees; do not replace that distinction with an invented universal warranty period. An official support page and a seller's return window answer different questions, and each can have its own conditions. The archived Bridge image identifies a controller body but cannot prove its purchase date, qualifying seller or remaining support. If a later issue arises, retain the relevant correspondence and exact product information rather than relying on a screenshot of a similar product listing.
Review the file when the setup changes
Add a dated note when you replace a hub, move equipment to another platform or change the intended use. Preserve the original purchase evidence while keeping current instructions accessible. A simple folder index can name model identification, offer, payment and delivery, support, and later correspondence as separate entries; avoid including passwords or unnecessary personal data in a shared copy. The finished file should make a future question easier to answer from evidence. It does not certify electrical safety, determine individual consumer rights or promise that every compatible service will remain available throughout the product's physical life.
Open official model documentation ? Open official model documentation ? Open official model documentation ?
