The Gold Standard of Automated Warehouse System Commissioning | Safe Robots, Accurate Stock and Proven Handover

An automated warehouse can move pallets, totes or cartons through conveyors, shuttles, storage cranes and driverless industrial trucks. Successful commissioning is not merely watching a robot complete one impressive journey. The system must protect people, coordinate its machines, correctly identify stock, respond to failures, communicate with the warehouse management system and return usable records to its owner. The gold standard is a safe installation whose inventory accuracy, throughput, exception handling and operational responsibility can be demonstrated under clearly defined conditions.

Imagine a fictional Singapore distribution centre preparing to commission an automated storage-and-retrieval system with 12,000 tote positions, conveyors and two autonomous mobile robots. A supplier runs a smooth demonstration, but the next acceptance test shows that several scanned products reach the wrong logical inventory location when a conveyor rejects a label. Meanwhile the robot traffic system has not been verified for every pedestrian access condition. Management wants to open before a peak order period. This guide follows the decision using Singapore MOM risk management, ISO 3691-4:2023, ISO 10218-1 and -2:2025, ISO 13849-1:2023 and IEC 62061 with its 2026 amendment. It addresses full-system acceptance, separate from Industrial Conveyor Maintenance Services.

Which automated-warehouse acceptance decision needs proof?

Follow one warehouse project from physical and software boundaries to safe robotic movement, accurate stock, exceptions, interrupted operations and accountable handover.

1. Begin with the customer’s real warehouse service

A warehouse automation project may promise accurate receipts, putaway, storage, retrieval, picking and dispatch, or a defined throughput during the busy season. Those are different functions. A high-speed conveyor demonstration cannot establish that an order was matched with the correct SKU, lot and delivery destination.

Write a commissioning acceptance plan around the warehouse’s intended goods, dimensions, volume, handling restrictions, order types and staff workflows. A system built for totes may not be suitable for every pallet or hazardous product. Test results should distinguish equipment capability from overall commercial performance. When the original contract promises correct customer orders, a robotics demonstration alone is not full acceptance.

2. Define the physical and digital system boundaries

Automated warehouses combine storage structure, conveyors, motors, lifts, shuttle or crane systems, sensors, doors, safety devices and software. The warehouse management system may plan inventory while the warehouse control system sends machine instructions. Different suppliers can own each component and interface.

List every subsystem and its responsible engineering party. Confirm which hardware, control software, interface and master-data revisions are in the acceptance scope. A vendor reporting that its robot passed factory tests may be entirely truthful while the installed interface to the customer’s ERP remains unverified. A coherent system register makes faults easier to locate and prevents each supplier from claiming that an unresolved issue belongs exclusively to someone else.

3. Apply Singapore WSH risk management during commissioning

MOM’s workplace risk-management guidance explicitly includes commissioning, repair and maintenance among non-routine operations requiring risk assessment. The process involves identifying hazards, evaluating risk and implementing control measures according to the hierarchy of control. Moving machinery and mixed traffic need these protections even before the warehouse begins normal operations.

The operator cannot treat commissioning as an exception to workplace safety merely because only engineers are present. Contractors, operators and visitors may encounter unfamiliar motion or temporary work arrangements. Use competent multidisciplinary review and site-specific approvals. No commercial schedule should require bypassing a protective device simply to produce a passing throughput demonstration. A recorded safety concern remains open until professionally resolved.

4. Use ISO 3691-4:2023 for driverless industrial truck systems

ISO 3691-4:2023 covers safety requirements and verification for driverless industrial trucks and their systems, including automated guided vehicles and relevant autonomous mobile robots. Its third-edition replacement was still a Draft International Standard under development in October 2026, so 2023 remains the published edition at this checkpoint.

A vendor claiming that ISO 3691-4:2026 is already the current published edition would be inaccurate. The standard’s application depends on the robot type and system. The owner needs actual evidence about the installed vehicles and traffic context, not one supplier brochure asserting compliance with a standard number. The responsible engineers must interpret safety requirements against real pedestrian areas and operating conditions.

