5
17 Comments

I stopped adding image tools and rebuilt around one ecommerce workflow

Fernpix used to look like a collection of image utilities. That was technically useful but commercially vague.

I have now rebuilt the entry flow around one job: a marketplace seller has a folder of product photos and needs to know what will fail, why, and how to deliver a corrected catalog.

The current flow is: choose Amazon / Shopee / Lazada / TikTok Shop → check one photo or a folder → group failures → fix supported issues → export the catalog and QA report. Processing stays on-device.

The hard lesson: traffic from generic launch audiences does not equal seller demand. This version has platform-specific landing pages and measures own-photo checks and successful exports, not page views.

Try the marketplace photo checker:
https://fernpix.com/marketplace-product-image-checker?utm_source=indiehackers&utm_medium=post&utm_campaign=marketplace_checker_20260914&utm_content=builder_update

If you manage marketplace listings, I would love feedback on one thing: does the report tell you enough to fix the catalog without guessing?

on September 14, 2026
  1. 1

    That's the evidence I'm waiting on. I can see own-photo checks and completed exports as events, but I cannot yet tell "same seller came back." From what I have, it's mostly first-run catalog checks, and the sample is still tiny. Repeat usage is the next number I'll actually instrument.

  2. 1

    You're right that four platforms is four products. The site has four rule profiles, but I'm treating Shopee as the one to own first — rejected listings there are frequent and the rules (white bg, 1:1, 800px) are concrete enough to productize. Amazon / Lazada / TikTok stay as profiles, not four parallel roadmaps.

    And yes — IH is the wrong room. I've started spending time in seller forums and agency inboxes instead of launch audiences.

  3. 1

    Nice pivot. The platform-specific point is the key: I’d pick one marketplace and instrument the shortest path from first scan to successful export, then segment repeat usage by seller rather than raw scans. A useful activation metric could be “fixed at least one flagged image and exported a clean catalog within 24h,” paired with the top failure category. I’m running a $0 experiment with digital-seller tools, and the same lesson is showing up for me: catalog breadth gets attention, but one measurable job gives distribution a chance. Curious whether repeat sellers or first-time audits currently dominate.

    1. 1

      Agreed — I was measuring scans, not completed jobs. The path exists today: pick a marketplace → drop a folder → grouped failures → fix supported issues → CSV report, plus a ZIP from Workbench. What I don't have yet is seller-level repeat vs first-time, or your 24h metric ("fixed at least one flagged image and exported a clean catalog"). Analytics are still anonymous events.

      On the question: first-time audits dominate, and the sample is still too small to call a seller base. I'm putting that 24h export path on Shopee first.

  4. 1

    The pivot from "collection of utilities" to "one workflow for one persona" is exactly right. Generic tools attract curious visitors; workflow tools attract returning users with a job to finish.

    The on-device processing is a genuine competitive moat for marketplace sellers who deal with proprietary product images — they won't paste those into a cloud tool if they can avoid it.

    One thing worth testing: the failure grouping step. If sellers see the same failure type repeating across 200 photos, the impulse is to fix in batch. If your export flow surfaces the top 3 failure patterns with a "fix all like this" option, that becomes a reason to upgrade or pay vs. just check and close the tab.

    Also curious — are you seeing repeat use from the same sellers, or is it mostly one-and-done catalog checks before launch?

    1. 1

      On-device is the part I don't want to lose — photos never get uploaded to Fernpix.

      Failure grouping exists as counts (e.g. "White background · 12"), but it's not top-3, not clickable, and there's no "fix all like this" for one failure type. Closest is "Fix all failing photos in Workbench," which sends every failing file through per-file steps. Batch ZIP is free up to 5 photos.

      Repeat vs one-and-done: still mostly one-and-done. I don't have a returning-seller cohort yet — that's the next measurement.

  5. 1

    Going from a toolbox to one job is the right call, but the harder version of that decision is still ahead: Amazon, Shopee, Lazada and TikTok Shop are four different products with four different rejection rule sets, so supporting all four rebuilds the same vagueness one level down. I would pick the platform where a rejected listing costs the seller the most money and own that one completely. And marketplace sellers are not on launch platforms, they are in seller forums and inside the agencies managing catalogs for them, which is where I would spend the next month.

    1. 1

      You're right that four platforms is four products. The site has four rule profiles, but I'm treating Shopee as the one to own first — rejected listings there are frequent and the rules (white bg, 1:1, 800px) are concrete enough to productize. Amazon / Lazada / TikTok stay as profiles, not four parallel roadmaps.

      And yes — IH is the wrong room. I've started spending time in seller forums and agency inboxes instead of launch audiences.

  6. 1

    The sharper workflow is a big improvement: you’ve turned ‘image tools’ into a marketplace problem with a clear outcome.

    I’d make the first promise even more concrete: ‘check your catalog before it gets rejected,’ then show one platform-specific failure, the fix, and a before/after report. That gives sellers enough proof to act before committing a whole folder.

    1. 1

      The homepage already says "ready before it goes live." After a fix, the checker has a before/after slider, and Workbench has Original / Result / Compare.

      What's missing is that proof on the first screen: one platform-specific fail, the fix, and a before/after before someone commits a whole folder. I'll make the Shopee landing lead with that.

  7. 1

    This is a really honest lesson to share — "traffic from generic launch audiences does not equal seller demand" is something a lot of us learn the hard way after a launch. Going from "collection of utilities" to "one specific job for one specific user" seems like it would also make your marketing way easier, since you're not trying to explain five different use cases at once anymore.

    On your question: platform-specific grouping (Amazon vs Shopee vs TikTok Shop) is smart since their actual rejection reasons differ. Does the QA report tell sellers exactly which rule was violated (e.g. "background not pure white" vs just "image failed"), or is it more of a general pass/fail per photo right now?

    1. 1

      The report is specific, not pass/fail. A fail looks like "White background — Background not pure white" or "Need >= 800x800, got 600x600", tagged Platform rule vs Recommended. The CSV has the same per-photo reasons.

      What it is not: a paste of the Seller Center policy paragraph. Composition issues (fill / center / crop) are often advisory, so they may not block a pass.

  8. 1

    The shift from generic traffic to own-photo checks and exports is a much stronger signal. Once sellers actually run their catalogs through it, do you see repeat usage or completed exports from the same sellers, or is that the next piece of evidence you’re waiting on?

    1. 1

      That's the evidence I'm waiting on. I can see own-photo checks and completed exports as events, but I cannot yet tell "same seller came back." From what I have, it's mostly first-run catalog checks, and the sample is still tiny. Repeat usage is the next number I'll actually instrument.

      1. 1

        Repeat usage is clearly the next meaningful signal. If you’re open to it, what’s the best email to reach you on?

  9. 1

    The move from a bag of image utilities to one seller workflow feels much clearer. Measuring completed photo checks and exports instead of page views is the right correction too. For the report, I’d want each failed image to show the exact marketplace rule and a before/after example, because “wrong aspect ratio” still leaves a seller guessing what to change.

    1. 1

      Each failed photo already shows the named check plus a measured detail ("wrong aspect ratio" is "Need 1:1, got 1200x800"). After a fix, there's a before/after.

      What I don't show on an unfixed fail is a sample "this is what it should look like," and I don't paste the official marketplace clause. That's the gap I'll close on the Shopee report first — exact rule + example, not just the diagnosis.

  10. 1

    This comment was deleted 14 hours ago

  11. 1

    This comment was deleted 14 hours ago

  12. 1

    This comment was deleted 14 hours ago

  13. 1

    This comment was deleted 14 hours ago