We realised not every seller wants the same embed
One thing I've learned while building Pluribox: not every seller wants the same embedded checkout experience.
Our original assumption was that sellers wanted a complete product widget.
But some sellers already have a page that does the selling. They don't need the image, description, and price again. They might just need a clean Buy button.
Others want to build trust by showing reviews wherever they make sense on their site.
So we made the embed modular.
You can now choose what actually renders on your page:
* The full product box
* Just the Buy button
* Just the reviews section
Buy Button mode keeps things clean.
Reviews can now also be embedded independently, with a friendly "No reviews yet" state so new sellers have a path to their first review - even if their sales happen elsewhere.
Existing embeds remain unchanged. Also built a test harness to verify that the new and old versions render identically.
Next up: reducing friction for free products. If a seller only wants to collect an email address, the embed will handle it directly inline on the page—no popup required.
I'm curious: if you sell digital products, would you rather have a full product widget, or have complete control to embed only the pieces you need?
I like that the change came from questioning whether every customer was actually trying to solve the same problem.
Sometimes the product doesn't need to become bigger. It needs to become flexible enough to fit into different ways people already work.
Indeed, and moreover, the user can also use more than one element on the same page. Each element works independently while also being interconnected. Building blocks with full control and customization is the goal
That makes sense. The interesting trade-off with that flexibility is usually deciding where customization should stop.
Have users pushed you toward combinations or workflows you hadn't originally designed the building blocks for?