FoodOrders.ai

Product Updates

What's new at FoodOrders.ai

Every meaningful improvement to ordering, the AI phone and chat agent, kitchen operations, the Kitchen Printer Agent and Android tablets — written for restaurant owners, not engineers.

Released milestones and improvements

Completed work that is now live or available in its stated release channel.

  1. Kitchen Printer AgentKitchen Pilot

    Cleaner, stable Windows Agent screens

    The Kitchen Printer Agent now keeps each dashboard screen laid out reliably while switching between Status, Configuration, Diagnostics and Stations, including on high-DPI Windows displays.

    • Keeps the selected Configuration tab visibly highlighted in FoodOrders.ai blue.
    • Prevents the Configuration action cards and buttons from overlapping one another.
    • Eliminates stale, clipped and horizontally displaced Diagnostics content when changing screens.
    • Preserves the existing print queue, ticket renderer, pairing, saved printer and server-authoritative routing controls.
    Learn more
  2. Kitchen Printer AgentKitchen Pilot

    Verified, attended Agent updates

    The Kitchen Printer Agent can now verify and install a downloaded FoodOrders.ai update through an attended, print-safe workflow instead of relying on an operator to trust an installer manually.

    • Adds Help → Install downloaded update for signed Agent installers obtained from the secure tenant dashboard.
    • Verifies the exact published SHA-256 checksum and trusted FoodOrders.ai Windows signature before installation.
    • Refuses to begin an upgrade while locally queued or review-required print work exists.
    • Uses one explicit Windows administrator prompt and leaves forced or unattended installation disabled.
    • Preserves the existing print queue, ticket renderer, pairing, printer choice and server-authoritative routing controls.
    Learn more
  3. Kitchen Printer AgentKitchen Pilot

    A clearer, more reliable Windows Agent dashboard

    The Kitchen Printer Agent now keeps restaurant identity and operational pages clearly rendered, provides more room for printer details, and makes installed-versus-published software versions explicit.

    • Keeps the linked restaurant name and address visible in the Agent header after refreshes and page changes.
    • Prevents content from a previous page showing through when Setup, Diagnostics, Stations or Account is opened.
    • Gives the Configuration tab and printer panel enough room for labels, connection details and readiness messages.
    • Shows both the installed version and newest published signed version whenever staff manually check for updates.
    • Adds Support to the Help menu so restaurant staff can reach the existing support path from any Agent page.
    Learn more
  4. Kitchen OperationsKitchen Pilot

    Stack A is live: one safe print route for every kitchen

    FoodOrders has completed and deployed the Stack A print-routing foundation: each restaurant location now has one server-authoritative choice for sending new kitchen tickets to a Windows Agent, an Android Station, or nowhere while printing is paused.

    • A single control in the restaurant dashboard selects Off, Windows Agent or Android Station for each location.
    • The canonical queue now allows only the selected device class to lease new jobs, so Windows and Android cannot compete for or duplicate the same ticket.
    • Route changes are recorded in an audit history, while acknowledged or locally spooled work stays with the device that already accepted it.
    • The rollout preserves the existing FoodOrders order lifecycle, print queue and kitchen-ticket renderer instead of creating a second print system.
    • Production verification confirmed the selected Android route, blocked Windows from leasing new work and left nine existing queued jobs unchanged.
    Learn more
  5. Kitchen Printer AgentKitchen Pilot

    Better-aligned Windows printer test pages

    The Kitchen Printer Agent now respects the selected printer's printable area and hardware margins when producing its standard Windows test page.

    • Positions the fallback test page inside the printer's reported printable area instead of assuming the physical page begins at coordinate zero.
    • Reduces visibly offset or clipped test output on compact receipt-printer queues.
    • Keeps the production 80 mm kitchen-ticket renderer and automatic order-printing safeguards unchanged.
    Learn more
  6. Kitchen Printer AgentKitchen Pilot

    A cleaner, responsive kitchen printer dashboard

    The Kitchen Printer Agent now presents pairing, printing and diagnostics in a polished layout that remains readable from compact windows through full-screen support views.

    • Keeps restaurant identity, status text and controls from overlapping as the window changes size.
    • Uses clearer selected tabs, navigation states and business-focused typography.
    • Adds softer cards and controls while preserving the established FoodOrders.ai visual identity.
    Learn more
  7. Kitchen Printer AgentKitchen Pilot

    Clearer pairing recovery and readiness diagnostics

    The Kitchen Printer Agent now distinguishes an outdated server response from a genuine pairing mismatch, keeps the repair action fully visible, and reports restaurant connection failures without remaining stuck on a loading message.

    • Explains when the server heartbeat must be updated instead of asking staff to repeat a successful pairing.
    • Makes the pairing repair window taller so its action button remains visible without awkward resizing.
    • Replaces the indefinite restaurant loading message with a clear connection-unavailable diagnostic after a failed heartbeat.
    Learn more
  8. Kitchen Printer AgentKitchen Pilot

    Cleaner kitchen tickets with the details that matter

    The Kitchen Printer Agent now removes repeated item-name notes from kitchen tickets while preserving genuine choices, modifiers and special instructions.

    • Stops legacy summaries from printing a second time when they only repeat the menu item name.
    • Keeps real modifiers and special instructions visible for kitchen staff.
    • Adds a shared kitchen-ticket contract fixture to keep future Windows and Android ticket formatting aligned.
    Learn more
  9. Kitchen Printer AgentKitchen Pilot

    Repair a mismatched pairing without losing printer setup

    The Kitchen Printer Agent now offers a guided pairing repair when its protected local enrollment no longer matches the restaurant or location returned by the server.

    • Replaces the unhelpful unpair action with Repair pairing when the server reports a restaurant or location mismatch.
    • Guides the operator through a fresh Windows pairing code while preserving the saved printer and local job history.
    • Makes the website pairing card explicitly Windows-only so Android Station provisioning cannot be confused with the Windows Agent workflow.
    Learn more
  10. Kitchen Printer AgentKitchen Pilot

    Pair once, stay connected

    The Kitchen Printer Agent now keeps an approved computer paired until it is deliberately revoked and renews its protected device credential automatically.

    • Replaces the confusing pairing-expiry countdown with a clear paired-until-revoked status.
    • Automatically renews the hidden device credential using proof from the computer's protected device key.
    • Adds a local pause and resume control so restaurant staff can stop Windows printing from the Agent without weakening the owner's server permission.
    Learn more
  11. Kitchen Printer AgentKitchen Pilot

    A polished FoodOrders.ai printer dashboard

    The Kitchen Printer Agent now presents pairing, automatic printing, and printer readiness in a clean FoodOrders.ai dashboard with built-in release information.

    • Rebuilds the Agent as a focused FoodOrders.ai dashboard with a navigation rail, system-status bar, restaurant banner, and printer-focused artwork.
    • Makes setup, readiness, and diagnostics easier to scan while retaining the existing pairing, queue, and automatic-printing controls.
    • Adds the installed version, About information, and the current release history under Help.
    Learn more
  12. Kitchen Printer AgentKitchen Pilot

    A brighter Menu Steward dashboard with reliable startup

    The Kitchen Printer Agent now uses a light, portrait-friendly Menu Steward dashboard and includes the startup repair required after the initial 0.4.3 pilot build.

    • Introduces a brighter glass-style dashboard inspired by the Menu Steward product direction while keeping kitchen readiness information prominent.
    • Uses a taller, portrait-friendly layout with bounded cards so pairing, automatic printing, printer setup, and diagnostics remain readable without overlapping content.
    • Repairs the startup failure in the initial 0.4.3 pilot build while preserving existing pairing and print-queue behavior.
    Learn more
  13. Kitchen Printer AgentKitchen Pilot

    A clearer kitchen dashboard with safer ticket handling

    The Kitchen Printer Agent now has a compact Blue Glass dashboard, safer recovery for uncertain print outcomes, and automatic pagination for long kitchen tickets.

    • Introduces a compact, modern dashboard that keeps pairing, automatic printing, printer selection, and diagnostics visible without awkward scrolling.
    • Prevents duplicate ticket output during replay and preserves uncertain print outcomes for explicit staff review instead of silently retrying.
    • Splits long orders across clearly numbered pages while preserving the canonical FoodOrders.ai print queue.
    Learn more
  14. Kitchen Printer AgentKitchen Pilot

    Safer Windows upgrades and clearer Agent controls

    The Kitchen Printer Agent now upgrades safely when an earlier copy is running, uses clearer FoodOrders.ai naming, and can check for newer pilot releases.

    • Stops an earlier Agent gracefully during an upgrade and keeps rollback available if installation fails.
    • Uses the full FoodOrders.ai Kitchen Printer Agent name in Windows, shortcuts, and the Agent window.
    • Adds Check for updates now and an optional automatic update check to the Help menu.
    Learn more
  15. Kitchen Printer AgentKitchen Pilot

    Clearer kitchen setup and printer confirmation

    The Kitchen Printer Agent now makes it easier to confirm that a restaurant is connected and ready to print.

    • Shows the paired restaurant name and location.
    • Uses three numbered readiness checks.
    • Displays the exact saved kitchen printer.
    • Keeps printer testing separate from saving.
    Learn more
  16. Online OrderingGenerally available

    Storefront themes and seasonal styling

    Restaurants can choose a storefront look that matches their brand, including light and dark styles, fonts, banners and seasonal touches.

    • Choose a theme and colour mode for your ordering page.
    • Upload a logo and banner.
    • Optional seasonal decorations.
  17. AI Phone & ChatGenerally available

    Mid-conversation language switching

    The AI phone and chat agent can follow a customer who changes language part-way through an order.

    • Supports 27+ languages in one conversation.
    • Keeps the order in progress when the language changes.
    • Faster spoken responses on the phone.
  18. Kitchen Printer AgentKitchen Pilot

    Automatic ticket printing for paired kitchen computers

    Paired Windows computers can print eligible orders automatically as kitchen tickets, with the order still visible on the kitchen screen if the printer is busy.

    • Automatic printing for paired kitchen computers.
    • Test page before a printer is used for live tickets.
    • Tickets remain on the kitchen screen as a fallback.
    Learn more
  19. Kitchen OperationsGenerally available

    Background alerts for the kitchen screen

    The kitchen screen keeps alerting staff about new orders even when the tablet has been left on another screen.

    • Audible and visual alerts for new orders.
    • Works when the kitchen tab is in the background.
    • Clear count of orders waiting to be accepted.
  20. Reliability & SecurityGenerally available

    More reliable sign-in and two-step verification options

    Sign-in is more resilient, and restaurant owners can add an authenticator app plus a backup email for two-step verification.

    • Authenticator app support (Google Authenticator, Microsoft Authenticator, Authy, 1Password, Bitwarden).
    • Backup email factor for account recovery.
    • Improved sign-in reliability on published sites.
    Learn more

