Delivering for the neighbour, without handing over the guest.
ALLRECA Delivery Network is shared delivery capacity between independent local restaurants. A business without a free driver can rely on a local cluster.
The order stays with the business that accepted it. Another member performs the trip. Not as a marketplace, but within agreements on capacity, assignment, working time and settlement.
This page describes the model. No live cluster locations or coverage areas are claimed.
The guest orders from the business, not from the network.
A Delivery Cluster is a local group of participants with agreements on capacity, assignment and settlement. The network does not change who owns the guest, the order or the revenue. It only changes who performs the trip.
That keeps the guest relationship local. A participant supplies capacity to another business; the two businesses settle the supplied time and costs among themselves.
Keeps the guest, the order, the payment and the revenue.
The business remains the guest's point of contact and decides on alternatives if the trip cannot be filled.
Provides capacity and receives a fee.
It places a suitable employee within the agreed capacity and receives reimbursement of the costs of that deployment.
- GuestOrdering from A
- ATracks order and revenue
- ClusterSeeking capacity
- DDelivers the route
- A ↔ DSettles the deployment
The same order, the same payment, the same revenue. Only the execution of the delivery shifts.
From capacity request to completed run.
The cluster is not an extra ordering channel. It is a layer on top of the existing ordering, delivery and settlement flows.
- 01Order
Order blijft bij de zaak
The guest orders from the restaurant. That restaurant keeps the order, the customer relationship, the payment and the revenue.
- 02Check
Own capacity first
The business looks at its own confirmed delivery capacity. If there is none, the request can go to the local cluster.
- 03Rotatie
Rotatie kiest een lid
Het cluster bepaalt welke deelnemer volgens de afspraken aan de beurt is. De aanvragende zaak is uitgesloten van de eigen rit.
- 04Aanbod
Lid wijst een bezorger toe
Het aangewezen restaurant kiest een geschikte medewerker, met toestemming en binnen de arbeids-, rust- en verzekeringsafspraken.
- 05Shift
Rit wordt uitgevoerd
Pickup, onderweg en aflevering worden vastgelegd. Adres en telefoon zijn alleen beschikbaar binnen het actieve bezorgvenster.
- 06Settlement
Tijd en kosten worden verrekend
Gewerkte tijd, kosten en de onderlinge verrekening blijven aan de rit gekoppeld. De restaurants factureren en betalen elkaar.
Planned is not the same as available.
Shared capacity is the sum of what participants confirm, not what they once hoped to deliver. A participant records each week which delivery capacity is planned and confirmed and makes the confirmed capacity available within the cluster. Only confirmed capacity counts as available. Scheduled hours are an expectation, not a live courier.
Temporary exceptions — unavailable, closed or limited — reduce available capacity. A member without confirmed capacity receives no offer; the reason is recorded.
Capacity is per member and per time window. The requesting business does not take part in its own shift.
| Capacity | Indicator | Quantity |
|---|---|---|
| Planned | 6 | |
| Confirmed | 4 | |
| Available | 2 | |
| In use | 1 | |
| Temporarily unavailable | 1 |
Illustrative capacity, no live cluster.
Not whoever reacts first, but whoever's turn it is.
The assignment follows a weighted rotation. This takes into account the contribution to delivery minutes, completed deliveries, recent assignments, available capacity and the maximum simultaneous assignments.
A restaurant that just did a trip gets temporarily lower priority when other suitable members are available. Every selection and every skip is recorded.
The exact weighting and rest period are cluster configuration. Without a defined configuration a cluster is not activated.
Illustrative status, no live assignment.
The trip stays visible. The costs too.
Contributions, assignments, delivery times, costs and draft settlements stay linked. This makes it traceable after the trip which business supplied capacity and which costs belong to it.
The platform does not issue a final invoice and does not move money. The restaurants invoice and pay each other according to the cluster's agreements. The platform fee is separate from that.
Mutual settlement is not platform revenue. VAT, invoicing and fiscal treatment require external review.
| Shift | Requester | Delivers | Time | Costs | Status |
|---|---|---|---|---|---|
| Shift 1042 | Restaurant A | Restaurant D | 18 min | Cost price agreement | Concept |
| Shift 1043 | Restaurant C | Restaurant A | 24 min | Cost price agreement | To review |
| Shift 1044 | Restaurant B | Restaurant C | 16 min | Cost price agreement | Concept |
No amounts: the costs follow the cluster's agreements and are not published as a public price.
Swipe horizontally for all columns.
Three attempts, then a human.
Not every request can be fulfilled. A member may have no capacity, an offer may expire or a courier may be unavailable. That is recorded, not whitewashed.
After a maximum of three attempts, automatic assignment stops and manual intervention follows. The order remains confirmed. The original business decides on an alternative or an explicit cancellation; no automatic refund follows.
- 01Recorded
No confirmed capacity
The rotation skips the member and records the reason.
- 02Limited
Maximum three attempts
Each subsequent candidate receives their own offer and deadline.
- 03Intervention
Capacity exhausted
The request gets a clear end status and manual intervention.
- 04Order remains
Original venue decides
The order remains confirmed. The business chooses an alternative or cancels explicitly.
A local cluster, not an open marketplace.
Participants are not admitted automatically. A cluster is composed on geographic proximity and operational suitability. Participation requires an active membership and an operational legal and pilot status.
The coordinator is the operational point of contact. Platform administration manages configuration and membership, but does not supply on behalf of a restaurant.
- Participating restaurant
- Manages own employees, availability and capacity. Sees own shifts, deliveries and settlement.
- Coordinator restaurant
- Is the operational point of contact, flags bottlenecks and nominates members. Does not independently change rotation, capacity or settlement.
- Platform management
- Manages clusters, memberships, rotation parameters and audit. Cannot supply a driver on behalf of a restaurant.
What you want to know beforehand.
The answers below describe the model. They do not replace cluster agreements, legal review or pilot approval.
01Is het Delivery Network een bezorgmarktplaats?
Nee. Het is een samenwerkingsverband tussen lokale restaurants. Een rit wordt niet openbaar aangeboden aan consumenten of zelfstandige bezorgers. Deelname, toewijzing en verrekening verlopen volgens de afspraken van het cluster.
02Wie blijft eigenaar van de bestelling en de omzet?
Het restaurant waar de gast bestelt. Dat restaurant houdt de klantrelatie, de order, de betaling en de omzet. Het deelnemende restaurant levert alleen de bezorgcapaciteit en ontvangt daarvoor een vergoeding.
03Kan elke zaak meedoen?
Nee. Deelname vraagt een actief, goedgekeurd lidmaatschap, bevestigde capaciteit en een operationele juridische en pilotstatus. Clusters worden niet automatisch gevuld met alle restaurants in een stad.
04Wat gebeurt er als een zaak geen capaciteit heeft?
Then that business gets no offer. The rotation moves on to another suitable participant. The reason is recorded; a lack of capacity is not silently skipped.
05Wat gebeurt er als niemand kan leveren?
After a maximum of three attempts, automatic assignment stops and manual intervention follows. The order remains confirmed. The original business decides on an alternative or an explicit cancellation; no automatic refund follows.
06Wie wijst de bezorger aan?
Het deelnemende restaurant dat het aanbod accepteert. Het kiest een geschikte medewerker uit de eigen personeelsadministratie, met toestemming en binnen de geldende arbeids-, rust- en verzekeringsafspraken.
07Hoe worden kosten en opbrengsten verrekend?
Contributions, assignments, delivery times, costs and draft settlements are recorded. The platform does not create a final invoice and does not move money. The restaurants invoice and pay each other according to the cluster's agreements.
08Zijn er al live clusters?
This page claims no live locations or coverage areas. Participation follows an approval and pilot process. Operational availability differs per cluster and requires external legal, tax and insurance review.
09Wordt de bezorger in dienst genomen door de aanvragende zaak?
Nee. De bezorger blijft in dienst van het deelnemende restaurant. Het platform is geen werkgever, payrollpartij of uitzendbureau. De arbeidsrechtelijke en verzekeringstechnische behandeling blijft onderdeel van externe beoordeling.
10Welke klantgegevens worden gedeeld?
Open aanvragen bevatten geen adres of telefoonnummer. Na toewijzing worden die gegevens alleen beschikbaar binnen het actieve bezorgvenster. Na afronding of annulering wordt de operationele kopie opgeruimd.
Orders and trips in one desk.
In the business environment, the Delivery Network has its own desk: delivery orders, assignments, run statuses and issues are listed side by side here.
The order itself stays with the business that accepted it; the desk coordinates who picks it up and when it is back. Capacity and rotation determine the assignment, not a loose schedule.
Desk · orders · trips · assignment
Who is available when and where.
Delivery planning links trips, zones and participant availability. A peak in the cluster is visible before the first order arrives.
Zones and availability per participant are configured agreements, not external market parameters. This keeps the network's planning under the companies' agreements.
Planning · zones · availability · peak
One app for service, trips and handover.
The driver works on their own phone via driver.allreca.nl: shifts start and end, the trip steps run from pickup to delivery, and each order shows only what the driver needs — pickup restaurant, phase and the expected time.
The handover is watertight: the customer receives a unique code on their order that the driver must enter to complete the trip. Wrong or missing codes are rejected, so an order cannot accidentally be marked as 'delivered' at the wrong address.
Besides deliveries, the driver sees his own staff schedule and open shifts in the same workforce environment — roster, shift requests and network matches without a separate app.
Driver app · trip steps · customer code · own schedule
Ordering via Tastey.nl — the alternative to Thuisbezorgd and Uber Eats.
Tastey.nl is the ordering brand of the network: guests order their food there, while the order, the payment, and the revenue stay with the restaurant itself. Not a marketplace sitting in between — the restaurant keeps the guest relationship and pays no high commission.
For the guest it is the familiar checkout: menu, delivery or pickup, directly from the restaurant. For the restaurant it is its own online channel alongside its own website — with transmission to the Delivery Network when in-house capacity falls short.
Explore whether a local cluster fits.
A cluster does not start with a button. It starts with the question of which businesses operate in the same environment, what capacity they can confirm, and what agreements are needed for allocation and settlement.
Participation is not automatic enrollment. An approval and pilot process follows, with external review of the legal, tax and insurance conditions.