Network Railcard discount on Boundary Zone fares after upcoming price increase

[arb]

I was originally looking specifically at buying a Boundary Zone 6 to Ash Vale ticket, which I'm entering into the forum's journey planner as a journey from Waterloo to Ash Vale, and specifying that I already have an off-peak travelcard. Outward journey on Saturday 15th March (so no minimum fare with the railcard to worry about) at 10:00, return journey on the same date at 16:00. The price offered is £14, with or without the railcard.

Comparing to this coming Saturday (1st March), before the price increases, I'm offered £13.40 without a railcard or £8.90 with the railcard.

Digging deeper, and looking at prices on BRFares, I've looked up Boundary Zone 6 to a variety of different stations, including Guildford, Dorking, Tonbridge and Stevenage. In all cases, it reports "Invalid railcard specified" and lists no fares if you select a network railcard and the fare period after March 2nd.

Is there some rule change about how railcard and boundary zone fares can be combined after the upcoming fare increases?

 

[MrJeeves]

Digging deeper, and looking at prices on BRFares, I've looked up Boundary Zone 6 to a variety of different stations, including Guildford, Dorking, Tonbridge and Stevenage. In all cases, it reports "Invalid railcard specified" and lists no fares if you select a network railcard and the fare period after March 2nd.

RDG have screwed up the fares data because of the Railcard price increases.

They have created new data records for the £35 Railcard pricing, but the "query from" date is set to 2 March, meaning journey planners cannot use these Railcards to discount tickets after 2 March until 2 March. This affects all tickets eligible for these Railcard discounts.

TrainSplit's data has now been reverted to that of yesterday's to restore the correct discounts, and Trainline and some other retailers have seemingly rejected the fares data update or implement the "query from" date differently to us, but various other retailers (such as OnTrack) are affected. It will have to wait for tomorrow for a (hopefully) fixed data file with a different "query from" date.

 

[arb]

Thanks, I can confirm that:

1) TrainSplit is offering me the discount again
2) Investigating further in BRFares, it does affect all tickets, not just Boundary Zone.

And as an added bonus, investigating this had led to me discovering the existence of a cheaper ticket than the one I wanted to buy in the first place, which is valid for the journeys I want to make. So, thanks RDG