The encyclopedia · Engineering & Operations · Technical decision · 2016–2018
Nitori's logistics arm put 60 robots on a grid and quintupled shipping efficiency
Furniture giant split logistics into its own firm, robotized the warehouse, and turned shipping efficiency up fivefold.
Nitori Holdings · Home Logistics
the move
Nitori, Japan's biggest furniture-and-home-goods retailer, built its low-price promise on controlling the chain from factory to living room. Logistics was spun into its own company, Home Logistics, which handles customs clearance, warehousing and delivery — even taking on outside clients once the network matured.
In February 2016, the e-commerce shipping center installed AutoStore: a grid of stacked bins with 60 robots scurrying across the top, lifting and stacking containers and keeping fast movers on upper levels. Within about a month, shipping efficiency improved 3.75 times; continued tuning pushed it to roughly five times, and ergonomic picking stations let older and less physically strong workers handle the work.
The Toyo Keizai report frames the move as a management fix: logistics is the hidden cost of 'prices lower than expected,' and Nitori's answer was to make logistics a separate business with its own P&L, robots and external sales — a logistics platform that even competes with specialist firms.
why it works
- In-house customs cuts cost and time on every import.
- A dedicated P&L forces logistics to earn its keep.
- Robots solve both efficiency and the labor shortage.
- External sales turn a cost center into a revenue line.
what transfers
When logistics is your cost base, internalize it first: owning customs, warehouses and delivery cuts handoffs, then pays for robots from the savings.
what came after
Home Logistics kept rolling out automation and expanded its third-party platform business, while Nitori continued its manufacturing-logistics-IT retailer model with overseas factories feeding its own network; the AutoStore approach became a reference case in Japanese logistics reporting.
references
spotted an error? The archive wants to know.