Magento – Store information for the link variables to assess & Follow up eMail & Email to order

Reviews are now a significant part of the honesty of an online store. Many shady companies are on the loose and so the customer always suspicious. A confidence-store assessment is thus always an advantage.

Here is also the site of the Hamburg-based company Shopauskunft.de Ltd. & Co. KG. The Hamburg-based company has been 2006 the market and claims to be Germany's biggest online store rating site.

Convenient for the customer or. the evaluator is, that endure no comprehensive registration via can be, but as stated by e-mail and user name (freely selectable) the Bewerung in key criteria such as e.g.. Can deliver user-friendly and delivery.

The application of the shop in the portal is made very easy and fast. The Costs vary from a free Basic Package, which covers the main points and is perfectly adequate for the beginning, bishin for Enterprise package that proud 490 Euros per year and 49 € monthly costs.

After registering you can then evaluate its own customers can shop.

But what is most useful for Magento, to leave the shop rate? Prior to the delivery of the package or. the goods are not usually really worthwhile, but only after the receipt. Thus was called here by a. “Follow Up eMail” Use can be made.

Magento, there are some extension offers. Among other things, one of Ahead Works “Follow Up eMail” for € 199 and one of Lunja “Followup Orders” for € 40. Both are compatible with Magento 1.3 – 1.5.

We work with the extension of Lunja, Coming as this is fully satisfactory and is administered.

After installation of Magento, is in the back end item under a new system > Configuration. This is called “Followup Orders”. There you can quickly and easily, as one would expect from the sale of e-mails is set for the various Store Views ande customers as guests different transaction templates.
These can be created as usual, to then be selected.
Unfortunately I could not, as reported in the manual of the Lunja “several files”, and find I've just created a new mail transaction.
Furthermore-and this is very important- must be set, should be sent to this e-mail how many days. It would indeed be futile, that the email arrives in front of the package. This is also adjustable to store view, so that international mail go out later.

In this transaction, mail should now be a link, Store responds to the information. The customer should then click on this link and is then automatically routed to the portal. Pleasant is, that you can give to some variables, so that the customer must not enter everything yourself. An example of this link is:

https://www.shopauskunft.de / ecms.php?page=appraisal_new&pv[haendlerID]=[IhreKundennummer]&pv[Order]={{var order.increment_id}}&pv[email]={{var order.customer_email}}&pv[orderDate]={{var order.getCreatedAtFormated('short')}}

With this link (after replacing [IhreKundennummer]) will be brought by clicking on the link to shop for information and automatically you're in the right shop depreciation area, The order number was used as well as customers email and order date.

This link works for guests as well as customers.

UPDATE vom 01.08.2011:

After some back and forth with the extension of Lunja, Today we have once familiarized with the extension of Works Ahead. The problem with Lunjas extension was, that we work with an external system, the orders and then the status in this “Completely” changes. This happens directly via the interface and thus the extension has not “noted”. If the processing of the order via the shop handled directly, everything went well.

But the extension of Works Ahead: 199$ is of course another and whistles as the scarce 70 $(!) der Lunja Extension. But they also offers MUCH more. Lunjas extension has what it promises.
Works Ahead extension provides a relatively wide range. Thus, possible functions include the following:

eMail (user definable template from transactional emails) after

• all different Bestellstati
• Birthday
• certain goods basket values
• certain articles
• some stores
• specific customer groups
• certain categories (or. Categories can be excluded)
• Newsletter subscribers (Ja / No)

Furthermore, can be automatically generated and inserted according to the definition of vouchers (Birthday, etc.). These are in addition (as desired) also be limited in the validity.

In summary, a number of occasions and rules defined, so that this extension is definitely worth the money. Who just a follow up email searches and extension does not change with external interfaces states, But definitely good advice with Lunjas Extension.

Both programmers you as a customer in good hands and gets good support for questions.

UPDATE vom 09.08.2011:

I just noticed the following on: The Followup someone writes Extension Works Ahead of all data from the mail log (sent and emails waiting to be sent) in the database. There in the table aw_followup_queue. If you determine, therefore,, that there is a bug in the email rule or in the associated transactional email, brings a change just for emails FUTURE. All emails already waiting to be manually changed in the database. It is also important to know, that the variables had BEFORE the entry in the database must be properly. So there is nothing, Use variables in the email in the DB. It must be directly controlled by the variable use of the text used gewesene.

Used in Magento versions 1.4.1.1 and 1.5.1.0 Comments? Additions? Notes? Gladly!

UPDATE vom 13.08.2013:

Zwischen Magento 1.4 und Magento 1.5 f.f. scheint es eine Umstellung im Zeitformat gegeben zu haben. In Magento 1.4 wurde bei der Datums Variablen “short” nur das Datum ausgegeben. Bei Magento 1.5 und folgenden wird hingegen nach dem Datum auch noch eine Zeitangabe miterstellt. Shopauskunft möchte diese Zeitangabe aber nicht haben, sondern nur das Datum. Daher kann die o.g. Variable für die Zeit leider nicht mehr so verwendet werden.

Ich habe aktuell jedoch keine Zeit, to look, wie man die Variable so umbaut, dass wirklich nur das Datum übertragen wird, Therefore, I have the area

&pv[orderDate]={{var order.getCreatedAtFormated('short')}}

completely omitted.

Maybe someone has a solution?