Wavesteam
HomeCasesSolutionsKnowledge & InsightsWavesteam AppAbout
中EN
Wavesteam

QR ordering

Device receipts

QR ordering

Device receipts

Merchant operations

Merchant operations

Cooking Robot Ordering & Operations Platform

Connect QR ordering, payments, cooking receipts and collection with a companion mini program and an operator workspace for stock, recipe permissions and service exceptions.

Try the interactive demoIndustry report (Chinese)

A cooking device needs a fulfilment model

Selling a meal requires an available menu, a payment record and an accountable service journey.

Industry context

Customers buy a meal. Operators deliver a complete service.

China’s National Bureau of Statistics reported RMB 5.7982 trillion in catering revenue for 2025. This is context for the broader catering sector, not an estimate of the cooking robot market. For an operator, the immediate questions are local: can a customer order, can the device fulfil that order, and can someone resolve a failed handoff?

National Bureau of Statistics · 2025
Choose a meal
Cook against an order
Support fulfilment

Business relationship illustration. Ingredient replenishment, cleaning and food safety remain the operator’s responsibility.

User and operator needs

Diner

Know what is available and when to collect it.

Enter through the location’s device code, choose an available dish and track the order after payment. Eligible meals that have not entered production can follow a refund workflow.

Merchant operator

Keep stock, menus and device availability aligned.

Update portions after replenishment and stop new orders when ingredients or the device are unavailable. Investigate existing tasks rather than sending a new cooking command blindly.

Platform owner

Coordinate merchants without exposing their data.

Manage device ownership and shared recipe permissions. Each merchant works within its own menu, inventory and orders; operations, finance and support have different access rights.

Shared recordOrder → Device task → Service receipt

Learn from established kitchen systems

Different automation models suggest different choices for integration and ownership.

Established products

Commercial cooking and kitchen execution

BOTINKIT OMNI + KMES

OMNI combines commercial cooking hardware with cloud recipes. KMES links an incoming order with the start of cooking. The useful lesson is to treat kitchen execution as an operating system, rather than a standalone appliance feature.

Chain restaurants and commercial kitchens evaluate the equipment, kitchen integration and associated services. Pricing and licensing require supplier confirmation.

Official product information
1Kitchen order
2Recipe selection
3Device execution
4Meal handoff

Adopt the mechanism: link each sellable dish to a validated recipe version and each order to a specific device task.

Boundary: Chinese mini program payments, multi-merchant settlement and third-party hardware licensing require separate evaluation. No integration with BOTINKIT is claimed.

Analysis of public supplier material, not a hands-on assessment of authenticated products. Supplier performance claims are not commitments for this solution.

Build or integrate

1

Use the manufacturer’s platform

If the existing cloud service already covers menus, payments and single-site operation, assess configuration, ongoing charges and data portability before commissioning new software.

Verify coverage and recurring costs
2

Connect the existing ordering system

When a POS or mini program is already in use, link orders to device tasks, receipts and refunds without duplicating the menu or customer base.

Test one order in both directions
3

Build for distinct operating rules

Consider custom development when multiple device models, merchants, private recipes or reconciliation rules need a common operating layer.

Start with documented interfaces and permissions

Design around the handoff of every meal

A consumer mini program and a shared operator workspace serve distinct responsibilities.

Product positioning

One order connects a meal, a device task and an auditable set of receipts.

Designed for commercial cooking device brands, fleet operators and multi-site foodservice businesses. A WeChat mini program and Web workspace coordinate ordering and operations while the existing Qt client, firmware and device safety controls retain their responsibilities.

Order
Meal linePaymentDevice taskReceipt

Product architecture

Consumer mini program

Device-specific menus, stock reservations, payment, progress and refund requests

Access to the diner’s own orders↕

Merchant / platform workspace

Inventory, device availability, recipe permissions, exceptions and audit events

Merchant and role scopes↕

Shared business services

Orders and lines, reservations, payment transactions, device tasks and refunds

Linked objects with separate states↕

Adapter and existing device client

Task acceptance, heartbeats, recipe versions and cooking receipts

Requires device and protocol validation

Ordering and collection journey

Identify the location

Resolve the device code, check availability and load the correct menu. Changing devices releases the previous cart reservation so an order cannot silently move to a different kitchen.

Device ID · operating stateProposed workflow

An exception needs its own path.

Device offline

Stop new orders; retain paid orders.

Keep paid orders pending dispatch. On reconnection, query the original task before retrying. Escalate unresolved or expired fulfilment to support.

Do not create a fresh task blindly

Reconcile transactions with device execution

Payment, cooking and refund completion each need their own source of confirmation.

Automation and AI boundaries

Use validated cooking rules. Generative AI does not control the first release.

1

Approve recipe versions

Validate temperature, timing, ingredients and rotation against the dish and device. Authorised staff publish a version linked to compatible equipment.

2

Keep safety on the device

Emergency stops, lid checks, thermal controls and power-loss recovery belong to the device. A cloud event, phone interface or generated text cannot replace these controls.

3

Evaluate assistance separately

Future copy or alert summaries could use approved information with human review. They would not automatically change recipes, allergen statements, prices or refunds.

Approved recipeDevice safety checksExecution receipt

Technical architecture

Mini program / WebTransaction servicesTask adapterExisting device client

Confirm financial events

Use the selected WeChat Pay integration’s signature checks, amount validation, duplicate handling and order queries. Track payment, refund and fulfilment separately; a client redirect is not a settlement record.

Adapt to the device protocol

Plan a reliable event outbox, task deduplication and MQTT/REST adapter. Message delivery and cooking completion are different events. Task history and recovery depend on the device’s actual protocol and storage.

