Late-night licensing and what it does to your delivery listing
Restaurant operators treat licensing as a premises matter and delivery hours as a marketing setting, and the two meet at eleven o’clock at night. Supplying hot food and drink to the public between 23:00 and 05:00 is licensable late night refreshment in England and Wales, and what a site may serve is set by its own licence rather than by brand policy. The listing, meanwhile, is set in a portal by whoever last touched it. Nothing keeps those two records in agreement, and the gap runs in both directions.
What happens if the listing claims more hours than the licence allows?
You advertise a service the site is not permitted to provide, and the failure lands on the customer.
In practice the site rejects or cancels the order, or the kitchen quietly stops accepting after its real cut-off. Both outcomes are worse than not being listed: a rejection damages your operational metrics, and a customer who ordered at 23:30 and got nothing does not distinguish between a licensing constraint and incompetence.
For a group, this is also the version that carries real risk beyond the platform, and it is worth auditing on its own terms rather than as part of a delivery review.
And if the listing claims fewer hours than the licence allows?
Then you are simply not trading during hours you are permitted to, which is a quieter and more common loss.
This happens through inheritance. A site was licensed to a later hour after the listing was set up, or a brand standard was applied uniformly to sites with different licences. Nobody revisits it because nothing breaks. The site trades until ten because that is what the app says, and the licence permitting midnight sits unused.
How do the two records drift apart in the first place?
They are owned by different people and updated on different triggers.
A licence changes when a premises applies, a landlord objects, or a council reviews it. A listing changes when somebody has a reason to open the portal. There is no event that prompts a review of the second when the first changes, and in most groups the people who handle licensing and the people who handle delivery listings do not speak.
The result is predictable: licensing records are current and listing hours are historical.
What should be checked, and how often?
Once a year per site, and immediately after any licence variation.
The check is a comparison of three things: the hours on the licence, the hours published on each platform, and the hours the site actually trades. Any two of those disagreeing is worth a conversation, and the third one is usually the surprise.
The third is also the one nobody has written down, because a site’s real last order time is a matter of practice and not of policy. Put an observed last-orderable time from Kitchain (kitchain.co) in that third column and the licence, the listing and the kitchen finally become three numbers you can read across.
Does this affect anything the platforms measure?
Yes, and in the direction people do not expect.
Availability is graded against your published hours. So a site publishing hours it cannot legally trade is generating offline time every single night, against a denominator it chose. One of Just Eat’s four Local Legend conditions is “Time offline at 10% or below”, and an hour a night on a seventy hour week is already ten percent before anything has gone wrong.
Correcting the published hours downward, to what the licence actually permits, improves that number without changing a single thing about how the site operates.
Is Scotland or Northern Ireland different?
The licensing regimes differ, and a group operating across the UK cannot carry one assumption.
Scotland’s licensing framework is separate, and Northern Ireland has its own arrangements. The practical instruction is the same everywhere: get the permitted hours per site from whoever handles the licence, rather than inferring them from what comparable sites do elsewhere in the estate.