Regional Card Distribution Ledger

Problem

Distribution still lived in spreadsheets and counter books. Resellers could not see stock, sales, and billing as one record. A desktop tool that ignored the intranet, or a web tool that ignored the desk, would leave half the operation on paper.

Constraints

The system had to run inside a reseller intranet, not on the public internet. Desktop and web had to share a model. Billing and stock had to stay consistent when two clerks acted at once. This write-up does not describe the carrier, the denomination catalog, or any production records.

Architecture

A single domain model covered cards, resellers, sales, and billing. MongoDB stored the documents. An Electron shell wrapped the same UI used in the browser so a desk without a reliable browser still had the ledger. The web deploy sat on the intranet; authentication stayed inside that boundary. Tests ran against the reseller environment rather than against a fictional public staging site.

Role

I designed the domain model, shipped the UI, and owned sales and billing flows. I packaged Electron and the web deploy so the intranet and the desk ran the same ledger.

Outcomes

• Stock, sales, and billing sat in one record instead of in separate books.
• Desktop and web clients shared the model, so a clerk's desk and a browser did not diverge.
• The deploy stayed on the intranet; the ledger did not need a public surface.

Stack