Magecredit was just Acquired!

The popular eCommerce store credit system I built that worked for the Magento eCommerce platform called Magecredit was just acquired by a German consulting company.

I’d rather not disclose the acquisition amount but I can say that I am very happy with the result.

The acquirer does have technical expertise so I’m confident they will continue work for the current Magecredit clients to improve and grow the product with new features. I will remain available for the next 6 months on an “on-call” basis.

Advertisements

It’s more than a Magento store credit extension…

Last week I announced my latest obsession: Magecredit. Magecredit is a store credit extension for Magento. It all started a few months ago when I decided to tackle the problem that eCommerce stores experience a large amount of refunds in their lifetime. For some stores, this kills their performance. In fact, analysts have seen eCommerce store return rates of up to 25%¹, especially in the clothing industry.  That’s a 1/4 of all sales!

So what are merchants doing right now to combat this issue? Well, they’re basically giving customers back their money and hoping that the customer decides to chose another product… In my calculations I’d consider this a lost customer unless you can find a way to keep the money in your store. From an accounting stance, returns look ugly as well (especially with the credit memo system native to Magento).

Magecredit helps solve these issues. If you can create credit memos and returns that go directly to store credit, you can incentivize customers not only to continue to shop at your store, but to also potentially increase their purchase size (as suggested by Tony Hsieh of Zappos in Delivering Happiness).

The first step of this journey to retaining customer value is to build the store credit extension for Magento. I’m focusing on Magento store owners simply because I know the Magento ecosystem very well and I can keep close to the merchants using store credit in their store so I can learn and adapt the system to be the best that it can be for merchants. Later I’m going to look at implementing the system for Shopify and BigCommerce, and even some of the larger platforms like Demandware.

So you see see, it’s much more than a Magento module to me. Magecredit is about increasing customer happiness and loyalty. I’m excited to see merchants succeed with it on their side.


¹ Old school vs shiny new technology

Magento CMS Tutorial/Reference

I was helping someone learn how to use Magento CMS static blocks and pages and I couldn’t find a great reference. I’ve decided to write my own. 

Pages – Pages are what shows up in the front-end. The URL key is what you use to access the page (yoursite.com/urlkey) and the content is what appears in the page. Title shows up in the title bar. Simple.

Static Blocks – These can be inserted into any page and repeated. For example, if you had a page that had a block of text that you want to appear on another page but you didn’t want to rewrite it and have to sync between both pages then you would want to create a static block and include that static block in each page’s content. The static block si referenced by the Identifier field. Here’s an example of how this would be used. Static blocks and contain other static blocks too. 

Page Content Codes

When working in the Magento CMS you can enter any HTML into the content box, but you can also put in these special things:

  1. Store URLs: {{store url=”path_to_your_media_file_goes_here”}}
  2. Skin Image URLs: {{skin url=”path_to_your_media_file_goes_here”}} 
  3. Media Image URLs: {{media url=”path_to_your_media_file_goes_here”}}
  4. Static Block Content: {{block type=”cms/block” block_id=”page_identifier_goes_here”}}
  5. Other Data Blocks (advanced): {{block type=”module/blockclass” block_id=”choose_a_name” template=”template_file_path”}}

Now I’ll go into a bit more detail:

1. Store URLs
{{store url=”path_to_your_media_file_goes_here“}}

If you want to link to a CMS page or some other page on your site you should use this code.

Example: Click here for customer service

2. Skin Image URLs
{{skin url=”path_to_your_media_file_goes_here“}} 

Skin image urls can be inserted into a page as paths to a skin image or file. These are relative to the skin/frontend/*package*/*theme*/ directory in your website.

Example: Here is a picture of our company logo: <img src=”{{skin url=’images/logo.png’}}” />

3. Media Image URLs
{{media url=”path_to_your_media_file_goes_here“}}

Skin image urls can be inserted into a page path to point to an uploaded image or file. These are relative to the media/ directory of your website.

Example: Here is a picture of a duck: <img src=”{{media url=’ducks/duckpicture.png’}}” /> and click here for a PDF that we created for you.

What’s the difference between skin images and media images?

Great question! Skin images are store layout/theme dependent and may change depending on the store view, but media images are static and don’t care about what theme is currently being displayed to the user. Media images are typically files that are very likely to change over time where skin images 

4. Static Block Content
{{block type=”cms/block” block_id=”page_identifier_goes_here“}}

Static block content can be inserted into the content of one or more pages. This allows you to have repeated content in your pages without having to manage multiple content page coppies every time you make an update.

Example: Here is your navigation menu: {{block type=’cms/block’ block_id=’my_navigation_menu’}}

5. Other Data Blocks (advanced)
{{block type=”module/blockclass” block_id=”choose_a_name” template=”template_file_path}}

If you are coding template files nad custom block classes, you can include any block class as a singleton using this method .The type attribute is the code to create the block class and the block ID is a custom name you can choose for the block. This block name is used in caching sometimes. Finally, the template file path is a reference to the template file from the app/design/frontend/*package*/*theme*/template directory.

TIP: You can also set the the blcok type to core/template to create a simple block that does not have a specific block class.

Example: Here is my footer block content: {{block type=’core/template’ block_id=’footer_block’ template=’page/html/footer.phtml’}}

 

Static_block_within_static_block