Essential Seller Tools Missing on Fab – Wishlist, Cart Metrics, Regional Insights & More

General Feedback & Requests
, , , , ,
1

Essential Seller Experience Improvements for the Fab Marketplace

Hello Fab Team,
I’d like to share feedback from the perspective of an active seller who recently published a product on Fab (BlueprintOutline). While the publishing experience is smooth overall, there are several critical features missing that directly affect both sales performance and product strategy.

These are not “nice to have” features — they are essential tools every seller needs to operate sustainably and to understand their audience.

Below is a detailed list of requests and suggestions:

:star: 1. Wishlist Data for Sellers

Fab has a wishlist feature for buyers — but sellers cannot see:

  • How many users added the product to their wishlist

  • Wishlist growth over time

  • Regional wishlist distribution

Why this matters:
Wishlist count is one of the strongest indicators of product potential. On Steam, Epic Games Store, Unity Asset Store, and even gumroad-style marketplaces, wishlist tracking is a core metric for every creator. Without this, sellers are unable to:

  • Plan discount timings

  • Understand early interest

  • Forecast sales

  • Make informed decisions based on user behavior

:star: 2. Cart (Add-to-Cart) Analytics

Fab also shows “Add to Cart” for users — but sellers cannot access:

  • Total Add-to-Cart count

  • Abandoned cart numbers

  • Region-based cart stats

Why this matters:
If 500 people add a product to their cart but only 10 complete the purchase, that signals:

  • Pricing issues

  • Checkout limitations

  • Regional restrictions

  • UX friction

Without these insights, sellers are working completely blind.

:star: 3. Regional Sales Analytics

Currently, sellers only see completed sales with very limited detail.

It would be extremely helpful to know:

  • Which countries are attempting to buy but fail due to regional restrictions

  • Tax-applied vs non-taxed regions

  • Where potential demand is strongest

This is essential for marketing, pricing, localization, and planning.

:star: 4. Failed Purchase Reports (Extremely Important)

Many users report:

  • “Product not available in my country”

  • “Payment not allowed”

  • “Fab search not finding the product”

Sellers have zero visibility into these failures.

A simple dashboard metric would solve this:

  • Number of purchase attempts blocked regionally

  • Number of failed payment attempts

  • Reason for failure (geo-restriction, tax issue, unsupported payment, etc.)

This would dramatically improve seller understanding and support.

:star: 5. Public API or Plugin Development Opportunity

If Fab is willing, I (and likely many other developers) can build a plugin/dashboard that provides:

  • Wishlist analytics

  • Cart analytics

  • Regional heat maps

  • Price elasticity tools

  • Promotions optimizer

  • Metrics history

This would bring Fab closer to modern marketplace standards (Steam, Itch, Unity, Unreal Marketplace, EGS).

If Fab provides even a minimal API endpoint, I’d be happy to contribute.

:star: 6. Seller Notifications

Currently missing:

  • “Your product was wishlisted”

  • “Someone added to cart”

  • “User from X country attempted but couldn’t buy”

  • “New rating/review posted”

Basic notification tooling would increase engagement and improve seller reaction time.

:star: 7. Improved Verification Workflow

(Short note — optional to include)

Address verification and DSA trader validation are extremely important, but many sellers struggle with unclear formatting rules, lack of examples, and slow third-party processing. Providing:

  • Format examples per country

  • Real-time validation

  • Error explanations

  • Progress tracking

…would massively help new sellers onboard faster.

:check_mark: Why This Feedback Matters

Fab is growing fast, and many creators like me want to invest long-term into this ecosystem.
But without essential analytics and insight tools, sellers cannot:

  • Optimize pricing

  • Understand their audience

  • Plan marketing or discounts

  • Improve conversion

  • Predict revenue

Adding these features will significantly improve:

  • Seller trust

  • Marketplace quality

  • Overall revenue for both creators and Fab

:folded_hands: Thank you for reviewing these suggestions

I appreciate the team’s hard work and would be happy to help test features or provide additional feedback from a seller’s perspective.

If Fab is open to it, I’m also willing to develop tools/plugins to support this ecosystem.

Thanks again for your time!

— Muzaffer (BlueprintOutline Publisher)

Fab link : Blueprint Outline | Fab

2

I totally agree with you!!! The FAB marketplace lacks statistics that could help sellers sell better, so that sellers can better understand their business on FAB.

5 Likes
3

yea it’s crazy cause they bought sketchfab which has all of this already, but decided not to include them in fab??

3 Likes
4

hi @MchtMzffr, I appreciate you taking the time to compile and submit your proposal. We understand that having strong analytics is beneficial for sellers and is an important tool to enhance the seller experience. I’ve made a note of your comments in our documentation.

I wanted to discuss some of the points you made to understand the user case you have in mind. If you could please clarify them so we could see if that’s something we can address I’d appreciate:

  1. Many points are asking for regional distribution (wishlist, cart) - if I may kindly ask, what would the use of this information be for a publisher on Fab? We don’t offer regional pricing and are not currently planning to do so. How would this modify your experience on Fab? What features (aside from regional pricing), would you see going hand in hand with that?
    P.S. I agree that regional distribution for sales is an important data point though.

  2. I am not sure what regional restrictions you are referring to, could you please clarify?
    It’s mentioned a couple times, but I am not aware of any restrictions like that affecting the publishers. Can you please provide examples of what you mean and how this would benefit the experience on Fab?

  3. What is the purpose of the “Tax-applied vs non-taxed regions” distribution data? Fab calculates and handles taxes for transactions where legally appropriate and necessary, publishers get the tax report in their Seller profile every year, so they can pay taxes respectively. What purpose would an analytical report on tax vs non-taxed regional sales serve?

  4. How do you intend to use “failed purchase report” part, if you don’t mind me asking?
    I am curious, because the points mentioned in the post are either
    a) not addressable by the seller (failed payment, usually due to payment provider restrictions, these issues are handled by Fab support) or b) are not the case on Fab (product not available in my country, if it’s under the DSA regulations, the buyer won’t see the product at all and won’t be able to add it to cart or attempt anything).
    Do you have a particular idea in mind, on what these user cases might be?

Thank you!

1 Like
5

Hello @epik_kate

Thank you very much for the detailed and thoughtful questions, I truly appreciate the opportunity to clarify the use cases behind these requests. I’ll address each point one by one from a practical seller perspective:

1. Use Case for Regional Wishlist & Cart Distribution (Without Regional Pricing)

Even without regional pricing, regional demand visibility is extremely valuable for sellers for several strategic reasons:

**Targeted Marketing:**

Knowing that a product receives strong wishlist or cart interest from specific countries allows sellers to:

•	Run region-targeted ads

•	Focus community outreach (Discord, Reddit, YouTube, etc.)

•	Prioritize language localization

•	**Localization Decisions:**

If a high wishlist volume comes from non-English speaking regions, this directly justifies:

•	Documentation translation

•	UI language support

•	Region-specific tutorials

•	**Demand Forecasting:**

Wishlist and cart behavior by region signals latent demand, even if pricing is fixed. This helps forecast future sales and plan product roadmap.

•	**Promotion Strategy:**

If a region shows high cart volume but low conversion, that region becomes a prime candidate for promotions or feature adjustments.

So even without regional pricing, regional behavioral data is a core business intelligence tool, not only a pricing tool.

2. Clarification on “Regional Restrictions”

What I referred to as regional restrictions is based on real user feedback I personally received after publishing BlueprintOutline. Users reported:

•	Being unable to purchase despite seeing the product

•	Receiving payment-provider blocks tied to their region

•	Checkout failing silently without clear reason

From the seller side, we currently have zero visibility into whether:

•	The issue is caused by:

•	Payment providers

•	Local regulations

•	Tax/VAT handling

•	Sanctions

•	Platform-level filtering

Even if Fab blocks certain cases earlier in the flow, a seller-side diagnostic visibility layer (aggregated, anonymized) would allow us to:

•	Understand where demand is being blocked

•	Avoid misinterpreting low conversion as “no interest”

•	Provide proper guidance to users instead of blind troubleshooting

This is not about bypassing rules — it is about transparency and operational clarity for sellers.

3. Purpose of “Tax-Applied vs Non-Taxed Regions” Analytics

This data is not intended for tax compliance (which Fab already handles well), but for:

•	**Net Revenue Forecasting:**

Tax-heavy regions have very different net revenue outcomes even at the same base price.

•	**Promotion Planning:**

If a region has visually high gross sales but low net yield due to tax, sellers can:

•	Adjust promotional strategy

•	Shift marketing focus to healthier regions

•	**Strategic Product Positioning:**

Some products perform better in tax-lighter regions for purely economic reasons.

So this metric would function as a business intelligence layer, not a bookkeeping tool.

4. Intended Use of “Failed Purchase Reports”

Totally agree that sellers cannot directly fix payment provider errors — but visibility still matters for these reasons:

•	**Support Efficiency:**

When users contact me saying “I can’t buy your product”, I currently have no way to verify:

•	If a failed attempt actually occurred

•	What type of failure it was

With even a simple aggregated dashboard, I could:

•	Confirm the issue exists

•	Direct the user to the correct support channel with confidence

•	Avoid misdiagnosis

•	**Conversion Funnel Diagnosis:**

If:

•	300 add to cart

•	5 complete purchase

This is a critical business signal, regardless of where the failure is handled.

The goal is not to override Fab support — it is to understand where buyers drop out of the funnel.

Even a simple breakdown such as:

•	Payment failure

•	Geo block

•	Tax rejection

•	Provider decline

Would dramatically improve seller-side decision making.

Developer Access

My suggestion regarding an API is not a demand for sensitive data — even read-only aggregated endpoints would be enough to:

•	Build seller dashboards

•	Create internal analytics tools

•	Reduce pressure on Fab’s internal roadmap

•	Let the developer community extend the platform organically

This would strongly align Fab with modern creator-first marketplaces.

My core intention with all these points is simple:

I want to operate as a data-driven seller on Fab, not in the dark.

Right now, many critical business questions cannot be answered:

•	*Where is demand coming from?*

•	*Where does conversion fail?*

•	*Which regions are blocked?*

•	*Which regions are worth targeting for growth?*

Adding even a minimal analytics layer would drastically improve seller trust, retention, and long-term revenue for both Fab and creators.

Thank you again for opening this dialogue.

Best regards,

Muzaffer

4 Likes