Local commerce marketplace
A local marketplace where a listing becomes a reservation, a payment, and a QR-confirmed pickup. Live in Edmonton and Calgary.
CrowHub connects local buyers and sellers through listings, reservations, card payments, messaging, and QR-based pickup confirmation. Sellers get AI-written listings from photos, a store page, pickup windows, and subscription plans. Buyers reserve an item, pay online or at the door, and scan to confirm the handoff. I designed it, built it, shipped it, and run it.
Founder, product, and engineering. I took CrowHub from solution design through implementation, testing, deployment, and ongoing operation. I used coding agents extensively for implementation and tests, and personally owned the architecture, the security review, production behaviour, and every release decision.
Local commerce needs more than a product catalogue. A reservation has to hold inventory for a limited window, payment has to reconcile with the provider, and pickup has to give both parties a clear, verifiable outcome. Most local marketplaces stop at the listing and leave the hard part to a text thread.
A Next.js storefront backed by a separate .NET 10 API with explicit order state transitions, PostgreSQL persistence, Stripe Connect payment orchestration for sellers, and QR-token pickup confirmation. Hosted background services handle reservation expiry, reminders, notifications, and AI listing analysis outside the request path.
The Next.js storefront calls a separate .NET API. Marketplace transitions and payment rules live in the backend, and the interface can evolve independently. The cost is a second deployment boundary to operate, which I accepted for the clarity it buys.
The webhook handler verifies Stripe signatures before processing anything. Event claiming and duplicate handling are explicit, and every payment event reconciles provider state with local order state rather than assuming they agree.
The expiry sweeper cancels outstanding payment intents before releasing inventory, and skips orders whose payments already succeeded or cannot be safely resolved. Expiry and payment race each other, and the sweeper is written to lose that race safely.
.NET hosted services handle reservation expiry, payment-method expiry, notifications, and listing analysis with cancellation-aware processing, so interactive requests stay fast and background failures are isolated.
Seller registration, image uploads, AI-assisted listing generation from photos, store pages, and tiered subscription plans.
Time-boxed inventory reservations, Stripe payment flows with connected seller accounts, pay-online or pay-at-pickup, and signed webhook handling.
A QR token ties the digital order to the physical handoff. The seller scans, the card is charged, and both sides see the outcome.
Buyer-seller conversations, notifications, admin endpoints, and cleanup services that keep inventory and orders consistent.
The source repository is private. Happy to walk through the code in an interview.
Let’s connect
I’m looking for an Engineering Manager role where I can grow a team, own delivery, and keep a platform reliable while it changes.
Calgary, Alberta · Remote across Canada