The challenge
Printer meter readings had to reach the right billing counter in an existing ERP.
What we built
- MPS Monitor API3 connection with token caching and retries
- Device-to-printer and counter-to-charge mapping screens
- Scheduled sync, manual Sync Now and sync logs
The full story
The situation
A managed print services company had its printers monitored by MPS Monitor, but billing ran from an in-house CodeIgniter 4 ERP. Readings had to reach the right printer and the right billing counter, or invoices would be wrong.
What we built
- API connection with company settings, dealer selection, token caching, auto-refresh and retries
- Device sync that pulls paginated devices and stores their counter and consumable data
- Mapping screens linking each monitored device to an ERP printer, and each counter to a charge type
- Scheduled sync plus a manual Sync Now button, with sync logs and API error logs
The detail that mattered
Page counts in the ERP live on the contract-printer record, not the master printer. Mapping the mono counter to the right charge type on that record gave a working path from a live device reading to an ERP page count.
Result
Administrators can browse synced devices, manage mappings, inspect counters and consumables, and review sync history inside the ERP they already use.
