The most common pain point after buying AMRs or AGVs: robots run in silos and never really talk to the WMS. A WCS (Warehouse Control System) is the translation layer between WMS and hardware. This guide breaks down the three-layer architecture (WMS / WCS / equipment) and answers the question: "Does a mid-size warehouse actually need a WCS?"
The Three-Layer Architecture: WMS / WCS / Equipment
A complete automated warehouse runs on three layers. WMS (software decision layer) decides what should happen — e.g. "order A needs 3 units of product B picked." WCS (control layer) translates that into device commands — "dispatch AMR-007 to bin B-3 to pick." Equipment layer carries it out — the AMR actually drives over and picks. Three layers, three jobs, none skippable.
Why You Need a WCS
If a WMS talks directly to AMRs, three problems show up: (1) every AMR vendor exposes a different API, forcing the WMS to maintain a lot of integrations; (2) coordinating multiple AMRs (right-of-way, collision avoidance, charging schedules) gets complicated fast; (3) swapping AMR vendors means rewriting the WMS. A WCS is the translation layer — the WMS only talks to the WCS, and the WCS handles everything underneath.
When You Don't Need a WCS
(1) Only 1–2 AMRs — the simple control software from the equipment vendor is enough. (2) Single vendor, single model — no plans to switch. (3) Fully manual warehouse — with no automated equipment, a WCS has nothing to do. Once you cross 5 devices or mix models, a proper WCS starts paying for itself.
A Staged Path for Mid-Size Warehouses
We recommend a phased approach. Stage 1 (under 3 AMRs): WMS + the vendor's simple control software. Stage 2 (3–10 AMRs, mixed models): introduce a lightweight WCS (e.g. the cloud WCS from RobotShop or Locus). Stage 3 (10+ AMRs or a fully automated warehouse): a full WCS (Mirle, Manhattan WCS) plus Digital Twin monitoring.
Common WCS Integration Patterns in Taiwan
(1) GoWarehouse + the equipment vendor's control software (the most common setup, fits 1–3 AMRs). (2) GoWarehouse + Geek+ cloud WCS (fits 5–15 Geek+ AMRs). (3) Common in manufacturing: SAP EWM + Mirle WCS + AS/RS.
Frequently Asked Questions
QCan WMS and WCS be the same system?
ATechnically yes, but in practice we don't recommend it. Specialist WCS vendors have spent 20+ years on hardware control (Mirle, Honeywell), while WMS vendors specialize in software. Division of labor produces better results.
QWhat does a WCS cost monthly?
ALightweight cloud WCS runs NT$ 10,000–50,000/month. A full on-prem WCS is a one-time NT$ 3M–15M.
QCan I skip the WCS and build the integration myself?
AYou can, but cost it out first. Integrating one AMR vendor's API typically costs 2–4 engineer-weeks. Single vendor — maybe build it yourself. Multiple vendors — buy a WCS, save the headache.
QIf I change my WMS, do I have to change the WCS?
ANo. The WCS is a translation layer that can talk to any WMS. When you swap WMS, you just redo the integration.
QDoes AS/RS need a WCS too?
AAlmost always yes. AS/RS stacker cranes have far more complex control logic than AMRs and can't operate without a WCS.