In development · request access

R&D COPILOT POS

A fast sale at the till that also confirms stock and the fiscal receipt — not just the price.

01 / Workflow

From intent to a verifiable trail

The cashier scans, the commercial rule applies, payment and fiscalization happen, and the sale is written to stock exactly once — never twice.

Every operation retains company identity, actor, and source linkage.

Acceptance requires tests against the actual authorized version, integration, and data.

02 / Scope

Capabilities and boundaries

Designed scope

  • scanning and promotions
  • payment and fiscalization
  • reconciliation with stock

On the roadmap

  • Locking in the POSNext route and the exact version combination is the next step.
  • Validating the AMEF device, the payment terminal, and the real hardware comes next.

03 / API

Controlled integrations

Connections use authenticated APIs and durable events. Single sign-on does not replace data synchronization, and each service retains its declared authority.

  • Inventory API
  • ERP
  • AMEF

04 / Docs

Public integration notes

Working contract

Commands require an idempotency key, legal company, actor, source, and timestamp. Corrections use linked reversals and never silently rewrite history.

Access and availability

Validating the application entry point — origin, path, license, and release evidence — is the next milestone before the /app route goes live.

Price and inclusions

Pricing and commercial terms are being worked out; there is no published price or checkout yet. Reach out for where things currently stand.

05 / FAQ

Factual answers

Is the product available now?

Not yet — it's in development. Reach out and we'll tell you exactly where things stand and how to get early access.

Can I purchase online?

Not yet — there's no self-serve checkout while pricing and terms are being finalized.

What does this page prove?

It describes what's designed and what's still ahead — not a claim that this is production-ready or certified today.