Decakila Coupon System
Screens are faithful reconstructions of an archived system, rebuilt from its real database schema.
The brief
Field technicians earn reward coupons for every repair: issued, capped, activated and audited, across every branch.
Rewarding field technicians across branches means real money moving on paper: coupons need caps, activation records, and a straight answer to “who approved this?”.
What I built
A field-technician and coupon-rewards system for a consumer-appliance brand: technicians perform repair operations, the system issues coupons tied to a technician, a branch and an amount, caps them at a maximum, records who activated what and when, and keeps a full append-only audit trail under role-based permissions.
A coupon with a biography
Each coupon shows its value against its cap, its technician, its branch and its full activation history: real money, fully explained.
Technicians, measured fairly
Specialisation, rate, branch and coupons earned per technician. Rewards follow recorded repairs, not memory.
"Who approved this?" has an answer
An append-only audit log over every table plus a role-permission matrix down to view / add / edit / delete per group.
Repairs drive the rewards
Repair operations generate the coupons they justify: issued against a technician, a branch and an amount, capped at a maximum.
The hard part
A coupon lifecycle with a value cap and activation tracking; role-based permissions down to view / add / edit / delete per group; and an append-only audit trail over every table.
The result
Every coupon accounted for, issued, capped, activated and audited, across every branch and every technician.
Every coupon accounted for: issued, capped, activated, audited.
Role-based permissions down to the single action.
A straight answer to "who approved this?".
Delivered
