Long menus, dish numbers, meal-for-one and meal-for-two deals, modifier upgrades, bilingual kitchen tickets. Chinese takeaways are busy — your system should keep up.
A phone order for "26, 48, set menu C, extra fried rice, no MSG" lands on the pass and the kitchen stares at it. Dish numbers on one ticket, Chinese names on another, English mods scribbled between. Andromeda prints one clear ticket, three languages, every time.
One set menu, three picks, fair price — no phone call.
Every product carries an English name, a Chinese name (traditional or simplified — your choice), and a short dish code. Customers online pick by name and image. Phone orders go in by code. The kitchen ticket prints all three — no ambiguity.
Set menu builders let customers mix-and-match across groups: one from column A, one from column B, two from column C. Upgrades like special fried rice or king prawn substitution are priced fairly and stacked on the deal.
Pick 1 from A, 1 from B, 2 from C. Fair pricing. Upgrade prompts for fried rice, king prawn, prawn crackers.
English name, Chinese name, dish code — all printed clearly. Staff never guess what "65" is.
Caller ID pulls up the last order. Staff re-order with one tap. Dish codes make phone orders fast.
Monday meal deal. Family dinner bundle. Weekend banquet. Deals stack per day, channel and store.
One master menu, many shops. Central pricing. Local overrides. Works for 1 shop or 50.
Per-postcode zones, minimum orders, delivery fees. Free delivery over £15? Set it once.
| Capability | Uber Eats / Deliveroo | Generic EPOS | Andromeda |
|---|---|---|---|
| Dish code ordering | ✗ | SKU only | ✓ Dish code + name |
| Chinese character support on tickets | ✗ | Rarely | ✓ Built in |
| Set menu n-of-choices builder | Limited | Clunky | ✓ Native |
| Caller ID integration (phone orders) | ✗ | Add-on | ✓ Included |
| Cost per order | ~30% commission | Varies | ✓ Low flat monthly fee |
"We had dish numbers on phone orders and Chinese on the tickets — getting that to work on the website was the blocker. Andromeda just did it."
Yes. Every product has a short dish code field. Customers online still see the name and image; the till staff type the code; the kitchen ticket prints both. You don't have to change how your customers order.
Yes. Set menu builder lets you define n-of-choices from any groups, add forced upgrades or optional add-ons, and price the whole bundle fairly. Online customers see a clean picker; tills handle it with modifier buttons.
Yes. We support Unicode on thermal printers — you just need a printer with a CJK character set (most Epson, Citizen and Star models do). We'll check your hardware before go-live.
Absolutely. Restaurants with both dine-in and takeaway run both occasions side by side. Dine-in with table plans and running tabs; takeaway with collection and delivery; one menu, one reporting view.
Yes. Caller ID speeds up repeat customers massively. Orders queue into the kitchen display pacing-aware, not just dumped on the printer. Drivers get dispatched by postcode cluster, not first-come-first-served.
Yes. Per-channel price uplifts. Your website shows your price; aggregator users absorb the aggregator's cut. Set the uplift once, applied everywhere.
Book a demo. We'll print a ticket in English, Chinese and dish codes, and walk you through set menu C.
Book a demo