Detects the SUNMI built-in print service in print settings. If no printer has been configured, a detected V2 built-in printer is selected automatically, without an IP address or Bluetooth pairing.
Preserves existing external printer settings and manual choices. The SUNMI target uses 58 mm paper without cutting, with existing receipt styles, automatic or manual dispatch and reprint workflows.
Checks printer identity and status before submitting a job. Ambiguous results after a timeout or interruption are not retried automatically, helping avoid duplicate receipts.
Supports Android 5.0 / API 21 and keeps the existing signing identity. Print and check a test receipt before enabling; detection does not print automatically. Physical V2 output, consecutive jobs and recovery after paper replacement still require on-site verification.
Recognize customer receipts and confirm receiving rules
Recognizes supported text columns such as item name, quantity and subtotal, showing the table, source order number, items and quantities. Prices are never preparation quantities; missing source times or units remain explicit.
Compare the original receipt and confirm whether each print contains new items or the full order total. Save the rule for future tickets from the same sender, integration profile and format; cumulative receipts add only positive changes.
Preserves existing kitchen receipt handling and original records. Suspected duplicates, reductions, unknown content, reused order numbers across days and format changes still require review. Historical held tickets are not admitted in bulk.
Supports Android 5.0 / API 21 and retains the existing signing identity for upgrades. Recognition covers supported text formats, not arbitrary images or unknown layouts; receiving rules and real-device ticket flow still require on-site verification.
Adds standard and large-type receipt presets. Configure the shop name, title, footer, optional fields, order within groups, font sizes, bold text, spacing and separators. Table, dish and quantity remain visible.
Preview 58 / 80 mm layouts and print a test using the current draft. Saved changes apply to new outbound receipts; pending jobs and reprints retain their original layout.
This website update also includes table-based outbound batches and printing, batch review of held tickets, business-day handling, startup settings and local network alerts from the intervening local releases.
Built on 2026-09-30 with Android 5.0 / API 21 support and the existing signing identity. Printer compatibility depends on the exact model, interface and protocol; new layouts still need a physical print test.
The launcher uses an orange background and white screen-and-spatula mark, enlarged by 12%.
Retains Android 5.0 / API 21 and the existing signing identity for updates. Device launcher appearance and in-store operation still require validation.
Reserves space for preparation requirements and scrolls when needed. Waiting dishes use an amber border; overdue dishes use a full red border.
1.3.6
Multi-column dish selection
Multi-column dish selection
Select dishes using a responsive card grid, search, selection filters and select-current-results. Existing slot positions are retained.
1.3.5
Simpler kitchen board
Simpler kitchen board
Moves slot configuration to Settings → Dishes and slots. Listener details remain in settings rather than the main board.
1.3.4
Receiving and fault handling
More reliable receiving, with isolated fault records.
Fixes common printer status queries and continuous probes blocking later tickets. Faulty connections retain bytes already read and flag them for review.
New tickets can proceed when their source date is clearly later than every matching, completed historical ticket. Same-day, unclear-date and unfinished matches still require review.
Malformed ticket or quantity records are isolated without blocking valid tickets or resetting prepared quantities.
History displays 100 tickets per page while undo still targets the latest completed ticket. Probe-only traffic causes fewer refreshes; connection usage and low-storage warnings are visible.
Retains Android 5.0 / API 21, the existing signing identity and the Chinese-only app. Automated checks passed; real POS, physical-device and 48–72-hour operation still require on-site validation. The four-connection limit and growing history remain; this is not a zero-loss guarantee. Account activation and SaaS services are not included.
Tap a dish name or modifier to view details. Use the Complete button, or swipe right to the prompt and release, to prepare it. Short swipes, scrolling, canceled gestures and multiple fingers do not complete dishes.
One remaining unit completes directly; multiple or fractional quantities open a quantity selector. BBQ actions apply only to the selected modifier group, with fixed positions retained.
Whole-ticket completion first confirms the table, dishes, modifiers and remaining quantities. An outdated confirmation cannot be saved after quantities change.
A five-second undo shortcut targets the operation just completed. Later preparation or cancellation changes can block that undo. Repeated taps cannot stack detail dialogs, and completed action dialogs close.
Retains Android 5.0 / API 21 support and the existing signing identity. The app is Chinese-only. Automated regressions and native simulated screens were checked; device, POS and in-store validation remain necessary. SaaS analytics and account activation are not included.
Clearer 2dp slate separators between dishes, bold warm-yellow modifiers on their own wrapping lines, and prominent ticket notes.
Fixed dish positions and summaries also emphasize preparation details, while preserving receiving, quantity actions, partial completion and undo.
This website download moves from 1.0.1 to 1.3.2, including automatic preparation entry introduced in 1.2.0 for complete, unambiguous supported tickets. Exceptions still require review.
Includes local layout, font size, capacity and fixed-position settings introduced in 1.3.0, plus configurable yellow/red alert thresholds defaulting to 5/10 minutes.
Android 5.0 / API 21 or later, with a Chinese-only app. Relevant regressions and native simulated screens were checked; this does not replace device, POS or in-store stability validation. SaaS analytics and account activation are not included.
Business logic carried forward from 0.1.20. Minimum Android 5.0 / API 21.
Insufficient source identity does not automatically establish a reprint or cancellation. Resuming listening does not recover missing tickets.
Confirm application identity and signing compatibility before updating. Do not uninstall or clear data first; check records and receiving afterwards. These releases do not establish universal POS support, account activation or production stability.