Development and pilot updates

Work in progress, separate from available software releases. These updates do not offer downloads.

Pilot testingUpdated

First complete demo-store order printed through Android Station

One attended FoodOrders order has completed the canonical queue, paired Android Station and Star kitchen-printer path on real pilot hardware.

  • The restaurant's server-selected Android route delivered the accepted order to the paired Ingenico M70 without competing with a Windows Agent.
  • The M70 durably stored the ticket before printing, produced one readable Star TSP143IIILAN kitchen chit and completed the cutter and server acknowledgement path.
  • A signed 0.1.23 recovery build also preserved a previously queued order across its original lease expiry without reassigning it to another device.

Availability and limitations

  • This is one attended pilot result on one M70 and one TSP143IIILAN configuration; it is not a broad field-readiness or compatibility claim.
  • A preceding paper-path jam showed that successful network submission cannot prove that paper physically emerged, so unattended fault handling remains an acceptance gate.
  • Long-run order soak, power interruption, rollback, field-support drills and the incoming TSP143IV X4 SK acceptance remain open.
Pilot testingUpdated

Expanding the Android Station printer test bench

FoodOrders can continue its Star SDK integration work, and a current-generation TSP143IV X4 SK evaluation printer is being added to the Android Station test bench.

  • The existing TSP143IIILAN remains our physically tested regression printer while the incoming TSP143IV X4 SK becomes the forward reference unit.
  • Both generations will use the same durable FoodOrders queue, kitchen-ticket contract and duplicate-prevention rules.
  • The new printer will complete model, firmware, connectivity, media, fault and recovery tests before its support status changes.

