Retail POS & Customer Ledger/● Live Product / Pilot

BizimVeresiye

Offline-First Credit Ledger & Barcode POS for Small Retailers

Visit Product Websitebizimveresiye.com.tr
Platform
Windows 10/11
Offline Database
SQLite
Pilot Releases
58
Free Trial (Days)
30
01 // CONTEXT & PROBLEM

The Operational Problem

Context & Domain

In Turkey, small shops (bakkal, market, büfe, phone accessory shops) still extend credit to regular customers and track it in a paper notebook. Existing programs are either full ERP suites that are too heavy for a two-person shop, or cloud subscriptions that stop working when the shop's connection drops. Many of these shops also have years of balances in older desktop programs that they cannot afford to lose.

Overview

The ledger is money. A sale that lowers stock but not the cash register, a double-click that books a sale twice, or a return that refunds cash to a customer who actually owed money all turn into real disputes with real customers. And all of it has to work on an ordinary Windows PC behind the counter, with or without internet, operated by people who are not computer users.

02 // TOPOLOGY & ARCHITECTURE

System Architecture

BizimVeresiye is offline-first: the full product runs on a local SQLite database and never waits for the network. Every business operation (sale, credit sale, collection, return, stock count, cash movement) is a single EF Core transaction that writes the document, its stock, cash and ledger movements, an audit entry and a SyncOutbox event together. Money records are never deleted; cancels and returns write reverse movements. An optional cloud module reads from the outbox to share data between shop computers and show reports on a phone.

SYSTEM_DATA_FLOW_MAP
┌───────────────────────────────────────────────────────────────────────────┐
│ WPF DESKTOP  (.NET 8 · MVVM · keyboard-first POS)                         │
│ barcode queue · customer ledger · stock · cash shift · reports            │
└─────────────────────────────────────┬─────────────────────────────────────┘
                                      │ Application services (OperationResult)
                                      ▼
┌─────────────────────────────────────┴─────────────────────────────────────┐
│ ONE EF CORE TRANSACTION PER OPERATION  (SQLite, local)                    │
│ Sale + Items · Payment · StockMovement · CashMovement                     │
│ CustomerAccountMovement · AuditLog · SyncOutbox (Pending)                 │
│ LocalTransactionId unique index → retries never duplicate a sale          │
└─────────────────┬───────────────────────────────────────┬─────────────────┘
                  │ daily                                 │ HTTPS, when online
                  ▼                                       ▼
┌─────────────────┴─────────────────┐   ┌─────────────────┴─────────────────┐
│ LOCAL BACKUP                      │   │ CLOUD MODULE  (optional)          │
│ .bksbackup · SHA-256 · integrity  │   │ ASP.NET Core API · PostgreSQL     │
│ USB / OneDrive folder             │   │ shared data · phone reports       │
│ RestoreTool swaps DB atomically   │   │ hosted in Turkey                  │
└───────────────────────────────────┘   └───────────────────────────────────┘
Desktop (WPF)01

Keyboard-first POS and back-office screens; ViewModels talk only to application services and never touch the DbContext

WPFMVVM.NET 8
Application & Domain02

Sale completion, credit limits, collections, refund allocation, cash shift and stock count rules, all testable without UI or database

C#xUnit
Local Persistence03

Migration-based SQLite database with tenant, branch, register and device built in from day one, plus backup, restore and health checks

EF Core 8SQLitePBKDF2
Cloud & Delivery04

Optional sync API on PostgreSQL fed from the outbox, cloud backups, licence activation and signed over-the-air updates

ASP.NET CorePostgreSQLInno Setupnginx
03 // TRADEOFF ANALYSIS

Engineering Decisions

Offline-First, Cloud as an Add-On

Rationale

A shop cannot stop selling because the modem restarted, and many owners do not want their customers' debts on someone else's server.

Trade-offs Considered

Multi-computer use needs the cloud module and an outbox-based sync instead of a shared live database, but the core product works on day one with nothing but a Windows PC.

