E-commerce & ordering
Software Development for E-Commerce, Marketplaces and Food Ordering
Peregrine builds ordering platforms: multi-vendor marketplaces with split payments and vendor onboarding, food delivery platforms with real-time driver dispatch, and restaurant POS and online ordering that keeps working offline.
The three published case studies below cover a bilingual Arabic and English marketplace for 400+ vendors, a delivery platform for 200+ restaurants, and POS and ordering across 120+ restaurant locations.
Fit
Is Custom E-Commerce, Marketplaces & Food Ordering Software the Right Fit?
A good fit when
- Several sellers, restaurants or locations transact through one platform, and money has to be split between them.
- In-store and online orders live in separate systems and are reconciled by hand.
- Locations lose sales when the internet drops.
- Dispatch runs on messaging groups, and customers call to ask where the order is.
- You sell in a market or language that hosted store platforms do not handle properly.
Probably not the right fit when
- A single brand selling its own products online. A hosted store platform is the cheaper start; if it needs extending, see Shopify development.
- One restaurant or a few locations that an off-the-shelf POS and a delivery marketplace already serve.
- You plan to store or process card numbers yourself. Use a payment provider's hosted fields or terminals, and ask the provider what that leaves in your PCI scope.
What we build
What E-Commerce, Marketplaces & Food Ordering Software Includes
Multi-vendor carts and split payments
Orders that contain products from several vendors, with commission, tax and payouts calculated for each vendor through Stripe Connect.
Shown in: Multi-Vendor E-Commerce Marketplace with Split Payments & Bilingual UX
Vendor onboarding and inventory sync
Self-service onboarding, bulk catalog import and stock sync, so vendors who sell on several channels do not oversell. The marketplace in our case study went from 50 vendors at soft launch to 400+.
Shown in: Multi-Vendor E-Commerce Marketplace with Split Payments & Bilingual UX
Bilingual storefronts
A server-rendered storefront in Arabic and English, with layouts that mirror for right-to-left reading.
Shown in: Multi-Vendor E-Commerce Marketplace with Split Payments & Bilingual UX
Order routing and driver dispatch
Orders assigned to the nearest restaurant branch and pushed to drivers ranked by distance and current load, with live status for the customer, the kitchen and the driver.
Shown in: Food Delivery Aggregator for Multi-Restaurant Marketplace
Offline-capable POS and kitchen displays
A tablet POS that stores orders locally and syncs when the connection returns, kitchen displays fed over WebSocket, and a nightly job that reconciles in-store and online payments.
Case studies
E-Commerce, Marketplaces & Food Ordering Case Studies
Multi-Vendor E-Commerce Marketplace with Split Payments & Bilingual UX
How we engineered a marketplace for 400+ vendors in the Gulf region — with automated split payments, vendor onboarding, and full Arabic/English support.
400+ Active Vendors · 85K+ Monthly Orders · <2s Page Load · 9 Months
Read the case study · Service: SaaS DevelopmentFood Delivery Aggregator for Multi-Restaurant Marketplace
How we built a FoodTech aggregator with 200+ restaurants, 50K+ orders/month, and real-time driver dispatch, with <3min average delivery in the pilot zone.
200+ Restaurants · 50K+ Orders/Month · <3min Avg Delivery (Pilot) · 11 Months
Read the case study · Service: SaaS DevelopmentRestaurant POS & Online Ordering for QSR Chains
How we built a POS and online ordering platform for 120+ locations — with offline-first tablets, kitchen display, and 25K daily orders.
120+ Locations · 25K Daily Orders · 98% Uptime · 8 Months
Read the case study · Service: SaaS DevelopmentServices
Services for E-Commerce, Marketplaces & Food Ordering Companies
SaaS Development
Multi-tenant SaaS platforms, from MVP architecture to scaling an existing product.
API Integration
Reliable integrations between your product, your vendors and your internal systems.
Shopify Development
Custom Shopify apps, storefront work and integrations with the systems around the store.
Cloud & DevOps
Cloud architecture, CI/CD and performance work for platforms that need to scale.
Scope
What Determines the Scope of E-Commerce, Marketplaces & Food Ordering Software?
These are the inputs that change the effort. None needs a final answer before the first call, but each one you can answer makes the estimate tighter.
- Sides of the platform
- Buyers, vendors or restaurants, drivers and your own operations team each need an app or portal.
- Money flow
- Who the merchant of record is, how commission and tax are calculated, payout schedules, refunds and chargebacks.
- Payment methods
- Cards, wallets, buy-now-pay-later and in-person terminals, and which providers serve your market.
- Card data
- Whether any card data touches your systems. Bring your payment provider's guidance on your PCI responsibilities instead of assuming.
- Catalog and menus
- The number of items, variants and modifiers, how vendors supply them, and how often prices change.
- Peak load
- Orders in the busiest hour, such as a flash sale or a lunch rush, which sets the load-test target.
- Offline and hardware
- What must work without a connection, and the tablets, printers, terminals and kitchen screens in use.
- Delivery
- Your own drivers, third-party fleets or pickup only, and whether live tracking is needed.
- Languages and regions
- Languages, right-to-left layouts, currencies and tax rules for each market.
A sensible first phase
A sensible first phase follows one order from placement to payout using payment test accounts: one vendor or location, one payment method, one fulfillment path. The projects in our case studies then launched small: a soft launch with 50 vendors in one, offline testing at a pilot location in another.
What to bring to the scoping call
- Each side of the platform and rough counts: vendors, restaurants or locations, drivers, monthly orders and the peak hour.
- How money should move: the commission model, payout timing and who handles refunds.
- The payment providers you use or prefer, and what they have told you about your PCI responsibilities.
- Sample catalogs or menus in the format vendors actually supply.
- The hardware at each location.
- The systems used today for orders, POS and delivery, and what is reconciled by hand.
- Markets, languages and currencies.
Partial answers are fine. Whatever is missing becomes the first item on the call.
Technical consultation
Building a Marketplace or Ordering Platform?
Tell us about your vendors, order volume and the payment and delivery systems involved. An engineer will tell you how we would approach it.
- A 30-minute technical discovery call with an engineer, not a salesperson.
- Fixed-scope projects, monthly retainers, or a combination, agreed after the call.
- Small, well-defined tasks get a scoped estimate. We reply within 1 business day.
Prefer to pick a time? Book a call on Calendly
