Every quantity. Every modifier.
Keep dishes, units and preparation instructions distinct.
POS INTEGRATION · KITCHEN OPERATIONS
Connect your POS.
See every kitchen ticket.
OneKDS is a kitchen display system for restaurants. Bring supported kitchen tickets to an Android display, manage preparation and trace exceptions.
Public download: 1.4.15 · Android app in Chinese only
SaaS business workspace is planned, not yet available.
Android kitchen client
FROM CLEAR TICKETS TO BETTER-INFORMED DECISIONSEXPLORE ↓
Different systems. One kitchen.
Dine-in, delivery and multiple POS systems: bring supported kitchen tickets together in OneKDS. View items, manage preparation and trace exceptions on one kitchen display.
Source examples, not verified integrations or official partnerships
Delivery order sources
- Meituan Waimai
- Taobao Shangou
- JD Waimai
In-store POS systems
- Shouqianba
- Keruyun
- 2DFire
- Pospal
- Huiguanjia
- Other POS
OneKDS
Android kitchen client
Ticket collection · Preparation tracking · Waiting alerts
Confirm the connection with your POS and sample tickets.
Compatibility depends on the POS version, print output, ticket format and store network. This is not universal POS or delivery support, or direct payment integration.
Check POS compatibilityBEFORE YOU CONNECT
- POS version
- Confirm the system and actual version.
- Print output
- Check kitchen-print output and the store network.
- Ticket format
- Review complete, redacted source samples.
02 / KITCHEN WORKFLOWNative interface detail · Simulated data
From received ticket to completed prep.
- 01
Receive
From supported POS output
- 02
Check
Process supported tickets; review exceptions
- 03
Prepare
See items, quantities and instructions
- 04
Trace
Retain source tickets and action records
Complete what is actually prepared.
Complete a ticket or part of it, retaining action records. A completion action is not proof of customer delivery.
Trace exceptions to the source.
Review unknown, incomplete or ambiguous tickets separately. An analysis never replaces its source record.
Current release: complete, unambiguous supported tickets can enter preparation automatically. Unknown, incomplete, suspected reprint and unclear cancellation tickets still require review.
Read the public-version setup guide03 / Android kitchen client
Different kitchens. A layout that fits.
Keep the kitchen focused on tickets and preparation. Explore how information can fit different kitchen workflows.
View each ticket with its preparation details.
See the table, dishes and modifiers together when coordinating a full meal.
Local settings capabilities
Set layout and reminders on the kitchen device.
Layout preview, saving and waiting thresholds are Android device settings, separate from the SaaS business workspace. Saving a setting does not send it from the cloud.
Public release 1.4.15 includes local layout and alert settings. The examples below are web simulations.
Try a kitchen layoutInteractive example · Simulated data
Board layout
One column on narrow screens
Table A06
3 min · On timeSample ticket · Batch 01
- Kung pao chicken× 1
Mild
- Tomato & eggs× 2
Regular
Table B02
3 min · On timeSample ticket · Batch 02
- Pan-seared chicken× 1
Sauce on the side
- Mushroom pasta× 1
No onion
Table A12
3 min · On timeSample ticket · Batch 03
- Steamed sea bass× 1
Less salt
- Seasonal greens× 2
Regular
0 min15 min
On time < 5 minAttention 5–<10 minOverdue ≥ 10 min
Yellow and red thresholds are configurable on the device. This example uses 5 and 10 minutes only.
All visuals are rebuilt web examples with simulated data, not device screenshots of the current release. Changes apply only to this page, do not update a device, and do not imply automatic rules for every kitchen type.
04 / TWO DISTINCT WORKSPACES
Focus in the kitchen. Clarity for the owner.
Digital operations mean more than putting paper tickets on a screen. First preserve the work itself; then use a web workspace to explore patterns, investigate issues and review changes.
IN THE KITCHEN
Android kitchen client
Receive and view tickets, manage preparation, see waiting alerts and configure the local display. Keep the team focused on work that needs attention.
Client capabilities and versionsFOR OWNERS · PLANNED
SaaS web workspace
Business statistics, issue analysis and a proactive assistant belong in the web workspace, not the kitchen client. Cloud data integration and account services are not yet available.
Explore the web conceptCentral configuration and future app access are planned directions. Current layouts and alerts are configured locally on Android, not pushed from the cloud.
SaaS web workspace · Planned
See the data.
Spot operational problems sooner.
Start with a change worth checking, inspect the evidence, consider an action, then review it. Business analysis is planned for the SaaS web workspace, not the Android kitchen client.
Simulated dataNo AI connection
This is a scripted demo. No live business data or cloud synchronization is connected.
What deserves a closer look today?
The current average is 14 minutes, 4 minutes above the historical sample (+40%).
Only 4 valid current tickets and 8 historical tickets are included. The 40% difference is arithmetic for this small simulated sample, not a trend or evidence of causation.
Check the evidence before judging.
Batch completion taps, menu mix, or preparation may affect the records. They cannot establish a staffing shortage or individual performance.
Evidence makes an insight useful.
Of 6 simulated current tickets, 4 are included and 2 excluded. The baseline contains 8 valid tickets from the same Thursday window in the previous 4 weeks. Every included record, exclusion, and time boundary is listed below.
History contains 2 tickets per date at 8 and 12 minutes: 80 ÷ 8 = 10 minutes. The current total is 56 ÷ 4 = 14 minutes.
Turn the signal into a small check.
Ask the shift team whether completion taps were batched or the menu mix and preparation changed. If records are accurate, compare the same station, time window, and menu mix.
Example action: check evening completion records
Note an investigation to revisit when new comparable data becomes available.
Cannot assess improvement yet.
There is no new comparable data. Recording an action does not demonstrate improvement. Even if duration falls later, sample coverage and other changes must be checked before attributing it to an action.
No demo action recorded. Try recording one in Suggest.
Inspect simulated source tickets and scope
Demo store / connected source A; timezone Asia/Shanghai. Both groups include valid tickets received from 18:00–20:00 and marked complete by 20:30 on that date. Timing runs from receipt to completion tap, not active cooking time. All dates and tickets are fixed simulated samples.
| Internal ID / date | Received → completed | Minutes |
|---|---|---|
| T012026-09-24 | 18:10 → 18:26 | 16 |
| T022026-09-24 | 18:20 → 18:32 | 12 |
| T032026-09-24 | 18:40 → 18:58 | 18 |
| T042026-09-24 | 19:10 → 19:20 | 10 |
| H1A2026-09-17 | 18:10 → 18:18 | 8 |
| H1B2026-09-17 | 19:10 → 19:22 | 12 |
| H2A2026-09-10 | 18:10 → 18:18 | 8 |
| H2B2026-09-10 | 19:10 → 19:22 | 12 |
| H3A2026-09-03 | 18:10 → 18:18 | 8 |
| H3B2026-09-03 | 19:10 → 19:22 | 12 |
| H4A2026-08-27 | 18:10 → 18:18 | 8 |
| H4B2026-08-27 | 19:10 → 19:22 | 12 |
Sample source ticket T01: table A08, 12 lamb skewers, mildly spicy. Simulated event log: received at 18:10, whole-ticket completion tapped at 18:26, no undo. These details only illustrate traceability.
Current exclusions: T05 (2026-09-24 19:20, awaiting review, no reliable completion time) and T06 (2026-09-24 19:25, suspected reprint). Neither enters the total or denominator; neither counts as zero minutes. The historical demo has no additional exclusions.
T01–T06 and H-prefixed IDs are demo internal identifiers, not POS order numbers. Unconnected sources, unfinished tickets, and missing completion times are outside the metric. This sample cannot represent the whole store.
Verified revenue and costs, payments, refunds, and ingredient records are missing. Profit cannot be assessed.
Follow up · Scripted answers
Choose a question to explore the limits of this demo.
No operational conclusion
Incomplete data needs a clear boundary.
This scenario lacks some sources and historical completion records. Store-wide slowdown cannot be assessed. Missing data is not zero, and no percentage change is produced.
Check source coverage, timestamps, and completion records, then collect comparable samples. Cannot assess improvement or profit.
Actions exist only in this page’s memory and disappear on refresh. No real tasks, notifications, or data uploads are created.
What is OneKDS?
A KDS (Kitchen Display System) displays kitchen tickets and preparation progress on a screen. OneKDS supports restaurant kitchen execution; it does not replace POS checkout or payment systems.
OneKDS Android kitchen display system for supported local kitchen tickets, exception review, preparation, layout and alert settings, and source tracing.
- Public download
- OneKDS 1.4.15 · 2026-10-27
- Platform
- Android 5.0 / API 21 or later; each device requires validation
- Language
- Android app in Chinese; website in Chinese and English
- Compatibility
- Confirm POS versions, text ticket templates and store networks; not universal POS support
- Analytics and assistant
- Planned SaaS web workspace; not included in the current public release
Public-release facts. Verify against: release notes · package and checksum · Android product details
BEFORE YOU START
All questionsAnswers before you start.
Does OneKDS work with every POS?
OneKDS is designed for multiple POS integrations, but the brand alone does not establish compatibility. Confirm the version, output, ticket format and network, then test real tickets. Image-based and unknown formats are not assumed to work.
View the answerWhere will analytics and the business assistant be available?
Planned analytics and the assistant belong in the SaaS web workspace, not the Android kitchen client. The client focuses on tickets, preparation and local settings. The homepage uses simulated data with no AI connection. Cloud integration, account services, metrics and availability will be announced separately.
View the answerAre both the website and app available in English?
The website supports Simplified Chinese and English, with more languages planned. The initial Android app is Chinese only; English instructions include the Chinese controls. Account services are not open. The planned registration defaults are phone in China and email overseas, independently of website language.
View the answerGET STARTED
Bring OneKDS to your kitchen.
Confirm compatibility, then verify your store’s workflow.
Downloads & device requirementsRead the integration guideExplore the one-month activation trial planTrial release pending; registration and activation are not open.
PARTNERS
Serve more restaurants together.
Referral commissions · Wholesale resale
Explore partnership options