What it takes to list a data product on Snowflake Marketplace

This guide is for a data team deciding whether to list a data product on Snowflake Marketplace. It sets out, from Snowflake's own documentation, what a provider needs before a first listing, what the listing must contain, how review and regional delivery work, and what you owe consumers afterwards, so that you can cost the work before you commit to it. A data marketplace gives a product a place to be found and a way to deliver it. It does not decide what you are allowed to sell, which is a question for your licences.

What a listing is

A listing wraps a share or a Snowflake Native App in descriptive metadata. Snowflake's documentation separates private listings, offered to named consumers, from public listings on Snowflake Marketplace, and it describes three kinds of access: free; limited trial, which gives access for 1 to 90 days and lets the consumer ask for the full product; and paid, with pricing plans and offers. A Marketplace listing can attach a secure share, a Native App or a connected app.

For a product that is a set of tables, the share is the usual choice. Secure Data Sharing copies and transfers no data between accounts: the consumer creates a read-only database from the share and queries it in place, and pays for the compute that does so, while the storage stays with you. A direct share works only between accounts in the same region, which is why a listing carries its own regional delivery, described below. The guide to Snowflake Secure Data Sharing covers the mechanism in more depth, and the guide for buyers on Snowflake Marketplace shows the consumer's side of a listing.

What you need before you start

Snowflake's provider documentation sets these requirements:

1. A full Snowflake account. A trial account can share data with named consumers but not on Marketplace, and a reader account cannot be used.
2. The ACCOUNTADMIN role, or a role with provider privileges: the global privileges to create listings and shares, and ownership of the listing and of the share or application package attached to it.
3. An organisation administrator, holding the ORGADMIN role, who accepts the Snowflake Provider and Consumer Terms, and a read of the Provider and Consumer Policies by whoever will run the listing.
4. A provider profile, set up in Provider Studio and approved by Snowflake, which the documentation says Snowflake answers in about one business day.
5. For paid listings, a billing address in one of the countries the documentation lists, and a Stripe Express connected account, because Marketplace payouts are processed through Stripe.

The terms are accepted at organisation level by a different role from the one that builds the share, so ask for that step first.

What the listing must contain

The documentation, on its page for configuring listings, sets the fields below for a public listing. A private listing needs less: a title, a profile, a description, terms of service and the consumer accounts.

Quick start examples are validated when you submit, so write them against the shared objects and make each return a row. The data dictionary lets a consumer inspect columns before installing.

Take an illustrative product with one row for each company and day, refreshed daily and covering companies worldwide. Its attributes would read: update frequency, daily; geographic coverage, worldwide; time range, from the first day loaded. Its quick start queries can be written so that each returns a row whenever the table is not empty, by choosing the day and the company from the data and not hard-coding them:

select max(day) as latest_day, count(*) as companies
from published.company_daily
where day = (select max(day) from published.company_daily);

select company_id, open_roles
from published.company_daily
where day = (select max(day) from published.company_daily)
order by open_roles desc
limit 10;

select day, open_roles
from published.company_daily
where company_id = (select max(company_id) from published.company_daily)
order by day desc
limit 7;

Describe the product exactly. The Provider and Consumer Policies require an accurate description of the update frequency, the geographic scope, the regions where the product is available and the completeness of its fields. For a product with model-made labels, completeness means saying which fields can be empty and what an empty field means, so that a consumer reads each label correctly.

Review, publication and regions

A Marketplace listing is submitted for approval. The provider workflows page says Snowflake checks the listing's metadata and replies in about one business day, and that a Native App also gets a functional review, which can take up to 14 days. An approved listing is published unless you chose manual publishing, in which case it stays approved until you publish it. A rejected listing comes back with instructions by email on what to correct. After the first publication, later changes that need approval are published automatically once approved, unless you chose manual publishing.

Regional delivery needs its own setup. With Cross-Cloud Auto-Fulfillment Snowflake replicates the data product to consumer regions as needed, so that you do not replicate it by hand or approve each request. Setting it up involves the organisation administrator again, because the provider documentation says the ORGADMIN role must first delegate the privilege to set up auto-fulfillment. The documentation states that making a data product available in other regions incurs additional costs, that the default size limit is 10 TB and that an account administrator can raise it, and that you choose how the copies are refreshed: on demand, at an interval from one minute to eight days, or on a schedule. A table refreshed daily fits the interval or schedule option. Whichever you choose, a consumer in another region sees the data as of the last refresh, so state the refresh in the listing.

What you owe consumers afterwards

The Provider and Consumer Policies set duties that continue after publication. A product must match its listing and must not change materially, for example by dropping core fields or cutting the update frequency sharply. You must hold the rights to share or sell what you list, and if the product contains personal data you must be legally authorised to share it. A product offered publicly may not reveal sensitive personal data. Providers are expected to reply to enquiries from Snowflake and other customers within three business days.

You can watch use in Provider Studio and in the DATA_SHARING_USAGE views of the SNOWFLAKE database. The LISTING_CONSUMPTION_DAILY view returns one record for each consumer account that queried the data on a date, with up to two days of latency and 365 days of retention, according to its documentation page. Access needs the ACCOUNTADMIN role or a role granted the right privileges.

Licensing the data you list

If the product contains data you license from someone else, your right to list it comes from that licence, and Snowflake's policies make you responsible for it. Fokals is licensed by written agreement for internal use, embedding in a product or redistribution. Whatever the provider, the right to list a product built on licensed data is a term to settle in writing before you build. The page on data licensing for platforms, the guide to what a data licence covers and the guide to redistributing company data under licence set out the questions to put.

Deciding whether to list

Five questions decide whether the work pays for itself:

1. Do your buyers already work in Snowflake? A listing reaches consumers who query in Snowflake, so buyers on other platforms need files or an API as well.
2. Is the product a set of tables and views that fits a share, or does it need an application?
3. Which regions must you serve, and can you carry the replication cost and keep each copy refreshed on the schedule the listing states?
4. Will you charge through Snowflake or by contract? Paid listings use usage-based or subscription-based pricing plans, paid out through Stripe or, where a consumer spends a capacity commitment, by Snowflake. The pricing documentation states no fee rate, so ask Snowflake for its current terms.
5. Do your licences allow it, and can you meet the accuracy duties and the three-day reply?

Frequently asked questions

The queries and code on this page are examples to adapt. Test them in your own environment before you rely on them.

What this page says about the products it names was checked against their public documentation on 4 October 2026. Product and company names are trademarks of their owners. Fokals is not affiliated with them or endorsed by them.