Case study · Commerce & operations
Connecting online ordering to the operation behind it
Ecommerce engineering across storefront, inventory, supplier purchasing, delivery scheduling, CRM, marketing automation and cloud infrastructure.
- Engagement
- Chief Technology Officer
- Scale
- Platform serving 30k+ monthly active users
- Team
- 4 teams / 16 engineers across Australia, the UK, India and the Philippines
- Integrations
- Payments, Xero, route planning, CRM
- Infrastructure
- On-premises to Google Cloud
The problem
For an operational ecommerce business, the storefront is only the start. Orders have to remain connected to perishable stock, supplier purchasing, warehouse processes, delivery scheduling, finance, customer service and downstream communications. Fragmentation between these systems creates manual work and operational risk.
Work delivered
- A multi-tenant store platform on Rails, Hotwire and PostgreSQL, with P&L ownership across engineering, product, design, infrastructure and operations.
- Payments integrated into the ordering flow.
- Supplier ordering integrated with Xero, and stock management.
- Perishable stock management.
- Route-planning API integration for delivery scheduling.
- CRM and customer-service workflow integration.
- Customer-data and marketing-automation integrations.
- Migration of the database and infrastructure from on-premises MySQL to Google Cloud.
From order to fulfilment
- OrderStorefront and payment.
- StockAvailability checked against perishable inventory.
- Supplier purchasingPurchase orders raised and reconciled with finance.
- DeliveryScheduling and route planning.
- CustomerService workflow and communications.
Outcome
The work connected customer-facing commerce to the operational systems that actually fulfil the order, while improving the platform’s scalability and resilience.
What this demonstrates
Have an important software problem?
Tell us what you are trying to build, improve or untangle. You will speak directly with a senior engineer — no sales handoff.