A warehouse management system is the system of record for where inventory sits and which floor task should run next. It is not a shipping website and it is not an ERP by itself. Sigi’s named warehouse proof is 3DLogistiX, a multi-tenant SaaS WMS. Sigi engineers were embedded in that product team — staff augmentation, not a turnkey hand-off — and worked on core warehouse modules, the Flutter handset app, and admin dashboards. Commercial WMS work from Sigi lives on the logistics industry page and the warehouse management solution page.
What a WMS has to get right
On 3DLogistiX, four problems shaped the product. They are the same problems any operator hits when location codes live in a spreadsheet and the dashboard describes the floor as it was hours ago.
- Location-level accuracy across facilities: stock tracked to the exact rack and bin, because one bad put-away poisons picks and replenishment.
- Floor execution lag: paper pick lists and end-of-shift entry mean managers see yesterday’s warehouse.
- Legibility: rows of location codes do not show which zones are full, where pickers bunch up, or which aisle holds a delayed order.
- Tenancy: each customer needs isolated data, roles, and facility layouts on shared infrastructure — not a dedicated stack per site.
The surfaces to plan before writing code
A WMS is several products over one inventory model. 3DLogistiX splits into a React and Next.js web app for managers, a Three.js 2D/3D visualization of the same layout, a Flutter app for floor staff on iOS and Android, and tenant-admin dashboards for provisioning, roles, and reporting.
Web platform for managers and supervisors
- Multi-facility inventory searchable by SKU, location, or order, with quantities at rack and bin.
- Inbound receiving against expected deliveries, put-away tasks, and exceptions for short or damaged goods.
- Outbound release, pick tasks, packing confirmation, and dispatch — with an order hub that consolidates ecommerce, B2B, and wholesale channels.
- Task assignment so supervisors give picks, put-aways, and counts to named workers and watch progress live.
2D and 3D warehouse visualization
3DLogistiX’s selling point is a navigable digital twin: a 2D plan of zones and aisles, plus a 3D walk-through with bins colored by fill level. Stock movements arriving over WebSockets update the scene in the same session as a floor scan. The Three.js layer instances rack and bin geometry rather than one mesh per location, and paints inventory onto that static geometry so scene cost grows with distinct shapes, not bin count. Incoming updates batch into animation frames. The lighter 2D plan stays the default on modest laptops.
Flutter scanning app for the floor
3DLogistiX Mobile is published on the App Store and Google Play under the 3DLogistiX Pty Ltd account; the iOS listing has been live since May 2025. A single Flutter codebase covers receiving, put-away, picking, packing, and cycle counts — camera or handheld scanner — with guided task lists and instant writes back to dashboards and the 3D view. That cross-platform choice is the same pattern discussed in Flutter versus React Native.
Architecture that held up on 3DLogistiX
Under the four surfaces sit Node.js microservices, MongoDB as the primary store, Redis for hot quantity and task state, and WebSockets to browsers and handsets. The stack runs on AWS and is provisioned with CDK. Sigi does not invent Saturday-night infrastructure stories around this build — the notes below are the design decisions already documented in the case study.
- Services split by warehouse domain (inventory, inbound/outbound, tasks, facility layout, tenancy/auth). SQS and SNS carry events: a handset scan becomes a stock-movement that dashboards, the 3D view, and replenishment consume independently.
- Document storage for nested layouts and per-tenant configuration in MongoDB; Redis holds frequently read current-quantity and task-state data.
- Serverless at the edges — API Gateway and Lambda for spiky integration and webhook traffic; S3 and CloudFront for the web bundle and facility models; Amplify for the front end. WebSocket fan-out stays on persistent services.
Integrations and how the platform is run
Around those surfaces, 3DLogistiX integrates through an API-first layer: Shopify, WooCommerce, Magento, Amazon, and eBay for orders; Xero, MYOB, QuickBooks, and NetSuite for accounting; Starshipit, ShipStation, Shippit, MachShip, and SmartFreight for carriers; Stripe for subscription billing; and hardware scanners on the floor. The Shopify connector shipped as a dedicated Shopify App Store listing in July 2025. GitHub Actions builds and Playwright end-to-end tests run on every merge. Infrastructure changes go through CDK.
3DLogistiX sells on three published tiers (Starter, Growth, and Scale, listed from US$350 a month on the Shopify App Store) and offers a 14-day trial from its website. Those are the product’s published commercial facts — not Sigi delivery-fee figures.
A build sequence that matches how warehouses actually work
- Model locations and tenancy first: facilities, racks, bins, roles, and the tenant identifier on every record.
- Implement inbound and inventory accuracy before a pretty dashboard. If receiving and put-away are wrong, every pick is wrong.
- Add outbound (release, pick, pack, dispatch) against the same location model.
- Ship the scanning app so the floor writes the same events the web app reads.
- Layer visualization and channel integrations once the stock-movement event is trustworthy.
Related Sigi reading
The full architecture write-up is the 3DLogistiX warehouse platform case study. For last-mile rather than storage, see Antrak and Bix on the logistics practice. If the product is a two-sided shop network instead of a WMS, read how to build a multi-vendor marketplace. Mobile stack choice is covered in Flutter versus React Native. To scope a WMS commercially, start on warehouse management software or contact Sigi.