Custom age verification software
Appfront builds custom age verification for situations where you need to establish that someone is old enough: online sales, the till, doorstep delivery and access to restricted services. Demonstrably checked, with as little stored data as possible and without needlessly breaking the ordering process. Get in touch.
What is age verification software?
Age verification software establishes that someone has reached an age limit and records that the check took place, without storing more data than necessary. That last point is the heart of the matter: storing a copy of an ID document is both unnecessary and at odds with the principle of data minimisation.
In practice, it is a chain of moments. For an online order, the check happens up front; on delivery, the courier has to establish it again; and at the till, it happens on the shop floor. Each moment involves its own trade-off between certainty, ease of use and the evidence that remains.
Appfront builds this as custom software with integrations to the verification services you choose. If it concerns identification in a financial context, KYC/AML compliance software is the adjacent page.
Store only yes or no
The system records that a check took place and which method was used, not what was on the ID document. Storing less means less risk.
Multiple methods side by side
From an integrated verification service to a check by the courier, each with its own level of certainty, which you set yourself per product group.
No harder than necessary
A verification that breaks the ordering process costs revenue. We design it so that the strictest check is only requested where it is really needed.
Age or identity? Drawing the line
These two are often confused, and the distinction determines how much data you need.
Only the age limit
You don't need to know who someone is, only whether they are old enough. That allows lighter methods and means you hardly need to store anything. Relevant for the sale of age-restricted products, gambling and restricted services.
Establishing who someone is
In financial services, you have to establish and record identity yourself, with screening against sanctions lists. In that case, see KYC/AML compliance software.
Our development process for your verification
The legal question of what you need to demonstrate comes before the technical question of how. Otherwise you build something heavier or lighter than necessary.
We map out which age limits apply to which products or services, at which points in the process checks are required, and what you need to be able to demonstrate afterwards. That last point determines how much you store, and it is almost always less than people think.
We design the verification moments, the methods per level of certainty, the recording of results and the fallback options for people who cannot use the chosen method.
We build in short iterations with automated tests, structured logging and monitoring. You see working versions along the way and steer based on what your team actually needs in practice, rather than on a specification written months ago.
A controlled go-live with validation and a safety net, followed by ongoing management, monitoring and further development as your legal framework or product range changes.
What custom age verification delivers in practice
What you need differs per channel and product range. These are the components that come up most often.
Verification in the ordering process
A check at the right moment in the webshop, linked to the product groups it applies to, with a fallback option so nobody gets stuck.
Check on delivery
A step in the delivery app in which the courier confirms and records that a check has been carried out, including refusal with a reason where applicable.
Multiple methods and levels
From a light-touch check to verification via a linked service or digital identity, configurable per product group or risk level.
Record-keeping without a data mountain
Registration of the fact, the moment, the method and the outcome — not of identity details or document copies.
Till and access
Support for checks on the shop floor, with the same registration so that online and offline come together in a single report.
Reporting and spot checks
Insight into the number of checks, refusals and aborted verifications, plus the evidence you can present during an inspection or mystery shopper visit.
Typical use cases in practice
Age limits apply in more sectors than just alcohol and tobacco.
Webshops selling age-restricted products
Sellers of alcohol, tobacco, fireworks or other products with an age limit, where checks are needed both at ordering and at delivery.
Retail and hospitality
Chains that want to be able to demonstrate checks on the shop floor and see where things structurally go wrong, without holding staff accountable for a single incident.
Gambling and online services
Providers with a hard age limit and regulatory oversight, where the certainty of the method outweighs convenience.
Platforms and marketplaces
Parties that need to keep out providers or users who are too young, and want to do so without asking everyone for proof of identity.
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 we use
We leave the verification itself to specialised services; we build the logic, the recording and the connection to your channels. The exact choice depends on your processes, the systems to be integrated and your hosting preferences. We deliberately choose a stack that your own team can manage and develop further, without dependence on per-user licences.
Why choose Appfront for your age verification?
Appfront builds custom software for a wide range of organisations in the Netherlands. With verification, we start by asking what you actually need to be able to demonstrate. The answer is almost always more modest than the solution people have in mind, and that reduces both risk and drop-off.
We design for data minimisation: recording that a check took place, not what was seen. Data you don't store can't leak — it's the cheapest security measure there is.
On every project we write clear documentation and make sure your own team, or a future supplier, can understand and manage the system. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance. You own the solution and pay no per-user licence.
Also take a look at our broader services around custom software, KYC/AML compliance software and GDPR compliance platforms. Unsure about the approach? Get in touch.
Security and privacy in your verification
Age verification is a prime example of where privacy by design makes the difference. Appfront designs so that identity details never end up in your systems: verification takes place at a specialised service and you receive an outcome, not document data. We build in line with the OWASP ASVS.
What we do record — moment, method, outcome — is needed for your accountability and nothing more. We set retention periods based on what you need to be able to demonstrate, with automatic clean-up afterwards. We document the data flows for your record of processing activities.
More about our approach to security: information security policy and CVD policy.
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access following least privilege
- Audit trail of views and changes
- Secrets in a secure vault, not in code
- Documented data flows for your processing register
- No storage of document copies or identity details
Frequently asked questions about age verification software
Answers to the questions we get asked most often.
It establishes that someone has reached an age limit and records that the check took place, with which method and with what outcome. The aim is demonstrability, not collecting identity details — and in practice the two are often confused.
For establishing an age alone, this is almost never necessary and so almost never permitted; it goes further than the purpose justifies and exposes you to considerable risk. We therefore design so that you record that a check took place, not what was seen. For the legal assessment of your specific situation, we refer you to a specialist.
They differ in certainty: from a self-declaration at a low threshold, through a check on the payment method used, to verification via a specialist service or a digital identity. The heavier the method, the more customers drop off. We therefore design per product group rather than applying one rule to everything.
By placing the check as late as possible in the process, only for the products where it is needed, and by offering a fallback for those who cannot use the chosen method. A verification that affects everyone at the start of the ordering process costs unnecessary revenue.
Delivery is the moment that really matters, because someone else may have placed the order online. The delivery app includes an explicit step in which the courier confirms and records that a check has been carried out, with the option to refuse and record the reason. That record is your evidence.
Yes. The check takes place on the shop floor, but the record can be the same as online, so you get a single view across all channels. That shows where things structurally go wrong, which is a better basis for training than holding people to account for a single incident.
Then you need a fallback route, otherwise you exclude people who are in fact old enough, such as someone without a smartphone or without the required payment method. We always design at least one alternative route, with an equivalent level of certainty.
You buy the verification itself; we build nothing for that. The custom work lies in the logic around it: which products require which check, at what moment in which channel, what you record, what the fallback route looks like and how online and delivery together form one watertight whole. That is exactly what a standalone service does not arrange for you.
Ready to build your age verification?
Tell us which products or services are involved, through which channels you sell and what you need to be able to show in an inspection. We are happy to help think through the scope, integrations and the first version. A no-obligation first conversation gives you a clear picture of the possibilities and whether custom development pays off in your situation.