Scubbly is shutting down in 2017

With much deliberation, we have decided that 2017 will be the final year of operation for

When Scubbly was launched in 2009, it really was the “best of class” app of its kind, optimized for simplicity and maximum profit for sellers and affiliates. That is, unfortunately, no longer so.

While Scubbly has attempted to find “economies of scale” to keep delivering maximum benefit to member partners, we have found that the increasing costs of operation are outpacing revenue. The economics are no longer feasible. Given that Scubbly is already charging more than many of the competitors, we decided that rather than price ourselves out of the league, it’s time to shut Scubbly down, as gracefully as possible.

Note the word “gracefully”. We really mean it – we don’t want to just shut everything down immediately to the chagrin of all our users. So we have planned a gradual shutdown timeline that should give all our sellers and affiliates and customers enough of a “runway” to transition their e-commerce to another platform. We will also host redirection of all your Scubbly pages to another URL, while the Scubbly service is in transition.

TL;DR – All Scubbly sales will end April 1; you have until then to move to a different e-commerce platform, and the final payout will be in July.

Here is the detailed timeline of shutting down:

January 1:

  • monthly payout will happen as normal
  • communication to all members, with this announcement
  • sellers should:
    • make sure you have a copy of all your products. Download them from Scubbly if you don’t, by going into the admin tools under the “Files” tab.
    • research other e-commerce platforms, and start setting up shop somewhere else
    • make sure your customers have a way to contact you in case they need assistance
    • inform your customers and affiliates of the change

Once you are set up with a new e-commerce platform, please send “redirection” URLs to Scubbly, so that any traffic coming to your product detail page on Scubbly can be redirected to somewhere else. Send those redirection URLs to us as a spreadsheet (any format will do). The spreadsheet should have two columns: 1) the Scubbly product id, and 2) the URL where it’s being sold now. Send the spreadsheet to

February 1:

  • monthly payout will happen as normal
  • another email communication will be sent to all members, similar to this one
  • Scubbly will take down the “registration” page, so it will no longer accept any new sellers or affiliates signing up
  • every other part of the site will work as usual
  • Web traffic to product detail pages will redirect to the 3rd party URLs if they have been provided. If no redirection URL is provided, Scubbly will show the usual product detail page, just like it does now.
  • sellers should:
    • migrate their business to a new e-commerce platform
    • send a spreadsheet of redirection URLs to

March 1:

  • monthly payout will happen as normal
  • Web traffic to product detail pages will redirect to the 3rd party URLs if they have been provided. If no redirection URL is provided, Scubbly will show the usual product detail page, just like it does now.
  • sellers should:
    • continue migration to a new e-commerce platform
    • send a spreadsheet of redirection URLs to

April 1:

  • monthly payout will happen as normal
  • Scubbly will shut down service to the public, ceasing all sales.
  • Scubbly’s PayPal accounts will no longer accept new transactions from customers
  • Public view of the website will be replaced with a “sorry, we’re closed” message.
  • “Buy now” links will cease to work
  • “Instant link” links will cease to work
  • Widgets will no longer return a response
  • Scubbly blog will be shut down
  • Sign in and seller tools will still be online, so members can see reports and download their files
  • Web traffic to product detail pages will redirect to the 3rd party URLs provided. If no redirection URL is provided, Scubbly will show a 404 Not Found page.
  • the Scubbly “support” email address will be shut off
  • “” address will still work, in case anyone has questions or concerns
  • download tokens will still work for customers who previously purchased products

May 1:

  • monthly payout will happen as normal, for payments that have cleared
  • download tokens will still work for customers who previously purchased products, though by now their tokens will have expired (except in special circumstances where they have been extended longer than 30 days)
  • sellers should:
    • export any reports you want to keep (since there will be no new sales)

June 1:

  • monthly payout will happen as normal, for payments that have cleared
  • download tokens will still work for customers who previously purchased products

July 1:

  • by now, any sales made in March will have cleared, so there is no chance of any chargeback fraud happening.
  • the last payout. ALL balances will be paid out, no matter how small! All account balances will be zero.
  • negative balances will just be ignored (forgiven) and set to zero.
  • download tokens will still work for customers who previously purchased products
  • member area will be shut off
  • “” address will still work for a while, in case anyone has questions or concerns

