home / work and case studies / LOQOL seller portal
Client product contribution · implementation case
LOQOL seller portal case study.
A seller can spend several minutes writing a disclosure answer, then switch fields or get interrupted. Leon contributed to LOQOL's existing seller portal to connect those forms to backend APIs and handle unfinished answers more carefully.
The decision this solved
Let the seller finish typing before replacing their answer.
A seller is halfway through an answer when the page fetches an older saved copy. If the form replaces the text too soon, their unfinished work can disappear. Leon's work focused on that moment: keeping the answer being typed separate from the last saved version, and connecting each field to the right record.
What Leon built
Leon's implementation contribution.
Connect the form to the record
Connected React/TypeScript disclosure fields to backend APIs, the connections used to load and update the seller's answers.
Save at natural stopping points
Added save requests after a pause in typing, when the seller moves to another field, and when they close a form with an unfinished edit.
Keep the answer being typed
Kept the current draft separate from an incoming saved copy while the seller is editing. That separation is important when the page refreshes information in the background.
Evidence on this page
What supports the case.
- Leon's work covers the form interface, its API connections and handling unfinished answers. The team already had the product and its design.
- The diagram explains that work without showing seller records or private client documents. It is not a production screenshot.
- The older public disclosure demo is linked separately, so it is not mistaken for this seller portal.
Have a related problem?