Availability and limitations

  • The incoming TSP143IV X4 SK has not yet completed FoodOrders physical acceptance and is not currently marked verified.
  • Android customer-order printing remains disabled while the guarded delivery path is tested.
  • Reseller and Technology Partner program details are separate commercial steps and are not represented by this engineering update.
Pilot testingUpdated

Proving secure tablet identity and fleet health

Our first named Android Station has completed supervised restaurant enrollment, and the pilot now reports authenticated health without receiving customer orders or enabling automatic printing.

  • The platform administrator registers and reserves a FoodOrders-owned tablet, then creates a separate eight-digit, single-use Android activation code for its assigned restaurant and location.
  • The Station reports its application version and authenticated contact on a 15-minute schedule while its foreground agent is running.
  • The Fleet workspace distinguishes healthy, offline, renewal-due, expired and revoked identities, and the tablet can safely renew its protected credential before expiry.

Availability and limitations

  • Android customer-order delivery and automatic printing remain disabled; the enrolled tablet is still an internal hardware pilot.
  • Public APK downloads and preloaded customer shipments remain gated by model-specific acceptance, release signing and rollout approval.
  • A recent heartbeat proves authenticated device contact, not printer readiness, restaurant network quality or unattended production acceptance.
Pilot testingUpdated

Preparing a direct kitchen-printer test from Android Station

