Digital PowerMarketplace Platform

Software Development Proposal
November 2026
JinnByte
Digital Power Marketplace Platform
00Contents
00
Proposal

Table of Contents

01
Introduction

Overview

Digital Power Marketplace Platform is a multi-vendor marketplace where approved Saudi vendors sell products such as perfumes, bakhoor, dates and clothing to customers in Saudi Arabia and internationally.

The platform consists of a Customer App and a Vendor Follow-up App for iOS and Android, a Vendor Web Portal, an Admin Panel for Digital Power's team, and a backend with a documented REST API hosted on AWS in Digital Power's account. It works in Arabic and English, with prices shown in SAR, USD or EUR.

This proposal covers design, development, testing, store publishing and handover of the complete Phase 1 platform.

0Mobile apps for iOS and Android
0Web panels for vendors and administrators
0Third-party integrations
0Ways to add products
0Languages, with right-to-left layout
0Display currencies
02
Platform

System at a Glance

One backend and REST API serve every application, connect every provider and take products in from every source.

APPLICATIONSINTEGRATIONSPRODUCT SOURCESCustomer AppiOS and AndroidVendor Follow-up AppiOS and AndroidVendor Web PortalWebAdmin PanelWebHyperPayCards, Apple Pay, Google PayShipping CompanyRates, shipments, trackingWhatsApp ProviderOTP and notificationsGovernment VerificationCommercial registrationFirebase and Amazon SESPush and emailManual entryCSV or ExcelSallaZidVendor REST APIMarketplace PlatformBACKEND · REST API · AWS
ApplicationsBackend and REST APIData flowing between components
03
Roles

Users of the System

Four user types, each reaching only what its role allows. Access is enforced in the interface and in the backend.

Customer

Browses as a guest, registers by email, Apple, Google or WhatsApp code, shops, pays, tracks orders, manages wallet credit and requests refunds.

Vendor

Registers with a commercial registration number and, once verified and approved, manages store, products, orders, earnings and subscription.

Platform Admin

Manages vendors, pricing, orders, refunds, promotions and content. Access can be limited with permission profiles.

External System

A vendor's own system that creates and updates that vendor's products through the REST API, using its own API key.

UserCustomer AppVendor Follow-up AppVendor Web PortalAdmin PanelREST API
Customer
Vendor
Platform Admin
External System

Filled dot: where each user works. The Customer App and both vendor surfaces call the same REST API behind the scenes.

04
Deliverables

Scope of Work

The complete Phase 1 platform, from design to store publishing.

iOS and Android

Customer App

  • Welcome screens and guest browsing
  • Sign-in by email, Apple, Google or WhatsApp code
  • Password reset by email link or WhatsApp code
  • Profile, addresses, change password and account deletion
  • Home with banners, featured stores and trending products
  • Product lists by category, vendor or brand
  • Search and filters by category, vendor, brand and price
  • Product page with options, stock and pricing
  • Wishlist, and cart with stock and price checks
  • Checkout with shipping cost, promo code and wallet credit
  • Card, Apple Pay and Google Pay payments
  • Orders with status and multi-shipment tracking
  • PDF confirmations, receipts and invoices
  • Wallet, transfer-to-card and refund requests
  • Prices in SAR, USD or EUR
  • WhatsApp contact, FAQ, terms, privacy and push notifications
Web

Vendor Web Portal

  • Registration with government verification
  • Document upload when not verified
  • Vendor agreement and approval status
  • Dashboard, store profile and bank details
  • Products with variations, HS codes, volume and shipping details
  • CSV and Excel upload with validation and error report
  • Salla and Zid connection, sync errors and unmatched categories
  • API keys and API documentation
  • Orders with Preparing and Ready status and tracking
  • Earnings per order with CSV export, and sales summary
  • Subscription plans, payment, renewal and receipts
  • Notifications, Arabic and English
iOS and Android

Vendor Follow-up App

  • Login with the same account as the Vendor Web Portal
  • Summary dashboard: new orders, orders by status and today's total
  • Order list and order details
  • Status updates to Preparing and Ready
  • Push notifications for new and updated orders
New
Ready
New
Preparing
Web

Admin Panel

  • Dashboard: orders, sales, customers, vendors, reviews and refunds
  • Customers: search, details, block and unblock
  • Vendors: review, approve, reject, status and commission
  • Categories and external category matching
  • Products: stock, price, hide and publish
  • Orders, cancellations and manual refund records
  • Refund approvals and wallet-to-card transfers
  • Wallet credits and adjustments
  • Promo codes, subscription plans and subscription promo codes
  • Currencies, exchange rates and add-on percentage
  • Home banners and featured stores
  • Notification templates and notification log
  • Settlement report, low-stock and status alerts
  • Audit log, admin accounts and permission profiles
  • CSV exports
