The gate before the change
Picture a production plant with several warehouses and loading docks, where trucks bring raw materials in and leave with finished goods around the clock. Security at the gate checks every driver one by one: they ask for the carrier, the type of operation, the target warehouse and the appointment number, and then retype all of it into a form.
This is a rollout scenario, not a description of one specific client. We describe it because the same pattern repeats in plants that make machinery, packaging or building materials. Manual entry causes three problems: queues at the barrier, typos in carrier names and deliveries assigned to the wrong dock.
The customer's appointment system already knows these details, because the logistics team planned the delivery. What was missing was a bridge between the plan and the gate, where decisions are made in a matter of seconds.
How filling in from the card code works
The Deliveries and appointments module manages vehicles entering the plant: choice of gate, dock or warehouse, driver and closing the delivery. After a visit card code is entered, the system fetches the planned delivery data from the customer's appointment system and pre-fills the form. Security checks the data and confirms it, instead of copying it by hand.
The lookup goes out with one canonical five-character code. If the operator types leading zeros, the result does not change, so different habits between day and night shifts do not cause false rejections.
The card code as the delivery key
The visit card code is a separate field of the delivery and serves as the key linking the delivery in InnerWeb to the record in the customer's appointment system. Thanks to it, you can trace a delivery back to its source record without guessing from the truck registration.
Operation type and service point
The operation type from the appointment, unloading or loading, sets the delivery label. The service point name from the appointment is matched against the gate and dock codes configured in InnerWeb, so the driver is sent straight to the right destination.
Form fields to fill in by hand (example calculation)
What the system does when data is incomplete
Appointments are often incomplete in practice. When an appointment has no carrier, the system inserts a placeholder carrier so the delivery can be created and security does not block the queue. The gaps become visible later in the delivery register, where the logistics team can correct them.
The second case matters more from a GDPR point of view. A delivery with a completed transport in the appointment system is deliberately treated as missing data, because the external system can return the last completed transport for unknown codes. If InnerWeb accepted such an answer, the driver at the gate could be wrongly matched to someone else's delivery, and another person's personal data would appear on the security screen.
Missing data therefore means creating the delivery manually, not guessing. This is a deliberate design decision: one extra form is better than a wrong identification of a person.
Division of responsibilities: who does what
InnerWeb is an independent system that complements the customer's existing systems. We do not manufacture readers or appointment hardware, and we do not replace the appointment system. It remains the source of the delivery plan, while InnerWeb takes over from the gate onwards: the form, dock assignment, navigation and supervision of the vehicle.
The integration with the customer's appointment system runs over SOAP and requires implementation work. We do not promise integration with any appointment system without it. The details agreed with the customer's IT team are described in a separate article on the SOAP integration.
- Customer appointment system: delivery plan, card code, carrier, operation type
- InnerWeb: form on the security terminal, gate and dock codes, delivery supervision
- Security: data verification, decision on entry, choice of navigation for the driver
- Customer IT team: access to the SOAP service, technical accounts, maintenance windows
Effect at the gate and lessons from the rollout
The most important effect is a change in the role of security: from a person retyping data to a person confirming it. The number of fields to fill in by hand drops, and with it the number of errors that later have to be corrected in the register.
The second effect concerns messages. Error messages on the security terminal are shown in 6 interface languages, and the lack of an active transport for a card is reported in the operator's language. The security officer does not have to interpret technical codes.
The third effect is organizational. When delivery data comes from one place, the logistics team and security talk about the same delivery. Disputes about who mistyped the carrier disappear, and their place is taken by data analysis: how many deliveries had complete appointment data, and how many needed manual completion.
Video
Frequently asked questions
Does InnerWeb replace the customer's appointment system?
No. The appointment system remains the source of the delivery plan. InnerWeb fetches data from it using the card code and runs the delivery from the gate to completion.
What happens when the code is not in the appointment system?
The system treats it as missing data, and security creates the delivery by hand. We do not guess a delivery from other records, because that risks wrongly identifying the driver.
Can any appointment system be connected?
We do not promise that without implementation work. The integration runs over SOAP and requires agreements with the appointment system provider and the customer's IT team.
Sources
We will show you the delivery form filled in by card code
Book a call about delivery appointments at your plant. We will go through what data your appointment system provides and what has to be agreed with its provider.
Let's talk