August 1:

  • downloads will cease to work!
  • all files in storage will be erased, the secure distribution cloud will be emptied and shut off.
  • website will be completely shut down.
  • redirections will stop working
  • all Scubbly email will be shut off

To all our sellers and affiliates, thank you for joining us on this crazy ride. Some of you only joined recently, but others have been with Scubbly for its entire 8 years of existence. It’s been a blast, and I wish you well in your future business endeavours.


Ian Ring

Founder, Owner, Administrator of

Late payout: Jan 3, 2016

Happy New Year!

Well, at least I hope you’re having a good year so far – the January 1 payout was delayed until today, because of some minor health problems here. The payout just went out moments ago to all sellers that were eligible this month. Please accept my apologies for the delay.

You may fairly ask why the payout wasn’t processed automatically at the stroke of midnight of the new year. The truth is, payouts are not an automated process – they are handled manually, personally by me, one at a time to ensure accuracy and care. It typically takes about an hour, and requires diligent attention to detail; something that wasn’t fortuitous in my medicated state for the first two days of this year.

I’m feeling much better now. Here’s wishing you all health and wellness in 2016!

Ian Ring

New Feature: Gift Options!

Launched quietly last week with no fanfare, Scubbly now has a pretty neat new feature for giving a product as a gift. Allow me to explain.

The gifting options at Scubbly are a little different from other online stores, in a way that I think you’ll enjoy, because it’s so easy and flexible.

To give a Scubbly product as a gift, buy the product as usual. Put it in your cart, and check out with PayPal. As with any other Scubbly purchase, you’ll get an email with the download instructions. The email contains your “download token”, which works the same as it always has – click on it, and you’ll arrive at the product download page.

HERE is where you’ll notice something new:

There’s a cool blue button labeled “Click here for gift options”. Go ahead – click it! When you do, this is what pops up:

That’s the new stuff right there. Your purchase generated a “download token” for you, and it also generated a “gift code” – for you to give away. But here’s the important thing: YOU CAN USE ONE OR THE OTHER. NOT BOTH.

If you click “Download” and try to get the product for yourself, the Gift Code will stop working! Likewise, when your recipient uses the Gift Code, your Download Token will cease to work.


So, say you bought a set of knitting patterns for your sister. Find the patterns on Scubbly, buy them, and you get the Download Token by email. From this point, you have many options of how you deliver them:

1) Print’em and Wrap’em.
Use the Download button, and download the patterns. The Gift Code will cease to work. Print the patterns out on some nice paper, put them in a binder, and box them up with a few skeins of wool. DONE LIKE DINNER.

2) Download them and send them as digital files.
You’re a really awesome sibling and you bought your sister a Kobo e-reader, and you upload the knitting patterns onto that before gifting it. LIKE A BOSS.

3) Put the Gift Code, as a link, in an email
But don’t just send it as a link by itself, write something nice. Put some thought into that. Your sister will click the link, and download the patterns herself. KUDOS EARNED.

4) Use that Gift Code in a greeting card
Take that code and print it on a greeting card. Sign that thing. Your sister will need to visit Scubbly’s gift redeeming page and type that code in, but when she does? GIFT ACHIEVEMENT: UNLOCKED.

Whereas Download tokens have an expiry of 30 days, Gift codes last for a full year. You’ll need to retrieve the code within 30 days after buying, but if your sister’s birthday isn’t until April, you’re good. It will work.

I hope you enjoy these new features!


New Feature: sortable products

Hi everyone!

A new feature was launched this evening for sellers. When you’re on a product index page, now you can drag products up and down to change their sequence. This changes the order in which the products will be sorted in your public store. And as before, you can still drag products into another section.




Payout for March 1, 2015

The biggest payout ever! Today Scubbly paid out for sales made before the 60-day clearance period, which means we’re finally getting paid for all those Christmas purchases. Hooray!

Worth noting: After being announced two months ago – and then the one free month with no storage fees – today is the first time that the new storage fee policy was applied. Each seller who has more than 60MB of files in their space will be dinged with a few pennies per hundred megabytes. For most of you it will make no difference at all, for some you might see that the charge was a few cents more or less than usual.

