Goldlett

I moved my store's abandoned cart, browse abandonment and price drop over from another platform and they have been running on live orders since. Two things stood out. The abandoned cart email renders the real cart. Actual product titles, actual prices, the real product images from my own CDN, and a working resume-checkout link rather than a generic cart URL. I checked the delivered email rather than a preview. The second one matters more if you drive the app through its API. A write that will not take effect now comes back with a warning telling you exactly what is wrong and which fields are supported. Within a minute of reading one I found a real defect in my own email that had been shipping for weeks: the button and the band behind it were set to the same colour, so the call to action had no visible edge. I could not see it and nothing had errored. I reported two bugs. Both were fixed within days and I verified both on a real send. One thing to know before you start: enabling the web pixel is done in the dashboard, and nothing tells you it is off. Browse abandonment and cart recovery both depend on it, so check it on day one. Small team, quick to answer, and honest about what the product does not do yet.

We run a personalised jewellery store on ShineOn and we publish everything through the API rather than the dashboard. Two things stood out. Support got us API access quickly and answered clearly, and the publish endpoint does exactly what the docs say it does. We took our catalogue from 8 products to 26 without a single click in the ShineOn interface, which is the whole reason we chose a POD partner with a real API. Fulfilment has been clean so far and orders shipped without us chasing anything. Two things we would like to see improved. There is currently no way to add a variant to a product after it has been created, so offering an extra finish means rebuilding the product and re-applying every metafield. And after an API publish, placeholder images and internal SKU tags keep arriving on the product for some time afterwards, so we run our own cleanup on a schedule. Neither of those stopped us building what we wanted. Good product quality, responsive support, and an API that genuinely works.