A Multi-Vendor Ordering site has three layers: the organisation, the parent venue, and the child venues. Understanding what each part controls helps explain how MVO works.
Read this before you set up your first Multi-vendor ordering operator site, or when you are joining one as a vendor.
The three layers
An MVO is built from three parts that sit inside each other:
- The organisation is the top-level container. Everything to do with one MVO sits inside one organisation: the parent venue, every child venue, and any organisation-level settings.
- The parent venue is the operator's site. It exists inside the organisation and has the is multi-vendor venue toggle switched on. Guests scan into the parent and see one combined menu.
- Each child venue is an individual vendor. Each child has its own menu, its own staff, its own POS, and its own live orders screen. A child can also be part of more than one parent.
What the parent venue does
The parent venue acts as the central menu. It doesn’t have its own menu items. Instead, it combines categories from each child venue into a single menu for guests.
What sits at the parent level:
- The combined menu, built from linked child categories
- Organisation-wide settings such as surcharges and service charges
- The QR code guests scan to enter
- Centralised Live Orders Page
- Group Level Insights Dashboards
What does not sit at the parent level:
- Menu items
- Refunds
What each child venue does
Each child venue runs the way a standalone me&u venue runs. It has:
- Its own full menu, which is the source of truth
- Its own live orders screen showing only its items from any MVO order
- Its own sales reports
- Its own refunds, processed at the child level
- Its own POS integration
- Its own payout configuration
- It's own Individual level Insights Dashboards
Because each child is independent, vendors can join an MVO without changing how they run service day to day.
What lives where
| What | Operator (Parent) venue | Vendor (Child) venue |
|---|---|---|
| Menu items | None, linked categories only | Yes |
| Linking a vendor to the menu | me&u Support links vendors. You can unlink and reorder (pin) them | Can’t link. Linked by me&u Support once onboarding is complete |
| Upsells | Drinks upsells across all vendors | Upsells on their own menu only |
| Live orders | Yes, consolidated orders against all vendors | Yes, orders show on each vendor |
| Sales reports | Yes, consolidated Sales Performance in Group Insights Dashboard | Yes |
| Refunds | Not here. Open the order from Centralised Live Orders and it takes you to the vendor’s site to refund | Yes, refunds are made in me&u, also recorded in POS for reconciliation purposes |
| Surcharges and service charges | Set here, identical to all vendor | Same name and % as the parent. Managed by the operator |
| POS integration | Not configured here | Yes |
| Payouts | Depends on your setup: each vendor is paid into their own bank account, or all vendors are paid into the operator’s account | Paid directly, or through the operator, depending on your setup |
| Stripe Connect | Yes, the parent needs its own Stripe Connect with bank details. Set up by the me&u onboarding team | Yes, each vendor has its own. Set up by the me&u onboarding team |
| User access | Operator admins manage access. Access doesn’t carry over automatically when a new vendor is added | Each vendor manages its own team’s access |