The Android Station laboratory app produced a complete, cut raster test ticket on our Star network printer, confirming the first controlled tablet-to-printer path on real hardware.

  • The tablet uses its active Wi-Fi network to find local printer candidates and requires an operator to choose one.
  • The fixed laboratory ticket printed completely and readably, the cutter operated as expected, and the next build refuses known offline, open-cover and paper-empty states before writing.
  • The final APK is built for the Ingenico M70's Android 8.1 baseline, and automated checks keep legacy Bluetooth, storage and phone permissions out of the app.

Availability and limitations

  • This is one attended result on one Ingenico M70 and one Star TSP143IIILAN; broader devices and firmware versions remain unverified.
  • This laboratory feature does not receive customer orders, enable unattended printing or change the existing Windows Printer Agent and production queue.
  • The work does not establish universal Star compatibility, vendor certification or a customer-downloadable Android release.
Pilot testingUpdated

Star TSP143IIILAN verified for the Windows Agent

FoodOrders has physically verified one exact Star TSP143IIILAN Ethernet configuration with the Windows Kitchen Printer Agent and compact 80 mm kitchen-ticket output.

  • The official Star LAN setup path created the working Windows queue and produced both the FoodOrders test page and a complete kitchen chit.
  • Ticket width, wrapping and cutter behaviour were observed on the exact TSP143IIILAN Ethernet model with the Star TSP143IIILAN Cutter driver.
  • The Windows Agent 0.4.8 release baseline passed 205 test files and 1,152 automated tests, TypeScript validation, Windows MSI installation and major-upgrade CI, database/security checks and browser smoke tests.