One consequence of the policy change is that right now there are hundreds of accounts that have a negative balance, for the first time ever. These are “dormant” stores set up by people who uploaded a pile of little files, never did any marketing, have not made any sales, have no profit, and were – for the first time today – charged $0.03 or $0.06 this month for their storage. As a result, all those accounts are showing a balance that is a few cents “in the red”.

To those who are currently holding a negative balance – don’t fret! Scubbly is not going to make you pay back a few cents; it’s not worth it. Concentrate on marketing your product, and make some sales. The profit from even a single sale is usually more than enough to cover a few pennies of storage cost.

Accounts that maintain a negative balance for a long time will be handled on a case-by-case basis. If an account has no active products and no profit, but is accumulating storage fees, we’ll contact the seller to discuss the situation. If a seller doesn’t respond to repeated attempts to contact them, we might shut down the account and delete the files.

Congratulations to all the sellers who earned a payout today. Keep up the good work!

New Feature: Sales reported by Country


A great feature was added yesterday. This one was a fantastic suggestion by seller RightBooth, who has a pretty neat software product for setting up a photo booth system. RightBooth is preparing to submit taxes, and discovered that they need to know the country for each buyer, because VAT is applied differently at different rates depending where the buyer lives.

So, as of yesterday, the Country Of Residence – if it is known – is now reported as part of every sale confirmation email. Also, there’s a new report under Account > Stats > Sales, which can show you a summary of the sales you’ve made broken down by country.

On that note, you should already be aware that Scubbly does collect or remit taxes for your store. We have sellers all over the world, and buyers from all over the globe too. The complexity of figuring out taxes that apply between one country and another is an insanely complex problem that would add significant complexity to the software, so we’ve never tackled it. Plus, for the vast majority of Scubbly sellers – who might earn a few hundred or perhaps thousand dollars per year – the income generated is low enough that taxation is irrelevant.

So it is the seller’s responsibility to determine if their Scubbly income is taxable, adjust their prices accordingly so that they can pay their taxes to maintain a legal business in their own jurisdiction. Scubbly tries to provide the reports and data necessary to do that with relative ease. If you find that it’s difficult to get the information you need from the system, feel free to contact us and tell us about it! RightBooth did, and we quickly enhanced the system to deliver the needed data.


Important Announcement: changes to oversize fee calculation

Hello sellers,

The monthly payout just went out, but there were no oversize fees charged. For this month only,  we’re not charging for oversized storage – because we’re in the midst of implementing and communicating a change to the formula we use to calculate the fees.

The previous formula we used was: “$0.03 per 100MB or part thereof in excess of 60MB, per month or part thereof”. This was applied per product – and only to products that had a downloadable file that was greater than 60MB.

What we discovered was that the formula is OK – it adequately covers costs of file storage – but the way we were applying it was unfair. Along with many other changes that happened in early 2014, sellers were given the ability to attach the same files to multiple products, and bundle files in different configurations. The side-effect of that change (and our formula) was that the same large file might incur the oversize fee multiple times.

Applying the fee to individual products also meant that a seller with a single 1GB product would be charged a fee, but someone with a hundred 10MB files would be charged nothing, even though they were both consuming the same amount of storage space.

The new calculation uses the same formula as before, but we’re applying the formula to the sum of all a seller’s files – not to each file individually, nor to each product. That means that sellers that have thousands of small files are no longer getting a free ride – Scubbly will charge the cumulative size of all their storage used. Sellers who bundle the same files into multiple products will be charged only once for that file’s storage.

This change is going into effect exactly a month from today, on March 1, 2015. The wording on the fees page will meanwhile be updated to describe the fee accurately, and an email is going to be sent to all sellers who will be significantly affected by the change.

Ian Ring


Improving fault tolerance, and disaster recovery measures.

Hi Folks,

As promised in December, I’ve figured out why the crash happened in December, why the server didn’t just restart automatically when it went down, and what will be implemented to prevent future incidents of the same sort. I’ll keep the technical details succinct.

The crash was caused by a series of unfortunate events: a memory leak, a password protection on reboot, and the unusual situation that everyone who had the password for rebooting was away on vacation and couldn’t be reached.

