InnerWeb
Skip to main content

FAQ: delivery notice by card code and data protection

When security enters the card code of a delivery notice, the system retrieves the planned delivery, driver and vehicle data from the notice system. The data protection officer and the IT department then ask about the scope of data, wrong identification and the audit trail. We answer these questions based on how the deliveries and notice functions actually behave.

5 characters
canonical card code in the query
Source: karta
6
language versions of error messages on the terminal
Source: karta

How data retrieval by card code works

After the notice card code is entered, the system retrieves the planned delivery data from the client's notice system and pre-fills the form. Security therefore does not retype driver and vehicle data by hand; it only checks and approves them. Less manual entry means fewer typos and a shorter handling time at the gate.

The notice card code is a separate delivery field and acts as the key linking the delivery in InnerWeb with the record in the notice system. The operation type from the notice, that is unloading or loading, sets the delivery label, and the handling point name is matched against warehouse and dock codes.

  • The card code is the key to the client's notice record.
  • The delivery form is pre-filled, security verifies the data.
  • The operation type sets the label: unloading or loading.
  • The handling point is matched against warehouse and dock codes.

Questions from the data protection officer

The most important question is whether the system could assign a delivery to the wrong driver. For this reason a delivery with a completed transport in the notice system is deliberately treated as no data. An external system may return the last completed transport for unknown codes, which would mean wrong driver identification and a GDPR problem.

This is an example of data minimisation in practice: it is better to show security that no data exists than to display another driver's data. For the officer, this means a documented mechanism that can be described in the record of processing activities and in the risk assessment.

Which data goes into the form

The form receives the data needed to handle the delivery: driver, vehicle, carrier, operation type and handling point. The scope is agreed with the client during integration and may be narrower than what the notice system returns. The detailed list of fields and the legal basis are set by the data controller, and InnerWeb supports this with a description of the flow.

What happens when the carrier is missing

When the notice does not include a carrier, the system inserts a substitute carrier so that the delivery can be created. As a result, one missing field does not stop the vehicle at the barrier, and the gap remains visible in the data for later completion.

Questions from the IT department about integration

Integration with the client's notice system works over SOAP and requires implementation work. We do not promise integration with any notice system without that work, because the service contract, authentication and code format differ between plants. The IT department should prepare a service description, a test environment and a technical account.

InnerWeb works as an independent, complementary system. It does not manufacture readers or notice hardware, so it does not change the infrastructure on which the notice system runs. It only takes the data needed to handle the delivery on the plant grounds.

Questions about code errors and the audit trail

A card query goes out as one canonical five-character code. If security enters leading zeros, the result does not change. This removes the typical reason for reports that a card does not work, when different operators enter the same code in different forms.

Every search by card code is recorded in telemetry: code, result, status, response time and source. This makes repeated reports about cards that do not work possible to confirm or refute with numbers, and the audit trail shows who searched for the data and when. Error messages on the security terminal are translated into 6 interface language versions, and the lack of an active transport for a card is communicated in the operator's language.

What to prepare before the implementation talk

For the officer: a description of the data flow, the scope of fields and the retention period. For IT: documentation of the SOAP service, a test environment and a technical account. For security: a list of terminals at the gates and the people responsible for handling deliveries. On the InnerWeb side we support preparing the flow description, but the legal assessment belongs to the data controller.

Video

Frequently asked questions

Could the system fetch another driver's data for an unknown code?

No. A delivery with a completed transport is deliberately treated as no data, because the notice system can return the last completed transport for unknown codes.

Is integration with any notice system ready straight away?

No. Integration works over SOAP and requires implementation work, so we do not promise it with every system without an analysis first.

Can it be verified that a card really does not work?

Yes. Every search is recorded in telemetry with its result, status and response time, so reports can be confirmed with numbers.

Do leading zeros in the code affect the result?

No. The query uses one canonical five-character code, so entering leading zeros does not change the result.

Sources

Let's discuss delivery notice integration

We will go through the card code data flow and the scope of SOAP integration with your IT department and data protection officer.

Let's talk