Availability and limitations

  • FoodOrders Verified applies only to the recorded TSP143IIILAN Ethernet, Windows 11, 80 mm and named-driver configuration; it is not a certification of the full TSP100 family.
  • A stable printer network address and a successful on-site FoodOrders test print are still required at each restaurant.
  • Multi-printer station routing and Android customer-order printing remain separately gated pilot capabilities.
In developmentUpdated

Preparing secure restaurant pairing for Android Station

Android Station can now use the same short-lived restaurant pairing workflow as the Windows Kitchen Printer Agent while retaining a distinct tablet identity.

  • A six-digit code links the Station to the intended restaurant and location after an on-device confirmation.
  • The tablet creates protected device keys and stores its issued credential with Android's secure key storage.
  • Windows and Android share the server device registry, audit trail and revocation boundary without creating a second order or print system.

Availability and limitations

  • The pairing build and server changes are under review and are not yet activated for restaurant use.
  • Android customer-order delivery and production printing remain disabled pending physical POS-printer acceptance.
  • Pairing identifies the restaurant and tablet; it does not assign inventory custody or activate a printer.
In developmentUpdated

Preparing permanent tablet labels

We have prepared printable FoodOrders asset labels to help identify tablets during setup, shipment and return.

  • Labels show the FoodOrders asset number, make, model, original serial and recorded preparation date.
  • An inventory QR reference stays the same when a tablet changes assignment, without carrying restaurant details or activation credentials.
  • Vector downloads and a browser print sheet are prepared; longer identifiers wrap without being shortened.

Availability and limitations

  • The label feature is prepared in code; production publication and physical print/scan acceptance are still pending.
  • The QR is an inventory reference, not a setup link, pairing code or customer-order printing feature.
  • Label stock, sizing, placement and readability must be checked on the actual tablet.
Pilot testingUpdated

Tracking tablets from intake to return

Our internal tablet fleet screen and its supporting records are now deployed, helping our team track hardware before it reaches a restaurant.

  • Track make, model, original serial number, asset label and recorded physical custody.
  • Reserve a tablet for an existing restaurant account, record shipment and return, and retain assignment history.
  • Returned tablets require recorded inspection and wipe checks before being made available again.

Availability and limitations

  • Fleet management is restricted to platform administrators; restaurant self-service provisioning is not available yet.
  • An inventory assignment does not pair or activate a tablet. Android pairing, customer-order delivery and live printing remain pending.
  • The fleet currently supports one main location per restaurant account. Full admin intake and persistence acceptance remains to be completed.
Pilot testingUpdated

Testing tablet endurance and printer discovery

A powered two-hour test on our M70 lab tablet completed 48,100 simulated jobs. Restart and network-recovery checks are helping us assess it as a future kitchen station.

  • The same app process completed the powered workload, with sampled process memory around 42–46 MiB.
  • Test jobs survived restarts, and uncertain print attempts stayed marked for review instead of being automatically repeated.
  • Network discovery identified a Canon TR4700 by name, giving us an early check of the printer-finding experience.

Availability and limitations

  • These were simulated jobs on one USB-powered tablet, not customer orders or a battery-endurance test.
  • The discovered Canon produced no test ticket. Discovery alone does not establish printer compatibility.
  • POS kitchen-printer output, paper and network fault handling, overnight testing and more devices still need physical validation.
Pilot testingUpdated

First Android Station prototype running on an M70

Our first native Android test app is running on an Ingenico M70 with Android 8.1 and 2 GB of memory, an early step toward a preloaded tablet option for restaurant pilots.

  • The tablet displays device information, runs an HTTPS connectivity check and starts a background agent service.
  • Local storage self-tests passed, and simulated jobs can be retained for restart and recovery checks.
  • This Android component is developed alongside the existing Windows Printer Agent.

Availability and limitations

  • The prototype is a lab build with no customer download, restaurant orders, pairing or live printing.
  • Initial results on one device do not establish fleet-wide reliability or readiness for restaurant deployment.
