Building assisted commerce around trust, credit and access
Role-based verification, credit-linked purchasing and agent-assisted transactions helped different market participants use the service through workflows suited to them.
Publication boundary: This is a proprietary system. This page describes only the parts I worked on and omits confidential implementation details, client access and private project material.
At a glance
- Problem
- Agribusinesses faced connected barriers around credit, trust, logistics, market reach, language and digital access.
- My contribution
- I worked on role-specific KYC, retailer credit, call-centre transactions, repayment and delivery coordination, stock records, and market membership tools.
What the system recorded
These published records show the evidence structure without exposing private screens, client access or project data.
- Verification record
- Role-specific identity, address, face, document and shop checks.
- Credit record
- Retailer eligibility, approved credit and the repayment terms attached to each transaction.
- Assisted transaction record
- Orders completed by authorised agents, with delivery and repayment follow-up.
- Market record
- Member verification, fees and other charges managed by market leaders.
On this pageContext
Context
Operating situation
Amana Market brought retailers, suppliers, market agents, market leaders, logistics providers and enterprise users into one commerce environment. Each group had different verification requirements and responsibilities, while some users needed a person to help them complete the digital steps.
The problem
Agribusinesses and market participants needed a way to trade across distance, establish trust, access credit and complete transactions even when literacy, language or unfamiliar technology made self-service difficult.
Operating constraints
- Verification requirements differed by role and could include identity, address, face, document and shop checks.
- A retailer’s verification level affected how much credit they could use to purchase produce.
- Repayment terms varied by transaction type and had to remain visible to the people following up.
- The workflow had to support people who preferred to transact through a call-centre agent in their local language.
My contribution
- Role-specific KYC and compliance workflows
- Retailer credit allocation
- Call-centre assisted transactions
- Repayment and delivery coordination
- Stock-record updates
- Market membership and fee tools
How the system worked
I implemented verification flows for retailers, suppliers, market agents, market leaders, logistics providers and enterprise users. The evidence requested changed with the role, rather than forcing every participant through one generic process.
For retailers, verification fed into the credit-allocation process. Approved credit could be used to buy produce, with repayment due within 14 days of delivery and interest determined by whether the order was inter-market, intra-market or pay on delivery.
I worked on call-centre workflows that allowed authorised agents to transact for users, coordinate delivery, follow up on repayments and keep stock records current. Users who were comfortable with the application could still complete those actions themselves.
I also contributed to market-membership tools through which market leaders could verify members and track membership fees and other charges.
Important system decisions
- Treat verification as a role-dependent workflow rather than a single completed-or-not flag.
- Connect credit access to the retailer’s verified status so eligibility and purchasing rules stayed aligned.
- Make assisted service a first-class operating path instead of an informal workaround outside the product.
- Keep market-leader verification and membership records useful for day-to-day market administration as well as trust.
Result
The resulting workflows made it possible for retailers to purchase produce on credit, for users to complete transactions with help from an agent in their local language, and for market leaders to manage member verification and fees in the same environment.
What this demonstrates
A digital service does not become accessible merely because an application exists. When people already trade through conversations and trusted associations, the system should support those relationships instead of demanding that every user become fully self-serving first.