Cafeen
DIS Veteran
- Joined
- Jul 24, 2009
Let's use some numbers to illustrate. Much easier for me than trying to put it into words.Honestly, I don't follow what you're saying, at all. lol. Totally lost me. While it's true that you have to add the dining plan for the whole stay, the price per day is still the most meaningful price. They give the hotel price for each night (try booking a room only reservation, and it tells you the price being charged for each night).
Let's say you have a 7night, 8 day trip. DDP for this trip would run you ~$53*7 or $371. So this is what the difference would show on your trip via only the online reservation thingy and a calculator.
So, let's eat, each item is a per day total, they are random and only used for this illustration.
| 17 | 39 | 65 | 50 | 45 | 72 | 60 | 36 | (that's 8 days, 7 nights)
So, going day by day, we'll combine the first and last, since they were half days. So that's a flat $53.
We're short on day 2, high on day 3, short on day 4, short on day 5, high on day 6, high on day 7, even on day 1+8. What does this tell you overall? Does this suggest to you if you'll save money overall without doing any further math? From an averages standpoint, it's tough to tell, since we're short 3 nights, high 3 nights, and break even the 7th.
17+39+65+50+45+72+60+36 = $384
Compare this to $371 and we see we're saving $13 (yeah, it's not much, I tossed random numbers in there).
However, since it's addition, there's more than one way to get here.
(17 + 36) - 53 = 0
39 - 53 = -14
65 - 53 = 12
50 - 53 = -3
45 - 53 = -8
72 - 53 = 19
60 - 53 = 7
-14+12+(-3)+(-8)+19+7 = 13
So it works, it's just a bit more roundabout. The trick is, it doesn't matter if an individual day is over or under, what matters is that the final total is over or under. This is why the daily breakdown is unimportant in estimating if the dining plan is a good choice. It also allows for far greater freedom, as you're not worried if each meal makes the daily total, but rather then whole trip makes the entire trip's total.
I wasn't citing certain reasons, only possibilities. I don't trust the Disney web developers any more than I can throw them (and, since I'm a computer nerd, I couldn't throw them very far). I don't trust that they did it the "right" way the first time. Yes, they programmed this feature for tickets. That doesn't mean it can accept dining plan information, and that doesn't mean that they wouldn't have to rewrite core functionality of that page to insert this in.Funny you should mention ticket prices -- Disney certainly announces the prices, as they did publicly, recently. If buying tickets alone, the website lists the total price, AND the per day price. If being added to a package, it neatly lists the plus/minus effect of any change to the selected ticket. (You don't have to wait to see a new total).
If this can be done with ticket prices, there is no reason you can't apply the exact same technology to the dining plan. Whether listed per day or total... Instead of adding the DDP, and then seeing the price effect. (And then having to re-do it again, if you want to compare the other dining plans), There is no reason it can't simply calculate, "Add the QSDP for $200. Add the DDP for $300. Add the DxDP for $400" (Hypothetical numbers of course).
See, now you're getting into my territory . I know well the development cycle of web applications. I know all too well how the system in general works. I also know a thing or two about developing itself.
Depending on the technology that the site is written in, it could be very well that the function that drives the ticket display cannot drive a DDP display. Due to the different inputs (# of people, ages, length of stay) you couldn't just toss it in there, change the daily price, and you're good to go. It would have to be a very different function.
That's not to say it would be difficult to do, but it could very well affect core functionality of the site, something they weren't willing to risk. Since I don't know in particular how the Disney site is setup, I can't guess, but when adding something new, there's always a chance of catastrophically breaking something old. Even if the two features seem wholly unrelated!
Of course, developers also work by feature requirements. These state in clear business rules what the feature is supposed to do, and what it is not supposed to do (in some cases). If the DDP calculation was not in the requirements, it's not getting into the application. Depending on the company, adding something that's not in the requirements takes time, as they have to weigh it against other projects, features, and insure that they aren't going to break existing functionality as much as possible. (And then all the testing, sending it back and forth, beta testing, and then finally releasing that's done after all that).
It's a little more than just typing the equation out in Excel.
I did. It only let me go back to 2011 (I did it after I wrote that too, but that's beside the point ). There is no query string or subfolder (which is likely a masked query string) for the other years. It simply stays at that linked page and only allows 2011 and 2012.Partially, I'll ask you to trust my memory. But the part about the package comparison website is easily verifiable.... Disney is still using the same URL as past years... Go use the waybackmachine ... and you can see that they used to actually provide side by side pricing comparisons, and they no longer do so.
To be fair, I've seen bugs cause things like this as well. (Hey, I do QA, I blame the devs ALL the time!).
Sounds like you did get your answer. It makes perfect sense and I'd be led to believe that you weren't the only one to notice. Instead of having to update a static page (or pages) every time it changed, they felt it better to remove it overall.The reason I remember it so well--
I booked a Disney vacation last year, shortly after package pricing was released. It was before I discovered all the information on this website. I *know* the website said that the DDP was under $42 per person. I didn't take out a calculator to see if that's what I was actually charged down to the penny. I truly and honestly believed that I had actually paid $42 per adult for a 2011 package.
I then discovered this message board... I discovered that the dining plan price was actually $47. For my party, it ended up being a price difference of over $100. I had come communications with Disney.... First they maintained that I was charged the right amount, but that it was a package, so there really was no per night charge, etc, etc. Then, after consulting with their legal department, marketing department, and website department...They apologized... gave me a refund... and basically said that they just hadn't gotten around to updating the price on their website *yet.* And that same day... instead of updating the price on their website, they simply deleted it instead.
And since that day, no pricing information has been offered.
Not sure why you kept asking for the answer, looks like you had it all along.
Again, simply more possibilities. The presence of too many numbers on screen can easily confuse those with less than stellar math skills. I know, I hear about it whenever I post! (jk). That's all that possibility was based on, nothing more.I'm sure it does involve market research! But the point of all market research.. It's not so they can avoid people getting confused. The point of market research is to increase sales. Thus, I am fairly confident.. they they have found, if they prominently display the current price-- They will be sell less, than by burying the price.
If the DDP was a GREAT bargain.... 2 table service meals per day for only $29.99 (for example), do you have any doubt that Disney would be shouting out the pricing information?
Yes and no. Both reading the fine print and doing research are parts of being a responsible consumer, that's absolutely true. I see this more of a "know what you're getting going in" than a "ooh, what's that little line say about it being invalid on the 2nd Tuesday of the month?"I'd say it's a pretty similar responsibility --- The responsibility to read the fine print, versus the responsibility to pull out a calculator and computer the package with and without dining plan, and break down the cost yourself.
If you're doing to spend $20,000 on a car.. you should read the fine print. But how many people read every single fine print line in the sales contract? How many people then read every line of fine print in the owner's manual before completing the purchase?
Back to the camera example. There was no fine print there, nor even anything that can be analogous to it. Maybe the "your experience may vary", from the reviews, but that can be said for everything. It's more about figuring out what's best for your situation (which camera should I get?) and taking as much advantage as you can (within the legal and moral rules of course) of it (where can I find the best kit, price, shipping?). The DDP works much the same way. Which plan should I get? How can I best utilize the plan that fits me?
And that, I totally agree with . As well as the idea that as long as this discussion keeps going and keeps people thinking about making the DDP work (or letting it not work) for them, alls the better.I don't think we have any major disagreement. I am not condemning Disney to burn in the afterlife. I am not suggesting that the CEO should be locked away for the rest of his natural life.
I am simply saying they *should* state the pricing in a straight forward way, and make it easier for people to assess whether the dining plan is worthwhile for them. I'm not saying that Disney has to provide the spreadsheet you have created, but simply list the price.
(If we keep this up, we're going to break the database with extremely long, text-laden posts )