The organisation needed one commerce marketplace for buyers, vendors, and marketplace operations. The existing journey divided vendor onboarding, product catalogues, variants, pricing, search, carts, checkout, payment, fulfilment, returns, and reporting between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
A complete commerce marketplace shaped around buyers, vendors, and marketplace operations
The organisation needed one commerce marketplace for buyers, vendors, and marketplace operations. The existing journey divided vendor onboarding, product catalogues, variants, pricing, search, carts, checkout, payment, fulfilment, returns, and reporting between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
Discovery followed the full journey from the first customer or staff action to its operational and commercial close. That exposed the handoffs between vendor marketplace, checkout, and fulfilment, including the exceptions that a feature list would have missed.
- Map the people, decisions, and records across the whole commerce marketplace.
- Separate firm ecommerce rules from habits created by the old tools.
- Agree what the first release must complete from end to end.
The product joined vendor marketplace, checkout, and fulfilment without blurring roles
Give vendors bounded ownership of products and orders while the marketplace remains authoritative for checkout, payment state, and customer policy.
In the commerce marketplace, each audience receives a focused home while the underlying state remains shared. The interface shows what needs attention, who owns the next action, and why work is blocked, while secondary detail stays available for review without crowding everyday tasks.
- Design the primary journey for every audience named in the brief.
- Give exceptions, corrections, and cancellations an explicit route.
- Use realistic records to test the complete flow before widening the surface area.
Angular, ASP.NET Core, PostgreSQL formed one supportable commerce marketplace
The architecture follows business ownership rather than the navigation menu. Angular, ASP.NET Core, PostgreSQL share versioned contracts, server-side permissions, observable integrations, and one authoritative record for the decisions behind checkout.
In the commerce marketplace, slower or external work runs through durable jobs with idempotent handling and visible failure states. Logs retain the organisation, actor, and product record needed to investigate a problem without guessing from a generic error message.
- Angular supports the primary product surface.
- ASP.NET Core owns a bounded part of the product journey.
- PostgreSQL keeps operational data and handoffs reviewable.
The release had to prove the whole commerce marketplace, not one polished screen
Buyers receive one coherent shopping experience and vendors can operate their part without sharing administration access. The release plan therefore followed representative work across every audience and the complete path through vendor marketplace, checkout, and fulfilment.
Acceptance for the commerce marketplace included ordinary work, missing inputs, repeated requests, failed integrations, permission boundaries, and the route back to a trustworthy state. The team checked whether staff could understand and recover from a problem without direct database help.
- Run the busiest realistic journey from start to operational close.
- Rehearse a failed integration and a repeated customer action.
- Confirm that every role sees only the work and data it owns.
- Trace a management result back to the records that produced it.
What the work established
Buyers receive one coherent shopping experience and vendors can operate their part without sharing administration access.
- 01
The commerce marketplace now gives buyers, vendors, and marketplace operations one shared operating record.
- 02
Vendor marketplace, checkout, and fulfilment follow the same product rules.
- 03
The system makes ownership and exceptions visible instead of hiding them in manual follow-up.
- 04
The product can grow from clear workflow, data, and service boundaries rather than isolated features.