Roadmap

What comes next, in the order that matters.

Five250 grows one complete business outcome at a time, each built end to end before the next begins. No dates here: we commit to the order and to the proof, not to a calendar.

  1. Now

    • Point of sale: store credit and exchanges, then integrated card payments on the reader
    • Go-live accounting: opening balances and the cutover
    • Incoming customer orders at scale, with model pinning and output checks
    • Mutation testing of every money and tax rule, and secret scanning on every change
    • Readable record pages: every document reads the way the business reads it
  2. Next

    • Delegated AI actions with mandates, limits and review windows
    • AI reading of supplier invoices; supplier returns
    • Receivables aging, customer statements and reminders, deposits
    • Promotions, customer groups and margin alerts
    • Reservations against incoming supply and promised backorder dates
    • More sales channels and integrations; passkeys and a second factor for everyone
    • Plain-language reporting over approved measures
  3. Later

    • A food-distribution release: lots, first-expiry-first-out, recall
    • Italy as the second localization; multi-currency and multi-entity
    • Bins, RFID, designed labels and GS1 barcodes, replenishment proposals
    • Customer portal, offline selling, loyalty, delivery routes and carrier integrations

Quality gates

Ships when it is proven, not when it is due.

Building a feature is not the same as trusting it with your books. Every release that touches money, stock or access clears these gates, and none is skipped for a date.

  1. Accounting review

    Costing, revenue and tax treatments are reviewed by an independent accountant, with the worked examples that show them.

  2. Security

    A second factor for privileged users, rehearsed account recovery, and verification against OWASP ASVS.

  3. Recovery and operations

    Independent backup restores and retention, alerting with a named responder, and rehearsed outages.

  4. Capacity

    Proven at its supported size, such as 5,000-row imports under concurrent use, on the deployed system.