When package customization explodes, choose patch, satellite, or spine replace. This page states the phase-one documents, the owner and the acceptance metric. This narrative explains rework risk for «When Packaged ERP Won't Bend: Patch or Replace the Spine» and what phase one must freeze.
| Decision lens | Common trap or cost | Safer cut |
|---|---|---|
| patching standard docs | Scope drift | Freeze phase one: satellite write-back |
| upgrade wipes custom | Rework/blame | Owners+change orders |
| patch-on-patch | Post-go-live rollback | Accept: keep/satellite/replace matrix |
Why not all modules for patching standard docs?
All-modules stretch risk; close satellite write-back first, then extend.
Why custom vs SaaS/package?
Value is auditable boundaries and keep/satellite/replace matrix, not more menus.
How to estimate time/budget?
By transaction-chain effort for satellite write-back; change windows priced apart.
How does DaXi Technology accept?
Replay real work for satellite write-back; metrics in contract—not «feels ok».
Turn «patching standard docs» into an acceptable phase-one loop DaXi Technology scopes «When Packaged ERP Won't Bend: Patch or Replace the Spine» with boundaries and acceptance—call +86 139-2520-6166. partner page