5. Distinguish industrial robots from mobile truck applications

ISO 10218-1:2025 sets safety requirements for industrial robots considered as partly completed machinery, while ISO 10218-2:2025 addresses integration and robotic applications. These are not identical to ISO 3691-4’s scope for driverless industrial trucks. A fixed palletizing arm and a mobile tote carrier may therefore require different technical treatment.

Define which machines are industrial robots, driverless trucks, conveyors or other equipment. An ISO 10218 product declaration for a robotic arm does not establish every access gate, interlock or adjacent conveyor was integrated safely. The owner needs an installation-level safety assessment and evidence of the actual work cell. Correct standard selection makes the system safer and prevents misleading claims about a generic robotics certificate.

6. Apply ISO 13849-1:2023 to relevant safety control functions

ISO 13849-1:2023 provides design methodology for safety-related parts of control systems, including hardware and software. It does not specify the required performance level for every application; that must follow the actual risk and safety-function requirements.

Commissioning should trace the specified protective functions to the as-installed controls and appropriate verification by competent professionals. A normal software status screen cannot prove an emergency protective function works. One vendor’s safety PLC certificate is useful but not a blanket approval of all machine interfaces. The owner needs evidence that the safety control architecture corresponds to the warehouse design and actual hazards, without asking technicians to perform dangerous unplanned trials.

7. Recognise IEC 62061 and the 2026 amendments

IEC 62061:2021 addresses functional safety of safety-related control systems for machinery. IEC published Amendment 1 in 2024 and Amendment 2 in March 2026, creating an updated consolidated standard. It covers a distinct but related functional-safety engineering framework.

A project may use ISO 13849 or IEC 62061 according to its approved design; the two should not be casually combined into a made-up generic protection rating. Identify what was actually adopted and which test evidence supports the installed control functions. Commissioning should record software and hardware versions because later changes can affect previous results. The most recent edition number is not proof that a machine’s actual function has been verified.

8. Design the pedestrian and vehicle interface around real people

Warehouse robots may operate near pickers, cleaners, supervisors and delivery personnel. Their routes can cross shared floors, doors or handover stations. A driverless vehicle moving smoothly through an empty aisle does not establish how the system behaves when people occupy the relevant space.

Plan competent evaluation of intended access, separation, pedestrian and vehicle movement and appropriate safe behaviour for the installed traffic design. This article deliberately does not prescribe obstacle testing or ways to defeat protective devices. Operators must understand permitted routes and authorised responses when a path is blocked. The system should never rely on workers improvising near moving vehicles to achieve a promised dispatch rate.

9. Keep physical guarding and safe access within the acceptance

Automated storage cranes, conveyors, lifts and transfer equipment may have moving parts and elevated operations that present different hazards. Guards, gates and relevant access arrangements must match the design. A machine can complete every programmed move while one unsafe access opening remains.

Record the installed condition of guards, gates and relevant interlocks under the qualified safety assessment. A temporary fence used during construction is not automatically acceptable as a permanent safety solution. Contractors should document changes made to permit maintenance access and whether they affect the earlier accepted machine configuration. The owner’s handover must make clear who is authorised to enter restricted parts of the automated installation.

10. Distinguish mechanical capacity from software order correctness

A tote shuttle may lift and transport its rated load safely while the inventory software sends the wrong tote to a pick station. Conversely, perfect software matching is not evidence that the mechanical equipment has adequate load or lifting capacity.

Prepare distinct mechanical, electrical, software and inventory test schedules. The warehouse should not average these into one broad pass score that hides a critical defect. Each area has its own acceptance limits and responsible technical authority. A customer can legitimately reject software integration even when the physical machine performs well. It can also hold a mechanically unsafe lift while other software test cases have passed.

11. Build accurate SKU, lot and location master data

A warehouse system’s inventory decisions depend on physical labels and digital records. The correct product identity may include SKU, lot, serial, expiry, handling category and customer restrictions. Errors in master data can appear to be automation faults even when the sorter reads a barcode correctly.

