6.9 KiB
6.9 KiB
Product Finder - Project Features Summary
Date: March 25, 2026
Project: Product Finder Application for Columbia Metals
Participants: Jesse Salmon, Jason Soltys, Darlene Lampe
Core Application Features
1. Product Selection Workflow
- Multi-step navigation system using button-based interface
- Goal: Minimize text entry - "tap, tap, tap" workflow
- JSON-driven configuration for flexible navigation without code changes
- Sequential selection process: Color → Size → Model/Type → Accessories
2. Color Selection
- Visual color buttons (similar to current implementation showing Black, Bronze, Mill, etc.)
- Filters available products based on color selection
- Mill finish to be removed (not available for any door)
- Default hardware colors match door colors (e.g., bronze door = black pull, white door = white pull)
3. Size Selection System
Standard Sizes
- Three standard sizes for storm doors:
- 2668 (26" x 68")
- 2868 (28" x 68")
- 3068 (36" x 81")
- Display both nominal size (e.g., "3068") and actual dimensions (e.g., "36 x 81")
- Button-based interface (similar to color selection)
- Standard sizes auto-populate width and height fields (grayed out/non-editable)
Custom Sizes
- Custom option button reveals width/height input fields
- Storm doors: Opening size ONLY (no tip-to-tip)
- Display warning in RED: "Opening size only - not tip to tip"
- Patio doors: Either opening size or tip-to-tip allowed
- Toggle between standard size buttons and custom input
4. Product Categories
Storm Doors
- Models: Cobra, King, King Dual Vent
- Category filtering based on selected criteria
- Product images for each model
- Measurement requirement: Opening size only for custom orders
Patio Doors
- Standard size: 5069
- Can use opening size or tip-to-tip for custom
Products to Exclude
- Parts (Z-bars, inserts)
- Discontinued items (marked in database)
- M1200 patio storm door
- Storm door inserts
5. Hardware & Accessories
Hardware Selection
- Types: Brass lever, Satin silver, Black pull, White pull
- Labeled as "Hardware" in CGW system
- Default hardware based on door color
- Optional customization via dropdown
Hinge Side Selection
- Required field - no default setting
- Options: Left hand or Right hand
- Measurement instruction: "Facing the door from the outside, which side are the hinges on?"
- Visual prompt/popup to ensure customer understands measurement perspective
6. Visual Elements
Product Images
- Display product photos for each door model
- Door image flipping: Mirror image based on hinge side selection (JavaScript/CSS)
- Images sourced from website and database
Outside View Indicator
- Proposed design: Doghouse illustration with:
- Small roof/overhang
- Plant or bush beside door
- Wall indication
- Purpose: Help customers understand they're viewing from outside
- Simple, rough design acceptable
Navigation Elements
- Button-based interface throughout
- Visual color swatches
- Product thumbnails
- Continue/Next buttons
7. Data Management
Database Integration
- Source: CGW (Columbia Gateway Windows) database
- Locations: Iola, Kansas City, Lindsberg
- Google Sheets for product data management
- Product codes exported from CGW
Data Filtering
- Filter discontinued items (marked in spreadsheet)
- Remove accessories from main product list
- Column H (Door Type/Subtype): Delete to remove from product list
- Columns J & K: Accessory/hardware flags
Product Naming Consistency
- Challenge: Same products have different model numbers across locations
- Solution: Use catalog names (customer-facing)
- Internal CGW names vary by plant
- Need standardization project for matching products across locations
8. User Experience Features
Add to Cart/Order
- Button to add selected product to sales order
- Appears after all selections made
- Label: "Add to [cart/sales order/hardware]"
Measurement Instructions
- Link to PDF with measurement guidelines
- Accessible from size selection screen
- Shows how to determine hinge side, measure openings, etc.
Validation & Warnings
- Opening size requirement for custom storm doors (highlighted in red)
- Required field indicators (hinge side selection)
- Visual cues for defaults vs. custom selections
9. Architecture & Technical Approach
Navigation System
- JSON file manages all navigation flow
- Changes made via JSON manipulation (no code changes needed)
- Flexible architecture to support iteration
- Current limitation: Toggle functionality requires code changes
Development Philosophy
- Hard-code initial features for rapid iteration
- Avoid premature optimization
- Build architecture after understanding full requirements
- Keep front-end decoupled from back-end structure
10. Future Considerations
Windows
- Primary windows and storm windows have different measurement rules
- "Whole different ball game" - to be addressed later
Parts/Accessories Integration
- Parts sheet for storm door inserts
- Separate handling from complete products
- Discontinued items may need parts availability
Multi-Location Support
- Consolidate product naming across plants
- Maintain location-specific inventory
- Unified catalog names for customers
Key Business Rules
- Storm doors (custom): Opening size only
- Patio doors (custom): Opening size OR tip-to-tip
- Standard sizes: Auto-populate dimensions (read-only)
- Hinge side: Required selection with instructional prompt
- Hardware: Defaults based on color, optional customization
- Discontinued items: Filter from product display
- Parts/accessories: Exclude from main product categories
Implementation Priorities
High Priority
- Size selection with standard sizes as buttons
- Remove discontinued items from display
- Hinge side selection with flip image functionality
- Hardware dropdown with defaults
- Custom size with opening-size-only warning for storm doors
Medium Priority
- Outside view visual indicator (doghouse design)
- Link to measurement instructions PDF
- Add to cart/order button
- Product naming standardization across locations
Low Priority (Future)
- Windows integration
- Parts/accessories handling
- Advanced filtering options
- Multi-location inventory management
Quality & Accuracy Concerns
- Arnie's primary concern: Accuracy of the system
- Emphasis on preventing measurement errors
- Visual aids to reduce confusion
- Clear labeling and validation messages
- "It's too complicated" - need to prove simplicity through good UX
This summary was generated from the March 25, 2026 project planning meeting transcript.