Clear about what is live - and what still needs work.

SEZA plan checkout, invoices, billing status, and saved subscription payment methods are handled through Stripe.

The codebase includes Terminal-oriented endpoints and Android driver architecture. Production use requires provider approval, live keys, compatible readers, and the required native plugin in the Android build.

Availability depends on the connected Stripe Terminal reader, country, merchant account, device, and provider configuration.

A guided workflow for dividing one sale across multiple tender types remains planned.

The receipt workflow is present and requires valid SMS-provider credentials, a sending number, and compliant merchant consent practices.

The receipt workflow is present and requires the deployed email service and sender configuration to be active.

Receipt printing depends on a compatible printer, connection method, and device-specific setup.

Export-supported reports and directories can be moved into spreadsheet and accounting workflows.

Direct accounting synchronization has not been released.

Direct accounting synchronization has not been released.

A public merchant API for external catalog and inventory synchronization has not been released.

A supported two-way Shopify connector has not been released.

Standard keyboard-style scanners can work where the operating system exposes them as HID input.

Supported Android builds can use the device camera for barcode scanning.

Actual support depends on the printer model, connection, driver, and device configuration.

Drawer opening depends on compatible printer ports and command settings.

A documented external API for merchant-built integrations has not been released.

Configurable outbound sale, refund, and stock events remain planned.