Capture on the floor Scan instead of retyping Works without a signal

Custom app development for goods flow and customs documents on site

Your records must make the origin and destination of the goods easy to trace. That sounds like an accounting requirement, but it isn't. It starts on the loading floor, with the question of which pallet came from which container and where it was put down afterwards.

Appfront
Live

Where the trail breaks in practice

A licence holder keeps records in a form approved by Customs, showing the identification, customs status and transfer of the goods under the procedure. In an audit after import or export, this is what gets checked: not what happened, but what was recorded of it.

The trail rarely breaks in the system. It breaks on the floor, where a shipment is unloaded while the next lorry is already waiting, where a pallet is temporarily put down somewhere else, or where a document did arrive but is only booked in the next day.

If you act as a fiscal representative, you have a direct interest in this. Liability for the client's VAT is capped per calendar year by the security provided, but that ceiling only helps if the file can follow the shipment. A gap in the trail is a gap in your defence.

The retention period is seven years. Data may be moved to other storage media as long as it remains accessible to supervisors within a reasonable time. What starts on a paper list and ends up in a folder rarely meets that requirement, even if it has formally been kept.

How we build this

The core is the movement. Every time goods arrive, move or leave somewhere, a record is created with a time, a place and a person.

1
Scan instead of retyping

Container, seal, pallet or document: anything with a code gets scanned, so the data entered is correct and quick.

2
Record the movement

Arrival, unloading, moves within the site and dispatch, each with a time and place, even without a connection.

3
A photo of the exception

Damaged packaging, a discrepancy in quantity or a missing document: a photo taken at that moment saves an argument later.

4
Passing it on to the finance team

The movements land in the file per shipment and per client, which is what the declaration and the accountability rest on.

What the app actually does

Registration on the floor carries the whole process. What else you need depends on your scheme and on whether you run a customs warehouse yourself.

Scan container and seal

On arrival, record the number and the seal, including the moment the seal was broken.

Unloading per pallet

What actually came out, compared with what was on paper. That difference is exactly what you will be asked about later.

Location in the warehouse

Where something was put down, and where it went next. Without that, the transfer cannot be demonstrated.

Photograph the document

Waybills and accompanying documents go into the file as images, at the moment they arrive.

Works without signal

Warehouses, terminals and cold stores rarely have coverage. The app works locally and syncs as soon as there is a connection.

Escalate a deviation straight away

A missing document or a difference in quantity goes straight to the customs declarant, with a photo and timestamp.

Who we build for

Who does the registration differs per site. Four situations.

Warehouse staff

They unload under time pressure. Anything that takes more than a few actions gets done at the end of the shift or not at all.

Customs warehouse keepers

They must be able to demonstrate the status and location of goods under the scheme, even months later.

Drivers

They are often the only ones who see what was really in the cargo space on arrival.

Declarants and customs agents

They submit the declaration and don't want to phone around to find out what happened on the floor.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

Schemes differ, document types get added and sites are laid out differently. Fields, codes and movement types should be configurable rather than fixed in the app.

React Native or native iOS and Android Offline storage with synchronisation Barcode and container code scanner Photo with time and place Configurable movement types per scheme Location structure of your warehouse Works with gloves on and at a distance Roles for warehouse, declarant and management Integration with your administration History per shipment and per pallet

Why Appfront

The trail breaks on the floor, not in the system

We build the registration where the movement happens, because what is not captured there is not created anywhere else.

Scanning is faster than typing

A scanned container number is not only entered faster, it is entered correctly. That prevents most corrections.

Accessible for seven years is more than stored

The requirement is that data is available to the authorities within a reasonable time. A folder in an archive rarely meets that.

We do not file declarations for you

The customs-technical judgement stays with your declarant. We make sure the facts he relies on are correct.

Security and privacy

What is recorded on the floor touches on your clients' commercial data: suppliers, customers and volumes. We set access per role and per site, show an employee only the shipments they work on, and log every access. Data stored locally on the device is encrypted and can be wiped remotely if a device is lost.

For this subject, the reliability of the moment is the point. An unloading whose timestamp was changed afterwards is no longer a record at an inspection but a reconstruction. We record movements immutably with time, place and person, even when synchronisation happens later, and turn a correction into a visible correction alongside the original line. How we handle security ourselves is set out in our information security policy.

Frequently asked questions about recording goods movements

Because the record is created at the container and at the pallet, not at a fixed workstation. Anything entered after the shift is a recollection.

The identification, the customs status and the transfer of the goods under the procedure. In practice that comes down to: which goods, which status, and where they have been.

Yes. Warehouses, terminals and cold stores rarely have coverage. The app works locally and syncs as soon as a connection is available again, keeping the original timestamp.

The retention period on the customs side is seven years. Data may be moved to another archive, as long as it remains accessible for supervision within a reasonable period.

In the file per shipment and per client. We describe those records on our page about software for fiscal representatives.

Yes. The movements can be passed on to your declaration or warehouse system. See our approach to building an app.

Can you prove where this pallet was three months ago?

Take one shipment from the previous quarter and trace its route: arrival, unloading, place in the warehouse, dispatch. If a gap remains, that gap will also show up during an inspection. We build this as a standalone app and as part of a broader app development project.

Edit content