Anonymised by industry. The client’s identity is withheld pending consent; the engagement shape, integration scope, and capability claims are accurate.
Industry shape
Mid-market distributor selling consumer electronics into Australian and ANZ markets via marketplace channels (Amazon, eBay) plus direct B2B. Three-warehouse zone structure. Existing finance system on Xero. Growing dispatch volumes outstripping the spreadsheet-and-marketplace-exports operating model.
What the platform replaced
- Manual marketplace order exports (Amazon Seller Central, eBay seller dashboards) → CSV imports into a dispatch spreadsheet → manual Xero invoice entry
- Standalone shipping label generation (Easyship, Starshipit) requiring re-keying of orders
- Spreadsheet-based warehouse zone allocation
- Email-based customer warranty enquiries (no portal, no traceability)
What XCentral delivered
- Xero OAuth integration with read-write reconciliation
- Multi-marketplace order ingestion (Amazon + eBay) with rate-limited polling and idempotent processing
- Zone-based warehouse model with pick-pack-dispatch workflow
- Native Easyship + Starshipit shipping integration with auto-label generation
- Customer warranty portal (separate Vite app, separate App Service deployment, separate Entra ID app registration — the framework’s multi-portal separation pattern, in production)
- Pricing agreements module supporting per-customer per-SKU pricing
- Stock takes module with variance reconciliation
Velocity
- A focused sprint window delivered substantial new feature scope — Xero OAuth, multi-marketplace ingestion, dispatch routing, warranty portal — alongside the standing Phase 1 module set
- Estimation variance on completed work packages: single-digit percentage
- Delivered iteratively — new capability shipped continuously, not in a single big-bang release
Hours comparison
XCentral Phase 1 + warranty portal extension delivered framework-and-AI-assisted in a focused multi-week window. An equivalent traditional agency build (TypeScript + React + .NET + Azure stack, hand-written DTOs, manual integration plumbing, traditional QA process) would take several times longer.
Compression: 3.5–5×.
The framework absorbs the architecture decisions, the integration patterns, the test scaffolding, the deployment plumbing — every line of code that isn’t this business’s specific operation.
Proof beat
Integration depth.
Four distinct external systems (Xero + Amazon + eBay + shipping providers) plus a customer-facing portal, all running through a single coherent platform on day one of Phase 1 production.