Beyond day-to-day maintenance, I owned [a project / integration / migration] on the ERP side at INNOVIOR Africa Group. This entry walks through one piece of that work end to end. (Every bracket is a placeholder — swap in the real story.)
The problem
[Describe the starting pain in one or two lines, e.g. “Order data lived in a separate system and was re-keyed into the ERP by hand, causing delays and errors.”] This hurt [who] because [consequence, e.g. month-end close took too long / stock counts drifted].
The goal was to [objective, e.g. automate the sync / migrate legacy data into the new ERP / build a reliable integration].
The approach
I worked on [which ERP, e.g. SAP/Odoo/Dynamics] and tackled it in stages:
- Discovery — mapped [the data / the process] and agreed on [scope / source-of-truth] with [stakeholders].
- Build — implemented [what, e.g. an integration via REST API / a custom module / an ETL pipeline] using [tools/languages, e.g. Python, the ERP’s connector framework].
- Validation — reconciled [records / totals] and ran [testing approach, e.g. parallel runs, UAT with users].
- Rollout — deployed to [environment / users] with [cutover plan / rollback safety].
Key technical decisions:
| Decision | Why | Trade-off |
|---|---|---|
| [e.g. real-time vs batch sync] | [reason] | [trade-off] |
| [e.g. tool/library choice] | [reason] | [trade-off] |
| [e.g. data mapping strategy] | [reason] | [trade-off] |
The impact
After it shipped:
- [Metric, e.g. “reduced manual entry by X hours/week”].
- [Metric, e.g. “cut data errors / reconciliation time by Y%”].
- [Qualitative win, e.g. “users trusted the numbers again”].
[Optional: what I’d do differently, or what came next — bracket it.]
Takeaway
ERP work is less about flashy features and more about [theme, e.g. trustworthy data and reliable plumbing]. Replace the brackets above with the real numbers and names once they’re confirmed.