The engagement began with consultation and expanded into scanner tooling, return-sync middleware, subscription advice, and warehouse planning.
Hardware sales, recurring service, fulfillment, and returns crossed several systems, with different teams responsible for different parts.
I built the scanner extension and return-sync middleware. For subscriptions, I investigated Recharge and advised the client after an initial custom-app proposal. I did not build the activation or billing automation.
- 01Operational requirements
- 02Implementation or advice
- 03Clear ownership
This overview shows the concerns involved; the account below distinguishes delivered work from plans.
Clear ownership mattered as the engagement expanded. Advice, delivered software, and future plans should not be presented as one completed system.
Recharge was consultation
The proposed architecture separated the physical device from the recurring service and described activation-based billing deferral. My contribution was investigating capabilities and explaining options, not deploying the billing workflow.
Warehouse planning
I prepared architecture for a dedicated fulfillment application. The plan is being processed internally and awaits approval; implementation has not started.
Work outside my role
A Salesforce migration was shared as project context. I had no involvement in it and do not claim it as a contribution.