There’s an image library at Scubbly that is used to generate thumbnail images of the pictures you upload. That library is known to gobble up RAM and not release it. Over time, the loss of RAM will cause “swapping” to the disk. Swapping is bad. The cure for swapping is a reboot of the web server. It happens rarely, but when it does there’s hardly any service interruption at all. And there’s an automatic process in place with our web host that watches for swapping to trigger a reboot. All that stuff is set up and it’s good.

The failure can be blamed on password protection on the reboot process. Scubbly has authentication measures protecting pretty much everything from being screwed with. So when the web host rebooted the machine that is hosting Scubbly, the system required a password – literally typed in by a human logged in to the machine – before it would restart the web service.

Only one person has that password. That was me, on vacation with my family, at a resort with no wifi where no email could reach me for over a week. As we disembarked in Toronto after a week of sun and mojitos, I switched my phone out of Airplane Mode, that’s when the hundreds of downtime critical alert messages flooded in and I learned that had been in a coma for over three days. All I had to do is go home and type in my password to restart Apache. It took only a few seconds to fix the problem, but it was waiting for several days because of my own unavailability.

If there had been no password impediment (allowing the automatic reboot process to succeed) or if there was another person who could have intervened, then the interruption of service would have been completely avoided.

So. Here are some steps to prevent similar problems in the future. The first will be done immediately:
1) We will use a different authentication signing method to secure our web service, so it doesn’t require a human to be there when rebooting. This way our automated disaster recovery procedures will actually work without intervention. I’ll have that fixed some time in February.

The next two will happen some day, but not immediately:
2) Add some redundancy to the service by starting up a second server with a load balancer. Then if one machine goes kaput with RAM issues, the service will still be available running on other machines.
3) Some day Scubbly will invest in “managed hosting”. Instead of running on self-serviced machines maintained by me, the site will be managed by a hired team of professional geeks with 24/7 customer assistance and immediate incident management. Hosting like that is expensive, but it is where Scubbly is headed.
The impediment for those last two is budgetary – Scubbly will be able to do them when the service is earning enough to cover the increased costs.

That’s all. Once again, please accept my apologies for letting Scubbly flatline like it did.

Ian Ring



New Feature: videos!

Sellers will notice that yesterday a new feature was added: you can embed a YouTube video onto the product detail page.

Many types of products are difficult to describe using words alone. Being able to embed a video on the product detail page means you can deliver a preview to your customers so they can hear and see the product before buying. Video is also a powerful medium for persuasive marketing.

Scubbly has chosen YouTube as our video streaming service. Quite an obvious choice, really; they’re ubiquitous and reliable and have an excellent embedding feature that works on all devices and platforms. To embed video on Scubbly, first you must create a YouTube account, upload the video there, and then get its ID. Go to the new “Video” tab in the product editing tool, enter that ID and save the product.

For an example of a product using video as a Preview, look at this one:



December 13 – 17: Unexpected interruption of service

There was a long and unexpected interruption of service this past week. The interruption was caused by a total system crash of the machine that runs the website, and it occurred at a very unfortunate time, when no person was available to reboot the server for several days. The machine that serves was merely off, and the automated processes that are supposed to turn it back on didn’t do it properly.

Scubbly service was unavailable for approximately 3 days, 11 hours; from Saturday, December 13, 2014 19:43:30 (UTC) until it was manually rebooted at Wednesday, December 17, 2014 7:20:00 (UTC).

During this time, anyone who might have visited the website for any reason would have received either: 1) a timeout attempting to contact the Scubbly server, or possibly 2) a “service unavailable” error.

To sellers and customers, I apologize for the service interruption. We are investigating the reason for the crash, and for the failure to restart the service immediately following the crash. At this time we have no reason to suspect any foul play, and there was no damage to any historical data. All systems are working fine now.

Obviously, 3 days of service interruption is terrible. We want Scubbly to be working as close to 100% of the time as possible. Once we have identified why the crash happened, we will be using that knowledge to design a more fault-tolerant system, or to put processes in place to mitigate or manage “disaster recovery” situations more expediently; this could involve changes to Scubbly in ways that we can’t currently predict; any changes that will affect sellers or customers will be communicated here in the Scubbly blog.

With sincere apologies,
Ian Ring