In developmentUpdated

Preparing the next Pilot release safely

The supporting database records for location-specific printer allowances, menu-station assignments, Pilot applications and support requests are now installed. Website build checks also pass, but installation is not the same as enabling these services.

  • New location and station records have restricted access, with separate audit records for operational changes.
  • Pilot application, payment-reconciliation and support-request foundations are installed without starting payments or sending support messages.
  • The website build repair passed GitHub checks and Lovable compiler and production-build verification.

Availability and limitations

  • This is a development progress notice, not a new Printer Agent installer release or confirmation that the website build has been published.
  • New payment processing, automated support dispatch and printer-capacity enforcement remain inactive pending their operational acceptance.
  • Multi-station delivery remains off; representative printers and attended physical testing are still required.
  • Earlier dated development notices describe the state at their publication date, not the current migration state.
In developmentUpdated

Adding safer controls for each restaurant location

We have prepared separate safety switches so future kitchen-station routing can be introduced one restaurant location at a time without changing printing elsewhere.

  • Each location keeps its own station-routing and order-delivery settings instead of inheriting a company-wide switch.
  • New settings begin turned off, and sending station tickets cannot be enabled unless station routing is also enabled.
  • Policy changes are retained in an audit history and restaurant browser sessions cannot edit the database records directly.
  • A missing or mismatched policy keeps the new delivery path off rather than guessing.

Availability and limitations

  • These controls do not activate station routing or change current customer-order printing.
  • No restaurant location is enabled by this database foundation.
  • Manager controls, attended multi-printer acceptance and an explicit location activation remain required before pilot use.
In developmentUpdated

Planning printer options for kitchens of different sizes

We have defined a per-location direction for restaurants that need one consolidated printer, several preparation stations, or a larger kitchen fleet.

  • The planned ladder is CAD $29.99 per month for one production printer, $49.99 for two or three, $69.99 for four or five, and custom pricing for six or more at one location.
  • Any FoodOrders.ai subscription may add printer capacity, and every restaurant location keeps its own clear allowance instead of sharing an ambiguous company-wide pool.
  • Registered hot-spare printers are planned not to consume capacity when they are reserved for audited failover rather than everyday ticket routing.
  • Multi-printer kitchens are being designed to send the right items to stations such as Grill, Fry, Cold, Bar and Expo while preserving one complete order.
  • Authorized owners will be able to monitor several locations centrally without allowing one restaurant to print another location's tickets by accident.

Availability and limitations

  • These packages and prices are approved product direction but are not yet available to purchase and no billing has been enabled.
  • Printer-capacity enforcement, hot-spare failover and multi-location fleet controls are not active.
  • Station splitting remains in development and is not enabled for live customer orders.
  • The supporting database migration remains unapplied and existing pilot printing is unchanged.
In developmentUpdated

Preparing separate tickets for each kitchen station

We are building station routing so one accepted order can send the right items to Grill, Fry, Cold, Bar and Expo without creating separate orders.

  • Restaurant managers will be able to assign menu categories, products and modifiers to the station that prepares them.
  • Each station receives only its own items, while an optional Expo ticket keeps the complete order together for final coordination.
  • Unknown items fail safely to a chosen fallback station instead of disappearing from the kitchen.
  • Order changes can identify exactly which station needs an add, remove or stop notice, leaving unaffected stations alone.
  • Printer selection supports a primary and backup device within the same restaurant location.

Availability and limitations

  • Station routing is implemented as reviewed foundations only and is not enabled for live customer orders.
  • The multi-location database migration has not been deployed and no restaurant configuration has been activated.
  • Live multi-printer recovery, correction tickets and representative kitchen hardware still require attended acceptance testing.
  • No POS brand or printer model gains compatibility or certification from this development work.
Pilot testingUpdated

FoodOrders.ai publisher identity verified for the Windows Agent

