I’m building a small DrapCode app for a Boston furniture shop where customers can browse living room seating and filter by fabric, size and price. The catalog itself is what’s giving me trouble: each sofa or couch has several variants, and I’m unsure whether to keep one collection with variant fields or split the data across a parent collection and a child collection. I also want a details view to open with the right variant already selected, without slowing the page down. I’ve seen third-party listings for 2026 sofas and tried to map their attributes onto my form fields, but the dimensions, materials and seating counts don’t line up cleanly. My concern is that a single flat collection will get messy once the shop adds more pieces, while a relational setup may complicate the filters. Has anyone built something similar in DrapCode and can share how they modeled the data and bound the variant selection to the details view?
I found this roundup, Best Sofas & Couches of 2026, and its attribute list gave me a rough starting point for the parent/child split. I’m still unsure whether the relational setup will make the fabric and size filters slower in DrapCode, so I may test a small catalog before committing.