E-commerce & loyalty · Reorbit · loyalty platform (beta)

Reorbit — platform & Shopify-app engineering for a loyalty startup

Reorbit is a loyalty platform (in beta) I do platform and backend engineering for — a contract-first, service-based architecture with a Shopify app front end.

Published July 12, 2026

Platform eng
My role
backend services + Shopify app
Shopify app
Front end
React Router (embedded)
Contract-first
Boundaries
typed wire shapes (zod)

What it is

Reorbit is a loyalty platform, currently in beta. I do platform and backend engineering for it — the kind of e-commerce loyalty work that’s been my spike for years, applied to a clean, modern build.

What I build

  • A Shopify app as the merchant-facing surface, built on React Router and embedded in the Shopify admin.
  • A contract-first backend. The loyalty domain’s wire shapes are typed contracts that every service and client derives from — so a breaking change is a compile error, not a production incident.
  • Consistent service boundaries. Service-to-service communication follows one shared transport convention, so adding a service is routine rather than a fresh integration each time.

Status

Active engagement — the platform is in beta.

Frequently asked

What do you do on Reorbit?

Platform and backend engineering: the typed, service-based backend and the merchant-facing Shopify app, plus the conventions that keep them consistent as the platform grows.

What makes the architecture solid?

It’s contract-first — the loyalty domain’s wire shapes are defined once as typed contracts, and services and clients are typed from them, so boundaries can’t silently drift. Service-to-service calls follow one shared transport convention.

Services: E-commerce engineering, Platform & backend engineering

  • loyalty
  • shopify
  • react-router
  • typescript
  • microservices
  • zod

Want results like these for your team?

Get in touch