Overview
| Client | OO Precision Co., Ltd. — Written consent for name and logo [TBC] |
|---|---|
| Industry / Technology | Manufacturing / ERP |
| Period | Nov 2025-Apr 2026 (22 weeks) |
| Scope | Order, inventory and settlement modules | data migration | permission design |
| Stack | NestJS, Next.js, PostgreSQL, Keycloak, Metabase |
| Disclosure grade | L1 Named |
What was the problem?
Physical stock and the books differed by more than 5% at any given time, with no way to trace the cause. Unit prices lived in individual staff files, so the same customer could be quoted two different prices.
Why this approach?
Period-end accounting stayed in the specialist package already in use; we integrated with it rather than rebuilding it. Instead of extending the ERP across every function, we opened only the order-inventory-settlement axis first, with the goal of reaching real production use inside 22 weeks.
What we built
- 01Migrated 12 spreadsheets after documenting 24 cleansing rules
- 02Verified the migration with a row-count and total-value reconciliation table (zero mismatches)
- 03Field-level permissions - cost and unit price masked
- 04Automatic reconciliation of e-tax invoices against bank transactions
Before to After (measured in-house)
Inventory accuracy
94.8%
99.4%
Mispriced orders per month
7
0
Order processing lead time
2.1 days
0.6 days
Monthly settlement close
6 days
2 days
Figures were measured on the same basis before the engagement and after go-live, and the calculation records are retained.