Append-Only Money, Balance Derived from Movements

Rationale

Shop owners settle disputes by going line by line through a customer's history; an edited or deleted line destroys that trust.

Trade-offs Considered

Sales, payments and ledger lines are never deleted; cancels and returns write reverse movements. A customer's balance must always equal the sum of their movements, and an integrity check flags any drift above 0.01 TL instead of silently fixing it.

Idempotency Keys on Every Write

Rationale

Double-clicks, frozen screens and retries are normal at a busy counter.

Trade-offs Considered

Every sale, collection, return and stock movement carries a LocalTransactionId with a unique index, so retrying the same operation returns the original result instead of booking it twice. It costs a column and an index per table.

04 // COMPLEXITY RESOLUTION

Technical Challenges & Solutions

Refunds on Credit Sales

A customer buys partly on credit and partly in cash, then returns some items. Refunding cash first would hand money to someone who still owes the shop.

↳ Engineered Solution

A refund allocation service applies a return to the credit portion first, then cash, then card, subtracting earlier refunds. Partial returns split line discounts proportionally, and a full return of the remaining quantity uses the exact remaining net amount, so rounding never leaves a stray kuruş on the ledger.

Updating Software on Shop PCs Nobody Maintains

Some updates were only partly applied because a DLL was still locked, and the shop owner is not going to repair an installation by hand.

↳ Engineered Solution

The updater takes a backup before every update, verifies the installer's SHA-256 and size from an HTTPS manifest, then runs it after the app closes. The installer uses Windows Restart Manager to close processes holding locked files, and the updater checks that target files are really free before installing.

05 // CODE & STACK

Technology Stack

Desktop
  • • WPF
  • • MVVM
  • • .NET 8
Data
  • • EF Core 8
  • • SQLite
  • • PostgreSQL
Cloud
  • • ASP.NET Core
  • • JWT
  • • nginx
  • • Ubuntu
Delivery
  • • Inno Setup
  • • OTA Updater
  • • GitHub Releases
Testing
  • • xUnit
  • • Integration tests

Key Implementation Highlights

  • Barcode scans go through a queue with a semaphore, so fast consecutive scans are never lost
  • Price and stock are re-read inside the sale transaction; a stale screen cannot sell at an old price
  • Credit limits with an approval step when a sale would push a customer over their limit
  • Backups are zip packages with a manifest, SHA-256 and SQLite integrity check; restore runs in a separate tool that swaps the database atomically
  • Import tooling to bring customer balances over from older programs, verified customer by customer
06 // PRODUCTION UI & SCREENSHOT EVIDENCE

Production Screenshots & System Interface

High-resolution interface evidence, operational telemetry cockpits, and field runtime screens.

https://bizimveresiye.com.tr
SYSTEM TOPOLOGY // OFFLINE-FIRST POS
BizimVeresiye: Offline-First Sale Path and Cloud Module
Click to inspect full resolution

BizimVeresiye: Offline-First Sale Path and Cloud Module

Every sale, payment, stock change, cash movement and credit entry is written in one local SQLite transaction. The cloud is optional and only ever reads from the outbox.

FIGURE 01
07 // VERIFICATION & RESULTS

Results & Current State

Live Product (1.0.0 pilot)

BizimVeresiye is publicly available at bizimveresiye.com.tr with a 30-day full-feature trial and a one-time licence per computer. Shops in the pilot receive updates over the air; 58 pilot releases have shipped so far.

↳ 58 pilot releases delivered through the OTA updater
↳ 600+ automated xUnit tests across domain, application and integration
↳ Runs fully offline; internet only for updates and the optional cloud module

Key Architectural Takeaways

  • 01.For a ledger product, data integrity is the feature: idempotency keys and append-only money records matter more than any screen.
  • 02.Offline-first is simpler to trust than sync-first; the cloud should add to a working product, not hold it up.
  • 03.On shop PCs nobody maintains, the updater is part of the product: a backup step and verified installers are what make frequent releases safe.