Server and providers

Backend and Integrations

  • Pricing, commission, order, wallet, refund, promo code and subscription logic
  • One-way product sync for Salla, Zid and the REST API, with webhooks, a daily check, retries and logs
  • HyperPay card payments with Apple Pay and Google Pay
  • Payment webhooks and payment references
  • Shipping rates, shipment creation and tracking
  • Liquid-based shipment splitting
  • WhatsApp OTP and template messages from two numbers
  • Government verification with status mapping and admin override
  • Push, email and WhatsApp notifications for 13 events
  • Versioned REST API documented in OpenAPI
Pricing engineAdd-on and commission
OrdersLocked financial records
Wallet and refundsProportional reversal
Promo codesRule-based discounts
Product syncSalla, Zid, REST API
SubscriptionsExpiry and renewal
NotificationsPush, email, WhatsApp
DocumentsPDF in Arabic and English
UI and UX

Design

  • Customer App built from Digital Power's Figma designs
  • Missing customer screens designed in the same style: wallet, refunds, change password, account deletion, order history and details
  • Vendor Web Portal, Admin Panel and Vendor Follow-up App designed in the same style
  • Main screens of each surface approved by Digital Power before build

Solid: provided designs  ·  Dashed: designed by JinnByte

Out of scope

Not Included in Phase 1

  • Automatic subscription renewal
  • Automatic card refunds
  • Vendor payouts and withdrawals
  • Loyalty programme and recommendations
  • Advanced analytics and reports
  • ERP, accounting and ZATCA integrations
  • Live chat and SMS
  • Dark mode, tablet and landscape designs
  • Additional languages and currencies
  • Gift wrapping, saved cards and Facebook login
05
How it works

Key Workflows

The four journeys that carry the platform, end to end.

Order to Delivery

From the customer's cart to a delivered shipment.

CustomerPlatformHyperPayVendorShipping Company01Browse and cartGuest browsing,account at cart02Shipping rateLive cost foreach shipment03CheckoutPromo code andwallet credit04PaymentCard, Apple Pay,Google Pay05Order PaidConfirmed bywebhook06Vendor notifiedPush, email andWhatsApp07Marked ReadyOrder preparedfor pickup08ShipmentCreated, split ifover liquid limit09DeliveredTracking linksshown on the way10Records lockedReady forsettlementRatePayWebhookNotifyReadyTrackingDelivered

Vendor Onboarding

Commercial registration check, then admin approval.

VERIFIEDOTHER RESULTVendor registersCommercial registration numberGovernment checkAutomatic status lookupNo documents neededContinues registrationUpload documentsNot verified, not found, expiredAdmin reviewApprove, reject or overrideStore goes liveApproved, enabled, subscribed

Product Synchronisation

One engine for Salla, Zid and the REST API.

RETRYMATCHEDNOT MATCHEDSallaAuthorized storeZidAuthorized storeREST APIVendor systemSync engineWebhooks, daily check, logsCategory matchingExternal to platform categoriesPublishedVisible to customersHiddenUntil category is matchedPrice and stock always follow the vendor's own store.

Refund to Wallet

Every refund lands in the wallet first.

CustomerPlatform AdminPlatformBank01Refund requestItems andreason02Admin reviewApprove, reject,shipping yes or no03Wallet creditPaid amount,shares reversed04Use or transferSpend at checkoutor ask for card05Bank transferPaid manuallyby the admin06Marked doneAmount, dateand referenceRequestApprovedCreditedTo cardRecorded
06
Logic

Key Business Rules

The rules the platform calculates and enforces on every order.

Pricing and Commission

Example with a vendor price of SAR 100, the default 15% add-on and a 20% commission.

Customer paysSAR 0
Vendor price 100
+15
Vendor price split: vendor amount and 20% commissionSAR 0
Vendor amount 80
20

Liquid Shipment Split

Orders over the liquid limit (300 ml by default) are split into separate shipments.

Perfume 120 ml
Perfume 150 ml
Oil 100 ml
Shipment 1270 of 300 ml
Shipment 2100 of 300 ml

Commission changes

A new commission rate applies to new orders only.

Rounding

Two decimals per order line, half up. The order total is the sum of rounded lines.

Order records

Fourteen financial values stored per order line and locked once the order is placed.

Refunds

Approved refunds go to the wallet. Vendor and platform shares are reversed in proportion.

Promo codes

Funded by Digital Power. The vendor amount is calculated before the discount.

Synced products

The external store is the source of truth. Products stay hidden until their category is matched.

Subscriptions

On expiry, products are hidden and new orders stop. Existing orders stay manageable.

Settlement

The platform records every value and produces the settlement report. HyperPay settles the money.

07
Engineering

System Architecture

A single Laravel application on AWS, with each provider behind its own replaceable adapter.

