30knees

Great idea! I wanted to test the voucher for review rule, but I get "Failed to load rule" when I click on it after adding it. Do you have an idea why this might be?

@FactorThank you! Now it works. In the meantime I ran the core updater again. It didn't find anything to change, however. No idea what caused the temporary issue, but thanks for the nudge to check again. 🙂

Ah, really? So they always need to be matched. That's not the case now with all my emails. Then, together with the other answers, it sounds like the best way would be to keep everything very simple, have a text version I then use a WYSIWIG editor to make into a lookalike html email, and use that. Thanks @dynambeeand @Factor!

But isn't that quite a niche thing? I'm not saying it's a bad idea, I'm only mindful of whether it would be a significant attractor.

Maybe, and I could imagine this would help also to show that tb is actively being developed, we could have two demo installations on the website: bleeding edge (with latest update date) and stable.

Generally, I want to use text emails only because then I only have to maintain one set of emails. However, for some emails, like @datakick's great Revws module, I would like to use HTML emails because it's easier for a customer to click on the rating right in the email. I thought I could achieve this by: having the setting "send both html and text" activated deleting the html email templates and leaving only the text email templates, except for those emails that should use HTML This didn't work because then no email was sent. Then I tried to copy the txt content into the html content (so leaving out all the html formatting), but that looked horrible because the email was interpreted as not having any line breaks, etc because of the lack of HTML. 🙂 Does anybody have an idea how to achieve what I am looking for? Otherwise I'll just copy and paste my text into a WYSIWIG email creator and use that.

They show up under Customers>Shopping carts but I can't transform them to orders. Any idea where I can look to troubleshoot?

Hi, I updated to the bleeding edge and now I am unable to manually create an order in the backend. Nothing happens when I click to add the selected products to the cart. Could somebody using the bleeding edge please check whether they can manually create an order? Thanks

Ah, but I see that after the Revws update that shows up as a trigger (I used the wrong terminology when I wrote "record type"). Great integration!

That's great! I don't use push, so I can't tell you, unfortunately.

Those are brilliant actions! So cool, looking forward to implementing. Thank you! p.s. Would "Revws review" as a record type make sense to add (or I just didn't see it)?

No problems, I'm very happy. Fingers crossed they accept you!

You already have experience with Mailcow. You could go with a managed Mailcow https://servercow.de/mailcow#managed or a simple Mailcow: https://servercow.de/mailcow#hosted Support is fantastic. I really like being there. I don't see anything in English, but drop them a note: https://servercow.de/kontakt I'm sure it shouldn't be a problem. Fastmail is indeed another great option. I second @Brent Dacus.

Just a note that this happened again. I have a Paypal paid order that isn't in the shop. Paypal shows order number 123 but the store order number 123 belongs to a manually created order 123. Both orders were placed approximately at the same time. I guess some fluke meeting of orders?

I thought this was reported already but I couldn't find it. When a product or variant is added to an order manually in the backend with a quantity of x, the stock of that product is deducted by 2x. So if 2 is added, then 4 is deducted, etc. This also works in the thirtybees demo.

The VAT exemption module drops VAT based on the billing address only. Can it take the shipping address into consideration, too? Problem: For an EU-located store, a customer can add a (real or fake) billing address in Switzerland, a shipping address in Germany, and then get the order without VAT. This is a problem because in that scenario the customer would actually need to present the invoice to customs when crossing the border from Germany to Switzerland, get the invoice stamped, and send the shop a copy. Otherwise, the shop will be liable for the VAT that wasn't collected. Proposal: If the shipping address is NOT in a country where VAT shouldn't be charged, the order should always include VAT. If a customer presents a stamped invoice the shop can still refund the VAT.

Oh, I see. I'm very curious about the gamification part. Your shop is perfect for it. Ours is food.

Oh, I'd have thought you'd use it in your own shop! 🙂 But yes, the button should be fine.

Would it be easy to have the coins used automatically? I realize things are mostly much more complex on the inside than they seem to be from the outside for a non-coder. But a big fat button should also do the trick. 🙂

That's a good point. However, for this scenario to actually take place in my shop, the new order would have to be <5% of the previous order. That is *highly* unlikely. I don't know how likely it would be for other merchants, but I would guess that a single expiry of points coins would only lead to problems in the rarest of cases.

But isn't that the same principle? The main idea is that you need to place an order within a certain time period. And you never accumulate more coins than you spend because they're always automatically applied to the next order.

@wakabayashiThe native module has a validity period setting, see below. The idea is that the coins a customer gets give a discount on their next order, if placed within the validity period. So in my case below, if the customer orders again within 180 days, they get a 5%-of-the-previous-order discount on the new order. If they don't, the points expire and there's no discount. I came across this in another store and found it a quite strong motivator to order again.

The stats module already has best selling products (though unfortunately not by variant). It also knows the stock levels. Would it be possible to have a simple stock predictor that takes eg sales over the last 90 days, checks against current stock level, and predicts how long the stock will last?

The manual is really great! I also like the flexibility of adding different triggers. Especially awarding points for reviews is awesome. I scrolled through the early posts and remembered we talked about expiring points and sending an email to the customer eg 30 days before their points expire. You said it's quite difficult to implement. That's one of the main elements I want to use to get customers to come back to our store, so I'm thinking about either staying with the native module and Consequences or whether I can somehow get the same result with Krona and Consequences via Customer Groups. Another possibility: Use native and Krona together: Krona to award points for reviews, where these points don't expire, and native for expiring points for orders. I'll think about it some more.

I am setting up Krona and I just realised: Does this trigger work only with the native loyalty module or also Krona?