Connected fulfilment network

Deliver restaurant and grocery orders with one partner workspace.

Receive eligible jobs, match capacity, dispatch people or supported autonomous fleets, share live status, manage proof and exceptions, and reconcile platform fees and settlements.

Multi-modal networkHuman, robotic and drone partners
Order-linked statusMerchant and customer visibility
Clear settlement trailJobs, fees, adjustments and payouts
Delivery HubDispatch + Track + Settle
Restaurant ordersPrepared time and pickup point
Grocery ordersSlots, bags, temperature and hand-off
Human couriersDriver App, route and proof
Delivery robotsSupported fleet APIs and supervision
Drone operatorsEligible route and regulatory controls
CustomersETA, contact, proof and support
Delivery Partner OS

From job offer to settled delivery.

The same order context can connect merchant readiness, partner capacity, customer promises and financial reconciliation.

01 · ONBOARD

Partner and fleet profile

Define organisation, operating areas, vehicle or device types, availability, insurance and required documents.

  • Human courier and fleet records
  • Robot or drone operator details
  • Compliance-document reminders
02 · RECEIVE

Job marketplace and API

Receive suitable restaurant, grocery and B2B delivery opportunities through App, Web or integration.

  • Pickup, destination and service window
  • Package and handling information
  • Accept, reject or counter where enabled
03 · DISPATCH

Capacity and assignment

Assign the right courier or supported vehicle according to location, capacity, promise and service rules.

  • Manual or rule-based dispatch
  • Batching and route sequence
  • Shift and availability view
04 · NAVIGATE

Driver and operator App

Give the active worker or supervisor the pickup, navigation, contact and hand-off details required.

  • Step-by-step job status
  • Merchant and customer instructions
  • Safe contact and support hand-off
05 · TRACK

Live status and ETA

Share consented operational status with dispatch, merchant and customer through the connected order.

  • Pickup and delivery milestones
  • ETA and exception alerts
  • Customer-facing tracking view
06 · PROVE

Proof and exception handling

Capture the locally permitted evidence needed to complete or investigate a delivery.

  • PIN, signature, photo or scan
  • Failed-delivery reasons
  • Returns and item issues
07 · AUTOMATE

Robot and drone connectors

Connect supported fleet systems without treating autonomous delivery as universally available.

  • Mission and device status APIs
  • Handover and supervision workflow
  • Geofence and exception visibility
08 · SETTLE

Fees, adjustments and payouts

Match completed jobs, agreed platform fees, partner charges, failed deliveries and approved adjustments.

  • Job-level earning record
  • Settlement statement
  • Accounting export or integration
09 · IMPROVE

Operational analytics

Review service patterns without reducing quality to one score.

  • Acceptance and completion
  • Pickup wait and delivery time
  • Exceptions, zones and capacity signals
Connected delivery flow

A shared status from merchant hand-off to customer receipt.

OfferEligible partner job
AcceptCapacity confirmed
CollectScan and hand-off
MoveRoute and live status
CompleteProof or exception
SettleFee and payout record
Questions

Designed for local partner networks.

Can delivery partners use their existing dispatch system?

FoodsGrid is intended to support App/Web operation and API integration. Feasibility depends on the partner system, data model, authentication and implementation scope.

Does FoodsGrid itself operate robots or drones everywhere?

No. Autonomous delivery requires compatible partners, equipment, local authorisation, safe operating procedures and technical integration in each service area.

How are delivery fees and settlements handled?

The commercial model is configured through partner agreements. The platform can maintain job-level fees, adjustments, statements and payout references for reconciliation.

Connect your delivery capacity to the food ecosystem.

Start with a service area and fulfilment mode, then expand routes, merchants, automation or API integration as the network develops.

Discuss onboarding →