Risky actions stayed explicit.
Exceptional discounts and project kickoff required human approval. External delivery, accounting, payments, and destructive actions were prohibited.
ERP workflow engineering case study
Northstar ERPNext Pilot
Turning inquiry, quotation, accepted work, and invoice-review records into a safe, permission-aware operational command center.
The challenge
The records existed. The daily operating picture did not.
Small service teams often track inquiries, quotes, accepted work, tasks, and invoice follow-up across disconnected screens and spreadsheets. The pilot explored whether those records could explain what needs attention, why it matters, and who owns the next action— without granting automation unsafe authority.
Workflow architecture
From inquiry to draft-invoice attention.
Five bounded stages, with human approval where pricing or accepted work changes state.
- 01Inquiry and duplicate review
- 02Owned opportunity and quotation
- 03Approval and accepted work
- 04Project and three starter tasks
- 05Blocked-work and draft-invoice attention
Engineering decisions
Automation designed to fail safely.
Duplicate prevention was structural.
Deterministic keys, per-run locks, quotation row locking, a unique source constraint, and duplicate-race recovery protected repeated execution.
Failure became an owned state.
Runs recorded attempts, bounded retries, one manual retry, failure ownership, pause controls, acknowledgement, resolution, and manual fallback.
New controls installed safely.
Workflows installed inactive and automation rules installed paused, with no customers, invoices, credentials, endpoints, or external delivery configuration seeded.
Validation evidence
Tested beyond the happy path.
Results below apply only to the documented synthetic, offline, or disposable-site boundaries.
| Evidence area | Recorded result |
|---|---|
| Pilot scope | T01, T02, T04–T10, and T13–T17 passed inside recorded synthetic or offline boundaries. |
| Source contracts | 42 discovered: 33 passed and nine installed-site-only skips by design. |
| Installed validation | Four clean-install contracts and five lifecycle and permission tests passed on disposable ERPNext 16.27.0 and Frappe 16.26.3 sites. |
| Concurrency | Two simultaneous kickoff processes returned one deterministic Project with exactly three Tasks. |
| Lifecycle | Repeated migration, upgrade preservation, rollback, backup integrity, and uninstall readiness passed. |
| Prohibited effects | Communication, email, accounting, payment, banking, dunning, and Sales Invoice records remained zero. |
Honest boundaries
The decision to stop is part of the work.
- Synthetic data only; no employer or customer data.
- Production CSV import remained prohibited because preview validation was inadequate.
- The generated briefing and general assistant were deferred, not represented as completed.
- Inventory and manufacturing modules were outside the Northstar pilot.
- Professional IFS Cloud experience is separate from this ERPNext/Frappe project.
Need an operational workflow translated into software?
JBC scopes practical ERP, automation, and internal-tool work around the decision, permissions, exceptions, and support path.