The limited-time offer is 1 month free after registration and activation. The trial-enabled release is not yet available. Pricing, offer dates and expiry rules will be published before it opens. The current public release has no account activation.
Your questions. Clear answers.
From devices and installation to POS setup, trials and partnerships.
14 questions
The proposed flow separates registration from activation and shows the expiry after the first successful activation. Registration alone does not start the trial. The exact meaning of “1 month” will be confirmed; it should not be assumed to mean 30 days.
Renewal pricing, purchase methods, available features and data retention rules are still to be confirmed. Full terms will be provided before the trial opens. No automatic billing, grace period or deletion policy has been promised.
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.
The current public release requires Android 5.0 / API 21 or later and permission to install APKs. Device model, touch, storage and background receiving need checking. Windows, macOS and iOS cannot directly install this Android package.
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.
Distinguish no reception record from a received ticket waiting for review. Check listening status, the actual IP and port, POS destination and send time. If a source ticket exists, check its review reason. Keep records before reinstalling or clearing data.
Receiving data and understanding its meaning are separate steps. In the current public release, complete and unambiguous supported tickets can enter preparation automatically. Unknown, incomplete, suspected reprint and unclear cancellation tickets still need review; not every ticket is a new preparation task.
No. One ticket may be a print batch or a later add-on. Whole-ticket completion applies to its preparation tasks, not necessarily every order for that table.
Use an in-place update when application identity and signing conditions match. Do not uninstall or clear data first. Check source tickets, quantities, settings and receiving after updating. Ask support about signing conflicts.
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.
Contact the published email address info@onekds.com. Prepare the issue category, app version, device model, event time, POS version, errors and description on the contact page, then copy and send them yourself. Online submission is not open; form details are previewed locally in your browser and are not sent to OneKDS. Redact customer and payment details before sharing screenshots or samples.
Yes, choose referral commissions and wholesale resale together. Rates, attribution, quotations, refunds and settlement are agreed manually before business begins. You can prepare your details; online submission is not yet open.
This is not guaranteed. Saved records and tickets that never arrived are different. Restoring the network or listener does not recover missing tickets automatically. Compare interruption, paper and POS records before arranging any supported resend.
KEEP EXPLORING