The refund we spend the most effort designing against isn't caused by a broken document.
It's caused by a buyer guessing what was inside the box.
A resale package is a wrapped parcel with a price on it. And for years, the product description has been the product's name.
"Resale Package."
Great. What's in it?
"Resale documents."
Thank you.
So people buy the wrong one. A payment gets unwound, two people lose a morning, and a closing slips a day over a question that could have been answered for free.
The property page exists to kill that guess.Top of it: the address, plus three badges. Unit. Lot. Block.
One house, three naming systems, because the county, the developer and the association never agreed on one. Whichever one is printed on the buyer's contract is on the page.
Under that: the association, and the management company standing behind it. You know exactly whose shop you're in.
Then every package genuinely purchasable for that property, with its price and its options.
And beside each one, a small arrow. Click it, and the package unfolds.
Folders inside folders. Real file names. Real nesting — the same subfolder structure those documents actually sit in inside the management company's accounting system.
Nobody types that list. Nobody could.A package isn't a fixed pile of files. One item might be a live folder pulled from the accounting system. One might be a letter that only exists once you buy it. One might be an entire automation with its own steps.
So to draw the list, the page rehearses the order. It resolves every item, walks the automation's file-gathering and letter steps, and reports what would come out the other end.
A hand-typed contents list is a lie within a week. This one is true this morning.
Transparency before payment isn't a nicety. It's a refund-prevention feature that happens to look like a shop window.
Up next: why title companies never buy one house at a time — and what that does to a shopping cart.