The quiet tax every cross-border seller pays in browser tabs
If you run a storefront on Shopify, fulfill through Amazon FBA, or push SKUs on TikTok Shop and Temu, you already know the dirty secret of this business: the actual selling is maybe 30% of the job. The rest is file chores. Compressing a supplier PDF that’s too fat for an email. Stripping GPS metadata off a product photo before it hits a listing. Merging three signed vendor contracts into one PDF for your accountant. Sending a 400 MB raw photo pack to a freelance retoucher in Manila. None of this shows up in your P&L, and all of it eats your afternoon.
That’s why a small macOS utility called Ricly, built by Samir BAM, caught my attention this week. It’s not an e-commerce tool. It’s a Finder extension — 17 file tools that live in your right-click menu, run locally on your Mac, and cost nothing to start. But for operators who juggle supplier files, listing assets, and compliance paperwork across time zones, the pattern behind it is more interesting than the product itself. Let me explain why.
What Ricly actually solves — and why the framing matters
The maker’s pitch is refreshingly honest: he’s a music producer who got tired of paying for five subscriptions just to send a stem pack, resize a photo, and compress a PDF. His line — “I was paying for five, and still jumping between tabs for things that take ten seconds” — is the whole thesis. Ricly puts all of it in the Finder, where the file already is. Select a file, right-click, done. Nothing uploads unless you deliberately hit Upload & Share. Everything else runs on the Mac itself.
That’s the entire product. Seventeen tools, a configurable right-click menu, and a promise that new tools get added to the same menu with nothing to install.
Now, if you’re a cross-border seller, your first reaction is probably: “I don’t work on a Mac, and I don’t care about stem packs.” Fair. But stay with me, because the shape of this problem is identical to yours.
Think about what happens when your Guangzhou supplier sends you a 60 MB product spec PDF that won’t attach to an email. Or when your photographer delivers 200 HEIC files from an iPhone shoot and Amazon Seller Central won’t accept HEIC. Or when you need to strip EXIF location data off a lifestyle photo before it goes live on Etsy, because you don’t want your warehouse address embedded in a public listing. Or when you’re assembling a customs packet and need to merge six PDFs into one before your freight forwarder will touch it.
Every one of those is a browser tab. Every one of those is a free tool with a paywall at file #3. Every one of those is a ten-second job that somehow costs you twenty minutes of context-switching.
Why Amazon sellers should care more than Shopify ones
Here’s a distinction worth drawing. If you’re a pure Shopify DTC operator, your file workflow is mostly marketing assets — images, videos, ad creative. You probably already have a Canva subscription and a Dropbox or Google Drive account, and the pain is diffuse.
If you’re an Amazon FBA seller, the pain is acute and recurring. Amazon Seller Central has hard file constraints: image dimensions, file sizes, PDF-only documentation for some compliance categories, and a flat refusal to accept HEIC uploads in many flows. Multiply that by a catalog of 200 SKUs and you’re doing file surgery every single week. Same story on eBay for bulk listing uploads, and on SHEIN and Temu supplier portals where spec sheets and compliance docs have to be re-formatted for each platform’s uploader.
So the Ricly pattern — local, right-click, no upload, no account — is disproportionately valuable to marketplace sellers, not because the tools are exotic but because the volume of file chores is higher and the compliance stakes are real.
How it stacks up against the incumbents you’re already paying for
Let me be specific about what Ricly is actually competing with, because “17 file tools in a right-click menu” sounds like a commodity until you look at the alternatives.
The first incumbent is the browser-tool economy: Smallpdf, iLovePDF, TinyPNG, CloudConvert, WeTransfer. Every one of these is excellent at one thing and monetizes via a free-tier cap or a monthly plan. The Ricly maker’s claim is that he was paying for five of them simultaneously. If you’ve ever stacked a WeTransfer Pro plan, a Smallpdf subscription, and a CloudConvert tier just to keep supplier workflows moving, you know the math: that’s easily $40–60/month for tools you use for ninety seconds at a time.
The second incumbent is the OS itself. macOS has Preview, Quick Look, and a built-in Archive Utility. Windows has Paint, Snipping Tool, and Explorer’s built-in ZIP. Both are fine for one-off jobs and terrible for batch work or anything involving metadata.
The third incumbent is the pro desktop suite: Adobe Acrobat for PDFs, Affinity Photo or Pixelmator Pro for image conversion. These are genuinely more powerful, but they’re also $100–250 one-time or $20+/month, and they’re not sitting in your right-click menu.
Ricly’s bet is that the middle ground — more than the OS, cheaper than the suite, faster than the browser — is where most operators actually live. Based on the maker’s description, it’s free to start, and the tools that run locally don’t upload anything. That last point matters more than the pricing.
The privacy angle nobody talks about in e-commerce
Here’s a thing I don’t see discussed enough. When you drag a supplier contract into a free online PDF merger, you are uploading your supplier’s pricing, your MOQs, and possibly your payment terms to a server you don’t control. When you compress a product photo through a free web tool, you’re uploading an unreleased SKU image to a third-party CDN. For a solo operator, that’s a minor risk. For a brand doing $5M+ on Amazon, that’s a data governance problem your legal counsel would have opinions about.
The Ricly framing — “the work happens on your Mac, nothing is uploaded unless you deliberately share a file” — is the single most defensible thing about the product, and it’s the thing I’d steal for my own stack even if I never install Ricly. Local-first file handling isn’t a feature. It’s a policy.
What cross-border sellers should actually borrow from this
Let me pull out four transferable lessons, because the Ricly launch is more useful as a pattern than as a purchase decision.
1. Audit your file-chore stack for redundancy. Open your browser, count the tabs you have pinned for file utilities. If it’s more than three, you’re paying a tax. The maker’s “five subscriptions” confession is a mirror — most operators I know are running WeTransfer for big sends, Smallpdf for PDFs, TinyPNG for images, and a random HEIC converter they found on page two of Google. Consolidating even two of those into a local tool pays for itself in a month.
2. Treat metadata as a compliance surface. The maker’s third weekly use case is telling: iPhone photos → HEIC to JPG → Strip Metadata, “so the location isn’t in the file.” If you’re sourcing from a factory and shooting lifestyle content on-site, your photos carry GPS coordinates. If you’re a dropshipper using supplier-provided images, they may carry the supplier’s own metadata. Either way, stripping EXIF before upload is a five-second habit that prevents a category of problems you don’t want to discover during a brand registry audit.
3. Prefer tools that live where the file lives. The reason browser tools feel slow isn’t the processing time — it’s the context switch. Every tab is a decision, a login check, an upload progress bar, a download dialog. A right-click menu collapses all of that into one gesture. If you’re evaluating any file-adjacent SaaS for your team, “does it integrate into the OS or the platform I already use” is a better filter than “does it have more features.”
4. Watch the “new tools in the same menu” model. The maker explicitly says Ricly doesn’t stop at 17 — new tools arrive in the same right-click menu with nothing to install. That’s the same distribution logic that made Zapier and Make sticky in the automation world, and the same logic behind Shopify’s app ecosystem. For a cross-border operator, the implication is: pick tools whose surface area expands without requiring you to learn a new UI. Your attention is the scarce resource, not the $9/month.
Where the math breaks
I want to be honest about where this pattern fails, because I’ve watched operators over-index on “free and local” and regret it.
First, macOS-only is a real constraint. If your ops lead runs Windows and your 3PL contact runs a Chromebook, Ricly doesn’t help the team — it helps one person. Cross-border teams are almost always heterogeneous on OS, and a local-only tool creates a single point of failure.
Second, “free to start” is not “free forever.” The maker doesn’t disclose pricing beyond that phrase, and I’d want to see what the paid tier unlocks before I’d standardize on it. Browser tools have the same problem, but at least their caps are visible.
Third, and this is the big one: file chores are not actually the bottleneck for most sellers. They’re a friction tax, not a growth constraint. If you’re doing $50K/month on Shopify and spending four hours a week on file wrangling, saving three of those hours is worth maybe $200 of your time. Real leverage comes from fixing the upstream problem — getting your supplier to send files in the right format in the first place, or automating the pipeline so files never touch a human. A right-click menu is a bandage; a supplier spec sheet with format requirements is surgery.
Where my judgment says Ricly falls short
Three things I’d want to see before recommending this to a seller running serious volume.
No batch workflow visible. The maker describes single-file operations — “select a file, right-click, done.” For a seller processing 200 SKU images before a TikTok Shop launch, single-file is a non-starter. I’d need to see folder-level batch operations with naming conventions and output presets before this becomes a production tool rather than a convenience.
No team or shared-config story. If your VA in the Philippines needs the same right-click tools as your ops lead in Shenzhen, there’s no indication Ricly handles shared configuration. That’s fine for a solo operator and useless for a five-person brand.
The tool count is a vanity metric. Seventeen tools sounds like a lot until you realize most operators use four or five. The maker’s own weekly list is three: Upload & Share, PDF Merge, HEIC to JPG. I’d rather see five tools that are genuinely best-in-class than seventeen that are merely adequate. The “new tools are coming” promise is a red flag as much as a feature — it suggests breadth over depth, and breadth is exactly what browser tools already offer for free.
The comparison I’d actually run
If you’re a macOS-based Amazon or Shopify operator, here’s the honest test: install Ricly, use it for a week, and log every time you don’t open a browser tab. If that number is under ten, it’s not worth the menu real estate. If it’s over thirty, you’ve found a real workflow win. And if you’re on Windows, don’t wait for a port — go audit your Smallpdf and CloudConvert usage instead, and see whether consolidating those two subscriptions into one paid tier gets you the same result for less money.
What I’d watch / test next
This week, do three things. First, open your browser and screenshot every pinned file-utility tab — that list is your actual file-chore stack, and it’s probably longer than you think. Second, pick your single highest-frequency file operation (for most Amazon sellers, it’s image format conversion; for most DTC brands, it’s PDF merging for supplier contracts) and time yourself doing it five times in a row. That number, multiplied by 52 weeks, is the annual cost of not fixing it. Third, if you’re on a Mac, install Ricly and run the one-week tab-audit test above — the maker’s Product Hunt page has the install details, and the free tier is enough to know whether it sticks.
What I’m watching longer-term is whether the local-first, right-click model spreads to the tools that actually move the needle for cross-border sellers — bulk image processing, multi-language label generation, HS code lookup, and carrier label batch printing. Those are the file chores that cost real money when they go wrong. If someone applies the Ricly pattern to customs paperwork, I’ll be the first to write about it. Until then, treat this as a useful reminder: the cheapest efficiency win in your stack is usually the browser tab you keep forgetting to close.