Verify the relevant data population before live acceptance. A test using generic demonstration labels does not represent the real stock profile, especially when similar SKUs or supplier barcode formats coexist. Good commissioning reconciles location identifiers, allowable dimensions and storage restrictions. An owner should preserve mapping decisions so the next team can understand whether a discrepancy originates at goods receipt, label scanning, WMS instructions or mechanical transfer.

12. Verify receiving and putaway as complete business events

A supplier may demonstrate that one tote moves from receiving to an available storage location. A complete business process also needs the correct inventory record and confirmation that the specific goods are actually where the system says they are.

Test real representative scenarios: accepted goods, rejected labels, damaged packaging, capacity constraints and items requiring special handling. The details belong in a controlled, qualified acceptance programme. A record showing successful conveyor movement cannot substitute for proper stock identity and location confirmation. The owner should establish how an exception is detected and which system and person is responsible for resolving it before goods become available to sales.

13. Keep handoffs between conveyors, lifts and shuttles traceable

Moving goods through an automated warehouse involves multiple transfer points. A tote can reach the correct conveyor but fail at a lift or shuttle handover. Software can also record completion at an earlier point than the actual physical transfer, creating false stock confidence.

Identify every material handoff and its completion signal. Test normal and relevant exception states through authorised methods. A damaged scanner or inconsistent sensor timestamp should not be masked by manually editing inventory while the underlying problem persists. The owner needs an evidence trail from the source position to confirmed destination, with exceptions visible rather than overwritten by a green dashboard.

14. Test scanning and recognition without assuming every label is perfect

Products enter warehouses with different package materials, orientations and barcode quality. Some labels are damaged, obscured or nonstandard. Automated readers may reject certain cases even when the mechanical transporter works correctly.

Define expected valid-label populations, reading conditions and how rejected goods are safely managed. No system can be assumed to read every physically possible damaged label. A good acceptance test distinguishes genuine recognition errors from deliberately invalid stock and measures the exceptions. The operator needs a documented process for correcting records without losing product identity. Repeated manual overrides of unreadable labels can conceal a serious stock-control problem.

15. Use realistic order lines and product mix when testing throughput

Warehouse suppliers may quote totes per hour or orders per shift under a reference test. Actual fulfilment also depends on goods mix, item locations, stock availability, personnel and sequencing. A test that cycles one easy tote repeatedly may exaggerate usable operational capacity.

Agree test data and operating conditions before commissioning, including representative fast- and slow-moving products and realistic replenishment. A throughput figure should state whether it covers machine moves, successful picks or fully verified customer orders. The owner should not accept a high movement count as proof of correct inventory and dispatch. Reliability and product accuracy remain separate acceptance dimensions.

16. Recognise that nominal storage capacity is not always usable capacity

An automated storage system may advertise 12,000 tote positions, but some locations can be reserved, restricted by load dimensions or temporarily unavailable. The effective capacity under real product data and operational constraints may be lower.

A credible commissioning plan reconciles as-built physical locations, allowable loads and the WMS’s actual locations. Count inaccessible positions and other exclusions honestly. A scanned count of empty compartments does not prove that every compartment accepts every product. The owner needs usable capacity by relevant product category, not just a theoretical sum used in a sales proposal.

17. Protect structural rack and storage load assumptions

Automated storage equipment can interact with high racks, rails, frames and other structures whose permitted loading is part of the design. Adding heavier products or changing tote types after installation may create structural questions independent of the software’s capacity map.

Use current engineering and manufacturer records, with the relevant Singapore WSH storage obligations where applicable. The existing Warehouse Racking Inspection Services guide covers physical safe loads and damage controls. A warehouse algorithm should not permit a location assignment that conflicts with the approved load or storage arrangement. Reliable inventory requires safe physical storage, not merely correct database values.

18. Coordinate power, network and supervisory control interfaces

