IT systems · Practical guide

Validating viadat: from recorded warehouse status to the physical stock movement

A batch is blocked in the system of record but needs to move to another bin. May viadat initiate that movement, and what happens if release information arrives late? Bring the physical and digital states together. Test the transitions that matter in your GMP installation rather than counting warehouse functions.

Table of contents

At a glance

How do you validate viadat in a GMP warehouse?

Start with the intended warehouse processes, installed viadat version and connected systems. Demonstrate correct material and batch assignment, effective blocks on use and shipping, and controlled movements and confirmations. Supplier documentation can support the assessment, but it does not replace process requirements or tests of your actual configuration, interfaces and restart procedures in pharmaceutical operations.

  • Internal movement, quality release decision, and shipping authorization are separate decisions.
  • A work order in the WMS and a physically executed movement require a traceable reconciliation.
  • Viadat functionality documentation describes possible options; the installed version remains decisive.
  • Failures at system boundaries and upon retry should be included in risk-based evaluation.

1. Which viadat is actually being used?

viadat is warehouse management and material flow software within the viastore ecosystem. According to the vendor's profile in the logistics IT database, viadat supports document- and MDE-driven workflows across different warehouse formats. Please document the actual functionality delivered: which inventories, batches, transport movements, and associated equipment does your installation manage? Critical is the interaction between version, configuration, and customizations in your warehouse environment.

As of 1 April 2026, Toyota Automated Logistics viastore, Bastian Solutions, and Vanderlande's warehouse operations will operate under a single brand. This does not imply any proven rebranding of viadat nor does it indicate functional equivalence to other software products within this portfolio. Therefore, it is essential to maintain distinct records for product name, build, enhancements, control components, and responsible contractual partner.

Align external functional evidence to its specific scope. The logistics IT database of Fraunhofer IML serves for comparing logistics systems and supplier declarations. This is a distinct subject for evaluation from the GMP suitability of your installed warehouse. Therefore, request product documentation and limitations relevant to your current setup and assess which of your own requirements a particular piece of evidence actually addresses.

Sources: [2] [1] [3]

2. Link regulated use to specific decisions

GMP relevance arises, for example, when viadat influences the selection of a material, its assignment to a production order, or the release of a finished product. A simple guidance document for non-critical ancillary items may warrant a different evaluation. Therefore, describe the affected article categories, locations, and process decisions prior to blanket inclusion or exclusion of entire modules.

This article pertains to computerized processes involved in the manufacture of human medicinal products. EU GMP Annex 11 distinguishes between application validation and infrastructure qualification and requires a risk-based approach. Pure wholesale distributors, medical devices, or additional US regulatory areas necessitate separate assessment. The software brand does not establish the applicable framework.

Establish a clear process boundary as a working basis: What does viadat handle, what decisions are made by the ERP or quality management system, and what is confirmed by the document or operator? Extend the procedure to include sample handling, returns, and damaged cartons, as these may occur in actual practice. A clearly defined exclusion also specifies which other procedure controls the respective aspect.

Sources: [4] [5]

3. Create a responsibility matrix prior to test scripts

Start with a specific question: Who determines whether a particular product may be used for a specific purpose? Following this, consider transfer, technical implementation, and confirmation. The following work guide represents an independent structural proposal. It makes no claims to predefined viadat menu structures, message formats, or standard statuses.

Assign each open line to a responsible employee and a verifiable record. A single arrow in an architecture diagram is insufficient as evidence of acceptance. The team should be able to explain which information is received, which event triggers it effectively, and how a failure is detected. A manual handover may be part of the concept, but it must be supported by a traceable control.

Labour assistance: decision, implementation and proof in the associated storage process
LevelDecision to makeSpecific evidence
ERP or quality management system Who authorizes or withdraws the right of use? Approved decision data set with material, batch, and scope of validity
viadat Which orders are authorized for this inventory? Configuration plus authorized and rejected process scenarios
Material flow control Which mission has been implemented to which target? Order reference and appropriate feedback from the executing level
Operator and physical goods Does the identified container match the digital order? Observed scan/handling incident including misidentification
Operations management How is a discrepancy between these levels addressed? Responsibility, error reporting, assured inventory, and documented closure

Sources: [2] [5]

4. A transfer is not a quality release

