Data 360 Provisioning for ISVs moves partner apps that use Data 360 onto Flex Credits, where batch ingestion is free and the rest of the work is metered from a public rate card. Salesforce says the new SKU "replaces legacy Cloud SKUs by consolidating usage into a single Flex Credit currency" and offers "free unmetered batch ingestion" (Summer '26 ISV strategy). Free ingestion is the easy part. Identity resolution, streaming and real-time pipelines are where the credits go, and those are design choices your app makes.
For a SaaS company with a Salesforce app, that changes two decisions. One is how your product moves data into the customer's Data 360. The other is whether you resell credits or leave consumption on the customer's own bill. Appnigma's marketplace apps team builds native Salesforce apps for SaaS companies. The service covers "a native app, marketplace listing preparation, and review support." If you are a Salesforce customer pricing Data 360 for your own team, Salesforce's Data 360 pricing calculator is the better starting point.
Updated October 2026. Checked against the Salesforce Flex Credits rate card dated August 31, 2026, the Data 360 pricing pages and the Data 360 developer guide. This update corrects the earlier version of this post. It said Salesforce had no public rate card, that storage at rest was free and that only activation was billed. It also described per-cloud data volume quotas and a 70% savings example that no Salesforce source supports. It adds the meter-by-meter arithmetic, the $0 Provisioning SKU, who pays in each sales model and the partner org setup.
What Salesforce announced for ISVs, and what it didn't
The April 2026 announcement is one paragraph in the Summer '26 ISV strategy post. It calls Data 360 Provisioning for ISVs a "new SKU (generally available April 2026)" and says "You only pay when data is activated for an agentic outcome." It doesn't publish the SKU's price, included credits or who signs the order. Ask your partner account manager for those three things before you model margins.
The commercial route for partners came earlier. In December 2025 Salesforce wrote that ISVs can start "reselling Data 360 credits directly within your existing contracts," and that "Embedded licenses let you target companies outside the existing Salesforce ecosystem" (Data 360 for ISVs is GA). So the April SKU is a pricing change on top of a partner program that already existed.
Two naming details trip people up. Data Cloud is now Data 360 (Salesforce's own calculator is titled "Data 360 (Formerly Data Cloud)"), but Setup and permission sets still say Data Cloud, and the 2GP workflow guide still tells you to verify in "Data Cloud Setup." And the customer price list has its own "Data 360 Provisioning SKU," a $0 SKU covered in a section below. It shares a name with the ISV announcement, and Salesforce doesn't say whether they are the same thing.
The "legacy" model being replaced is Data Services Credits, priced from a separate rate card where external batch ingestion cost 2,000 credits per million rows. Customers on it aren't forced to move. The Data 360 pricing page says "There is no forced migration," and switching means swapping "all of your existing Data Services Credits." Some of your customers will be on each model for a while, and a batch-heavy app costs the ones still on Data Services Credits more, because their card bills external batch ingestion.
Which Data 360 meters still run after free batch ingestion
Free batch ingestion is not limited to the ISV SKU. The pricing page offers "free batch data ingestion and zero-copy integrations" to every Flex Credit customer, and the Flex Credits rate card has no batch ingestion line. Everything after ingestion has a multiplier. Additional credits list at "$500 per 100,000 credits" (pricing calculator), which is $0.005 a credit. The dollar column below is our arithmetic at that list price, at the base tier.
| Data 360 usage type | Credits at base tier | List cost |
|---|---|---|
| Batch ingestion | none listed | $0 |
| Queries, per 1M rows processed | 3 | $0.015 |
| Prep, per 1M rows processed | 40 | $0.20 |
| Segmentation, per 1M rows processed | 50 | $0.25 |
| Activation, per 1M rows processed | 60 | $0.30 |
| Streaming pipeline, per 1M rows processed | 3,500 | $17.50 |
| Unification, per 1M rows processed | 75,000 | $375 |
| Real-time pipeline, per 1M events, API calls and actions | 250,000 | $1,250 |
| Unstructured processing, per MB | 150 | $0.75 |
Activation is one of the cheapest lines on the card. Unification, which is identity resolution across sources, costs 1,250 times more per million rows than activation. The real-time pipeline costs about 70 times more per million events than the streaming pipeline costs per million rows. That flips the advice in most early coverage of this SKU. Your margin depends less on how much data your app activates and more on whether it needs identity resolution, sub-second freshness or unstructured files.
Two rules on the card change the arithmetic. Multipliers drop at volume, with tier 2 starting at 300,000 credits, and "Tier multipliers are based on the individual usage type and reset on the first day of each calendar month." Credits "must be used before the Order End Date" and "no rollover will be permitted." A customer who buys a year of credits for a seasonal workload loses whatever is left at the end of the term.
A worked example shows the gap. Say your app syncs 5 million rows a month from your backend into a customer's Data 360. In batch, ingestion costs nothing. Segmenting and activating those rows costs 550 credits, about $2.75 at list. Run the same rows through identity resolution and unification adds about 360,000 credits, because the first 4 million rows bill at the base tier and the last million at the tier 2 rate. That is about $1,800 a month at list, assuming nothing else in the org uses unification that month. The data is the same in both runs, and what changes the bill is the processing your app asks for.
What the $0 Data 360 Provisioning SKU covers
Salesforce sells a customer SKU called Data 360 Provisioning, also "referred to as Data 360 Everywhere SKU." The pricing calculator describes it as "a $0 SKU that provides all the functionality of the Data 360 Starter SKU." It is "provisioned for customers that don't have Data 360 use cases but are using other Salesforce products that are built-on or rely on Data 360 functionality." It includes 250K Flex Credits and 1 TB of data storage. Starter lists at $60K a year with 10M credits and 5 TB.
For an ISV, that SKU is the realistic floor in a customer org that hasn't bought Data 360. 250,000 credits are worth $1,250 at list. That covers about 4 billion rows of activation, or about 71 million rows through the streaming pipeline, at the base tier. It covers 3.3 million rows of unification, so one identity resolution run on a mid-size customer's contacts can use it up.
Storage is a fixed allowance in the SKU, not a metered usage type. The rate card has no storage line, and the calculator lists storage among the add-ons customers "can then add on." An app that keeps raw history inside Data 360 should plan for the customer outgrowing 1 TB.
Who pays when your app consumes Data 360 credits?
In the usual AppExchange model your package installs into the customer's org and runs against the customer's own Data 360. Credits come from that org's balance. The Data 360 provisioning decision guide says companion org usage is tracked "against the home org's credit allocation," and the customer watches it in Digital Wallet. Unless you resell credits, your app's processing shows up on their bill under their name.
That gives you three options, and each one sets who owns the bill.
| Option | Who holds the credits | What you have to build |
|---|---|---|
| Customer buys Data 360 directly | Customer | Usage guidance and in-app visibility, so the bill isn't a surprise |
| You resell credits in your contract | Customer org, sold by you | Pricing that covers credits plus margin, and usage reporting per customer |
| OEM with embedded Data 360 licenses | You sell the license | Full commercial ownership, including companies that aren't Salesforce customers |
The first two options sit in the December 2025 GA post, and OEM is the "embedded licenses" route in the same post. If you resell, you carry the risk that one customer's workload runs ahead of the credits priced into the deal. The Summer '26 post tells ISVs to start "shifting your thinking from per user per month to per action or completed process," which only works if you can count actions per customer.
You can read consumption from inside the org. The Apex ConsumptionCard class "Represents a Digital Wallet consumption card, including its consumption, total entitlement, and related consumption alerts." The Tenant Consumption Insights data object carries units consumed and multiplier tier. Salesforce doesn't document any way for an ISV to see a customer's consumption from outside that org. If you need it for billing, design the reporting into your app and get the customer's consent.
Getting Data 360 into your partner orgs and package
Your own orgs need Data 360 before you can build anything. Salesforce's partner article says to "Log a case with support to get Data 360 Licenses added to your Org," listing the IDs of your packaging, test and security review orgs (Data 360 Access and Provisioning). Partner trial orgs "expire after 30 days and cannot be extended," so don't keep test fixtures in one.
Scratch orgs need a second case. The Data 360 2GP workflow says partners "must log a case with Salesforce Partner Support," and Data 360 scratch orgs are "Only available for scratch orgs created from a Dev Hub that's part of your Partner Business Org." Your scratch definition then needs the CustomerDataPlatform feature. Testing isn't free either. The rate card says the sandbox multiplier "applies to pre-production environments, which include sandboxes as well as scratch orgs," and sandbox rates sit at the tier 2 level with no volume discount.
Data 360 metadata doesn't go straight into a package. "In Data 360, the features that you want to include must be added to a data kit first," and that data kit ships in either a "First-generation and second-generation managed packages with data kits" setup (app development comparison). The same path carries Tableau Next assets, covered in our post on packaging Tableau Next in a Data 360 data kit. Some Agentforce retrievers also land in a data kit, per our guide on which Agentforce components package and which go in a data kit.
Mistakes that inflate a customer's Data 360 bill
These are the design choices that move credits. Each one is visible on the rate card before you ship.
- Streaming data that could be batched. Batch is free and the streaming pipeline is 3,500 credits per million rows. Hourly or nightly batch is usually fine for CRM enrichment.
- Turning on identity resolution by default. Unification is the most expensive row-based line on the card. Make it opt-in, or run it on the subset of records your feature needs.
- Using the real-time pipeline for dashboards. At 250,000 credits per million events, keep it for features that need sub-second answers inside a live interaction.
- Sending files through Data 360 without a size budget. Unstructured processing bills per megabyte, and intelligent processing costs 600 credits per MB.
- Pricing a reseller deal on annual credits with seasonal usage. Credits don't roll over, so a customer with a quiet half year pays for credits they never use.
- Load testing in a scratch org without a budget. Pre-production use consumes credits at the sandbox multiplier.
Your app also needs a batch path from your backend into the customer's Data 360, and that sync has to keep working as both sides change. Appnigma's done-for-you team builds that kind of customer integration, with "custom logic, backend changes, and ongoing maintenance included."
Frequently Asked Questions
Is batch ingestion free in Salesforce Data 360?
Yes, under Flex Credits. The pricing page lists "free batch data ingestion," and the rate card has no batch line. Customers still on Data Services Credits are billed for external batch ingestion under the older card.
How much does one Flex Credit cost?
Salesforce lists additional credits at $500 per 100,000, which is $0.005 a credit before volume tiers and negotiated discounts (pricing calculator). An Agentforce action uses 20 credits, which is $0.10 (Salesforce press release).
Does Data 360 Provisioning for ISVs change the AppExchange revenue share?
No source says it does. The share on your app's sales is set in your partner agreement, explained in our AppExchange revenue share guide, and Data 360 credits are a separate line.
Can Appnigma build a Salesforce app that uses Data 360?
Appnigma's marketplace apps team builds "A Salesforce managed package or HubSpot app built around your product and customer workflows," with review support. We can check whether a Data 360 dependency fits your customers before you commit to data kit work.
About the author
Sunny Chauhan is the co-founder and CEO of Appnigma AI, which builds and maintains customer integrations and native Salesforce and HubSpot apps for B2B SaaS teams. Before Appnigma, he was on Salesforce's AppExchange team, where he worked with more than 300 SaaS partners. He has spent close to a decade on the Salesforce platform, including work at Zennify, and holds Salesforce certifications including Platform Developer II, Platform App Builder, Administrator, Data Cloud Consultant, and AI Associate.
Related Articles
- Tableau Next for ISVs
- How ISVs Can Embed Agentforce 360 in Their Products
- Building Agentforce Components for AgentExchange
- What Is Salesforce AgentExchange
- AgentExchange Go-to-Market App
- AgentExchange Builders Initiative
- Salesforce App Development Cost
Sources
- Salesforce, ISV Strategy for the Summer '26 Release
- Salesforce, Data 360 for ISVs Is GA
- Salesforce, Flex Credits Rate Card, updated August 31, 2026
- Salesforce, Data 360 Pricing
- Salesforce, Data 360 Pricing Calculator
- Salesforce, Data Services Credits Rate Card
- Salesforce Architects, Data 360 Provisioning Decision Guide
- Salesforce Developers, ConsumptionCard Class
- Salesforce Developers, Tenant Consumption Insights DMO
- Salesforce Help, Data 360 Access and Provisioning for Partners
- Salesforce Developers, Workflow for Data 360 Second-Generation Managed Packaging
- Salesforce Developers, Differences Between Developing Apps on Data 360 and the Salesforce Platform
- Salesforce News, Agentforce Flexible Pricing