Automated warehouses rely on electricity, networks, control servers and industrial software. A brief loss of communications can disrupt a transfer while some equipment remains physically moving or holding goods. The proper response must be engineered rather than improvised.

Identify the relevant installed interfaces and responsible supplier. A successful local controller test does not establish that an alarm reaches the owner’s supervision system or that records remain consistent through a network interruption. Qualified engineers should verify the approved recovery arrangements without creating hazardous tests. The final report needs actual hardware and software revisions so future support can reproduce the accepted configuration.

19. Plan safe response to jams and rejected stock

Goods can become obstructed because of damaged totes, misplaced loads or mechanical faults. Unplanned access to resolve a jam may expose workers to machinery and stored energy. A system that requires frequent unsafe manual intervention is not properly commissioned for production.

Define legitimate exception categories and approved response ownership. Operators should have clear indications and training but must not be encouraged to enter hazardous machinery spaces or defeat interlocks. The functional result is not simply that a conveyor restarts; it is that both material location and safety status are known and can be reconciled before work resumes. The service design should anticipate foreseeable exceptions.

20. Verify emergency and protective functions separately

An automated installation may have emergency stop devices, safe access interlocks and other risk-reduction controls. Their presence is not evidence of correct integrated operation. The technical requirements depend on the risk assessment and chosen functional-safety standards.

Use appropriately qualified verification of each specified function under an approved programme. No broad article should prescribe activation tests that could injure people or damage a live warehouse. A critical failed safety function cannot be offset by thousands of correct tote moves. Commissioning records should identify what was tested, what passed, what remains open and who is authorised to sign off each issue.

21. Reconcile stock after interrupted material movements

An emergency stop, power interruption or device fault can leave a tote between two logical locations. Physical stock may be safe, yet the database may record a completed transfer that never occurred. Restarting machines without stock reconciliation can then create incorrect picks and customer deliveries.

The WMS and controls provider should define approved recovery and inventory processes. Test their results in safe qualified conditions and preserve the discrepancy history. A successful machine restart is not sufficient proof that every stored item is correctly accounted for. When the owner’s business depends on lot or expiry tracking, the consequences of logical location errors may extend beyond one missed order.

22. Keep cybersecurity and system access in the support plan

Warehouse control software and remote vendor access can be necessary for diagnostics and updates, but create responsibility for authorised credentials, software versions and change history. A supplier’s shared installer account should not remain the sole route for future owner operations.

Define who owns accounts, backups, network interfaces, support access and security-related changes. A routine software patch can alter a previously accepted control or WMS integration behaviour, so relevant regression testing may be necessary. This is distinct from verifying the machines’ functional safety, though both can affect reliable service. The owner should receive supportable systems rather than become dependent on an undocumented personal laptop or password.

23. Separate scheduled service from the first commissioning result

A new automated installation may pass initial acceptance and still need qualified inspection, cleaning, calibration and software maintenance. Its components will wear, and warehouse business processes will change as customers and inventory evolve.

Provide a documented maintenance schedule, spare-parts information, system backups, response channels and conditions that trigger re-evaluation. A commissioning certificate is not a warranty that every future scan will be accurate. The equipment owner’s ongoing responsibilities should be explicit. A well-designed system allows competent staff to manage foreseeable deterioration and respond to faults without inventing unsafe workarounds.

24. Use one exception register across every supplier

Automated projects often involve a mechanical contractor, robot vendor, controls integrator, WMS developer and building operator. One supplier may close its own ticket while the overall problem remains open at the interface. Without a shared register, defects can reappear during live fulfilment.

Record each observation, relevant requirement, physical asset or software version, accountable owner, corrective action and appropriate verification. Preserve the original result after an authorised retest. A defect should not be closed merely because an email says another company has taken responsibility. The customer needs one truthful view of readiness before declaring the warehouse open.

25. The gold standard is safe, accurate and recoverable warehouse operation

