Case studies
Logistics & Warehousing · Japan
B2B Warehouse & Order Management System (Phase 1)
NTQ developed B2B Phase 1 for Commerce Robotics – product master, inbound/outbound instructions, allocation and inventory adjustment – while standardising supply chain business documentation to reduce errors during maintenance.
PythonFastAPIPHPCodeIgniter 3JavaScriptNext.jsMySQLNginxAWSGitLab
Project overview
- Client: Commerce Robotics – a supply chain company providing E-commerce / Order Management / Automation solutions
- Country: Japan
- Industry: Supply chain
- Scale: 27.75 MM, 01/08/2025 ~ 16/12/2025, team of 7
- Project type: Development (B2B Phase 1)
- Scope of work: Coding, UT, IT, UAT
Problem / Challenges
- The client's needs: reduce order processing time, reduce manual operational errors, increase the rate of on-time order processing, expand sales across multiple EC channels and ensure security/audit compliance.
- The system was mainly in the maintenance phase with many existing business processes, making it hard to grasp the full processing flow.
- Supply chain operations are complex and demand deep domain knowledge, while the team had limited domain experience.
- An incomplete understanding of the business led to errors during maintenance; the growing number of bugs affected system performance and stability.
Solution
- Stepped up sharing of supply chain domain knowledge within the team.
- Standardised business documentation and system processing flows.
- Applied thorough review and checking processes before release.
- Prioritised quality improvements in critical maintenance areas, gradually increasing stability and reliability.
- Rebuilt architecture: Next.js frontend, PHP (CodeIgniter 3.x) and Python (FastAPI) backend, cron jobs, MySQL; connected to the OMS and WMS modules.
Key features
- Product master
- Inbound instructions
- Permissions
- Outbound instructions and batch outbound instructions
- Inventory adjustment
- Delivery route master
- Pre-allocation / allocation
- Double transaction
Technology
- Languages: Python, PHP, JavaScript
- Framework/Platform: CodeIgniter 3.x, FastAPI, Next.js
- Database: MySQL
- Middleware: Nginx
- Tools: PhpStorm, Visual Studio Code, AWS
- Integration: GitLab
Results
- Errors arising during maintenance were handled and fixed according to priority.
- The team built up supply chain business knowledge through bug fixing; their understanding of the system and business improved over time.
Lessons learned
- A clear understanding of supply chain operations is key to reducing errors during maintenance.
- Domain knowledge training and sharing should start early for new resources.
- Business documentation and processing flows must be continuously updated and standardised.
- Review requirements and system impact carefully before fixing bugs to limit new errors.
- Quality in the maintenance phase depends heavily on process and domain experience.
Have a similar project?
Contact SSD