Life Inventory + Closet
Dayze turns owned items into life context: what you own, what it is worth, how often you use it, and what you should wear next.
What It Does
Value Tracking
Track purchase price, current value, depreciation, closet value, and unused value across owned items.
Closet Intelligence
Save clothes, shoes, accessories, bags, watches, and jewelry with color, brand, condition, tags, and occasions.
What To Wear
Dayze recommends outfits from your owned closet using occasion tags, wear history, and condition.
Wishlist Planning
Keep a clear buying queue with budget, reason, notes, and a one-tap path to mark items owned after purchase.
Owned vs wishlist
Owned — Things you already have: clothes in your closet, gadgets on your desk, gear in a bag. Dayze tracks value, wear count, cost-per-wear, and outfit picks from owned items only.
Wishlist — Things you want to buy or need to pick up: groceries, ingredients, gear you are eyeing, a jacket you saw online. Use category Other and tags like groceries, pantry, or ingredient. Wishlist items can also store a reason, budget, notes, order date, arrival date, and image.
Example — bacon for breakfast: You do not have bacon yet → add Bacon to your Inventory wishlist. After you buy it, tap Mark owned (and optionally log the spend in Finance). When you cook and eat it, log the meal in the Food Diary — that is the journal of what you consumed, not your shopping list.
How To Use It
- Open /inventory from the sidebar or profile menu. Toggle Owned vs Wishlist to switch views.
- Tap Add Item to open the focused modal, then add category, value, condition, location, tags, notes, and occasions such as work, dinner, travel, or gym.
- Switch between Grid (compact photo wall) and Cards (editorial product layout with wear stats, edit, and upload). Your choice is remembered in the browser.
- Tap the cover photo to open a fullscreen lightbox and browse other shots with ←/→ (same as Your People). Drop or paste onto the cover to add photos; open an item from Grid for the full photo manager.
- Tap Worn or Wear today to update wear count and cost-per-wear on any owned item (clothes and non-clothes).
- Hover a card and tap Edit to update name, price, category, condition, dates, photo URL, notes, tags, and wishlist reason without leaving the page.
- Use the “What to wear” occasion chips to get outfit suggestions from your saved closet.
- Tell Dayze Agent what you bought or own, such as “I bought a black Supreme shirt for $70 SGD in 2nd Street in Orchard Central 2 months ago,” and it records the item for you.
Dayze Agent Capture
Dayze Agent uses the create_inventory_item tool when a user describes a physical item they bought, own, thrifted, received, or wants to remember. It extracts brand, color, item type, purchase price, currency, approximate purchase date, store/location, tags, occasions, and current value where possible.
Inventory capture is separate from finance logging: owned items go to inventory_items. If the user also asks to track the spending, Dayze Agent can additionally log an expense.
Tracked Fields
- Name, category, type, brand, color, size
- Purchase price, current value, currency
- Condition, status, location, notes
- Wishlist reason and buying context
- Wear count and last-worn date
- Tags, occasions, seasons, resale URL
- Cover image + multi-photo gallery (lightbox on tap; manage photos in item detail)
Import from Dripped
Private Dripped closet rows (not only the public storefront at dripped.co/goh) can be copied into Dayze Inventory with an idempotent CLI script.
cd dayze-webapp-main npx tsx scripts/import-dripped-to-inventory.ts --dry-run npx tsx scripts/import-dripped-to-inventory.ts # optional: --username=goh --handle=goh --statuses=OWNED,FOR_SALE,WISHLIST
Re-runs match on metadata.dripped_item_id and update existing rows instead of duplicating them. Money fields are converted from Dripped cents to Dayze dollars.
Operator Notes
Data lives in inventory_items, created by migrations/20260526_inventory_items.sql. The table uses RLS policies scoped to auth.uid().
API route: /api/inventory. If the migration has not been applied yet, the API returns a setup-required message instead of crashing the page.