Old software? It's difficult enough to find documentation on the current Oracle database. You only get random versions through a search engine, and can neither navigate into a different one, nor replace the version on the URL and get to a functioning page. Also, you can't start from the top and try to follow the table of contents because it's completely different.
Under the rail franchise agreement during the bid process, the terms might mandate that journeys from A to B cost £10, and that journeys from B to C cost £5. There might be no obligation to price travel from A to D via B & C at a particular cost, so a rail operator might make that more expensive.
It’s silly from the consumer perspective, but it makes sense for the rail operators to do this in order to maximise profits.
Thanks for the explanation. I had the wrong idea that it could be due to, for example, if A->B belonged to a different provider than B->C, providers not reaching an agreement on what % to take each, for the journey from A->C - hence increasing the overall cost for covering demands from both.
No problem! You are right that it’s silly though, you shouldn’t have to split your ticket to get the lowest cost.
In real terms the main reason is to protect commuters and capacity - as a theoretical made-up example during the bid process they might be aware that lots of people travel from Milton Keynes to London so the council wants to put a cap on increases for that route. They might also still have lots of capacity on the route from Banbury to Milton Keynes on a morning, so that is priced much lower than Banbury to London. So if you go Banbury -> Milton Keynes you might get a “discount” for not a lot of people using the line, and travelling from Milton Keynes -> London you get the rate that’s protected for commuters, but if you go between Banbury and London then part of the route is already at capacity and there is less discount on the rate.
No, there's long been a centralised system to attribute the costs to different companies (IIRC, the system is ultimately the descendant of what the British Rail regions and later sectors used to split fare revenue between them).
There's no negotiations between the companies here, though they could ask the regulator (the ORR) to intervene if they believed the algorithm gave unfair results.
I feel you. Unfortunately, I don't think GDPR will be of much help on that case. A fine of up to 1% of they're revenue will hardly make a dent - it's just another tax. Misbehaviour will be still worth it.
Actually GDPR is of great help to them, by putting smaller competitors away from using similar techniques. For those, a 1% revenue is a lot.
In the UK, JustEat takes 30% of the order, same as UberEats, with 0 liability - if something goes wrong with the order, including problems with delivery time, driver taking a nibble, the restaurant just doesn't get paid. Deliveroo is a bit greedier and takes 35%.
It's definitely not the lack of competition... it's just that the competition doesn't behave much better compared to them.
Interesting to hear that Just-Eat acts this way; Takeaway (Thuisbezorgd) has similar practices in NL.
They take no liability on anything (delivery delays, food problems, missing items, etc). They have no customer care number, and take days to respond to emails. If anything goes wrong, they make you call the restaurant, and of course they redirect you back to Tkwy. In the end, you will receive no refund, none of the missing food, and have waited 1-3hrs for an order that should've taken <1hr.
It's a horrible experience, but they get away with it because they have a near-monopoly. Uber Eats & Deliveroo have <25% of the restaurants on Tkwy.
