FAEDA customer app
Every seller replies in one customer-safe language.
Standardizes replies across shops, street vendors, helpers, home chefs, pharmacies, service providers, and group buying so customers can compare safely before any order draft.
Aasaan alfaaz: customer pehle request karta hai, seller proof deta hai, phir payment/delivery safe partner flow se hoti hai.
Today
need
Near
seller
Safe
proof
Before anything is final
Request first, proof first, customer approval first.
Customer compares available, partial, substitute, quote required, time required, not available, and rejected with reason responses. This screen can prepare the request and show safe next steps. It cannot secretly take payment, hold stock, send a rider, release money, or punish anyone without proof.
Customer shortcuts
SwipeTry it now
Tell FAEDA what your family needs.
Save a request first. FAEDA can route it to a shop, vendor, helper, home chef, pharmacy, service provider, or group buying lane. This does not create payment, delivery, or stock hold by itself.
Best next route
Rider/helper
Customer needs someone to buy from nearby with a budget cap.
Next step
Errand request
Safety
No spending above budget without customer approval.
Ready check
100% request ready
Seller reply language
Every seller replies in words a customer understands.
A seller reply helps the customer compare options. It never creates payment, stock hold, rider assignment, payout, or final penalty by itself.
Seven allowed response statuses
Lane mapping
Customer comparison packet
Customer can compare this response against other sellers without seeing hidden seller cost, other-customer data, internal scoring, or private operations.
Step
Standard Seller Response Packet
Record
Seller reply
Route
Shop / retailer
Seller
Shopkeeper
Status
available
Status code
SELLER_RESPONSE_AVAILABLE
Amount candidate
PKR 1,850
Next action
Customer can compare, ask a question, or accept into an order draft later.
Reply is not final action
Why this matters
Shop, vendor, helper, home chef, pharmacy, service, and group lanes now speak the same response language.
Customer can compare responses safely before CCQ-011 decision hub turns one accepted response into an order draft candidate.
Rejected with reason is supported so sellers can decline honestly without silently damaging trust or hiding the reason.
People involved
Who may help with this request?
What customer can do
Compare seller replies using the same seven response statuses.
See clear meaning, next action, validity, proof requirement, and no-hidden-cost boundary.
Keep response evidence separate from acceptance, payment, dispatch, stock, ledger, payout, and trust penalty.
What seller must do
Reply with the same customer-safe language in every lane.
Give reason when rejecting, quote clearly when price is not final, and mark time required when preparation or arrival needs delay.
Avoid creating false stock, final delivery promise, or payment claim from a simple reply.
Proof records
Keep these proof records separate.
Safe actions on this screen
Compare replies
Select status
Record reason
Ask revision
Move to decision hub later
Safety checks before public use
All seven statuses visible
Every lane maps to same statuses
No response creates payment or inventory movement
What FAEDA will not fake
FAEDA will not show fake wallet balance
No money moves until licensed partner proof exists
Seller stock is not held until seller confirms
Rider is not assigned until dispatch is approved
Refund or replacement needs review first
Private seller cost is never shown to customer
Other families' data stays private
No trust penalty without proof review
Next safe steps