Building the whole commerce loop, from catalogue to delivery.
A live side/freelance project built end to end, with AI assistance—from the storefront to payment and fulfilment workflows.
01 / Context
The problem
around the work.
Built a full-stack commerce platform covering catalogue, product variants, stock, checkout, payments, and order management. I owned the project myself, using AI assistance to move quickly through implementation and iteration.
What made it interesting
A storefront is only one part of a commerce system. Gateway callbacks, payment checks, fulfilment retries, and cached catalogue data all need consistent behaviour when users refresh, services fail, or events arrive more than once.
02 / Decisions & approach
How the work
took shape.
Make payment verification authoritative
Payment reconciliation runs through server-side logic. A gateway completion must match the stored amount; a recorded paid status is not overwritten by subsequent checks.
Keep payment and fulfilment separate
Shipment booking is its own workflow. It requires confirmed payment, claims an order before booking, and records failures for retry without undoing payment success.
Build beyond the happy path
The project includes storefront caching, an administration area, inventory and variants, map-based address selection, and customer tracking. The stack combines React/TypeScript, Supabase/Postgres, Cloudflare R2, and external APIs.
if (order.payment_status === "paid") {
return {
paymentStatus: "paid",
state: "COMPLETED",
changed: false
};
}A recorded payment success is treated as a terminal state. Re-checking it does not change it.
03 / Outcome & evidence
What came
out of it.
The site is live. I built the product end to end, including the operational flows behind checkout: verifying payments, booking shipments, managing stock, and helping customers track their orders.
The project code covers payment reconciliation, shipment booking, storefront caching, product administration, checkout, and tracking. The storefront artwork and reconciliation excerpt shown here come from that implementation. Customer volume and commercial results are not claimed.
04 / Reflection
What stays
with me.
My main lessons were in system design, caching, shipping quickly, and taking responsibility for the complete experience rather than stopping at the visible interface.
About the source material
Supplied Shubh Bazaar repository, Product résumé, and direct project clarification. The implementation has been inspected as an artifact, not audited as a live payment system.