Microsoft Artifact Signing has produced and independently verified our first FoodOrders.ai-signed Windows Agent release candidate.

  • The Agent program and Windows installer carry the verified FoodOrders.ai publisher identity and a trusted timestamp.
  • Our release workflow uses short-lived GitHub-to-Microsoft authentication instead of storing a reusable signing password.
  • Automated release checks verified seven signed files and generated a SHA-256 checksum for the 0.4.0 installer candidate.

Availability and limitations

  • The signed 0.4.0 build remains a private release candidate and is not yet offered as a public download.
  • Representative printer, upgrade, rollback, reboot, network-loss and credential-revocation testing remains before customer distribution.
  • A verified publisher signature establishes file identity and integrity; it does not by itself certify compatibility with every printer or Windows configuration.
In developmentUpdated

Piloting safer order changes and cancellations

We are testing a verified, staff-reviewed process for customers who need to change or cancel an order after placing it.

  • Requests are linked to the original order without letting an unknown caller directly rewrite kitchen instructions.
  • A private text-message confirmation keeps an unknown caller from directly changing a kitchen order.
  • Restaurants can acknowledge a change, decline a request, or cancel an eligible unpaid order and notify the customer.
  • Approved change instructions can reach the kitchen as a clearly marked correction notice without hiding the original order.

Availability and limitations

  • This remains a controlled Kitchen Pilot capability and is not yet available generally.
  • Item repricing, card adjustments and refunds remain staff-managed.
  • Correction-ticket printing still requires physical-printer acceptance testing.
In developmentUpdated

Preparing safer scheduled pickup orders

We are developing same-day pickup scheduling that confirms an exact time with the customer and waits to send the ticket to the kitchen until preparation should begin.

  • Phone and web-chat ordering can present restaurant-approved pickup times instead of inventing availability.
  • The selected time is read back to the customer for confirmation before the order is placed.
  • Scheduled tickets are held from printing, released durably when preparation should begin and flagged for staff review if timing becomes unsafe.

Availability and limitations

  • This feature is disabled and is not yet available to customers.
  • Restaurant controls, operational alerts and live pilot testing must be completed before rollout.
  • Initial scheduling is limited to same-day pickup and does not promise delivery or multi-day catering availability.
In developmentUpdated

Preparing support for more kitchen printers

We are developing a Star Micronics SDK integration to improve kitchen-ticket formatting and printer-status reporting.

  • Initial connection, status and test-ticket adapter code has been prepared.
  • Automated tests check our ticket formatting and safety logic using a simulated printer.
  • Our adapter now builds against Star's library, and its command builder has passed an automated test-ticket check.

Availability and limitations

  • Not included in the customer installer. No action or download is needed.
  • Physical printer testing remains pending; automated command checks do not establish hardware compatibility.
  • This work does not establish certified compatibility or an official Star partnership.

Security, Privacy & Responsible AI

Our application is built on a backend platform that maintains SOC 2 Type II compliance and ISO 27001:2022 certification. We combine this security-focused infrastructure with privacy-conscious data practices, GDPR-supporting safeguards, and responsible AI governance informed by ISO/IEC 42001 principles. Payments are processed by Stripe, so card details never touch our servers. Our source code is maintained under branch protection, required peer reviews, and signed commits.

Platform certifications apply to our backend hosting provider and its defined systems and controls. They do not constitute independent SOC 2 or ISO certification of our company or this application. Compliance responsibilities are shared across our platform providers, application controls, connected services, internal operating practices, and our transparent, review-based development workflow.

  • SOC 2 Type II

    Built using a platform subject to independent security-control assessment.

  • ISO 27001:2022

    Supported by an information-security management framework certified at the platform level.

  • GDPR

    Designed with privacy, transparency, data minimization and user rights in mind.

  • Responsible AI

    AI practices informed by ISO/IEC 42001 principles for accountable AI management.

View Our Security PracticesPrivacy PolicyView Application Trust Center