David/WFDASH-WEBAPP
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
WFDASH-WEBAPP/docs/django-nextjs-parity-backlog.md
SJCoetz 7df7a8850f feat(item-history): add getItemHistory service with 5 PB queries 
Co-authored-by: Orca <help@stably.ai>
2026-07-29 14:51:58 +02:00

2.3 KiB
Raw Permalink Blame History

Django to Next.js Parity Backlog

Target Scope

Only these legacy areas are being rebuilt in Next.js/PocketBase:

  • wfdash basics: customers, companies, suppliers
  • quotes
  • orders
  • driver_list, combined with collection_pool
  • delivery_notes
  • repairs
  • stock flow, combined into order_items first and later separated into a dedicated stock collection

Current Next.js migration status

Core CRM

  • Customers: partial/live
  • Companies: partial/live
  • Suppliers: partial/live
  • Quotes: partial/live — email intake ✅ done (n8n IMAP poll → MCP quotes.create_from_email / quotes.append_reply; see quotes-email-monitor.md)
  • Orders: partial/live

Not migrated / minimal

  • Driver list workflows: partially started through new collection_pool foundation
  • Delivery notes: not migrated
  • Stock management: intentionally folded into order_items workflow for now
  • Repairs: not migrated

Mandatory parity recheck order

  1. Customers
  2. Companies
  3. Quotes
  4. Orders
  5. Driver list / collection pool
  6. Delivery notes
  7. Repairs
  8. Future stock collection

For each module, parity definition

  • Data model parity: required fields + relations
  • Workflow parity: statuses and transitions
  • UI parity: list/detail/edit actions available
  • Automation parity: n8n or API hooks in place
  • Reporting parity: exports/reports needed

Immediate next build tasks

  1. Customer: duplicate handling and merge strategy (replace legacy management commands)
  2. Company: details/address consistency and relation integrity checks
  3. Quotes: explicit quote-to-order action + safeguards against duplicate conversions (covered by quote → order flow on Orders board; duplicates prevented via findOrCreateByMessageId on the email side)
  4. Orders: status board + drv/collection states reflected in UI
  5. Collection pool: assignment UI and filtered work queue
  6. Delivery notes: generate delivery records from delivered/loaded order items
  7. Repairs: rebuild only the useful repair request/order flow

Out of Scope

  • stock_orders
  • customer_portal
  • rep_portal
  • internal_stock as a separate module
  • pos
  • ai_orders inside the app
  • system_monitor inside the app

AI/email/system monitoring moves to n8n and should integrate through API/webhook endpoints only.