Changelog
Every update to Arbyn, newest first. Features, improvements, fixes, and behind-the-scenes work, all in one place.
The chat widget's name and setup text in Shopify's theme editor used to show in English regardless of your store's language. They now appear in all 21 languages Arbyn supports.
The "seen" tick on a customer's chat message could never actually appear, because opening a conversation never triggered it. Opening a conversation now correctly marks the customer's messages as seen, and the customer's own widget shows the tick.
When a customer asked what data Arbyn holds about them, the response only covered their conversations and quiz entries, while Arbyn's own deletion process already covered two further kinds of record. All four are now reported together, so what a customer is told matches what Arbyn actually holds.
When a shopper taps the rating link in one of your emails and something is wrong with the link, for example it was clipped by a mail client or has aged out, they used to land on a page that named no store at all. A dead link is obviously an error. A real page that appears to belong to nobody, reached from an email the shopper believes came from you, is worse. Those pages now carry your store name, including the page a shopper sees if they tap their link a second time after already rating. Where the store genuinely cannot be identified, the page falls back to neutral Arbyn branding rather than guessing. We also gave these links their own signing key so that rotating your Shopify credentials can no longer quietly invalidate every rating link you have already sent. Links sent before that change keep working.
Every label, hint and option in the rule builder is now translated, so building a rule reads the same way as the rest of Arbyn in all twenty one supported languages. The condition and action values themselves stay in their original form, because those are the exact values Arbyn matches on rather than words meant to be read.
Arbyn does not cancel, refund, return or re readdress an order by itself. It passes those requests to you. So the one thing it must never do is tell a shopper the request is filed when nothing was filed, and there is a guard that checks every reply for exactly that before it goes out. That guard only understood English. A reply written in French, German, Spanish or Japanese could make the identical claim and pass straight through, which meant the protection your English speaking shoppers had did not exist for anyone else. It now reads the reply in whatever language it was written in, and it is careful about the difference between saying a request was sent and simply offering to send one or explaining how. Two things changed in what the shopper actually reads. In email, a reply like that was already never sent, and that is unchanged. In chat, the reply used to reach the shopper anyway while the conversation was flagged for you, so you could see the warning while the shopper had already been told the wrong thing. Now the shopper gets a short honest line instead: a person has their request and there is nothing more they need to do. That is true, because the handoff really has happened. The original draft is kept in the conversation so you can see what Arbyn had been about to say.
When a shopper asked about an order without having given an email, Arbyn refused correctly but explained itself badly. It said the email did not match the one on the order, even though the shopper had never provided an email at all. Nothing was ever revealed, but the wording described a check that had not happened, and a shopper who noticed would have been right to. Arbyn now tells the two situations apart. With no email yet, it simply asks for the one used when the order was placed. If a shopper has given an email and it genuinely does not match, it can still say so, because then it is true. The security behaviour is unchanged: an order is never shown until the email matches.
Changing your language showed the confirmation straight away and then took five to eight seconds to actually change. The switch was never slow. It was being undone and reapplied a moment later. It now applies immediately and stays.
If you unsubscribed from Arbyn own operational emails, there was no way back and every later alert quietly vanished. That can now be undone, so a single unsubscribe does not silence your escalation alerts forever.
When Arbyn refuses to run an action you approved, the reason was recorded but never shown. You saw a failure with no cause, on the one page whose whole purpose is deciding what Arbyn may do. The reason now appears on the row and in full when you open it. The same gap on the returns card is fixed too.
You can rewrite the subject and body of the emails Arbyn sends your customers. Saving those edits worked, and reading them back worked, but nothing connected the two, so the email that went out still used the original wording. Your edits now reach the customer, and the preview shows exactly what they will receive.
Only one discount applies per order, so when a shopper qualifies for a bundle and a discount offer in the same conversation, one of them has to win. Until now that was decided by the order the code happened to run in, and between two discount offers it was whichever you created first. Bundles and discount offers now both have a Priority field, on one shared scale. Higher wins. Everything starts at zero, so nothing changes until you set one. Once a code is saved to a conversation, only a strictly higher priority can replace it. That is deliberate: by then the shopper has usually already been told about it, and a promise you have made needs a better reason to break than another offer being equally good. When a second offer does lose, Arbyn says so plainly and names the code that applies, rather than quietly swapping it or claiming both. If a bundle loses the discount slot, its items still go into the shopper bag.