A plain-language boundary for the public website.
The FAQ keeps public promises aligned with the current app boundary and the staged roadmap in the grand scheme document.
Frequently Asked Questions.
Get answers to the buying, planning, and verification questions that should be clear before a project starts.
Planning
Is Verifurn a normal furniture checkout?
No. A cart behaves more like a project shortlist. Products move toward purchase only after fit, cost assumptions, verification scope, and buyer approval are recorded.
Can buyers save furniture before login?
Yes. The public site is designed for anonymous saves first, then those items can merge into a project after auth and Supabase persistence are connected.
Can a floor plan image become exact dimensions automatically?
It can help with intake, but exact dimensions still need calibration. Verifurn should treat every room plan as unverified until a known measurement scale is attached.
Verification
What proof do I get before purchase?
A verification dossier can include actual product media, measurements, supplier quote records, finish notes, packing assumptions, risk notes, and a buyer approval snapshot.
Does AI certify products?
No. AI can summarize, draft, and assist operators, but it cannot mark an item verified, approved, purchasable, compliant, or customs-ready.
What catalog details stay protected?
Public visitors see buyer-safe product information. Supplier contacts, source URLs, operator notes, and protected procurement data stay inside authenticated workflows.
Orders
When does furniture actually get purchased?
Only after the buyer approves the exact item spec, evidence packet, estimate assumptions, scope exclusions, and purchase coordination step.
What happens at warehouse handoff?
Receiving, packing, crating, documents, milestone updates, and issue notes stay attached to the same project record that holds the original approval trail.