Enforce scope and permissions

Validate merchant, role, resource and recipe permissions on the server. Audit access changes, configuration, refunds and recipe dispatch. Hidden frontend buttons do not enforce isolation.

Validate before sizing

A sample device, firmware state model, payment entity and site network are implementation inputs. Set capacity targets from the cooking cycle and load tests. The current interactive prototype uses simulated payments and device events.

WeChat Pay integration reference

Validate one location before expanding

Use site operations and real device tests to guide a practical rollout.

Application environments

01
Business campuses

Lunch peaks at fixed locations

Bind the entry code to a device, expose queue progress and coordinate replenishment. Limit new orders when production is constrained.

Validate peak throughput and site staffing
02
Neighbourhood meal points

Scheduled service with local support

Use location opening hours, an accountable contact and an exception workflow. Coordinate collection, cleaning and food safety with onsite operations.

Validate permissions, location and maintenance
03
Multi-site quick service

Preserve the current ordering channel

Map POS orders to authorised device recipes and return exceptions to the original order record, avoiding two separate transaction ledgers.

Validate POS access and menu mapping
04
Device rental operations

Separate merchant ownership

Assign devices and recipe permissions to merchants. Reconcile menus, data and unfinished tasks when equipment changes ownership or lease.

Validate contracts, payment entities and transfers

Business value

Meal fulfilment

Collected orders ÷ paid orders

Segment by location, service window and exception cause. Report refunded and unresolved orders separately.

Execution consistency

Unique device executions ↔ ordered meals

Test duplicates, reconnection and cancellation races. Message delivery is not a substitute for a meal completion metric.

Support performance

Refund completion − eligible request time

Distinguish automated processing from human investigation and reconcile against payment and device records.

Assess protocol integration, cloud services, payment charges, training, maintenance and exit costs together. Released staff time becomes a commercial benefit only when a real staffing or additional service outcome is demonstrated. No fixed savings or return is assumed.

Implementation and acceptance

  1. 1

    Confirm protocols and responsibilities

    Review device states, task queries, recipe versions, payment and refund entities, site permissions and supplier responsibilities. Convert critical unknowns into sample-device tests.

  2. 2

    Integrate a single-device transaction

    In an authorised test environment, connect an order, payment result, device acceptance, cooking receipt and refund. Inject duplicates, disconnections, rejections and timeouts.

  3. 3

    Run an accountable site pilot

    Cover normal ordering, stock shortages, reconnection, unstarted-meal refunds and support escalation. Agree samples, metrics, thresholds and onsite ownership before expansion.

  4. 4

    Expand merchants and operations

    Extend the validated path with tenant isolation, recipe permissions, recovery and load testing. Deliver code, protocol mappings, deployment guidance and operating documentation.

Validate duplicate callbacks, reconnection and cancellation races before a real-device rollout. Capacity, schedule and commercial terms follow the agreed scope.

Before development

Start with your equipment. Define the service around it.

Start with your devices, locations and payment journey to define the right integration and development scope.

Planning a cooking device platform?

Start with your devices, locations and payment journey to define the right integration and development scope.

Discuss your project

This solution covers commercial meal ordering and collection, with an operator workspace. Home recipes, household device controls and content subscriptions need a different product assessment.

It simulates device messages and payment results. Production integration requires a sample device, a documented protocol, task queries, defined safety responsibilities and authorised testing. Universal device compatibility is not claimed.

Start with configuration or integration if the current manufacturer platform or POS meets the operating needs. Consider custom software only for material differences in merchant rules, device adaptation, recipe permissions or reconciliation.

The operator owns food handling, cleaning, site permissions and onsite food safety. The equipment supplier owns device safety controls. Software supports traceability and exception handling; it does not replace licensing or safety validation.

Device models and samples, protocol and state documentation, menus and approved recipes, the payment entity, site workflows and existing system interfaces. These determine pilot scope and acceptance before costs, dates or capacity are agreed.

Let's Talk

Connect cooking equipmentto a complete meal service.

Start with your devices, locations and payment journey to define the right integration and development scope.

Business email
contact@wavesteam.com
Office
10F, South Block, Kingkey Yujing Times, Longgang District, Shenzhen

By submitting, you agree we'll use your information only for this consultation — never for unrelated marketing.

Related solutions

More Wavesteam solutions

AI, capital-markets docs, OCR, vision, IoT and membership operations — composable for your industry.

  • Enterprise Knowledge Base RAG

    Enterprise Knowledge Base RAG

    Connect enterprise documents and business knowledge with source citations and access controls. Start with a model API, or deploy processing, retrieval, and inference on an appliance for fully internal use.

    • AI
    • RAG
    • On-Premise
    Explore solution→
  • Capital Markets Doc AI

    Capital Markets Doc AI

    Connect terminology checks, version comparisons, human review and project handoffs for bilingual financial documents, with traceable decisions and review records.

    • AI
    • Capital Markets
    • Automation
    Explore solution→
  • Handwritten Order OCR

    Handwritten Order OCR

    Turn handwritten orders into structured records through field extraction, validation, and human review, ready for integration with your order management workflow.

    • AI
    • OCR
    • ERP Integration
    Explore solution→
Wavesteam Technology

Connect QR ordering, payments, cooking receipts and collection with a companion mini program and an operator workspace for stock, recipe permissions and service exceptions.

Contact us
© 2026 Wavesteam Technology. All rights reserved.
Email:contact@wavesteam.comAddress:10F, South Block, Kingkey Royal Tower, Longgang District, Shenzhen