No reception record
Check listener, actual address and port, POS target, send time and feedback.
Prepare your device, check your POS and send a test ticket. Six steps for local TCP setup in OneKDS.
This guide covers the supported local TCP / GB18030 text-receiving path in the current public release. A POS brand or configured IP alone does not establish compatibility. Other outputs, image-only tickets and unknown templates need an integration review first.
Prepare an Android touch device that runs OneKDS, a confirmed kitchen-ticket format and a POS with configurable test output. Verify actual network reachability between the POS and receiving device; the same Wi-Fi name does not prove that they can communicate.
Record the POS name and version, template name and version, output method, device model and Android version. Arrange an authorized test window, preserve the production print configuration and keep paper tickets for comparison. This guide does not require disabling your existing printer.
0 / 3 checked
This checklist is for preparation. Follow the steps to verify compatibility.
Record the POS name, version, output method and sample. Open 设置 → 模板支持范围 (Settings → Supported templates). Request a review for unknown formats; image-only tickets are not assumed to work.
Check: System and format are known; the production print route is preserved.
In 设置 (Settings), check the actual local IPv4 address and TCP listening port. Stop receiving before changing the port, then 保存端口 (Save port) and 开始接收 (Start receiving). Do not copy example addresses into a live store.
Check: Listening has started on the intended actual address and port.
Authorized staff configure a test output to the receiving device. Vendor menus vary. Confirm the actual IP, port and routing without replacing the production print configuration.
Check: The test destination is correct and production printing remains available.
Mark it “TEST — DO NOT PREPARE”. Record the send time and POS feedback. Inspect recent reception, 待做 (Preparation) and 待核对 (Pending review). A printer-status response alone is not a complete business ticket.
Check: The complete source ticket matches this test send.
Complete, unambiguous supported tickets can enter preparation automatically. For tickets needing review, open 待核对 → 查看并处理 → 核对后加入待做 (Pending review → View and handle → Add after review). Compare table, dishes, quantities, units and original/add-on status. Record the reviewer and evidence. Unknown, partial, reprint or cancellation tickets must not become independent new tasks.
Check: A complete, supported test ticket enters preparation with sufficient evidence.
Test whole-ticket or partial completion, source access and retained records. Reopen the app, check receiving intent and send a distinct test ticket. 设置 → 接入档案 (Integration profile) records configuration; it does not authorize automatic acceptance.
Check: Quantities are correct and another ticket can be reviewed. Production stability still needs testing.
In 设置 → 接入档案 (Settings → Integration profile), record the POS and template versions, output configuration, source configuration, reviewer and evidence. Saving a profile keeps a site record; it does not authorize automatic acceptance or replace real test tickets and production stability testing.
Check listener, actual address and port, POS target, send time and feedback.
Check Pending review. Do not resend or approve repeatedly to force a preparation task.
Keep the source and device/template versions. Hold the ticket for format review. Do not fill in default quantities or units to hide format errors.
Open 设置 → 中断记录与核对, compare paper and POS records, and verify source relationships before resending.