Services

Four pillars of the same event-sourced stack.

Each of these is usually its own product at its own vendor, held together by imports, exports and a spreadsheet someone updates by hand. StreamBit designs and builds all four as one system, animated by the same event log.

01

A register app for the lane

Point-of-sale

A real register interface designed for the way clerks and customers actually move through a sale — not a checkout screen bolted onto inventory software. Cash, card, split tender, refunds, voids and the audit trail are first-class, not afterthoughts.

Deliverable — Lane register (iPad)

offline-mode checkout · multi-till audit trail · cash drawer / scanner drivers

02

Counts that reconcile to the event log

Inventory & receiving

Cycle counts, receiving scans, dock arrivals, transfers between locations and stock adjustments. Every change is recorded as an event, so the on-hand quantity at any point in time is derivable from the log — not overwritten when a count gets rerun.

Deliverable — Receiving + cycle-count app

barcode-driven scans · event-log on-hand derivation · location transfers

03

One source of truth for listings

Web & catalogue

The same product data that drives the register drives the public storefront, so prices, stock and descriptions stop drifting behind the till. Catalogue edits flow through the event log and reach the site without a separate, fragile sync job.

Deliverable — Storefront + catalogue editor

event-driven listings · stock pulled from the projection · zero nightly sync

04

Books that read off the same ledger

Back-office & books

Daily close, payouts, tax summaries and owner reports are projections of the same event log the till writes to — so close at the end of the day reconciles by construction, not by a manual spreadsheet at midnight.

Deliverable — Daily-close dashboard

till-driven payout report · tax summaries · owner KPI views off the same log

How they fit together

One event log, four projections on top of it.

The four pillars above are not four products bolted together. They are four different views of the same event log — the same source of truth a sale at the till writes to.

The point-of-sale is a write path into that log. Inventory is a stock-state projection. The web catalogue is a listing-state projection. Back-office is a money-state projection. They cannot drift, because there is no separate source to drift from.

An event-sourced backbone reads like your business actually runs. Any past day, any past sale, any past inventory snapshot can be replayed on demand to answer a question your old CSV export could not.

That is what holds the four pillars together — not glue, not a nightly job, not a spreadsheet someone updates by hand.

event_stream.live
tail -f
  1. t+1sSale posted
    Lane 2 · register/12 · $48.20
  2. t+2sInventory adjusted
    -2 · SKU 4418 · mugs
  3. t+3sWeb catalogue updated
    11 SKUs pulled forward
  4. t+4sReceiving dock scanned
    PO-1449 · supplier A · +96
  5. t+5sSale posted
    Online · order 8821 · $112.00
  6. t+6sBooks reconciled
    Daily close · 0 mismatches
unified · audit · replay{ events: 6, sources: 3 }

one email · one conversation · no obligation

Tell us which pillars are breaking up. We will bring the architect.

Start a conversation

Sean Zicari reads every message directly.