Client system · 2026 · Platforms, Integrations
Derb3Omar seller operations platform
A multi-role wholesale marketplace dashboard that moves seller listings through review and reliable WordPress publication.
Problem
Approval is a human business decision; publishing is an external-system operation. Treating them as one step makes failures ambiguous.
My role
Application architecture, seller/admin/field workflows, data security, and WordPress synchronization
Stack
How the work moves
- Step 01Seller listingProfile, media, product data
- Step 02Admin reviewApprove the business record
- Step 03Sync queueSigned, retryable publication
- Step 04WordPressPublic catalog and analytics
The business problem
The public marketplace already lives in WordPress, while structured seller onboarding, media, review, and field operations need a purpose-built application. The integration must preserve a human approval even if WordPress is temporarily unavailable.
Architecture decisions
Approval and synchronization are two explicit states. An administrator approves the marketplace record first. Publication then runs as a signed external operation with visible pending and failure states. A retry does not reverse the business decision or silently lose the listing.
Seller, administrator, and field-agent areas share the same Supabase-backed model. Cloudflare R2 holds media, and replacement assets remain protected until the newer WordPress version succeeds.
Engineering focus
- Row-Level Security and column grants define what each role can read or change.
- Focused test scripts cover validation, analytics, sync state, field operations, and request signatures.
- Scheduled sweeps provide a backstop for delivery and abandoned media, not the primary sync path.
Outcome
The platform provides a recoverable bridge between a structured operations system and an established WordPress storefront.