About the project
Pastelocity needed a business system connecting products, customers, orders, payments, receipts and daily administration. The public storefront was one part of that work; the operational context behind each order mattered just as much.
Axelyn’s role covered product development, backend services, integrations and web implementation.
The challenge
Products, customers, orders, payments, receipts and files had grown across separate manual processes. Each task could be completed, but reconstructing the context around an order made the business harder to operate.
The project began with the workflow rather than a list of pages. Relationships between customers, products, commercial values, payment state, receipts and the next operational action became explicit before they became interfaces.
Key engineering decisions
Make the order the shared operating context
- Approach
- Connect customer, product, payment and receipt information around the order.
- Why it matters
- The business can follow related information through one application foundation.
- Boundary
- The relationships must reflect how the business actually operates, beyond simply storing records.
Treat administration as part of the product
- Approach
- Support the owner’s work of reviewing orders, changing state, producing documents and deciding what needs attention.
- Why it matters
- The administrative workflow is as important to daily operations as the storefront.
- Boundary
- Customer-facing pages and administrative actions serve different tasks within the same system.
Connect the interface to the surrounding services
- Approach
- Bring application services, authentication, notifications, tasks, file storage and reporting into the operational workflow.
- Why it matters
- An order’s context extends beyond the screen where its details are displayed.
- Boundary
- Each supporting workflow needs an explicit place in the application scope.
How the system works
The order connects information that previously lived apart. Customers and products establish the commercial context; payment state, receipts and administrative actions carry the work forward.
- Customers & productsThe commercial context
- OrdersRelated information brought together
- PaymentsPayment state within the workflow
- ReceiptsDocuments linked to the order
- AdministrationReview, next actions and reporting
Implementation and reliability
Services behind the storefront
Django REST and later FastAPI services supported the application layer. React and TypeScript powered the interface. Authentication, notifications, task management, file storage and reporting formed the surrounding workflow.
Preserve context across operational steps
The administrative interface was where the owner reviewed work, changed state, produced documents and decided what needed attention. Connecting those actions to the same order context kept the underlying business relationships visible throughout the application.
The documented scope establishes the connected application workflow. This case does not claim a measured uptime improvement, error-rate reduction or revenue increase.
Results and lessons
One application foundation
Pastelocity created one application foundation for previously separate business processes. The result preserved the relationships the business already depended on and gave each part of the workflow a shared operating context.
What carried forward
Good business software makes the workflow clearer. For this project, that meant defining the relationships and operational actions before treating the work as a collection of pages or database tables.
