Skip to content
B2B Commerce Let’s talk
B2B Commerce

Bitcom E-Commerce

B2B wholesale store on Next.js and Stripe: tiered pricing per account, bulk order pads, and a checkout that mirrors how trade buyers actually order.

Next.jsPostgreSQLStripe
Bitcom E-Commerce — B2B Commerce case study by Chetan Sharma
Client
Bitcom
Year
2025
Role
Full-stack development
Type
Web App
The brief

What needed solving

Wholesale is not retail. Prices depend on the account, the quantity and the season; orders arrive as phone calls and PDFs; and stock is only accurate when someone remembers to update it. The catalogue had to stop pretending it was a shop.

Approach

How it was built

(01)

Pricing resolved server-side per authenticated account, so a trade price can never be read from a client bundle or cached publicly.

(02)

Bulk order pad — paste a list of SKUs and quantities, see totals and availability immediately — because that is how buyers already work in a spreadsheet.

(03)

Minimum order values, slabs and credit terms kept as data, editable by the sales team.

(04)

Stripe for payment, with an invoice-first path for accounts buying on credit.

Outcome

What changed

Orders land structured, priced and payable. The sales team quotes from the same numbers the buyer sees, and the end-of-month reconciliation stops being a phone call.

PricingPer-account, resolved on the server
OrderingSKU list paste with live totals
PaymentsCard and credit terms in one checkout
Account and price-tier modelNext.js storefront with bulk order padStripe integration and invoicingAdmin tools for terms and slabsOrder export for accounting
Process

The same six stages,
every project

(01)

Discovery

Clarify the goal, users, constraints, current systems, success measures, and delivery risks.

(02)

Architecture

Choose the right structure, integrations, data model, security boundaries, and technology stack.

(03)

Design

Map important journeys and responsive states before expensive decisions are locked in.

(04)

Development

Build in reviewable milestones with clean code, documented decisions, and visible progress.

(05)

Testing & Launch

Validate functionality, performance, accessibility, security, and production readiness.

(06)

Support & Improvement

Monitor real use, resolve issues, and prioritize improvements using evidence.

Have something similar in mind?

Tell me the outcome you need and the deadline you are working to. I will tell you honestly what is possible.