| TLDR. Business impacting dashboard functionality removed. Need a drop in replacement for stripe. Oh, and support sucks. We use a couple of stripe integrations for our website and have probably done £50k of transactions in the last few months. Stripe has basic inventory management through products, SKUs, quantities and attributes. Today, a non technical member of my team went to amend and add product availability. The options for editing or creating product/SKU inventory were gone, this looked like a broken dashboard. Stripe support wasn’t good. At all. Email and phone are basically a messaging service with a robotic sounding “we’ll get back to you in 24h” - in fairness their reply was quicker. Just unhelpful. They told me that the API had changed. I told them we weren’t talking about the API, we use the dashboard. Then it transpires that their support advice of deleting and creating a product wouldn’t work either, both new and edit product were affected. Then an apparent escalation reveals that this is apparently a deliberate change and the functionality has been removed. Super. Now we apparently have to write our own front end to stripe to just update quantity or even set it active or not. Aside from an obvious regression in functionality, support clearly hadn’t been briefed and sent us chasing our tales for a few unproductive hours. Guess we’re not using stripe anymore. HN: what’s a good stripe replacement? |
So, long story short: We did a deploy yesterday for a thing which is not obviously related to the Dashboard's product SKU editing screen. There was an unplanned interaction between some work done for that deploy and the Dashboard product SKU editing interface; this resulted in some users having partially degraded HTML shipped to them (without the fields for editing SKU inventory quantity and SKU active/inactive status).
After we became aware that this happened due to Dan's comments, we opened an incident, diagnosed the regression, put a temporary fix in place, and started working on a more permanent fix.
I'm sorry we dropped the ball with respect to the support inquiry about this; our representative came to the conclusion that this was a planned change in functionality, even though this particular interaction was not planned. We'll look into how that happened and correct it.