A sealed batch may need to be moved for investigation or transported to a secured location under the approved release inventory concept. This does not confer the right to release or deliver the batch into production. Therefore, a clear and specific rule must be established for each action: internal reallocation, sample provisioning, production supply, and dispatch may have different prerequisites.

Chapter 3.21 of the EU GMP Guideline requires equivalent security when a system replaces physical quarantine. A colored status indicator alone does not demonstrate this. Assess your process, for example, whether scanners, manual order entry, and alternative sampling points effectively enforce the same restriction. Additional warehouse requirements must be considered for rejected, recalled, or returned goods.

For finished dosage forms, it is also necessary to distinguish between QP certification and subsequent transfer to sellable inventory. Annex 16 outlines these steps. Not every material usage decision constitutes a QP certification. Document which decision the WMS actually receives and which actions are permitted as a result.

Sources: [6] [7]

Further reading:

5. Review orders and status messages for discrepancies

The critical question regarding interface functionality is not merely whether a message has been received. What matters is whether the correct inventory, with the correct interpretation, has been processed. Define identifiers for material, batch, package, order, and optionally location. A technically successful transmission may still be incorrect from a functional standpoint—for example, if the same batch number exists for a different material.

Develop error cases based on your actual architecture: A status change occurs later than the order installation; a feedback is repeated after connection interruption; an order refers to a bundle that has been repackaged. Define beforehand which combination should be processed, rejected or stopped for clarification. Whether communication works synchronously or asynchronously results from the installation.

A repeatable demonstration links the inbound event, the processing decision, and the resulting inventory. For a duplicate case, the unaltered original event remains as the reference. Repetition must not trigger a second professional product effect within the defined target. How this is achieved must be demonstrated through the specific interface design; a particular technical solution is not assumed.

Sources: [2] [5]

6. Test example: 120 packages, one lock, two storage locations

The following example does not constitute a completed product release. Initial state: Batch C-17 includes 120 cartons, comprising bundle G-A with 80 and G-B with 40 cartons. Both bundles are located in Zone Q1. The batch is locked for production and distribution. The only permitted activity is a documented internal transfer to the similarly secured Zone Q2.

In this scenario, the following is defined: A repeat of the same confirmed shipping notification does not generate additional movement or quantity. A shipping instruction remains rejected until an authorized usage decision is made. Upon confirmed acceptance of such a decision, a new order may ship 30 units from G-A. This is a defined example rule, not a statement regarding pre-configured viadat system behavior.

Own required matrix: Each step builds upon the previous state.
StepAction or failure scenarioIndependently established expected resultTo ensure
0 Take opening balance forward Q1: 120; Q2: 0; Total: 120; Shipping locked Batch, Pallet, Status and Release List
1 Move G-B with 40 internal to Q2 review Q1: 80; Q2: 40; Total: 120; Lock remains Order, physical destination, and feedback
2 Send the same response again Q1: 80; Q2: 40; Total: 120; no second booking Original and repetition including processing
3 30 from G-A want to ship Rejection; Q1: 80; Q2: 40; Total: 120 Not only a report, but also an unchanged inventory effect
4 Take authorized decision; perform new dispatch for 30. Q1: 50; Q2: 40; Total: 90; Shipping: 30 Decision reference, new order and actual dispatch
5 Final reconciliation 50 + 40 + 30 = 120; no loss and no overage Stock, shipping document, and physical reconciliation

Sources: [5] [6]

7. Scanner, operator interventions, and actual movement to be included

A WMS screen test can indicate that an order is intended. Whether the correct product reaches the correct location remains unverified. For critical pathways, select representative real-time transfers: identification at the pickup point, pallet exchange, destination confirmation, and handling of illegible labels. During observation, also assess whether an operator can inadvertently correct a wrong scan through manual entry.

For interventions carried out by lead staff or service personnel, a separate question arises: Who is authorized to cancel an order, modify a target, or correct inventory? Distinguish routine warehouse operations from privileged error correction. Service privileges must not inadvertently confer technical release authority. Use realistic role-based permissions during testing; an all-powerful administrator account obscures such boundaries.

