SKQ-039

Seller Server Map

Future API contract readiness

Aasaan alfaaz

Yeh screen seller preview data ko future API contracts se map karti hai. Abhi koi live server call, order, payment, stock, ledger, payout, ya trust change nahi hota.

Contracts

7

Evidence

0

Ready

100%

Server readiness map ready. This maps preview packets into future API contracts only.

Preview source map

Local packets to future records

Contract matrix

DTO readiness

SellerRequestPacketDto

Customer need packets, safe customer hints, seller reply drafts, and retry-ready offline copies.

Endpoint

GET /v1/seller/requests

Blocked

Cannot create final order, expose customer wallet, expose exact private family notes, or send unreviewed reply.

Event and permission map

Event

seller.request.opened

Permission

seller.request.view

Source keys

inboxPackets, replyDrafts, voicePackets, offlinePackets

Storage migration map

Local preview packet

Future server record - Migration rule

seller reply draft

seller_reply_drafts - draft-only until customer decision gate accepts

packing checklist

seller_packing_proofs - proof-only until handover proof gate

rider handoff

delivery_handoff_drafts - no rider job until dispatch gate

customer receive proof

customer_handover_proofs - issue window must remain open

partner/COD proof

payment_evidence_records - ledger stays separate from payment proof

settlement view

seller_settlement_views - read model only, not payout authority

Readiness runner

Request inbox

Select checks before saving a contract-readiness packet.

Checks

5

Evidence

0

Ready

100%

Saved readiness packets

No readiness packet saved yet. Save only after scope, DTO, permission, event, and no-runtime checks are selected.

Boundary locks

Map only, no runtime

SKQ-039 maps preview data to future API contracts only. It does not call a server, create a database row, create an order, assign rider, move stock, post ledger, pay seller, refund customer, or change trust.
Local storage packets are demo evidence. Future backend must revalidate actor, role, shop, zone, customer scope, proof, and permission before accepting anything.
Seller can see only seller-safe customer data. Customer wallet, family-private details, exact private notes, internal review comments, and hidden scores must stay server-protected.
Money evidence remains separate from accounting truth. Partner callback, COD note, ledger entry, and settlement release must each have separate gates.
Offline drafts can sync later, but conflicts, duplicate packets, stale prices, expired holds, and issue-window changes must be reviewed before any final action.

Connected seller surfaces

End-to-end demoSeller QASeller inboxReply builderPreparationSettlement pending