With the freight, not in the office Documents via DMS Works offline

Custom app development for paper documents in customs shipments

The paperwork for a customs shipment originates on the dock: a consignment note, a certificate the driver brings along, a seal that is or isn't intact. Right now that travels as a photo in a chat group or a pile on a desk, and it reaches the declaration hours later. Since May 2026 those documents have to come in via DMS, and a chat group is no longer a route.

Why the dock is the starting point

A customs declaration needs supporting evidence: invoices, certificates of origin, licences and transport documents. Since mid-May 2026, declarants have to submit those documents directly via DMS rather than by email. That changes where the document has to end up and who is responsible for it.

Some of that paperwork doesn't originate in the office. A driver brings a document, a seal turns out to be broken on arrival, a pallet differs from the packing slip. Those moments happen at the dock and are currently captured with a phone photo that gets forwarded by message.

That worked as long as there was a mailbox where everything came together. Now that the document has to be linked to a declaration with the right type and the right number, a loose photo is only half the job: someone in the office still has to work out which shipment it belongs to and what type it is.

If you work under a simplified procedure, booking in a shipment is itself the declaration. That is a different action at a different moment; see the app for entry in the declarant's records on receipt.

How we build this

The shipment is the unit here. If a document is captured against the shipment the moment it's in hand, submitting it becomes a technical step.

1
Walking the dock with you

We look at which paperwork comes in, who accepts it and what happens to it. At most companies there are three routes and nobody has the overview.

2
Capture against the shipment, not separately

Scan the shipment or the licence plate, photograph the document, choose the type. Three actions, and the link is made straight away.

3
Findings as their own category

A broken seal or a differing quantity isn't a document but an observation with consequences for the declaration. We deliberately keep these separate.

4
Passing it on to the declaration

What has been captured ends up with the declaration it belongs to, ready to be submitted via DMS.

What the app actually does

The app does little, and that little has to work on a dock. Which components you need depends on how much paper physically comes in.

Recognise the shipment without searching

Scan the consignment note, the container number or the licence plate and the app knows which shipment it is. Choosing from a list leads to the wrong link at volume.

Capture a document with type and number

A photo of the document, the type, and the number where possible. That last part is exactly what DMS asks for and what a loose photo lacks.

Seal and quantity as a finding

A broken seal, a differing number of packages, damage to the cargo. That isn't a document but an observation with consequences, and it gets its own route with an owner.

Working fully offline

At a dock, in a warehouse or at a terminal, the network drops out. Capturing carries on with the actual timestamp and syncs afterwards.

See what is still missing

For each shipment, which documents are present and which are expected. That is the question that otherwise only gets asked at the office, once the driver has already left.

Passing it on to the declaration

What has been captured reaches the declaration via integrations. That side is covered on DMS software.

Who we build for

How much paper physically arrives determines the gain. Four situations.

Warehouses and cross-docking

Many shipments a day and many drivers bringing something with them. Scanning the shipment is what makes the difference here between a linked document and a photo in a group chat.

Freight forwarders with their own warehouse

You handle both the declaration and the physical handling. The gain is then twofold: fewer follow-up queries and fewer declarations waiting on a document.

Manufacturing with its own imports

Few shipments, but special arrangements and certificates. Here it is less about volume and more about getting the right paper with the right shipment.

E-commerce with returns flows

Returns from third countries bring their own documentation. That is the flow where the administration is usually set up worst; see also international e-commerce software.

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

The app is an input channel for your declaration process, not a declaration system. What it captures ends up in the administration from which the declaration and its submission follow.

React Native or native iOS and Android Offline storage with the actual timestamp Scan of consignment note, container or licence plate Photo with document type and number Findings with an owner and a consequence Overview of missing documents Integration with your declaration or forwarding system Integration with TMS or WMS Works with gloves on and in bright light Roles per location and per client Tamper-proof recording of image and timestamp Remote management of the device Audit logging per action Hosting in the EU

Why Appfront

A loose photo is only half the job

Now that documents have to go through DMS, the type and number matter. We have people choose these at the moment of capture, because sorting it out afterwards costs more.

Linking by scanning, not by selecting

At volume, picking from a list leads to the wrong shipment. We build the recognition on what is printed on the paper or the container.

At a dock there is no signal

Offline is the starting point. An app that stalls there gets replaced by the phone in the pocket, and then nothing is linked.

You would rather see missing paperwork now

For each shipment, we show what is still expected while the driver is still there. At the office, that becomes a phone call to someone who has already left.

Security and privacy

A device at a dock holds data about shipments, clients and values. If you work for several clients, they must not see each other's shipments, not even by chance in an overview. We therefore set permissions per client and per location, limit offline storage to the shipments of that shift, and make sure a lost device can be disconnected remotely.

On the evidence side, the photo is the document. In an after-the-fact inspection, the question is which document belonged to the declaration at the time, and an image that may have been replaced later does not answer it. We therefore record image, timestamp and employee in a tamper-proof way, and make a replacement a visible replacement alongside the original. The same goes for a finding about a seal: that is an observation with possible consequences for the declaration, and it must not be able to disappear quietly. How we handle security ourselves is set out in our information security policy; reports from outside go through our CVD policy.

Frequently asked questions about the customs app

No, and that's deliberate. The app records the document and links it to the shipment; filing is done from your declaration system or by your freight forwarder. That keeps responsibility for the declaration where it belongs, and the dock worker doesn't need to know anything about DMS.

Because since mid-May 2026, documents for a customs declaration must be submitted directly via DMS rather than by email. A photo in a chat group or an email to a shared mailbox is no longer a valid route; the document has to be attached to the right declaration with the right type.

Yes, that is the starting point. Photo, integration and finding are stored locally with the actual timestamp and synchronised as soon as there is a connection. In warehouses and at terminals, having no signal is the normal situation.

That is a finding rather than a document, with possible consequences for the declaration and sometimes a duty to report to Customs. We therefore give it its own route with an owner and a deadline, instead of letting it end up as a photo among the other documents.

They can, but it is rarely a good idea. A driver works for another party, and you don't want shipment data on their device. What does work is having your own employee accept and record the document while the driver is still there.

No. Your forwarding or declaration system stays; we build the input channel for it. Two sets of records for the same shipment are bound to drift apart, and with customs that difference is hard to explain later.

This app covers the physical side: paper and findings at the cargo. The DMS software deals with the declaration data set, the permits and the statuses after filing. They share a single shipment record.

That depends on the number of sites, which scanning approach suits your shipments and which system it needs to integrate with. Capturing documents with a scan and document type is usually usable quickly; the overview of missing documents takes more work. We give a well-founded estimate after the discovery phase.

Linking paper where it arrives?

Count how many customs documents from last week ended up as a photo in a chat or mailbox. That number now has to be attached to a declaration via DMS. We build this as a standalone app and as part of a broader custom app or custom software project.

Edit content