The fictional distribution centre resolves its incorrect logical location handoffs and obtains qualified verification of the remaining mobile-robot safety interfaces. The acceptance plan separately reports physical throughput, inventory correctness, safe operation and recovery after approved interruptions. The owner knows which systems and suppliers remain responsible after opening.

Gold-standard automated warehouse commissioning joins safe machines, correct digital records, real storage capacity, order accuracy, credible exception handling and durable handover. Its promise is not that a robot can travel quickly down an empty aisle. It is a facility that can move the right goods safely to the right place and recover coherently when real-world operations do not go exactly to plan.

Worked example: 99% correct moves do not settle warehouse readiness

Suppose a fictional commissioning test defines 1,000 expected tote retrievals. Eight hundred and ninety-five complete the correct physical and inventory handoff, seventy-five succeed mechanically but require inventory correction, twenty stop safely through the intended exception route and ten have invalid or unverified results. If only the 895 correct completed handoffs count toward the intended outcome, that is 89.5%, not a vague 99% movement success. Even a 99.9% warehouse throughput claim would not compensate for an unverified pedestrian protection function. In a separate storage audit, 12,000 nominal locations include 600 reserved or unsuitable positions, giving 11,400 currently usable locations for the stated product mix. These are distinct denominators. A credible report names the test population, actual exceptions, safety conditions and the business outcome rather than averaging all of them into one percentage.

Which commissioning record supports which claim?

Record	What it supports	What it cannot prove alone
Robot or AGV manufacturer records	Specified product characteristics and type scope	Complete installed traffic safety
ISO 3691-4 and safety integration verification	Defined driverless truck system protective requirements	Every WMS inventory location correct
WMS stock reconciliation	Location and product data under tested transactions	All conveyors and robots mechanically safe
Throughput and order accuracy testing	Operational outputs under stated product mix and periods	Future exception recovery always successful
Integrated exception and handover report	Documented ownership, faults, corrections and limits	All future software changes automatically accepted

Questions warehouse owners ask before automation go-live

Is ISO 3691-4:2023 still the current driverless truck standard in October 2026?

Yes. A replacement third edition is under development; 2023 remains published.

Does ISO 10218-1:2025 cover every automated mobile warehouse vehicle?

No. It concerns industrial robots, while ISO 3691-4 addresses driverless industrial trucks within its scope.

What does ISO 13849-1:2023 cover?

Safety-related parts of control systems and design methods; the required safety performance level depends on the application.

Was IEC 62061 updated in 2026?

Yes. Amendment 2:2026 supplements the 2021 edition and 2024 amendment for machinery control-system functional safety.

Does a high totes-per-hour demonstration prove order accuracy?

No. Correct product identity, location, stock reconciliation and exception handling need independent evidence.

Can a warehouse open if one safety interface remains unverified?

Only the authorised professional and legal acceptance process can determine operation; favourable productivity averages cannot waive applicable safety requirements.

Do software updates require any review after handover?

Material changes can affect accepted controls or integration and may require competent risk assessment and retesting.

Is nominal 12,000-position storage identical to usable capacity?

Not necessarily. Load, dimension, reservation and operating restrictions determine usable capacity.

Automated warehouse owner commissioning checklist

Identify all machines, WMS/WCS interfaces and supplier boundaries.
Apply Singapore WSH risk assessment through non-routine commissioning.
Use ISO 3691-4 for appropriate driverless industrial truck systems.
Apply ISO 10218, ISO 13849-1 and IEC 62061 within their real functions.
Verify safe pedestrian and machine access under competent procedures.
Reconcile physical locations, SKU data, scan results and stock identities.
Test representative workflows, exception handling and recovery.
Report throughput and inventory accuracy with explicit denominators.
Record software revisions, backups, access ownership and vendor support.
Close applicable safety and business acceptance findings before go-live.

ISO, IEC, MOM and related eduKate primary references

These standards are applied within their respective machinery and system scopes, and safety tests require suitably qualified procedures. This educational article does not prescribe machine-bypass, robot intervention or dangerous failure demonstrations. For broader evidence principles see The Gold Standard master guide.