Marketplace settlement ledger

Trace seller balances through commissions, refunds, holds and simulated payouts.

Open the demo

Opens marketplace.taiphamsolutions.com in a new tab. No account, no signup, and nothing you do in it leaves your browser.

What it does

Trace seller balances through commissions, refunds, holds and simulated payouts.

Create a split order, advance the release clock, then simulate a payout failure and reconcile the ledger.

Create a split order, advance the release clock, then simulate a payout failure and reconcile the ledger.

Features

Seeded examples use English names. Switch between English and Vietnamese.

Balanced journal and seller statements

Create a split order, advance the release clock, then simulate a payout failure and reconcile the ledger.

Simulated roles

Switch roles to explore workflow permissions. This is not secure authentication.

The flow it closes, end to end

Every step below happens inside the demo. There is no point in it where the work leaves the browser and comes back.

  1. Try the workflow

    Create a split order, advance the release clock, then simulate a payout failure and reconcile the ledger.

  2. Inspect the result

    Reload the page to inspect the records saved in your browser.

What is real, and what is not

There is no server behind any of this, which decides both columns. The left one is what that constraint made worth building properly. The right one is what it rules out.

Actually handled

  • Balanced journal and seller statements
  • IndexedDB persistence

Deliberately not real

  • No backend, real accounts or cross-device synchronization.
  • Payments, tax and transfers are simulations. Do not use sensitive documents; local data is unencrypted and may be cleared by the browser.

How it is built

The write-up sells harder than the application does, so it is on the page rather than in a repository nobody can open.

Frontend
Preact + TypeScript
Storage
IndexedDB
Hosting
Cloudflare Workers

The services this is evidence for

A demo exists to prove something on the offer list rather than to be impressive on its own. These are the ones this one argues for.

Want the version of this with your rules in it?

This one was built to a constraint nobody would choose. Yours would have a server, real accounts, and the parts of the domain that are actually hard. Tell us what the software has to do and we will tell you what it takes.

Bring the messy version of the problem. That is the conversation we enjoy most.

Email us