Moving to your own restaurant ordering system
A controlled migration from marketplace dependency to direct ordering — menu, domain, payments, printers, test orders and launch.
Before you start: decide the end state
Decide whether you are replacing marketplaces with direct ordering, or running both. The second model is usually more realistic.
Step 1 — Prepare the menu
- Export your menu from the marketplace or POS.
- Remove marketplace-specific items.
- Standardise modifier groups and allergen tags.
- Set sold-out and availability rules.
Step 2 — Domain and branding
Direct ordering should live on your own domain, not a subdomain of a marketplace.
Step 3 — Payments
Connect your payment gateway and test card, wallet and any local payment methods. Confirm payout timing and refund handling.
Step 4 — Printers and kitchen routing
Configure kitchen and bar printers or KDS. Test station routing so drinks do not print in the kitchen and food does not print at the bar.
Step 5 — Test orders
- Delivery inside and outside each zone.
- Collection with a time slot.
- Orders with modifiers and allergens.
- Phone orders entered by staff.
Step 6 — Launch and measure
Track direct-order share, failed orders and average order value. Keep marketplace listings active during transition.
Related
Frequently asked questions
How long does migration take?
A single-site restaurant can typically migrate in days to a few weeks, depending on menu complexity, payment setup and printer configuration.
Can I run marketplaces and direct ordering at the same time?
Yes, and it is usually the right approach. Keep marketplaces for discovery while migrating repeat customers to direct ordering.
What should I test before going live?
Test the full order path on mobile and desktop, including modifiers, delivery-zone rules, payment, printer output and order confirmation.