How to build online ordering + delivery + pickup: from LINE ordering to payments and kitchen ops (with costs and a 90-day roadmap)

Opening pain + real scenario

A three-branch noodle chain burns a whole staff member on phone orders at peak; delivery runs entirely on platforms that take 30–35% commission, leaving almost no margin on a NT$180 meal. The owner wants to build online ordering, but quotes range from NT$50k to NT$600k with no clue what differs. This piece breaks down the "online ordering + delivery + pickup" class — tech choices, payments, kitchen ops — so you can judge which to build, what it costs, and what to watch in 90 days.

When it fits × when it doesn't

Good fit for building (or semi-building):

• Meaningful revenue where platform commissions clearly eat margin — the savings cover build cost.
• A repeat-customer base you want to own and remarket to (platforms don't give you the customer list).
• Menu customization (toppings, spice, combos) that platform specs can't hold.

Not a fit — use an off-the-shelf option first:

• Single store, low order volume: validate demand first with a LINE Official Account + a ready-made ordering plugin or payment link.
• No one to watch the back office: even a great system fails without someone reading orders.
• You just want "something," no membership plans: a platform or Google Business ordering link is enough.

Alternatives matrix

Full process breakdown (with tools and deliverables)

• Phase 1: requirements + menu modeling (3–5 days). Items, options (toppings/spice/combos), branches, hours, delivery zones. Deliverable: menu data model + flow diagram (Figma/Notion).
• Phase 2: UI + ordering flow design (1 week). Ordering page, cart, checkout, LINE binding UX. Deliverable: Figma prototype.
• Phase 3: backend + payments (2–3 weeks). Order state machine, payments (ECPay/JKOPay/LINE Pay), inventory/sold-out control. Deliverable: a test env that takes orders.
• Phase 4: kitchen + notifications (1–2 weeks). Kitchen tickets (print or tablet board), customer notices via LINE Messaging API ("cooking"/"ready"). Deliverable: full order-to-pickup chain.
• Phase 5: launch + training (1 week). Staff training, load test, go live. Deliverable: SOP + launch.

Full cost breakdown

• Dev: semi-custom ~NT$80k–250k; full custom NT$250k–600k (by branch count and depth).
• Payment fees: ECPay ~2.75%–3.5%, Stripe ~3.4% + NT$10, LINE Pay/JKOPay by tier.
• LINE push: OA billed by message volume beyond the free tier.
• Hidden costs: SSL (usually bundled), SMS/push, monthly payment minimums, post-launch maintenance (budget 10–15%/yr of dev), and the cash-flow gap between "request" and "settlement."

Implementation truth vs client imagination

• Client thinks "build it and they'll come"; reality: driving traffic (LINE menu, table QR, Google Business linking to the ordering page) is the key — the system only catches it.
• Client thinks "online ordering fully replaces platforms"; reality: platform traffic is hard to drop short-term; most run "own channel for regulars, platform for new customers."
• Client thinks "adding delivery is easy"; reality: delivery involves driver dispatch, distance pricing, and time-slot control — far more complex than pickup.

Common traps × how to avoid

• Peak-hour missed orders: no clear "new order alert + sound" → add prominent unhandled-order alerts and overdue warnings.
• No sold-out lock: popular items still orderable when out → real-time inventory/sold-out toggle and a one-tap take-down.
• Reconciliation hell: multi-channel (cash/LINE Pay/card) won't tie out → design unified order IDs and a reconciliation report from day one.
• Menu option explosion: toppings/combos with no data model → model with option groups, don't hard-code.
• Notification spam or misses: push with no unsubscribe → provide status-notice toggles and frequency control.

Success metrics + 90-day roadmap

• Day 30: online-order share, average ticket, order completion rate (add-to-cart → paid). Fix drop-off points.
• Day 60: repeat rate, LINE-bound members; launch the first remarketing push (lapsed-customer nudge).
• Day 90: net margin of own vs platform, delivery/pickup mix; decide whether to add branches or a loyalty program.

Decision checklist

• ☐ Does a year of platform commission exceed the build cost?
• ☐ Is there someone to read the back office and handle orders daily?
• ☐ Does the menu have customization platforms can't hold?
• ☐ Do you want to own the customer list and remarket?
• ☐ Is your core audience on LINE?
• ☐ Delivery, or pickup/dine-in only first?
• ☐ Are payment channels decided (card/LINE Pay/JKOPay/cash)?
• ☐ Do you have traffic entries (table QR, OA menu, Google Business)?
• ☐ Is peak-hour missed-order risk designed for?
• ☐ Is maintenance budgeted (~10–15%/yr of dev)?

FAQ

How much does building online ordering cost?

Semi-custom (LINE + basic admin) ~NT$80k–250k; full custom (multi-branch, kitchen display, loyalty) NT$250k–600k. What to compare isn't dev cost but whether a year's saved platform commission covers it.

Do I still need delivery platforms?

Short-term, run both. Platforms bring new customers; your own channel keeps regulars and reclaims data and margin. Most run "new via platform, repeat via own channel."

How are payment fees calculated?

ECPay is generally ~2.75%–3.5%, Stripe ~3.4% plus a fixed amount, LINE Pay/JKOPay by tier. Factor the "request-to-settlement" gap into cash flow.

How long to launch?

Semi-custom ~6–8 weeks; full custom ~8–12 weeks, depending on branches, delivery complexity, and payment channels. "Pickup first, add delivery later" is a common phased approach.

Call to action

Want to first figure out whether "build vs platform" actually pays off for your store? ScriptWalker plans and builds online ordering/delivery systems (from NT$80,000). Book a free consult and we'll lay out menu complexity, payments, and a 90-day roadmap.

• Email: [email protected]
• Phone: 0916-224-047
• LINE: @ufv9089p