Case studies

Logistics & Warehousing · Japan

Maintenance of the WMS / OMS / Inspection App System Cluster

NTQ maintains and extends Commerce Robotics' (CMR Labo) WMS/XP, OMS and inspection app cluster in a multi-vendor environment; rewriting the slip printing function cut processing time by ~85%, meeting the client's target.

PythonFastAPIJavaScriptNext.jsMySQLMongoDBDockerAWSGitCursor

Project overview

  • Client: Commerce Robotics (CMR Labo)
  • Country: Japan
  • Industry: Logistics – warehouse and order management
  • Scale: 120.61 MM, 16 months (06/2024 ~ 09/2025), team grew from 2 → 10 people
  • Project type: Maintenance Service
  • Scope of work: Basic design, Coding, Integration Test

Problem / Challenges

  • When taking over the project, NTQ was responsible for only a small part of the CMR system cluster and did not yet understand the overall business flow, the system structure or the components developed by other vendors.
  • The system shares source code and APIs with the CMR cluster (partly NTQ, partly other vendors), so every enhancement request needed careful assessment and considerable optimisation effort.
  • The order slip printing function was slow; the client wanted to cut processing time by about 80–90%.

Solution

  • Internal brainstorming to define the business flow, followed by Q&A and illustrative mockups to reconfirm understanding with the client.
  • After updating the business flow, held joint meetings between vendors to ensure the business logic was correct and did not affect other vendors' components.
  • Performance improvement: rewrote the entire printing function, reduced the number of database queries and optimised SQL statements.

Key features

WMS / XP

  • Inventory, inbound and outbound management
  • Order sorting batches
  • Printing warehouse operation slips: invoices, waybills, combined slips, picking lists…

OMS

  • Product and order management
  • Creating inbound instructions
  • Robot-based standardisation of product and order data

Inspection app

  • Inspection for regular orders
  • Inspection for batch 1-1 orders

Technology

  • Languages: Python, JavaScript
  • Framework/Platform: FastAPI, Next.js
  • Database: MySQL, MongoDB
  • Tools: Cursor, Git, Docker, AWS
  • Integration: OMS (Order Management System), PMS (Print Management System)

Results

  • Clarified and standardised the overall business flow, giving NTQ and the other vendors a shared understanding of the system and reducing miscommunication.
  • Cross-vendor discussions detected and prevented potential logic conflicts early.
  • Order slip printing time was cut by about 85%, meeting the client's target; database load fell thanks to fewer queries and optimised SQL; performance remains stable even at high volumes.
  • The client reported smoother operations and faster order processing.

Lessons learned

  • When taking over a multi-vendor system, build an end-to-end system map and business flow from the outset.
  • Clear mechanisms are needed for sharing documentation and API specifications and for managing source control between vendors.
  • Before optimising performance, benchmark and analyse the root cause to avoid optimising in the wrong direction.
  • When refactoring code or queries, run regression tests to ensure other parts are not affected.
  • Communicate proactively and regularly with the client to confirm the real need (reducing user waiting time or reducing server CPU load).

Have a similar project?

Contact SSD