A production-minded Windows application for a Tunis automotive-parts shop, covering stock, clients, suppliers, negotiated invoices, returns, reporting, backups, and multilingual delivery.
I designed and engineered Ben Mahmoud Stock as a professional offline desktop application for Etablissement Ben Mahmoud. Electron keeps the shop independent from internet availability, while a typed IPC boundary protects the React renderer from raw Node and filesystem access. SQLite migrations, integer-millime money, transactional invoice finalization, immutable sale snapshots, returns, audit history, PDF printing, backup and restore, and a French-first interface make the system practical for everyday counter work.
Client product for an automotive-parts shop02 /Product experience
What the product does.
01Counter Operations2 capabilities
Parts & Stock
References, OEM codes, compatibility, shelf locations, suppliers, prices, quantities, alerts, and movement history.
Negotiated Invoicing
Customer-specific unit prices, whole-invoice adjustments, drafts, automatic numbering, A4 preview, PDF export, and reprint.
02After-Sales2 capabilities
Returns & Exchanges
Partial or complete returns restore only the accepted items, preserve the reason, and can open a replacement invoice.
Audit History
Stock movements, invoice changes, cancellations, returns, and business events remain traceable locally.
03Business Control2 capabilities
Sales Reporting
Day, week, month, and year views report net sales, estimated margin, and best-selling parts after returns.
Exports & Backups
CSV stock exports and verified SQLite backups support everyday reporting and recoverable client delivery.
04Client Fit2 capabilities
Three Languages
A French-first interface switches to English or right-to-left Arabic without changing the underlying workflow.
Offline by Design
The shop can sell, print, report, and restore data without a remote API, subscription, or internet connection.
03 /System design
How the pieces connect.
System workflow
Offline stock-to-invoice system
Every counter action crosses a narrow desktop boundary before business services update the local ledger, historical invoice snapshot, and recovery layer.
Daily counter workflow
Shop operator
React workspaceStock, clients, suppliers, invoices, returns and reports
Typed request
Desktop boundary
Electron preloadNarrow, validated contextBridge API
Electron mainOwns Node, files, printing and business services
Transactional command
Local source of truth
SQLite databaseParts, people, movements, drafts and immutable invoices
PDF / printerA4 previews, exports and historical reprints
Verified backupsAutomatic, manual and USB-ready recovery copies
01A Protected Desktop Boundary
The React renderer never receives raw filesystem or Node.js access. A sandboxed preload exposes only typed business operations; the Electron main process validates each request and owns database, invoice, backup, export, and print services.
Renderer
Fast counter workflows and multilingual presentation.
Preload
A small contract surface instead of an unrestricted bridge.
Main process
Business rules, local persistence, files, and printing.
02Operational Context
The product was shaped around a real parts counter: stock must remain available when the internet is not, negotiated prices must be visible before validation, and the client must be able to back up data without technical help.
React workspaceStock, clients, suppliers, invoices, returns and reports