Customer story · PhoneSoap
PhoneSoap — the UV sanitization company with over 3 million units sold — handed Membrane five catalog tasks on a Monday. By Wednesday every one was live or in Amazon’s review queue, and every change arrived in writing with links to prove it.
On the first day, PhoneSoap listed the work: launch the new PhoneSoap Baby listing, rework HomeSoap so the two products stop competing, retitle the catalog with A/B tests on every family, remove a phantom "3‑pack" from the Toothbrush Sanitizer listing, and re‑attach a child ASIN that had come loose from its parent. Access came through Membrane’s standard Amazon authorization plus two scoped Seller Central permissions — with everything else left at "None."
Dates and times are from the engagement channel. Every change shipped with a written note of what was done and why.
The client connected the account through the standard authorization and granted two scoped Seller Central permissions — Manage Your Experiments and the case log. Everything else stayed at "None."
The phantom "2‑pack / 3‑pack" overlay was gone from both affected live listings, confirmed with links. The detached child ASIN was re‑attached the same afternoon — plus a second detached child nobody had asked about, found and fixed in the same pass.
Titles went live for every product family. Inconsistencies in the inputs were caught before publication: missing parent-listing rows, a duplicated line, and titles over Amazon’s 75‑character limit.
The title experiments the client requested were queued for Amazon’s earliest available start date, closing out the Monday list: every one of the five asks was now live or in Amazon’s review queue — two days after handover.
Asked at 3:49 pm whether a warehouse spike meant trouble, Membrane answered at 4:20 pm with the records: no removal order, return rates flat (XL White 12.3% in May, 10.0% in June), the spike was the client’s own automated removals working as configured. Underneath it: about 400 unsellable units accruing storage fees, 93 of them on one SKU the auto‑removal setting missed. The client updated the setting the same afternoon.
A written summary of every change made and every item on the radar — so nothing rested on memory or a chat scroll‑back.
When Amazon’s catalog blocked the new product’s UPC over a stale ASIN association, Membrane ran the support case — evidence, GS1 documentation, follow‑ups — asking the client only for what no one else could provide.
The catalog is monitored and kept in order as a recurring service — suppressed offers, variation families, titles, images, and A+ content.
Questions about inventory, returns, or fees are answered from the account’s own records — with the numbers to back them.
Prices and product claims are held for explicit confirmation before they ship — every action is logged with the reason it was taken.
Each figure below is computed from the dated record of the engagement and says what it covers.
Membrane has been phenomenal. They knocked out in days a list we had been sitting on for months, caught my own errors before they went live, and every change came with a written explanation of what was done and why.
Built by the team behind Membrane (getmembrane.com). Membrane is an independent service. Not affiliated with, endorsed by, or sponsored by Amazon.