Source and deliveryClient applicationsAmazon Web Services · Digital Power accountDigital Power provider accountsDevelopment, test and production run the same setupApplication environment, auto-scaledCode repositoryGitHub, in Digital Power's nameCI/CD pipelineBuild, test and deployCustomer AppiOS and AndroidVendor Follow-up AppiOS and AndroidVendor Web PortalBrowser, HTTPSAdmin PanelBrowser, HTTPSVendor systemsREST API with API keyCertificate ManagerSSL certificatesSecrets ManagerKeys and credentialsAWS WAFFirewallLoad balancerHTTPS entryLaravel appAPI and web panelsQueue workersJobs and schedulerMySQLPrimary databaseS3 storageImages, documentsAmazon SESOutgoing emailCloudWatchLogs, monitoring and alertsEncrypted backupsDaily, kept for 14 daysHyperPayCards, Apple Pay, Google PayShipping CompanyRates, shipments, trackingWhatsApp providerOTP and notificationsGovernment verificationCommercial registrationSalla and ZidProduct catalog syncFirebasePush notificationsApp Store, Google PlayApp publishingDeploySSLKeysHTTPSIntegrationsWebhooksStore builds signed with the App Store Connect API key, no passwords

Commit

Daily push to Digital Power's repository

Build and test

Automated on every push

Development

Integrated daily build

Test

Digital Power reviews each delivery

Production

Released with Digital Power's approval

Keys and provider credentials live in AWS Secrets Manager. No passwords or two-factor codes are ever shared.

08
Technology

Technology Stack

Mobile apps

Flutter

Two separate apps with separate store listings, phones in portrait, adapted for tablets.

Backend and API

Laravel and MySQL

PHP, versioned REST API with JSON over HTTPS, documented in OpenAPI 3.

Web panels

Laravel

Responsive, Arabic and English with right-to-left layout and a language switch.

Hosting

AWS

Bahrain or UAE region, recommended at kickoff with a monthly cost estimate.

Security

WAF and Secrets Manager

Encrypted backups, named access with two-factor authentication.

Notifications

FCM, SES, WhatsApp

Push, email and WhatsApp messages in the user's language.

Payments

HyperPay

International cards, Apple Pay and Google Pay, with payment webhooks.

Delivery

GitHub and pipelines

Automated build and tests, TestFlight and Google Play testing.

09
Governance

Security, Access and Ownership

Digital Power owns every account from day one. JinnByte works through restricted roles only.

GitHubAWSAppleDeveloperGooglePlayFirebaseHyperPayShippingWhatsAppDigital PowerOWNERJinnByte · role access
Accounts

Opened in Digital Power's name

GitHub, AWS, Apple Developer, Google Play, Firebase, payment, shipping and messaging accounts. JinnByte receives restricted role invitations, never an owner role.

Passwords

Never shared

iOS releases use an App Store Connect API key (.p8). Android releases use restricted Google Play Console access. No passwords or two-factor codes change hands.

Code

In Digital Power's repository from the first line

Daily pushes from named accounts with two-factor authentication. The main branch is protected, so every change is reviewed and recorded.

Secrets

Stored in AWS Secrets Manager or Parameter Store, never in code or messages.

Payment data

Card data is never stored on, or passed through, the platform.

Application security

OWASP Top 10 review, high and critical findings fixed before release, security report at delivery.

Maintenance

PHP, Laravel and all dependencies kept on security-patched releases.

10
Testing

Quality Assurance

Automated tests where money is calculated, real devices where people tap.

Load testSpeed at launch load
Manual device testingiOS and Android, Arabic and English
Automated API flow testsMain flows and login
Automated calculation testsPrice, commission, rounding, settlement, payment, wallet, promo codes
0%

Under 1 secondAt least 95% of standard API requests at the approved launch load, proven by a load test before launch.

  • 01Test plan and test cases covering every module
  • 02Regression testing before every delivery
  • 03Test report with every delivery
  • 04Tablet layout and right-to-left checks
  • 05Retest of every correction
11
Process

Delivery Approach

Two phases, with a working build in Digital Power's hands every two weeks.

Phase 0

Discovery and Setup

  • Dependency list within 5 business days of signing
  • Architecture, AWS region and monthly cost recommendation
  • Repositories, environments and build pipelines
  • First test call to every provider
  • Main screen designs for approval
Phase 1

Build and Launch

1Customer journey
2Vendors and product sources
3Integrations
4Beta and regression
5Launch and handover
  • Customer App with simulated shipping and payment, reviewed on test builds
  • Vendor Web Portal, Vendor Follow-up App and every product source
  • Live payments, shipping, WhatsApp and government verification in test
  • Full retest, security and speed reports, then production and store publishing

Every working day

Code pushed to Digital Power's repository.

Every week

Written progress report.

Every two weeks