Testing of moving equipment is planned and controlled. The storage routing and responsible equipment safety personnel must define appropriate test materials, secured areas, and emergency shutdown options. Software validation does not replace the safety assessment of conveying technology. Additionally, clearly document which simulation only loads the message processing function and which test actually covers the physical process flow.

Sources: [2] [5] [6]

8. History and reconciliation of technical and operational data for reprocessing

In supplier documentation, specifically inquire about the available order, inventory, and change histories for the version in question. Public function lists do not indicate which fields are stored with old value, new value, user, and rationale. Select relevant evidence based on specific investigation questions: Who made the order change? What authorization was in effect? Was the material actually moved?

For a retry test, a deliberately paused transport order is appropriate. The order has already been issued, physical movement has occurred, but confirmation is missing from the restored data set. A correct response cannot be derived solely from a successful restore. Your procedure must detect this distinction and enable responsible coordination prior to authorizing further movement of the same goods.

Original records shall be provided, and any necessary corrections shall be justified. A newly generated report must not silently replace the original event sequence. For future reference, legibility, context, and access must be ensured for the prescribed duration. A general log retention period from the service agreement may be shorter than the required retention period for your process.

Sources: [5] [8]

Further reading:

9. Manage effort through preparation and targeted change evaluation

For a small and medium-sized enterprise (SME), the absence of decision-making is often more time-consuming than completing a test protocol. Prior to project initiation, the warehouse manager requires the actual product flow, QA needs authorized usage decisions, and IT requires the system architecture along with operational responsibilities. The supplier provides version-matched functional and interface documentation. Agree on who resolves open contradictions and who authorizes test times at the facility.

The scope expands primarily due to different locations, manual exceptions, customer-specific adaptations, and unavailable test environments. Existing qualified evidence may be utilized, provided it covers the relevant site and purpose. A supplier assessment is neither dismissed in a blanket manner nor considered unverified for the overall validation conclusion.

In an update, you will look at the effects on processes, data and controls. For example, a modified transport prioritization may affect previously unchanged blocking tests elsewhere. This will result in a well-founded selection of additional tests, no automatic full-retesting and no complete renunciation of testing. Document remaining limits, operating documents and the decision to use them.

Sources: [5]

10. Checklist for reliable viadat detection

Use the following list as a discussion basis prior to acceptance. Each point should reference a specific basis, a verified configuration, or a evaluated test result. The mere fact that other tests were successful does not automatically render an open point acceptable.

  • Product status, components, modifications, operating procedure, and supplier responsibility are clearly defined.
  • The primary decision for material usage and shipping includes the scope of applicability.
  • Permissible internal movements and unauthorised withdrawals are specified separately.
  • Identifiers and meanings are consistent across ERP, viadat, control, and physical goods.
  • Duplicates, sequence errors, interruptions, and manual corrections were considered in light of the architecture.
  • Realistic authorizations are verified for relevant roles and privileged interventions.
  • The retry accounts for already moved goods and still open digital orders.
  • Historical records, operating procedures, training, and change evaluations are the responsibility of the accountable owners.

Sources: [5] [6] [7]

Project experience and collaboration

Trace stock, blocks and confirmations through the warehouse process

With the warehouse, quality and IT teams, we use a known batch with defined partial quantities as a reference. During put-away and retrieval, we compare identity, permitted use and system confirmations. A limited manual workflow may need targeted evidence. Automated equipment and interrupted messages need further cases. We coordinate recovery testing so a technical restart alone is not accepted as evidence that stock is correct. The controls depend on actual warehouse operations.

Frequently asked questions about viastore viadat

Must an existing viadat warehouse be fully revalidated?

Not automatically. Start with actual usage, known issues, and existing evidence. Assess whether this aligns with the current version, configuration, and existing product distribution. Missing documentation and real-world process risks should be evaluated separately. A traceable stock record may remain usable; a historically unverified shipping lock cannot be justified solely by prolonged periods of uninterrupted operation.

Sources: [5]

What do Fraunhofer data indicate regarding viadat?

First, verify the intended evidence: The logistics IT database distinguishes between system specifications and validated reference projects. As of October 18, 2026, the vendor profile lists seven validated WMS reference projects; however, it does not provide validated system specifications for the current online selection. Evaluating the functional scope of a WMS or a reference project does not constitute GMP validation of your installation. For your specific application, requirements, installed version, and internal process assessments must be aligned. Clearly specify the scope, reference year, and version of any provided evidence.

