How we modernized a legacy commissary platform for a multi-state corrections vendor.

Aging on-premises architecture

A monolithic, on-premise codebase with no cloud path — every facility required on-site servers, manual updates, and expensive truck-roll support contracts. Extending the platform meant modifying a brittle core with no test coverage.

Siloed, inaccessible data

Inmate rosters, commissary orders, account balances, and grievance records lived in separate systems with no API surface. Cross-facility reporting required manual exports and spreadsheet consolidation.

Manual operations at every layer

Inventory reordering was done from gut feel, indigent account resets ran on a manual schedule, and grievance routing was entirely email-based. Staff time that could be automated was consumed by repetitive administrative work.

Dated hardware-locked UI

The inmate-facing kiosk interface hadn’t meaningfully changed in a decade. Facility procurement teams were starting to cite the UI as a contract-renewal objection — a platform modernization delay was turning into a revenue risk.

Representative product UI — illustrative, anonymized

Modern kiosk ordering — indigent logic, limits, and live balance built in

Modern inmate commissary kiosk software handles indigent account management, weekly spending limits, and order cut-off windows as first-class platform features — not as workarounds bolted onto a legacy thick client. The rebuilt kiosk runs in a browser, works on any touchscreen hardware, and stays in sync with the facility’s jail management roster automatically.

• →Indigent status synced from the JMS — no manual override required
• →Per-inmate weekly spend limits enforced at cart level, not on submission
• →Real-time account balance visible throughout the ordering flow
• →Cut-off window enforcement: orders lock automatically at the configured time
• →Lobby and booking kiosks share the same codebase and admin platform

Role-based admin with facility-level configuration inheritance

A commissary admin platform for a multi-state operator must support corporate-level defaults that individual facilities can override — not a flat permission model. The rebuilt admin enforces a role hierarchy from central operations down to facility staff, with every config change audited and every override visible at the corporate level.

• →Multi-tier RBAC: corporate ops, facility director, floor staff — each scoped correctly
• →Facility inherits corporate menu and pricing; local overrides tracked separately
• →Fulfillment queue, inventory, and weekly revenue in a single view
• →Order status, holds, and indigent-account exceptions managed from one screen
• →Audit log on every config change — compliance-defensible at inspection

Representative product UI — illustrative, anonymized

Inmate and lobby kiosk ordering

Web-native touchscreen ordering for inmate commissary — real-time cart, live account balance, automated indigent-status logic, weekly spend limits, and cut-off window enforcement. Lobby and booking kiosks on the same platform, one codebase, zero per-terminal licensing.

Role-based admin with facility inheritance

A multi-tenant admin platform where corporate operators configure global defaults and facility managers override only what differs locally. Role-based access controls govern what each staff tier sees and can modify — from central ops down to individual facility staff.

Jail management system integration

Automated roster import from the facility’s jail management system keeps the inmate population list current without manual re-entry. Classification, housing unit, and indigent-status flags flow directly into the commissary and grievance modules.

Payment hardware integration

Native integration with bill-reader kiosk hardware and payment processors — deposits reflected in real time, without a third-party middleware layer. Family deposit portals on the same stack, reconciled automatically against the hardware event stream.

Representative product UI — illustrative, anonymized

Representative product UI — illustrative, anonymized

Demand forecasting per facility

Weekly commissary demand predictions trained on order history, population movement, and seasonal patterns. Buyers receive a pre-populated reorder recommendation every Monday morning — stockout events dropped substantially in the first operating quarter.

Kiosk upsell recommendations

Contextual product suggestions at the checkout step of each kiosk order, driven by order history, facility demographics, and current inventory position. Deployed at the point of maximum purchasing intent — not as a banner or pop-up.

Fraud and indigent-abuse detection

Velocity checks, balance anomaly scoring, duplicate-order detection, and unusual deposit-pattern flagging — all running automatically. The fraud team receives a prioritized queue of flagged accounts rather than raw transaction logs to review.

AI-assisted grievance triage

Each incoming grievance is classified by category, priority level, and deadline risk within seconds of submission. The model drafts a policy-compliant response for staff review. Average handling time dropped significantly after rollout, with deadline compliance reaching near-100% in early data.

Legacy replaced without downtime

The on-premise monolith was decommissioned facility by facility in a parallel-run migration — no client-facing outage, no lost order data, no manual re-entry. The modern web platform came online incrementally while the legacy system remained in read-only standby.

AI running in production, not a pilot

Demand forecasting, kiosk upsell, fraud detection, and grievance triage are all live in production across every facility — not isolated to a proof-of-concept environment. The AI systems were built as first-class platform features, not bolt-on additions.

Six-figure R&D tax credit outcome

The engineering work done on this engagement — novel AI systems, new platform architecture, custom hardware integration — qualified for substantial R&D tax credits. Code and Trust documented and structured the work to maximize defensible claim value for the client.

Platform now differentiated in procurement

Facility procurement committees that previously cited the client’s aging UI as a renewal objection now cite the modern kiosk experience and AI capabilities as strengths. The software product moved from a liability in contract renewal conversations to a selling point.

What happens after you submit:

• →We respond within one business day — usually same day
• →A 30-minute fit call to understand your platform and goals
• →If there’s a match, we scope a discovery engagement
• →No pitch decks, no RFP theater — just a real conversation