The Web Is Now a Product You Can Remanufacture — And That Changes How We Sell
Every cross-border seller I know has the same dirty secret: we don’t actually use the tools we sell into. We build storefronts on Shopify, list on Amazon, and optimize for TikTok Shop — but we consume those platforms as passive users, the same way a tourist consumes a city. We never question the architecture. We just work around it. That’s why the launch of Sider Code from the Sider team matters more than another AI writing assistant or another analytics dashboard. It’s not a new channel. It’s a new way to reshape the channels we already depend on. If you can take a website built for everyone and bend it to your own operational workflow — removing clutter, adding functions, rebuilding information architecture on the fly — then the platforms we sell on stop being fixed constraints and start being raw material. For operators who live inside Seller Central and Shopify admin every day, that’s not a novelty. That’s a competitive edge.
The Problem It Actually Solves: Your Tools Don’t Fit You
Let’s be blunt about the state of e-commerce tooling. We’ve spent the last decade layering SaaS on top of SaaS. You’ve got Helium 10 for keyword research, Klaviyo for email, Jungle Scout for product validation, and a half-dozen other subscriptions that each solve one narrow problem. The result is a dashboard ecosystem that mirrors the mess it’s trying to organize. Every platform ships with its own opinionated UI, its own information hierarchy, its own idea of what you should see first. And none of them were built for you — they were built for the median user, which is to say, no one.
Sider Code takes the opposite approach. Instead of building a new website, it lets you reshape the sites you already use. You describe what you want changed in plain language. The tool understands the page, writes the code, and applies it — turning your words into a working feature you can save and control. That’s not a plugin. That’s a remanufacturing layer for the entire web.
Think about what that means for a seller who lives in Amazon Seller Central. The default interface is dense, cluttered, and organized around Amazon’s priorities, not yours. You’re constantly scrolling past FBA inventory alerts, advertising performance summaries, and policy updates to get to the one metric you actually care about. With Sider Code, you could strip that page down to your daily operational dashboard: units sold, net margin after fees, and buy box status. Nothing else. Or you could rebuild a scattered thread of customer messages into a focused action list. The tool doesn’t just filter — it restructures.
Why Amazon sellers should care more than Shopify ones
Here’s my contrarian take: Amazon sellers have more to gain from this than Shopify store owners. Why? Because Shopify is already customizable. You can edit your theme, install apps, and reshape your admin through the Shopify App Store. The platform gives you a toolkit. Amazon gives you a cage. Seller Central is notoriously rigid — you get what you get, and the workarounds are manual and brittle. Sider Code’s ability to remove entire content formats, add capabilities the site never had, and save those changes for your next visit is a way to build your own custom Seller Central without Amazon’s permission. That’s not a small thing. That’s the difference between working inside someone else’s system and building your own system on top of theirs.
How It Differs From the Incumbents
Let’s be clear about what Sider Code is not. It’s not a browser extension like Grammarly that checks your writing. It’s not a productivity overlay like Notion that tries to replace your workflow. And it’s not a scraper like Octoparse that pulls data out of pages. Those tools work with the web as it exists. Sider Code works on the web as it exists.
The closest comparison is probably Tampermonkey or Greasemonkey, the user-script managers that let you inject custom JavaScript into any page. But those require you to write code — or at least to understand what you’re pasting in. Sider Code’s pitch is that you describe the change in natural language and it does the engineering. That’s a meaningful difference for the 99% of sellers who can’t read a line of JavaScript but know exactly what they want their tools to show them.
The maker team’s responses in the Product Hunt comments reveal the current limitations honestly. When asked about heavy single-page applications where the DOM is constantly updating, Joel confirmed that the generated code is currently frozen — meaning if the underlying page changes, your customization might break. They plan to build a detection feature to handle disruptive changes, but that’s future work, not current capability. Similarly, when asked whether changes can be shared, Rick Fan confirmed you can export them, and Joel added that a share feature is in the works. So the tool is powerful but not yet bulletproof.
Where the math breaks
Let’s talk about the frozen-code problem more seriously, because it’s the difference between a useful tool and a liability. E-commerce platforms update their front-ends constantly. Amazon runs A/B tests on Seller Central. Shopify ships theme updates. TikTok Shop’s creator marketplace changes weekly. If Sider Code’s generated code is frozen at the moment of creation, then every customization you save is a ticking time bomb. The moment Amazon changes a CSS class or restructures a DOM element, your custom view breaks — and you’re left staring at a half-rendered page you built, not one the platform gave you.
The team says they’re working on a detection feature. That’s good. But for cross-border sellers who depend on these tools daily, “we plan to” isn’t a deployment timeline. I’d want to see how the detection works before I let it become part of my operational stack. That said, the three-day free window is a smart way to test it on your own workflows without committing budget.
What Cross-Border Sellers Can Borrow From It
Even if you never install Sider Code, the philosophy behind it is worth stealing. Here’s what I mean.
First, the idea that your tools should adapt to you, not the other way around. Most sellers treat platform UIs as fixed constraints. You log into Seller Central, you look at the dashboard they give you, and you work around it. Sider Code’s whole premise is that this is a choice, not a law of physics. You can reshape information. You can remove what you don’t need. You can add capabilities the site never had. That mindset shift alone — from accepting the platform’s defaults to questioning them — is worth more than any feature.
Second, the emphasis on personalization over templates. The Product Hunt launch copy explicitly says these aren’t templates you have to choose from. That’s a direct critique of how most SaaS tools work. They hand you a set of pre-built dashboards and expect you to make do. Sider Code lets you build your own. For sellers, this translates to a broader lesson: your operational stack should be bespoke, not off-the-shelf. If your competitor runs the same Jungle Scout reports and the same Helium 10 workflows as you do, you don’t have an edge — you have parity. The edge comes from building custom processes, custom views, and custom automations that no one else has.
Third, the idea of saving and controlling your customizations. Sider Code lets you save each feature for your next visit and switch it off or on whenever you want. That’s a governance model, not just a feature. For a cross-border operation, this is how you should think about every tool you adopt. Can you turn it off? Can you export your data? Can you control what it changes? If not, you’re building dependency, not capability.
The research workflow angle
One of the commenters on the Product Hunt page, Saksham Shukla, said he’d use Sider Code on Reddit first — turning long scattered threads into something easier to follow while keeping the original discussion underneath. That’s a great use case for product research. Cross-border sellers spend hours digging through Reddit threads, Facebook groups, and forum posts to understand what customers actually want. The information is there, but it’s buried in conversation. Sider Code’s ability to rebuild a scattered thread as a focused article with its own navigation could turn raw community chatter into structured market research. That’s not a minor convenience. That’s a research workflow upgrade.
Where My Judgment Says It Falls Short
I’m not going to pretend this is a finished product. It’s a clever prototype with real potential, but it has structural limitations that matter for serious operators.
The frozen-code issue is the obvious one. But there’s a deeper problem: persistence. The web is not a static document. It’s a living system of APIs, server-side rendering, and client-side state. When Sider Code applies a customization, it’s working with the page as it exists at that moment. If the page’s data layer changes — if a chart updates, if a feed refreshes, if a new ad loads — does the customization still hold? The team’s answers suggest that the code is applied once and stays put. That’s fine for static pages. It’s fragile for dynamic dashboards.
There’s also the question of what happens when the underlying site’s terms of service change. Amazon, Shopify, and TikTok all have policies about automated access and page modification. Sider Code is a browser extension, so it’s running client-side, but that doesn’t mean platform terms can’t be updated to prohibit this kind of reshaping. If Amazon decides that modifying Seller Central’s DOM violates its terms, you could find your customizations blocked — or worse, your account flagged. That’s a real risk for sellers who depend on Amazon for their livelihood.
And there’s the collaboration gap. The team says sharing is possible, but it’s clearly not the focus yet. For a cross-border operation with multiple team members — a brand manager in the US, a listing specialist in China, a logistics coordinator in Europe — shared customizations would be essential. Right now, it sounds like each user builds their own. That’s fine for individual productivity, but it doesn’t scale to team workflows.
The ad-blocking temptation
One commenter asked, can you remove the ads with that? The makers said yes — you can completely customize your own adblock, and not just ads but clutter UI components. That’s a fun feature for personal browsing, but it’s a trap for sellers. If you’re using Sider Code to strip ads from competitor sites or marketplaces, you’re also stripping the information those ads contain. Ad placements tell you what competitors are bidding on, what products they’re promoting, and what messaging they’re testing. Removing ads for cleanliness is like removing the scoreboard to make the game less noisy. You’re losing signal, not just noise.
What I’d Watch / Test Next
If you’re a cross-border operator, here’s how I’d approach Sider Code this week — not as a permanent tool, but as a diagnostic exercise.
First, install it and use the three-day free window to reshape one page you actually work in daily. Pick your Amazon Seller Central dashboard or your Shopify admin. Describe one change you’ve always wanted — hiding a section you never use, adding a metric that’s buried, restructuring a list into a summary. See how close the output gets to what you imagined. Don’t judge it on the first try; judge it on whether the direction is right.
Second, test the persistence. Apply a customization, then reload the page multiple times over a few hours. Watch what happens when the underlying page updates. The team has been honest that the code is frozen — so expect breakage. But observe how it breaks. Does it fail gracefully, or does it take down the whole page? That tells you whether you could ever trust it in a production workflow.
Third, export a customization and try to share it with a team member. The export feature exists, but the share feature is still being built. If the export format is readable and portable, that’s a signal the team is thinking about collaboration properly. If it’s a blob of JSON that only the tool can read, that’s a sign they’re not ready for team use.
Finally, ask yourself the strategic question: what would you build if you could reshape any tool in your stack? Not what Sider Code can do today, but what the idea unlocks. The answer to that question is your roadmap — not for adopting this tool, but for building your own operational advantages. The web is becoming remanufacturable. The sellers who treat it that way will be the ones who win.
