Peer-to-Peer Delivery Feature Built Into an Existing Logistics Platform

Shgardi is a multi-service delivery platform operating in the Middle East — think a combination of on-demand grocery delivery, restaurant ordering, and last-mile logistics in a single app. The platform already had a consumer mobile app, a courier app, and an admin dashboard in place when Peppernode joined the project. The client needed a team to build out a specific new module: a peer-to-peer parcel delivery feature, called Cheetah Delivery, that would sit inside the existing consumer app and allow users to send packages directly to other people within the city.

Shgardi’s existing delivery offering focused on goods from businesses — restaurants, grocery stores, pharmacies. There was no way for one user to send a personal parcel directly to another person. The client wanted to close that gap with a dedicated P2P delivery flow that felt native to the existing app and worked alongside its infrastructure.

Peppernode joined a project that already had an established codebase, built by a separate team. The work required fitting a new, moderately complex feature into an existing architecture — matching established patterns, reusing payment infrastructure that was already live, and delivering a flow that covered multiple user roles, decision branches, and edge cases without disrupting the rest of the platform.

• 1 Project Manager / BA
• 1 Tech Lead (Backend)
• 1 Backend Developer
• 1 Mobile Developer
• 1 QA Engineer

Peppernode’s team integrated into an existing product mid-cycle, which meant the first priority was understanding the live system well enough to build on top of it without introducing risk. The team worked within the existing architecture, reused payment methods already connected to the platform, and designed the Cheetah Delivery module to slot cleanly into the consumer app’s existing structure. Development ran across both iOS and Android in parallel, with QA involved throughout to validate each stage of the flow before moving to the next.

• Sender Flow. The sender specifies pickup location, recipient phone number, preferred pickup time, and any order references. The destination can be entered by the sender or left for the recipient to provide later.
• Receiver-Confirmed Delivery. If the recipient’s address isn’t known upfront, the sender places the order without one. The recipient gets notified, enters their address, and confirms before the courier is dispatched.
• Flexible Payment Assignment. The sender chooses whether they or the recipient covers the delivery fee. Three payment methods are supported: card, cash, and Shgardi’s internal wallet.
• SMS Onboarding for New Recipients. Recipients without the app installed get an SMS prompt to download it and accept the incoming delivery — no existing account required on the receiving end.
• Order Confirmation Flow. The recipient can confirm or decline an incoming parcel before the courier is assigned. Once confirmed and payment is resolved, the order enters the courier queue.

Peppernode worked as an embedded development team within a larger product ecosystem. The PM/BA coordinated directly with the client on requirements and scope, while the development team handled implementation against the existing system. Given the integration context — joining a live product with an established codebase — close communication was essential to keep the feature aligned with the platform’s existing logic and delivery expectations.

• Cheetah Delivery module completed for both iOS (Swift) and Android (Kotlin)
• Full sender and receiver flows built, covering all branching logic
• SMS-based recipient onboarding integrated
• Three payment methods supported, including split-payment between sender and receiver

• Shgardi’s platform expanded from B2C delivery into P2P parcel shipping without a separate product
• The feature reused existing payment and order infrastructure, reducing scope and integration risk
• New users (recipients) can be onboarded passively — through receiving a delivery — without a direct acquisition effort
• The module was designed to operate independently within the consumer app, keeping the feature’s logic self-contained