Adding errand delivery to your business has two paths: plug into a third-party errand app (their brand, their commission, their customer) or add Custom Orders to your own platform (your brand, your margin, your customer). They look similar from the customer's side. They're completely different businesses from yours.
When operators decide they want to offer errand delivery — pickups, drop-offs, on-demand fetches that aren't tied to a menu — they almost always evaluate two options.
Path one: sign up with a third-party errand app and let them handle the requests, the drivers, and the customer experience. Path two: build the capability directly into the ordering platform you already run, using your existing fleet.
The first path is faster to start. The second path is faster to compound. This guide breaks down what you're actually trading on each side so the decision isn't made by accident.
There are five axes that actually matter. On four of them, the two paths point in opposite directions.
Third-party app: the customer opens the third party's app, sees their branding, gets their notifications, and stores their card with them. You are an invisible supplier. When the customer needs another errand, they open the same third-party app — not yours.
Custom Orders on your platform: the customer opens your app, sees your branding, and stores their card with you. Every errand strengthens the muscle memory of opening your app first.
Third-party app: commission per order typically runs 15–30%. Some platforms add a base subscription fee on top.
Custom Orders on your platform: no per-order commission. You set the per-kilometer rate and the customer pays the full delivery fee directly. The full margin stays with you.
Third-party app: the errand goes to the third party's driver pool. Your drivers don't get those trips. If you employ your own fleet, those drivers stay idle between food orders.
Custom Orders on your platform: requests are dispatched to your existing fleet. The same drivers, the same dispatch, the same operations. Fleet utilization goes up without adding headcount.
Third-party app: sign up, complete onboarding, get listed. Usually a few days. Faster than building.
Custom Orders on your platform (Ordering.co): toggle on in the admin dashboard, set three values, go live. Under one minute from login to live button on the storefront.
Third-party app: coverage matches the third party's driver network — sometimes broader than yours.
Custom Orders on your platform: coverage matches your fleet. If your fleet is regional, your errand coverage is regional. The boundary you set with your maximum distance value defines it.
It would be dishonest to claim the third-party path never wins. Two scenarios where it does:
In both cases, the third party is solving a capability gap. You're renting the capability rather than building it.
If you already have a fleet and a customer base — which describes most operators running on Ordering.co — neither of those gaps exists. You'd be paying commission to a third party to do something your own drivers could do for free.
The math is straightforward. Three things have to be true for the Custom Orders path to win, and most operators already have all three:
If all three are true, the question isn't whether to use Custom Orders. The question is why your platform isn't doing it yet.
Every time a customer in your zone opens a third-party errand app instead of your platform, three things happen:
The third party gets the order revenue and the customer relationship. Your fleet stays idle. Your customer learns to associate "errand" with the other app — making it harder to win that intent back later.
None of these losses show up in your dashboard. They look like nothing. They're the most expensive form of nothing in the delivery business.
WHAT HAPPENS WHEN ERRANDS STAY ON YOUR APP Compound ownership over time 01 Opens your app Customer needs an errand 02 Your driver delivers You keep the margin 03 Habit deepens "Open ___'s app first" 04 Default choice Next errand, same app Every errand that runs through your platform makes the next errand more likely to run through your platform too. The third-party path interrupts this loop on every single trip.Yes, and many operators do. Run Custom Orders on your own platform for everything inside your delivery radius, and lean on a third party for trips that fall outside it. The two systems don't conflict.
What happens to the customer experience if I switch off a third-party app? +If you've been using a third party, customers placing errand orders through that app won't be affected — they continue using it. The change is that errands originating in your own app no longer route to the third party, so you keep the margin and the relationship on those orders.
How do I price my Custom Orders competitively? +A practical starting point: check what local errand apps charge for a similar-distance trip and price slightly below it. You don't have to undercut by much — most customers will choose your app for the convenience of one less login. You can adjust the per-km rate any time in the admin dashboard.
What about driver supply during peak meal hours? +Your dispatcher decides priority. Custom Orders sit in the same dashboard as food orders, so during lunch and dinner rushes you can hold or decline them. The whole economic case is the opposite case — using Custom Orders to fill driver hours when food volume is low.
Try Custom Orders free for 2 weeks. No credit card, no setup call required, full platform access. Toggle it on, set your guardrails, and let your existing fleet earn from the trips it was missing.
Start your free trial