SimplesCTe
Freight tax document issuance in seconds for carriers and independent truckers.
- My role
- Front-end Developer
- Context
- SBSistemas · Smarten Venture Builder
- Category
- SaaS Product
Web and mobile platform for issuing freight tax documents. I worked on the product's front-end, focused on the issuance flow, the SEFAZ integration, and the mobile experience used by drivers on the road.
Results
- 15,000+
- active customers Carriers, independent truckers and accounting offices
- ~11s
- per document issued From the start of filling in to authorization
- 2 min
- average support time Public metric disclosed by the product
The problem
Carriers and independent truckers need to issue CT-e, MDF-e and CIOT documents to operate legally. The available options were the government portal — slow, unfriendly and full of re-typed fields — or management systems too heavy for a sole proprietor with one truck. The result was repeated manual data entry, filing mistakes, rejected documents and a truck stuck in the yard waiting for it all to get sorted out.
The solution
A product that resolves issuance in around eleven seconds: documents are pulled automatically from SEFAZ, the manifest route is suggested by the system, insurance endorsement happens through integration, and batch issuance covers anyone dispatching dozens of documents a day. On the front-end, the challenge was turning a huge tax form into a flow a driver can complete on their phone, standing next to the truck.
Key challenges
-
Reducing a tax form with dozens of required fields to a short flow, pre-filling as much as possible from data already returned by SEFAZ.
-
Guaranteeing a genuinely usable mobile experience out in the field — large touch targets, clear loading states and tolerance for an unstable connection.
-
Handling batch issuance without blocking the interface, with per-document feedback and recovery from partial failures.
-
Translating SEFAZ rejection messages — raw, barely descriptive codes — into guidance the end user can act on alone, without opening a support ticket.
Technologies used
- React
- TypeScript
- Next.js
- Vite
- Zustand
- TanStack Query
- React Hook Form
- Zod
- Styled Components
- Material UI
- Vitest
- Cypress
- Sentry
The context
Freight is an industry where downtime is a direct loss. Every minute a driver spends fighting a form is a minute the truck isn’t moving — and that completely shapes the product’s design priorities.
My role
I worked on the platform’s front-end, focused on the issuance flow and the mobile experience. It’s the project that taught me the most about the real cost of interface friction: here, one less step in the form isn’t a UX detail, it’s revenue for the client.