Software Updates

Remove emojis and improve logo display with inline styles for better email client compatibility

Add branded magic link template for employee invitations

Match website fonts - add Playfair Display for headings and brand

Update logo URLs to use simpler filename without spaces

translate tasks TaskCard and fix imports

Fix orders API syntax error - remove duplicate code sections

Add manual migration instructions for source column

Make orders API resilient to missing source/customOrderDate columns - use select instead of include

Add migration for order.source and run migrations during vercel build

Force Vercel rebuild to regenerate Prisma Client

Add extensive logging to orders API to diagnose 500 error

Fix TypeScript file input ref typing in order dialogs

Add error handling for order transformation and fix paymentStatus type conversion

Add debugging and error handling for order source updates

Fix Prisma type issues in orders API - add type assertions for customOrderDate and source fields

Fix orders API 500 error - add source field to response with fallback

Add debug logging to orders page to diagnose empty orders issue

Fix admin orders page to use AdminI18nProvider instead of next-intl

• Replaced useTranslations() from next-intl with useAdminTranslations()
• Updated translation calls to use admin translation structure (t.orders.title)
• Fixed runtime error: 'Failed to call useTranslations because context not found'
• Admin pages use custom AdminI18nProvider, not NextIntlClientProvider
• Kept English as fallback for labels not yet in admin translations
• Portuguese translations already exist in AdminI18nProvider for orders

Add safer fallback for order source field

• If source is missing, infer from isShopifyImport
• Prevents errors on orders created before source field existed
• Production rebuild will regenerate Prisma types with source field

Improve analytics error logging for debugging 500 error

Add order source management and fix sorting by custom order date

• Orders now sort by customOrderDate (if set), then createdAt
• Added Order Source field with options:
• Katura Website (default)
• In Person
• Private Commission
• Shopify
• Other
• Changed 'Site' label to 'Katura Website' throughout
• Added Order Source card in order detail page with inline editing
• Updated orders API to include and update source field
• Updated Portuguese translations with new source options
• API already had correct sorting logic (customOrderDate nulls last, then createdAt)

Add Portuguese translations for admin Orders page

• Added comprehensive admin translation section to messages/pt.json
• Includes translations for:
• Common admin UI elements (buttons, actions, loading states)
• Status labels (pending, paid, in_production, shipped, etc.)
• Dashboard stats and labels
• Orders page (titles, table headers, filters, actions)
• Updated /src/app/admin/orders/page.tsx to use translations:
• Added useTranslations() hook
• Replaced all hardcoded English text
• Updated status humanization to use translation keys
• Table headers, filters, and action buttons now in Portuguese
• Created reference document at docs/admin-translations-pt.json

humanize status in list, include customOrderDate in API response

use error.issues instead of error.errors for Zod validation

expose delete, humanize status, persist customOrderDate, show attachments & address lines

add founding client status and manual customer creation

• Add isFoundingClient, foundingClientVerifiedAt, foundingClientVerifiedBy fields to User model
• Create database migration for new fields with indexes
• Implement discount calculation in lib/military-discount.ts
• Apply founding client discount at checkout (stackable with military/gift balance)
• Store discount in Stripe payment intent metadata
• POST /api/admin/customers - Create customer without password
• Customers can register later and account is linked automatically
• Support for military and founding client flags during creation
• PATCH /api/admin/customers/:id now supports isFoundingClient toggle
• Tracks who verified and when
• Existing customers without passwords can register
• Password added to existing account
• Preserves all history, orders, and special statuses

comprehensive audit, fixes, and new route scaffolding

• Fix: Remove double-fetch in products-tab.tsx
• Feat: Add SETTLED_ORDER_STATUSES constant and getAnalyticsOrderFilter() utility
• Feat: Scaffold 6 new analytics routes (funnel, attribution, search, retention, fulfillment, inventory)
• Docs: Add comprehensive audit and roadmap with findings, recommendations, and implementation plan

Add customOrderDate, photoAttachments fields and regenerate Prisma client

• Added customOrderDate and photoAttachments to Order model query
• Regenerated Prisma client to include new fields
• Created migration runner script for order customizations
• Ran migrations successfully

Add order deletion for owners and improve order list UX

• Only OWNER role can delete orders
• Only CANCELLED orders can be deleted
• Confirmation dialog before deletion
• Audit log entry created on deletion
• Cascades to delete related records (items, payments, etc.)
• Entire table row is now clickable
• Clicking row opens order detail page
• Better UX - no need to find the dropdown
• Hover effect shows row is interactive
• Shows customOrderDate if set, otherwise createdAt
• Label '(custom)' appears next to custom dates
• Orders sorted chronologically by display date
• Dropdown click events stop propagation (don't trigger row click)

add cancel order functionality to admin orders page

convert Decimal to number and move components to client side

move mapOrderStatusToStage to server-side in orders page

checkout/payment/db fixes and orders card (2026-01-18)

add TypeScript fixes completion summary

• Document resolution of 3 TypeScript errors (collection import, refund-policy, returns)
• Explain root causes and solutions
• Provide patterns for future policy pages
• Confirm all compilation errors resolved ✅

resolve TypeScript error in returns page metadata

• Changed from dynamic getPageSEO() call (which expected 'returns' key in SEO_TEMPLATES)