# Finqu Commerce

> Long-running full-stack work on the merchant-facing application of a multi-tenant ecommerce platform, across catalog, orders, customers, pricing, integrations, and background processing.

## The merchant-facing core

Finqu Commerce is the merchant-facing application used to run an online business. It brings together product and catalog work, inventory, pricing, orders, customers, discounts, sales channels, integrations, domains, and account-related workflows.

Over multiple generations of the application, I worked across its JavaScript and Vue frontend, PHP backend, APIs, data, integrations, and background processing. A lot of that work also crossed into the shared backend and domain services used by Commerce, APIs, and other parts of the platform.

## One product, several technical generations

The application carries established jQuery and Handlebars interfaces alongside newer Vue surfaces, all connected to a PHP application and shared services. Product work often means understanding which generation owns the behavior before deciding where a change belongs.

## Following a feature through the stack

1. **Merchant workflow**: Start with the operation the merchant needs to complete.
2. **Application logic**: Trace frontend state, validation, and PHP behavior.
3. **Domain and data**: Follow rules into shared services and SQL-backed persistence.
4. **External path**: Connect APIs, integrations, sales channels, or delivery work.
5. **Background work**: Move imports, exports, and other asynchronous tasks off the request path.

## Representative product areas

- Products, categories, variants, inventory, media, and pricing
- Orders, customers, discounts, and merchant workflows
- Apps, integrations, domains, and sales-channel configuration
- Imports, exports, scheduled processing, and integration delivery
- Frontend and backend evolution across JavaScript, Vue, PHP, and shared services

## Working safely in a mature product

Changes in a long-running commerce product rarely stay inside one file or service. The useful work is tracing the current promise across layers, preserving the rules that still matter, and testing the path merchants actually use.

## Technologies

- PHP
- JavaScript
- Vue
- jQuery
- Handlebars
- Webpack
- SQL-backed persistence
- APIs
- Background tasks