Marketplaces and platforms
Local delivery for your platform, connected by API.
Send Porch Route a delivery with one API call keyed by your own order reference and hear back on a signed webhook when it’s scheduled, on the way, delivered, failed or skipped. Retries are safe, nothing is filtered by zone, and every text, email and tracking page carries your brand — never ours.
Free up to 150 orders a month · No credit card · Last updated
The problem
Why is delivery hard for marketplaces?
- Orders created in your system that need to become delivery routes
- Keeping order status in sync when deliveries change
- Knowing for certain when an order was delivered, or why it wasn’t
- Customer messages that have to carry your brand, not a vendor’s
How Porch Route helps
What does Porch Route do for marketplaces?
- Create or update deliveries with one API call keyed by your own order reference, safe to retry
- Signed webhooks for every outcome, with retries, reconciliation and a delivery log
- API orders are never rejected for falling outside a zone, because your checkout already decided
- Customer texts, emails and tracking pages carry your business’s name, never Porch Route’s
- A message log of every text and email that went out
What it looks like on the day.
The webhook delivery log for a store's endpoint, and the JSON body of a stop.delivered event.
Every number in these screens is the planner’s own answer for a demo day — not a mock-up of one.
stop.delivered8:49 AMstop.en_route8:00 AMstop.scheduled7:45 AM{
"event": "stop.delivered",
"data": {
"external_ref": "10241",
"status": "DELIVERED",
"proof": { "photo_urls": ["https://…"] }
}
}One delivery day
What does one delivery day look like?
Step 1: Checkout creates the delivery
When an order is paid, your platform POSTs it to /api/v1/orders with the order number as external_ref, the address, date, items and temperature. Sending the same external_ref again updates it; an Idempotency-Key makes retries safe.
Step 2: Each seller plans its day
Every seller is its own business in Porch Route with its own vehicles, drivers, zones and API key. Their dispatcher (or yours) builds the routes and dispatches; stop.scheduled reaches your endpoint.
Step 3: Drivers get links
Dispatching texts each driver a no-login link to their route, or staff drivers open My routes. No app to distribute to a fleet of part-timers.
Step 4: Customers hear from the seller
Texts, emails and the tracking page carry the seller’s name — never Porch Route’s — with a link that shows only that customer’s delivery.
Step 5: Outcomes arrive signed
stop.en_route, stop.delivered (after the undo window, with proof links), stop.failed with the reason, stop.skipped, stop.undone and route.completed, each signed with HMAC-SHA256 over the raw body and retried with backoff for a day.
Step 6: Nothing goes missing
Reconciliation reports anything still owed past its grace window; the delivery log shows every attempt and lets you resend one. Read an order’s status and tracking link any time.
Pricing
What does Porch Route cost marketplaces this size?
Every feature is on every plan. Plans differ only by how many orders and customer texts they include each month, and by support — never by drivers or vehicles.
| Business | Orders a month | Vehicles | Plan | Price |
|---|---|---|---|---|
| Pilot region | 1,000 | 5 | Porch | $79/month |
| Growing platform | 5,000 | 20 | Route | $189/month |
| Multi-market platform | 20,000 | 60 | Fleet | Custom |
Monthly billing; annual billing is two months free. Porch and Route include unlimited vehicles and drivers. Fleet is priced for your volume.
Questions
What marketplaces ask us.
Is there an SDK?
The API is plain HTTPS and JSON with bearer-token keys, documented at /docs/api with request and response examples. Any language that can make an HTTP request can integrate; no SDK is needed.
Can each seller have its own account, drivers and key?
Yes. Every business is its own tenant with its own vehicles, drivers, zones, team and API keys, kept apart on the server and by row-level security in the database.
What are the rate limits?
Integration calls are limited per API key at 600 a minute — ten requests a second sustained — which is far above what a checkout produces. Limits hold across server instances.
Do your zones filter my orders?
No, deliberately. Orders that arrive over the API are never rejected or re-filtered for being outside a zone: your checkout already decided the order is deliverable. Zones apply to orders added by hand or CSV.
Related pages
Plan your next delivery day in a few minutes.
Add your vehicles and a day of orders — by hand, from a CSV or over the API — and build your first routes.
Free up to 150 orders a month · No credit card