Working test build on TestFlight and Google Play testing.

Each delivery

Live test link, release notes and test report.

12
Schedule

Project Timeline

Two months of build with parallel workstreams, followed by app store review and the 30-day warranty.

Workstream
Week 1Week 2Week 3Week 4Week 5Week 6Week 7Week 8Store reviewWarranty
Discovery and setup
UI design
Backend and API
Customer App
Vendor Web Portal and Admin Panel
Vendor Follow-up App
Integrations
QA and regression
Beta on TestFlight and Play testing
App store review and launch
Warranty
Milestones
M1
M2
M3
M4
M5
M6
W
App store review (set by Apple and Google) Warranty Milestone
13
Commercials

Investment and Milestones

USD0
Fixed priceComplete Phase 1 scope
2 monthsPlus app store review time
Upwork EscrowEach milestone funded before work starts
30-day warrantyIncluded
20%M1
20%M2
15%M3
15%M4
10%M5
10%M6
10%Warranty
MilestoneDeliveredDuePayment
M1FoundationAWS environments, database, first API documentation, registration and login, Admin Panel basics, provider test callsEnd of week 2USD 1,10020%
M2Customer AppComplete Customer App with simulated shipping and payment, PDF receipts, Arabic and EnglishEnd of week 4USD 1,10020%
M3Vendors and Product SourcesVendor Web Portal, Vendor Follow-up App, subscriptions, manual entry, CSV, Salla and ZidEnd of week 5USD 82515%
M4IntegrationsPayments, Apple Pay and Google Pay, wallet and refunds, settlement report, REST API, WhatsApp, government verification, live shipping in testEnd of week 7USD 82515%
M5Beta and RegressionTestFlight and Google Play testing builds, full retest, security and speed reportsEnd of week 8USD 55010%
M6Launch and HandoverProduction on AWS, apps published or approved and held, live check, handover and admin trainingAfter store approvalUSD 55010%
WWarranty30-day defect fixing after launch acceptance30 days after M6USD 55010%
TotalUSD 5,500

Hosting and third-party service costs are paid directly by Digital Power.

14
Completion

Handover and Warranty

Everything Digital Power needs to run, maintain and extend the platform without JinnByte.

Source code

Full history in Digital Power's repository, build and deployment instructions

Data and architecture

Database schema, sample data and architecture description

API documentation

OpenAPI documentation and a Postman collection

Design files

Figma files with full access, fonts, icons and images with licences

Runbook

Release, rollback, backups, monitoring and alerts

Accounts and keys

Where every account, key and certificate is held, without passwords

Guides and test reports

Admin guide, vendor guide, test cases and final test report

Admin training

Recorded session of up to 2 hours, backup restore test, access removal

Warranty

30 days after launch acceptance

Every defect in the delivered work is fixed within the agreed response and fix times, including store resubmission for the apps.

Day 1Day 30
15
Inputs

Client Dependencies

What JinnByte needs from Digital Power to keep the timeline.

Access
  • GitHub, AWS, Apple Developer, Google Play and Firebase invitations
  • App Store Connect API key
Design and content
  • Customer App Figma designs
  • App icon and branding
  • Terms, privacy policy and vendor agreement
  • Final categories and WhatsApp templates
Providers
  • Confirmed Shipping Company and WhatsApp provider
  • HyperPay test access
  • Government verification sandbox
  • Salla and Zid partner accounts
Decisions
  • Commission, refund and promo code rules before customer screens
  • Invoice fields and return rules by the Freeze date
  • Feedback on each delivery within 5 business days
16
Basis

Assumptions

01

The Shipping Company and WhatsApp provider offer documented APIs and test environments.

02

Government verification is available through a documented API with sandbox access.

03

App store review time is not included in the 2-month timeline.

04

Hosting and third-party service costs are paid by Digital Power.

17
Partner

Why JinnByte

A software and AI development company with a record of shipping consumer apps, payments and multi-vendor platforms.

0+

Years of delivery

Clients in the US, UK, Europe and the Middle East.

0+

Products delivered

Mobile apps, web platforms, AI products and integrations.

Top 0

FaceBloom

Lifestyle category on the App Store, 50,000+ users and $1M+ revenue.

0%

BUFF

Increase in monthly recurring revenue, with a 40% reduction in churn.

Top Rated Plus

Upwork

The highest Upwork rating tier, earned through consistent client results.

Live

Marketplace payments

Multi-vendor payment integrations running in production today.

18
Start

Next Steps

1

Approve

Approve the proposal and fixed price.

2

Contract

Start the contract on Upwork and fund M1 in escrow.

3

Dependency list

JinnByte sends the dependency list within 5 business days.

4

Kickoff

Kickoff meeting, and Phase 0 begins.

Prepared by JinnByte

jinnbyte.ai

JinnByte