E-commerceLive2026
Commerce Suite
Catalogue, orders, membership and supplier settlement in one system.
The problem
A seven-thousand-line catalogue cannot be run from a spreadsheet. Stock arrives from several suppliers at different landed costs. Every line carries its own state: on sale, sold out, hidden, awaiting approval. Every order carries payment, delivery and member points. With those four sets of data in four places, margin per line cannot be calculated.
The solution
Catalogue, orders, members and supplier settlement share one system. Product state filters from the top of the table. An order keeps its payment state and its fulfilment state separately. A member record links to the signup path, the membership window and the orders behind it.
The screens
- 01Seven thousand lines, filtered by state and supplier
- 02Orders carrying payment and fulfilment state separately
- 03Members: membership window, signup path and order count
Key features
Catalogue at scale
Seven thousand lines, filtered by supplier, category, stock and registration date.
Payment and fulfilment split
Two independent states, so an order that is paid but not yet shipped stays visible.
Supplier settlement
Landed cost and settlement cost per line, kept apart from the sale price.
Membership and points
Membership window, points balance, signup path and marketing consent.
Bulk in, bulk out
Bulk upload and Excel export for both the catalogue and the member list.
Stack & numbers
- 7.057
- Products in catalogue
- 3.058
- On sale
- Medusa
- Next.js
- PostgreSQL
- Redis
- TossPayments
- AWS