CMS Architecture for Estate Sales

Why estate sale sites need structured content

Estate sale companies run a high-turnover content operation. Sales go up, run for a weekend, and come down. Photos need to load fast and display in order. Shoppers want to browse by date, location, and category. A structured CMS keeps this cycle manageable without rebuilding pages every week.

Recommended collections

Sales

The primary collection — each item represents one estate sale event:

• Title (PlainText, required) — descriptive name, e.g., "Midcentury Modern Estate - Pacific Heights". Used as the primary field.
• Slug (PlainText) — URL-friendly identifier.
• Description (RichText) — detailed sale description including highlights, parking info, and payment terms.
• Short description (PlainText) — teaser for cards and listings. Help text: "1-2 sentences for search results and social sharing."
• Featured image (Image, required) — primary photo for cards and hero.
• Street address (PlainText) — full street address. Help text: "This address will be hidden until the reveal date."
• City (PlainText, required) — for location filtering.
• State (Option) — U.S. state abbreviation.
• Zip code (PlainText) — for radius search.
• Address visible (Switch) — controls whether the full address is shown. Help text: "Toggle on when the address should be revealed to the public, typically 1-2 days before the sale."
• Categories (MultiReference) — link to Categories collection.
• Status (Option) — upcoming, active, completed, cancelled.
• Featured (Switch) — highlight on homepage.
• Terms (Option) — cash only, cash and credit, all forms of payment.
• Percent complete (Number) — optional field for day-two or day-three discount indicators.
• External ID (PlainText) — EstateSales.NET listing ID for sync. Help text: "Your listing number from EstateSales.NET."
• Company notes (PlainText) — internal notes, not displayed on the website.

Sale Dates

A companion collection for the specific dates and times each sale runs:

• Sale (Reference, required) — link back to the parent sale.
• Date (DateTime, required) — the calendar date of this sale day.
• Start time (PlainText, required) — e.g., "9:00 AM". Help text: "Doors-open time for this day."
• End time (PlainText, required) — e.g., "3:00 PM".
• Day label (PlainText) — e.g., "Day 1 - Full Price", "Day 2 - 25% Off", "Day 3 - 50% Off".
• Discount (Number) — percentage discount for this day (0, 25, 50).
• Order (Number) — display order.

Sale Photos

A companion collection for photo galleries with sort order:

• Sale (Reference, required) — link back to the parent sale.
• Image (Image, required) — the photo.
• Caption (PlainText) — describes the item shown.
• Category (Reference) — link to Categories so photos can be filtered by type.
• Order (Number, required) — display order in the gallery. Help text: "Photos are sorted by this number, lowest first."
• Featured (Switch) — use as an additional cover image.

Categories

Reusable item categories that span across sales:

• Name (PlainText, required) — e.g., "Furniture", "Jewelry", "Art", "Kitchenware", "Tools", "Vintage Clothing", "Electronics".
• Icon (Image) — category icon for filter badges.
• Order (Number) — display order in filter menus.
• Description (PlainText) — short explanation, e.g., "Sofas, tables, chairs, dressers, and bedroom sets."

Key relationships

• Sales -> Sale Photos (companion multi-reference) — photos reference back to their sale, enabling large galleries with sort order and captions.
• Sales -> Sale Dates (companion) — each sale has 1-3 date entries with times and discount tiers.
• Sales -> Categories (multi-reference) — tag each sale with the types of items available.
• Sale Photos -> Categories (single reference, optional) — tag individual photos for in-gallery filtering.

Integration considerations

If you sync listings from EstateSales.NET, store the external listing ID on each sale. Photo sync requires a companion collection approach since EstateSales.NET listings often have 50-200 photos per sale.

See Companion Collections for the pattern and Date Fields for working with date ranges.

Tips for estate sale CMS

1. Address privacy is critical — estate sale addresses are typically hidden until 1-2 days before the sale to prevent early arrivals. Use the "Address visible" Switch field and conditionally display the address in your Webflow design.
2. Photo sort order matters — buyers browse photos to decide if a sale is worth visiting. Use an Order field so you can put the best items first.
3. Separate dates from sales — a sale running Friday through Sunday is three date entries, not three sales. The companion collection pattern keeps this clean.
4. Categories enable browsing — shoppers searching for "mid-century furniture" or "jewelry" need category filtering. Use a standalone collection, not tags.
5. Plan for volume — active estate sale companies may run 5-10 sales per week, each with 100+ photos. Consider your CMS plan item limits when estimating capacity.