docs: data structure foundation for lead-to-service pipeline
ERPNext doctype relationships and field additions:
- Customer → Service Location → Subscriptions + Equipment
- Project with installation task templates
- Dispatch Job linked to project and location
- New custom fields: wifi_ssid/password, sip_username/password,
gpon_serial, cwmp_serial, radius credentials on Service Equipment
Order wizard flow (website + agent):
- Address check → plan selection → customer info → dates → payment
- Atomic creation: Customer + Location + Subs + Equipment + Project
+ Tasks + Dispatch Job + fibre port reservation
Existing field tech app inventory:
- TasksPage (jobs + tickets), ScanPage (photo/live/manual),
DevicePage (detail + customer link), DiagnosticPage (speed test)
- useScanner composable (3-strip photo scan for multi-barcode)
- Offline queue with replay
Migration gaps identified: WiFi/VoIP provisioning data,
RADIUS credentials, product catalog, fibre→RQA address matching
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
fa37426f34