Designing .NET 8 APIs for Fashion Rental Inventory LifecyclesDesigning .NET 8 APIs for Fashion Rental Inventory Lifecycles
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Syed Muhammad's avatar
Syed Muhammad Ali
pro
• Oct 26
A rental business is really an inventory problem wearing a fashion brand.
When I worked on the backend for FashionPass (https://fashionpass.com), a clothing rental platform, the storefront was the easy part. The real work sat behind every item: a member subscribes, picks a piece, it ships, gets worn, comes back, and has to show up as rentable again.
Every one of those steps touches accounts, billing, inventory and shipping at the same time. If one drifts, a member gets charged for something that isn't available, or a returned item quietly disappears from the catalog.
On the .NET 8 API we treated each of those as its own area: accounts and auth (JWT/OAuth2), membership and billing, catalog and inventory, shipping and returns. Integration tests and API docs meant the React frontend could move without waiting on the backend.
The lesson I'd pass to any founder building subscriptions around physical goods: map the full lifecycle of one item on paper before you design a single screen. The UI is easy to change later. A broken lifecycle shows up as refunds and angry support tickets.
If you run a subscription product, which part breaks first for you: billing, inventory, or returns?
saas.NETBackend Development
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started