Customer Onboarding SOPs

This directory contains the standard operating procedures for onboarding new ERP Unlocked customers.

Which SOP to use

New customer signed contract
        |
        v
Is their ERP already in our registry?
  (prophet21, netsuite, odoo, dynamics, eclipse_e4)
        |
   YES  |  NO
   |         |
   v         v
SOP-OB-001   SOP-OB-002
Fast Path    Full Path
3–5 days     4–8 weeks

Documents

Document	Title	Audience	Timeline
SOP-OB-001	Onboarding — Supported ERP (Fast Path)	CS + ENG	3–5 business days
SOP-OB-002	Onboarding — New ERP Integration Required	CS + ENG	4–8 weeks
SOP-OB-003	ERP Integration Build Checklist	ENG	(used inside SOP-OB-002)

Currently Supported ERPs

ERP	Slug	Status	Write-back
Epicor Prophet21	prophet21	GA	Yes
NetSuite	netsuite	Beta	Partial
Odoo	odoo	Beta (no Dagster sync)	Limited
Microsoft Dynamics	dynamics	Beta	Limited
Eclipse E4 (VMS EPMS)	eclipse_e4	Active (actions-only)	Yes (submit only)
Demo	demo	Internal	N/A

Any ERP not in this table requires SOP-OB-002.

SAP Business One (sap_b1) isn’t listed — it was a design-only stub, never wired into the Dagster sync pipeline or the ERP service factory, and was removed as dead code in #3038 (2026-08-16). A separate, equally-unimplemented sap slug also exists in the DB schema and integration registry (predates #3038, untouched by it) — connection creation for it is explicitly blocked server-side (not_wired error in create-erp-connection.ts). Neither is onboardable; see SOP-OB-001 for detail.

Odoo has real order write-back but no Dagster sync pipeline yet — SOP-OB-001’s fast-path timeline doesn’t apply until that’s built.

Related Docs

• P21_Quick_Start_Guide.docx — Customer-facing Prophet21 setup guide
• P21_Access_Requirements.docx — Prophet21 service account prerequisites
• ../erp/how-orders-are-handled.md — Order processing flow overview
• ../erp/erp-order-verification.md — Order verification and agentic validation
• ../configuration/flagsmith-feature-flags.md — Flagsmith flag reference