Three refund flows
Full, partial and general refunds — three separate branches of state, money and documents. They are easy to confuse at the UI level, so each flow walks the user down its own route with its own checks and confirmations.
case study · B2B · corporate travel
Sapar — a corporate travel platform
A B2B platform for corporate travel: a company books trips for employees, approves them, and handles documents and refunds. Remix + React.
RemixReactSCSSPostCSS
The task
Companies send employees on business trips: booking, approvals, reporting. The platform needed a personal dashboard, company and employee management, a catalog, cart, chat, news, notifications, documents and a security section.
The stack was set by the client: Remix + React, styles in SCSS with a PostCSS pipeline.
What was hard
Many screens without sprawl
On a platform with lots of screens, consistency is the cheapest thing to lose. Shared Remix layout routes, reusable forms and a single SCSS pipeline kept the platform whole: a new screen is assembled from existing parts.
A foreign ecosystem
The primary background is Vue. Here — Remix with its data loaders and nested routes: data loads on the route, not in the component. The framework thinks differently, and that thinking had to be adopted, not overridden by habit.
What was done
- Dashboard, company, employees, catalog, cart
- Chat, news, notifications, documents, security section
- Three refund flows: full, partial, general
- SCSS with a PostCSS pipeline
The result
The platform covers the full business-trip cycle — from picking in the catalog to getting money back.
A similar task?
A B2B platform, many screens, complex flows — let’s talk.