Custom app development for supplier visits and supply chain signals
Due diligence is judged on what you did after you knew something. That knowledge rarely starts in a questionnaire and usually starts during a visit: someone sees something on a production floor, in a conversation or on the site. What is recorded there, and whether it reaches the file, determines whether you can later show that you acted.
Why the visit is the weak link
Since Omnibus I, the due diligence duty focuses on a company's own operations, subsidiaries and direct business partners, with investigation further down the chain only when there is plausible information about adverse impacts. Member states must transpose it by 26 July 2027 at the latest, and the first group of companies must comply from 26 July 2028.
That wording puts the weight on signals. A questionnaire yields answers that the supplier writes down itself; a visit yields observations that it did not choose. Those observations are exactly what counts later, because they constitute the plausible information the directive refers to.
In practice, they disappear. Someone drives to a factory, sees something that isn't right, makes a note in a notebook or takes a photo on their phone, and doesn't write it up once they're back home. When it comes to accountability, that observation then doesn't exist, even though the organisation did make it. That isn't ill will but a lack of somewhere to put it.
How we build this
The visit is the unit of work here. If what was observed ends up in the file at the moment itself, the rest of your due diligence process has something to build on.
We look at how a visit currently runs, what gets written down and what gets lost along the way. That shapes the design more than the legal framework does.
A hundred-point questionnaire gets skipped through on the road. We build a short structure with room for what doesn't fit the list, because that is usually where the finding is.
Factories outside the EU, sites without guest networks, roaming you don't want to pay for. The app works without a connection and syncs later.
Every observation that needs attention automatically becomes a case with an owner and a deadline by the time you are back home. Without that link, it stays a note.
What the app actually does
The app records what someone sees and makes sure it arrives. Which components you need depends on how often and where you visit.
Visits with a short, fixed structure
A limited number of topics per visit, always with room for free-form observations. A list that is too long gets rushed through and delivers less than a list that is short.
Photo with time and location
A blocked emergency exit, unguarded storage, a shift roster on the wall. Timestamped images are more convincing than a description after the fact when you need to demonstrate accountability.
A finding immediately becomes a case
Anything that needs attention gets an owner and a deadline on the spot and ends up in the same file as the questionnaire. The directive looks at what you did after you knew, and that starts here.
Working fully offline
Visits continue without a connection and are synced later, with each visit showing whether that succeeded. Outside the EU, that is more the rule than the exception.
Sensitive signals handled separately
A report about working conditions can be traceable to a person. It goes into a separate stream with its own permissions, kept apart from the regular visit report.
History per business partner
All visits to the same partner side by side, so you can see whether a finding recurs. One observation is an incident; the same observation three times is a pattern.
Who we build for
Who carries out the visit differs greatly per organisation. Four situations.
Procurement at production sites
Your buyer already goes there for price and lead time. That same visit can serve the due diligence side, as long as recording it takes no more than a few minutes.
Brand owners with changing supply chains
With seasonal purchasing, locations change per collection. A visit history per partner is then more valuable than an annual snapshot, because the partner may be gone next season.
Trade and distribution
You buy from parties who in turn buy from others. Your observations at the direct supplier are what you have; what lies behind that only comes into view when there is a signal about it.
External auditors and inspection bodies
If a third party carries out the visits, you want the findings in your own file and not only in their report. That resembles the approach in an inspection app, with a different assessment framework.
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 the field side of your due diligence file, not a separate administration. What it records goes into the same register as the questionnaire and the risk assessment.
Why Appfront
Accountability is about what you did after you knew
That is why we link an observation to follow-up straight away. A finding without an owner counts against you in an inspection rather than reassuring anyone.
The places that matter have no coverage
We build offline-first. An app that stops working on a factory site delivers nothing in exactly the place where the observation is worth the most.
A signal about people is not an ordinary finding
Reports that can be traced back to an individual or a whistleblower get stricter permissions and separate follow-up.
One file, no second reality
The app writes to the same register as the office side, via integrations. That side is covered on CSDDD software.
Security and privacy
On a device that travels abroad, the risks are different. A phone can be inspected at a border crossing, lost or left behind. That is why we limit what is stored offline on the device to the visits of that moment, and make sure a device can be disconnected remotely without disrupting anyone else's work.
The content also calls for restraint. Findings about working conditions can be traced back to individual employees of your supplier, and those people have no interest in their name being in your system. That is why we separate the observation from the source, give sensitive signals their own permissions model and record who has viewed them. On the evidence side the opposite applies: photo, time and observer should be immutable, because a report that has been amended afterwards proves nothing. 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 supplier visit app
Since Omnibus I, the directive only applies to very large companies, so you are probably indeed not covered. Your customer may well be, and they will then ask you what you know about your own supply chain. If you record your visits, you answer that question with observations rather than a statement.
The actions look similar, the purpose does not. An audit tests against a standard and delivers a verdict; this records what someone has observed, even if it falls outside any standard. It is precisely those free-form observations that make up the plausible information the directive looks at.
That is the most important design requirement, not an objection. If recording takes more than a few minutes, it won't happen, and then you have a system with no content. That is why we keep the structure short and let the app fill in most of it itself: partner, location, time and who was there.
Yes, that is the starting point. Visits, photos and findings are stored locally and synchronised as soon as there is a connection, with the status of each visit visible. Without that, you miss exactly the visits that deliver the most.
They can, and it often delivers more than visits from the Netherlands, because someone on the ground visits more often and speaks the language. Input can be multilingual, with fixed choices instead of free text where possible. You do need to arrange in advance who may see which findings.
It becomes a case with an owner and a deadline in the same register as your information request, so the follow-up is visible. That is exactly what counts when it comes to accountability: not that you found something, but what you did next. The register side is covered on CSDDD software.
That is the other side of the same chain. If you receive the request from a large customer, you answer it from a register; see VSME software. This app is about what you observe yourself at your own suppliers.
That depends on the number of visit types, whether multilingual input is needed and how heavily the app must work offline. The visit with photo and finding is usually quick to get working; the separate flow for sensitive signals and the integrations cost more. We give a substantiated estimate after the discovery phase.
Want to capture the visits that currently disappear?
Ask the buyer who last visited a supplier what struck them, and see where that was written down. That gap is what you lack when you have to demonstrate due diligence. We build this as a standalone app and as part of a broader project, custom app or custom software.