One POS. Built to adapt to your business.

Aetion POS is a modular point-of-sale platform designed to adapt to different business workflows through a configurable core and extensible functionality.

Aetion POS is in early development and has not been released yet.

Aetion POS concept

Preview a business type

Products

  • Cotton tote9.00
  • Notebook A56.50
  • Ceramic mug12.00
  • Scented candle14.00
  • Gift card25.00
  • Greeting card3.50
Retail extension Walk-in sale at counter 1
  • Cotton tote2 ×18.0014 left in stock
  • Notebook A51 ×6.5031 left in stock
  • Ceramic mug1 ×12.00Last 3, reorder suggested
Subtotal
36.50
Member discount 10%
−3.65
Tax 5%
1.64
Total
34.49

Payment

  • Card
  • Cash
  • Split

Concept illustration, not a screenshot of working software. The highlighted rows show what an industry extension could add. Everything else is the shared core. Items and amounts are examples.

Changing how you work shouldn't mean replacing your POS

Most point-of-sale software is built for one kind of business. When a shop adds a café counter, or a salon starts selling products, the system that fit yesterday often has to be replaced, along with the data and the staff habits built around it.

Aetion POS is being designed to avoid that. Selling, the part every business shares, lives in a common core. Anything specific to a trade is meant to be added as a module, so the system can change one piece at a time.

What the architecture is intended to do

  • Add functionality without replacing the core system.
  • Keep one catalogue and one sales history as requirements change.
  • Let different kinds of business run on the same foundation.

What has been demonstrated so far

Aetion POS has not been released or run in a live business. The points above are design goals, not measured results. This page will change as that does.

What Aetion POS is being built to do

Nothing here is available to buy or install yet. Each capability is marked by how far along it is, so you can tell current work from plans.

  • Point-of-sale workflows

    Ring up a sale from start to finish: pick items, build a cart, apply discounts and tax, and take payment.

    In development
  • Modular architecture

    Functions such as inventory or customer records sit in separate modules around a shared core, instead of one tightly coupled application.

    In development
  • Plugin-based extensibility

    A plugin system for adding functionality without modifying the core. There is no plugin marketplace or third-party publishing today.

    Planned
  • Configurable business workflows

    Adjust how a sale runs, such as which steps appear and in what order, to match how a business operates.

    Planned
  • Integration capabilities

    Connection points for payment, accounting and other outside systems. No integrations have been built yet.

    Planned
  • An architecture that can evolve

    Clear boundaries between the core and its modules, so one part can be changed or replaced without rewriting the rest.

    Design principle

One core, extended in layers

The intended architecture has three layers. Each one builds on the layer before it, and a business would only add the parts it needs.

  1. Layer 1

    Core POS

    The selling functions every business shares.

    • Catalogue
    • Cart
    • Pricing and tax
    • Payment
    • Receipts
  2. Layer 2

    Business modules

    Optional functions that many kinds of business have in common.

    • Inventory
    • Customers
    • Staff and roles
    • Reporting
    • Promotions
  3. Layer 3

    Industry-specific extensions

    Workflows that belong to one trade.

    • Retail

      Product sales and inventory-related workflows.
    • Restaurants

      Order and table-related workflows.
    • Pharmacies

      Specialised product and sales workflows.
    • Salons

      Service-oriented sales workflows.
Conceptual diagram of the proposed architecture. The modules and extensions named here are examples of what it could support, not a list of plugins that exist today.

One account for every branch

The owner would see every branch in one place and decide who can do what. Each branch manager would do the same for their own team.

Planned Not available yet. The pictures below show how it is meant to work.

What a business owner could do

  • Add branches and watch how each one is doing.
  • Set each branch manager's role and permissions.
  • Approve or decline requests from managers.
  • Manage the Aetion POS subscription for the business.

What a branch manager could do

  • Set roles and permissions for their own employees.
  • Approve or decline requests from their team.
  • Pass bigger decisions up to the owner.

Business ownerSees and manages every branch

  • City centre

    • Branch manager
    • 3 cashiers
    • 1 stock clerk

    Waiting for managerA cashier asked to refund a sale above their limit.

  • Riverside

    • Branch manager
    • 2 cashiers
    • 1 supervisor

    Waiting for ownerThe manager asked to change a product price.

  • Station road

    • Branch manager
    • 2 cashiers

    No requests waiting.

Example of a business with three branches. Requests go one level up: employees ask their manager, and managers ask the owner. Branch names, roles and requests are made up for illustration.

Design your own printed invoice

You would choose what appears on the invoice or receipt and see the result before anything is printed. Try the options below.

Paper
Show on the invoice
Colour

Your business name

12 Example Street, Your City

Invoice 0001City centre branch

  • 2 × Cotton tote18.00
  • 1 × Notebook A56.50
  • 1 × Ceramic mug12.00
Subtotal36.50
Tax 5%1.83
Total38.33

Thank you for your visit.

The preview changes as you pick options.

Illustration of the planned invoice designer, not the working feature. The options shown are examples.

Who Aetion POS is intended for

These are the kinds of business the platform is being designed around. None of them has a finished, production-ready version yet.

  • Retail and grocery

    Barcode-led product sales, stock levels and frequent price changes.

  • Restaurants and cafés

    Orders tied to a table or ticket, item modifiers and kitchen handoff.

  • Pharmacies

    Regulated products, batch and expiry details, and prescription-linked sales.

  • Hospitality

    Charges posted to a room or a stay, across more than one outlet.

  • Salons and personal services

    Services sold by time and staff member, alongside retail products.

  • Other businesses

    Any business that takes payment at a counter and has its own way of working.

About Aetion

Aetion POS is a product of Aetion Solutions. It is being developed around a simple idea: businesses should be able to extend their point-of-sale software as their needs evolve.

By combining a common foundation with a modular approach, Aetion aims to provide a flexible platform for different business workflows. The project is at an early stage, and this site describes where it is heading as well as where it stands.

Product
Aetion POS
Company
Aetion Solutions
Availability
Not yet released
Contact
obaydul@aetion.space
  • Adaptability

    Businesses change what they sell and how they sell it. Their software should accommodate that without a migration project.

  • Extensibility

    New capabilities should be added alongside the core, through defined extension points, not by editing it.

  • Maintainability

    Keeping each function in its own module is meant to keep the software organised as it grows.

Get in touch

Email is the way to reach Aetion. Tell us what kind of business you run and what your current POS doesn't handle well.

Email obaydul@aetion.space

Aetion POS

Product
Aetion POS

There is no contact form. Your message opens in your own email app.