Last updated · May 2026
Mission trajectory
Central Market Online ships as a full-stack marketplace mesh: storefront discovery, authenticatable dashboards per role, Paystack-powered checkout lanes, manual reconciliation hooks where the business demands hybrid rails, and dispute timelines grounded in chat plus immutable order histories.
This isn't passive listing software — it's the cockpit where fulfilment signals, payment proofs, and moderation decisions converge so commerce stays traceable, reversible where appropriate, and explainable to every party.
Engineering spine
The surface you interact with is assembled with Vite, React 19, and TanStack Router / Start — prioritizing instant transitions, typed navigation contracts, and streaming-friendly route boundaries so dashboards stay responsive even when data planes fan out.
Persistence and identity flow through Supabase — PostgreSQL at the core with Row Level Security enforcing tenant-aware reads/writes, hardened auth sessions, and carefully scoped database helpers for maps, payouts, and anonymised public insights where operators enable them.
Server modules encapsulate payment initialization, fee orchestration, email dispatch, and privileged admin mutations — keeping secrets off the client while preserving a single coherent mental model for engineers extending the stack.
Settlement intelligence
Checkout flows emphasize Paystack-compatible initiation paths so authorization, redirects, and webhook-ready references remain normalized across carts and subscriptions alike.
Where regulators or counterparties require manual transfers, operators can expose prescribed deposit templates — pairing depositor metadata, proof uploads, and admin verification queues without breaking the buyer promise timeline documented in our Refund & dispute policy.
Coordination fabric
Commerce-grade messaging threads anchor negotiations and dispute evidence. Notification surfaces prioritize role-aware urgency — vendors see fulfilment pressure, buyers see delivery deltas, agents see pickup clusters — always respecting moderation outcomes.
Mapping experiences embed privacy-conscious geospatial primitives — blending approximate rider telemetry with vendor-address intelligence — while honoring browser permission UX and offline degradation paths.
Governance
Operators wield dashboards spanning vendor onboarding, payment proofs, manual payouts, analytics snapshots, and security tooling — each interaction emitting breadcrumbs suitable for post-incident narrations.
Buyers and sellers remain independent counterparties; the platform mediates trust through policy + tooling, not substitute warranties on physical goods unless explicitly stated per programme.
Participatory mesh
Operational security hygiene
Authentication leverages Supabase-managed sessions with refresh-token hygiene paths designed to shed corrupt tokens gracefully — minimizing invisible logout loops on degraded networks.
When in doubt, pivot to password resets and official channels listed inside authenticated surfaces — detailed data-handling language lives in our Privacy Policy.
Forward cadence
Release cadence favors incremental modules — observability first — rollback-friendly infrastructure hooks. Roadmaps bias toward richer telemetry on fulfilment SLAs, smarter anomaly surfacing for payouts, and deeper ecological integrations with Nigerian logistics realities.
Nothing here constitutes a binding roadmap promise — timelines flex with regulatory feedback, partner API stability, and operator priorities — yet the architectural runway stays thrilling exactly because merchants deserve tooling that feels cosmic-scale without sacrificing grounded accountability.
Legal anchors