Skip to main content

What happens to denied rebate claims

You go to the store, you purchase a thing, you download and print the rebate form, you cut out the UPC code, fill out the form, copy the receipt, package it all up and send it to the rebate processor or manufacturer.

Sometimes the manufacturer uses a rebate clearing house that keeps tabs on the process and offers feedback. Sometimes you simply have to wait for the check or the dreaded decline letter.

But what happens when you are declined? On the one-hand the reason you were being offered the rebate was so that the company can capture purchase and personal information about you. And you get cash in return for your personal information. It's a contract stupid.

But what happens when you're declined?

Does the company still claim and get access to your personal information? Does the 3rd party processor get to keep and resell your information? Or, once there is a decline, the processor or company quietly deletes your information after sending you an decline letter? And what sort of arbitration is there?

My advice, forget the rebates and forget that model. Chances are better than even that the seller, or "the house" if you're in a casino, is making bets; and given that they know more than you... chances are it's a loser.

  • forget the rebates
  • ignore products with rebates
  • know your products and model numbers
  • comparison shop
And there was some advice I received once. Check the model numbers on google and if the results are biased to one seller or even some particular promotion then stay away from it. It's likely bait; meaning inferior features or components.

Then again, unless you're an early adopter stay away from full retail.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…