Sources: [3] [5]

Is viadat a different product after the merger?

The current company website currently hosts the jointly branded Toyota Automated Logistics since April 2026. It does not indicate a general product renaming or technical equivalence across all software solutions. Therefore, for your system description, use the solution expressly referenced in the contract and the installed version. Clarify support responsibility, document access, and changes to the supply chain during any new contract or update.

Sources: [1]

Can restricted goods be moved in the warehouse?

This depends on the approved storage and process concept. A controlled internal transfer may differ from production supply or dispatch. Crucially, the movement must not compromise the required safeguards and identity. Explicitly describe permitted objectives and actions, and evaluate the unauthorized alternative scenario. A transfer from a portable container does not constitute quality release.

Sources: [6] [7]

Is a test of the ERP interface without conveying technology sufficient?

It can cover the transferred information and processing, but does not automatically encompass the full supply chain. Define the risks that arise specifically through scanning, operator actions, or physical movement. For these interfaces with the actual process, an appropriate additional justification is required. Use simulations where their validity is substantiated, and clearly state their limitations in the inspection report.

Sources: [2] [5]

How do we verify a double transport confirmation?

Obtain the first confirmation as an original and replicate the corresponding event in a controlled test. Subsequently, compare the business status against the previously defined expected state: order, location, quantity, and history. A mere error message is insufficient if the inventory is altered twice despite the absence of a valid justification. The handling of other, genuinely new events must remain distinguishable from this scenario.

Sources: [5]

What data should be available for future investigation?

Start with the investigation question and trace the relevant task. Frequently, material/batch reference, packaging, quantities, locations, status changes, and responsible actions are critical. Which of these are present in which history must be visible in your version. Not every technical fault report requires the same retention period. However, the linkage required for a GMP decision must not be lost due to separated or prematurely deleted records.

Sources: [8] [5]

Is the successful restoration of the database sufficient?

You are performing a technical recovery step. In an automated warehouse, the product may have already been moved to a different location than recorded in the secured data snapshot. Therefore, additionally verify the alignment of open orders, physical locations, and pending feedbacks. Responsible parties must be able to decide which activities may be continued or corrected; uncontrolled resending may introduce new errors.

Sources: [5]

Who must participate in a Viadat project within a SME?

You require at least the necessary inventory process, quality, system, and integration expertise; multiple roles may be appropriately structured. Particularly important are personnel who understand exceptions in real-world operations. Additionally, clarify who is responsible for conducting secure agent testing and who holds responsibility for quality decisions. Without this involvement, a supplier may demonstrate functionalities but cannot define all operational required decisions on your behalf.

Sources: [5]

What tests are appropriate following a configuration change?

First, assess which decisions, data pathways, and error handling procedures may be affected. For example, if a permitted target is changed, evaluate both the new pathway and existing restrictions as well as relevant exemptions. Continue to use valid documentation and address any resulting gaps. The scope is determined by the impact; a change does not necessarily require all tests or merely a single successful trial.

Sources: [5]

Sources and review date

Supplier profile and logistics IT database methodology retrieved on 18 October 2026; other sources as of 6 October 2026. The regulatory reference applies to the described human medicinal product GMP usage. Tables and inspection cases are standalone work aids.

  1. Toyota Automated Logistics – official brand integration
  2. Fraunhofer IML: current vendor profile with viadatProduct description and listed WMS in the current vendor profile. Replaces the brochure link no longer accessible at its previous address; does not include any prior version or certificate details.
  3. Fraunhofer IML: Methodology for Logistics IT DatabaseCollection, verification, and comparison of logistics system and supplier information. This audit subject must be distinguished from internal GMP system validation.
  4. EudraLex Volume 4 – Human Medicinal Products – GMP
  5. EU GMP Annex 11: Computerised Systems
  6. EU GMP Chapter 3: Premises and Equipment
  7. EU GMP Annex 16: Certification by a Qualified Person and Batch Release
  8. EU GMP Chapter 4: Documentation

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Ensure their viadat process is traceable and verifiable

We support you in integrating existing warehouse procedures, supplier certifications, and outstanding inspection questions into a reliable foundation for the intended GMP use.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →