Project description
We sell computer hardware online, and customers use a build configurator to pick a motherboard, processor, memory and other parts before checkout. Right now nothing stops a shopper from combining a CPU and motherboard with different sockets, or memory that doesn't match the board's supported type, and we only find out after the order ships back for a refund. We need a freelancer who can build a compatibility engine inside our configurator that warns about mismatched parts before checkout.
The core task is a specification database covering sockets, chipsets, memory types, form factors and power requirements, wired into rules that compare whatever is already in the build against each new part being added. When two parts won't work, the widget should explain why, not show a generic error, and suggest a fitting category instead. Borderline cases, like a cooler that technically fits but leaves almost no clearance, should also be flagged.
We're open to different approaches: client-side rules fed from our catalog, or a small service the storefront calls on each build change. What matters is speed, accuracy, and a way to update the rules ourselves as new components appear.
What we expect:
— socket, chipset, memory type/speed and physical fit checks
— clear warnings tied to the specific conflicting parts
— an editable rules table, not hardcoded logic
— notes on adding new component families later
The core task is a specification database covering sockets, chipsets, memory types, form factors and power requirements, wired into rules that compare whatever is already in the build against each new part being added. When two parts won't work, the widget should explain why, not show a generic error, and suggest a fitting category instead. Borderline cases, like a cooler that technically fits but leaves almost no clearance, should also be flagged.
We're open to different approaches: client-side rules fed from our catalog, or a small service the storefront calls on each build change. What matters is speed, accuracy, and a way to update the rules ourselves as new components appear.
What we expect:
— socket, chipset, memory type/speed and physical fit checks
— clear warnings tied to the specific conflicting parts
— an editable rules table, not hardcoded logic
— notes on adding new component families later
Web development Cash, Bank transfer
