Beneath the interface
Under the hood
For those who want to know what is underneath: how PLAN keeps a sale safe when the internet or the power goes, how the books keep themselves, and how your data stays yours. The home page has the summary in a shop owner's words.
LOCAL FIRSTRuns on your machineTauri, Rust and SQLite — selling never waits for a server
ONE TRANSACTIONOne transactionInvoice, stock and ledger succeed together or are not written
SYNC QUEUEA sync queueWhat was cut off catches up when the internet returns
SIGNED UPDATESSigned updatesThe machine verifies the source before installing
Read the full engineering section
One heart, not programs side by side
Every movement knows where it belongs
A sale is not entered once at the till, again in stock and a third time by the accountant. PLAN performs the whole movement in a single transaction: either all of it succeeds, or none of it is written.
ResultOne movement · a complete trail
✓
Every area has a clear job
The details you notice after the first week
Speed matters at the till, but management needs depth. So the selling screen stays light, while the advanced tools sit in their own spaces, by role and permission.
Selling and pricingFrom the counter to the quote
- Barcode, weight and discount
- Returns linked to the original
- Quotations before the invoice
- Retail and wholesale price lists
- Time-limited promotions
Inventory and movementHow much you have, and where it went
- Stocktakes with a counted-versus-expected sheet
- Purchases and supplier returns
- Cartons and pieces on one item
- Low-stock alerts before you run out
- Item card with its full history
Money and booksWritten once, correct everywhere
- Automatic double entry
- Customer and supplier debt
- Cash count at the end of each shift
- Expenses with their accounts
- Statements and reports you can export
People and trustWho did what, and when
- Roles with precise permissions
- An audit trail on sensitive actions
- Manager approval where it is needed
- Fast user switching at the till
- Encrypted backup and restore
THE DETAILS OF A WORKING DAY
More than a “Sell” button.
From the first quotation to shift closing, the tools follow your business. Available modules depend on product, plan and permission.
Retail and wholesale
Multiple units, price lists, barcodes and quotations that convert into sales.
Debt and collection
Customer and supplier accounts, partial payments, collections and statements in POS.
Inventory in detail
Purchasing, batches and expiry, stocktakes, documented adjustments and branch transfers.
Restaurant operations
Recipes, ingredients, prep, waste, tables, kitchen and delivery with cost tied to operations.
Time is a product too
In Games: open or timed sessions, reservations, waiting lists, resources, rates and extras.
Every role in its place
Permissions, audit trails, preferences, help and backups: working tools, not decorations.
Security you can actually follow
Your data is a responsibility,
and it belongs to you
The licence is bound to the machine, backups can be encrypted, and an update is not accepted unless it is signed. And most of all: each employee sees and does only what they need, and every sensitive movement leaves a trail.
✓Encrypted backupsAnd the age of the last one is in front of the manager
✓Updates with a checked sourceThe machine verifies before it installs a new version
✓Precise permissionsSelling does not mean seeing cost, and managing does not mean erasing the trail
✓Full exportYour data is not locked inside the product or a cloud subscription
BENEATH THE INTERFACE
Composed outside.
Engineered within.
Engineering is not a list of logos. It is the decisions that preserve a sale, protect the books and make interruptions understandable. These examples describe the PLAN POS foundation.
LOCAL → TRANSACTION → SYNC
Interfaces evolve.
Transaction integrity stays.
Arabic interface ReactLocal runtime Tauri / RustGuarded storage SQLite
01 / LOCAL FIRSTSelling lives on your device
+
A Tauri and Rust desktop app with a local SQLite database. Core operations do not wait for a remote server.
TAURI 2 / RUST / SQLITE02 / ATOMIC WRITESOne transaction. No half-written operations.
+
The financial path executes its steps on one connection inside one transaction: commit together or roll back together.
BEGIN → COMMIT / ROLLBACK03 / DURABLE STORAGEDurable writes. Startup integrity checks.
+
SQLite WAL, FULL synchronization and foreign-key constraints, plus a startup integrity check. Storage safeguards do not replace backups.
WAL / FULL / FOREIGN KEYS04 / SYNC QUEUEAn interruption is not a restart.
+
Movements wait in a local outbox, retry and receive server acknowledgement. Synchronization needs connectivity; local selling does not.
OUTBOX / ACK / RETRY05 / DATA OWNERSHIPYour data is not subscription collateral.
+
Independent exports and AES-256-GCM backups when encryption is selected. Keep a copy off-device and retain its passphrase.
EXPORT / AES-256-GCM06 / VERIFIED UPDATESAn update proves its source first.
+
The app verifies an update-package signature before installation. Staff permissions, branch scopes and audit trails govern everyday operations.
SIGNED PACKAGES / RBACBased on source review on 26 September 2026. These safeguards do not mean failures are impossible or that all three products have identical capabilities.
See it in your shop
All of this, in a 90-day trial
We install remotely anywhere in Libya, and visit in Tripoli, Benghazi, Misrata and Zawiya. No down payment.