Salsify pricing — quote only, and it is not a media platform

What the site says today, and what it does not

Read on 20 August 2026: salsify.com/pricing carries no price. No tiers, no dollar figures, no billing basis, no published minimum. The page presents product capability and customer proof and routes to "Request Demo" and "Watch Demo".

State that neutrally, because it is neither unusual nor a failing. Enterprise software with variable scope — how many SKUs, how many retailers, how many users, which modules — is genuinely hard to put on a rate card, and Salsify sits in company with Pacvue, Intentwise, Quartile, Criteo, Rithum, Flywheel and ShipBob, all of whom quote on a call. It is also, for the avoidance of doubt, exactly what we do on Dr. DSP.

What Salsify describes itself as, in its own words: an "Intelligent Product Experience Management (PXM) platform" for managing product data across physical, digital and agentic commerce channels, turning product data into revenue-driving experiences. The modules it names include PIM, a syndication network, Enhanced Content, an Intelligence Suite, a conversational assistant called Angie, SalsifyIQ, Digital Shelf Analytics, a GDSN data pool, Catalog Sites and a Grocery Accelerator.

And the thing most relevant to anyone who arrived here from an advertising search: advertising, retail media and Amazon DSP are not mentioned. That is not an omission on their part — it is not their category. But it means a shortlist that has Salsify next to a DSP has two different purchases on it, and the rest of this page is about telling them apart.

One more disambiguation while we are here. Amazon DSP means Demand-Side Platform — programmatic buying of display, video and audio inventory with Amazon shopping signal behind it. It is not Amazon's Delivery Service Partner parcel franchise, and it is not a content tool.

The arithmetic Salsify's own numbers permit

A vendor that publishes no price frequently publishes scale figures instead, and those figures tell you something more decision-relevant than a rate card would: who the product is actually built for.

From Salsify's own announcement of its acquisition by Cinven, dated 22 July 2026: more than 2,000 customers, approximately 750 million products published across 2,600 commerce destinations, and 70,000+ active users.

Divide those by the customer count and the picture sharpens considerably:

• Roughly 375,000 products published per customer. That is not a catalogue of a few hundred SKUs. It is an enterprise product estate, usually meaning many variants, many locales and many retailer-specific versions of the same item.
• Roughly 35 active users per customer. Thirty-five people touching the system means a merchandising or product-data function with real headcount — not one operations manager doing it on Fridays.

Those are averages across a book that certainly includes both very large and much smaller accounts, so no individual reader should treat them as a threshold. What they legitimately tell you is the shape of the typical buyer, and therefore the shape of the quote you should expect. If you have 400 SKUs and two people who would ever open it, you are far below the centre of gravity of this product, and the quote will tell you so before the demo does.

This is a more useful yardstick than a headline price would have been. A published figure would have applied to a tier you might not be on. An average customer profile tells you whether the conversation is worth having at all.

There is a second reading of the same figures that shapes the quote you should push for. 750 million products across 2,600 commerce destinations means the syndication network is very wide — but width is only worth paying for where it overlaps your own retailer list. A network with 2,600 destinations and not the four that matter to you is worth less to you than one with a hundred that includes all four. So the question to open the commercial conversation with is not "how many retailers do you support" but "which of my specific retailers do you already have live templates for, and which would need building" — because the second half of that answer is a services line, not a licence line, and it is where the year-one bill grows.

Apply the same test to the user count. Thirty-five average users tells you the product assumes a team with defined roles — someone owning taxonomy, someone owning assets, someone owning retailer relationships. If your version of that is one operations manager with a spreadsheet, the software will not supply the roles, and buying it before the roles exist is the most common way these implementations stall.

How to read a quote for software that publishes no price

When there is no rate card, the negotiation is the rate card. Six questions turn a quote into something comparable.

• What are the meters? PXM systems are typically priced on some combination of SKU or variant count, user seats, connected retail destinations, modules enabled, and API or syndication volume. Get every meter named, in writing, before you get a number.
• What happens when a meter moves? Ask specifically what a 30% catalogue increase does to the fee mid-term, and whether it is billed as an overage or forces a tier change. This is where banded software costs people money they did not plan for.
• Which modules are in the number? With ten-plus named modules, "Salsify" is not one product. Confirm exactly which of them your quote includes and what each excluded one would add.
• What is implementation? Data migration, taxonomy design, retailer template mapping and integration work are real projects. For a system of this class the year-one services line can rival the licence, and it is not on any pricing page anywhere.
• Term, renewal and notice. How long, does it auto-renew, how many days' notice and in what form?
• Data portability. On exit, what leaves with you — the enriched content, the taxonomy, the retailer mappings, the asset library — and in what format?

The sixth one is the one people skip and regret. A PXM system becomes the place where years of enrichment work lives. The cost of leaving is rarely the notice period; it is the reconstruction.

A useful device that applies to any vendor with a billing toggle or a discount claim: take the advertised annual total, divide it by twelve, and check whether it equals the monthly figure you were quoted. If it does not, you are looking at two billing bases and should say which is which. Run that on us as well.

The Cinven acquisition, and the clause it makes worth asking about

On 22 July 2026, Salsify announced that the international private equity firm Cinven had agreed to acquire it. Financial terms were not disclosed. Salsify's chief executive Piyush Chaudhari is quoted saying Cinven's "conviction in our vision and its recognition of our platform, market opportunity, and customer momentum reinforce the strength of all that our team has built to date". Cinven partners Daniel Garin and John Cuyulis describe Salsify as "a business that exemplifies the qualities we seek in a transformative software investment". Both parties describe intentions to invest in product and accelerate international expansion, and the deal remains subject to regulatory approvals and customary closing conditions.

We are going to say something careful here and then stop. A change of ownership is a fact, not a warning. Private equity investment in a growing software company is ordinary, frequently good for the product, and we have no basis whatever for predicting what it means for Salsify's customers. Anyone telling you otherwise is guessing.

What it legitimately does is make one contract clause worth reading, and that clause is worth reading at every vendor regardless of whether anything has happened to them. Change of control. Specifically:

• What happens to your rate at the next renewal if the company changes hands?
• Is there any price protection, and for how long?
• Does your notice period change?
• Does data portability survive?

This category has consolidated steadily for four years across ownership structures of every kind. That is a reason for a standard diligence question, not a reason for suspicion about anyone. Ask it of Salsify, ask it of their alternatives, and ask it of us.

The two budget lines, and which one is actually failing

Here is why a DSP company has a page about content software at all: these two budgets are confused constantly, and buying the wrong one first wastes both.

Budget line one is content. Product data, images, A+ content, syndication to retailers, keeping variants and locales correct. It is a licence plus services, it scales with catalogue and headcount, and it changes how well traffic converts once it arrives.

Budget line two is demand. Sponsored ads and display, which decide how much traffic arrives at all. It scales with media and it changes volume, not conversion.

A diagnostic that settles it in an afternoon: look at whether your problem is traffic or conversion, per product, on your best sellers. If your top products get plenty of sessions and convert poorly against category norms, more media multiplies a leak. If they convert well and barely anyone sees them, content polish will not fix that.

And the failure mode people actually hit is neither: spending on demand that was never incremental. That is the specific thing our products exist to test. Last-click attribution cannot prove incrementality, because it only ever sees the conversions it already claimed credit for — it has no representation of what would have happened otherwise. A holdout or a matched control can, and for Amazon that reconciliation happens in Amazon Marketing Cloud, where DSP and sponsored-ads event data sit together and stop double-counting each other.

For scale on the demand side: Amazon's own DSP page states that its managed-service option "typically requires a minimum spend of $50,000", varying by country. Across 30 advertisers in July 2026, our live Amazon DSP API pull recorded 6.04x return on ad spend, 78.4 million impressions at a $4.00 CPM, a blended $1.42 cost per click and a $5.49 cost per acquisition across 57,137 attributed purchases, 20.1% of them new to the brand. One month, thirty advertisers, scoped exactly as measured.

Where we sit, and what we do not publish either

Fair disclosure before any of the above reads as a sales argument. Dr. DSP publishes no price. Neither does Dr. Stock. Salsify publishes no price. On this specific dimension nobody in this comparison is impressive, and Skai — which publishes four exact annual tiers on its own site — is ahead of all of us.

What we can state exactly is the model. Dr. DSP is a demo, the first 30 days free, and pricing agreed on the call against your real media budget and the scope of work, with Orbit — the full software suite — included at no additional cost. Orbit is analytics and operations software; it is not a DSP and not a PXM, and we are not going to imply it substitutes for either.

Our sponsored-ads product does publish. Dr. PPC is $300 a month plus 3% of ad spend, capped, month-to-month, with the first 30 days free, and Orbit included. That is a real number on a real page and it is a fair guide to how the group thinks about fees generally.

Behind all of it: Full Circle, a full-service Amazon management company with more than $500M in managed revenue across 100+ brands. Fable 5 does the daily work; operators from that team supervise it; you choose the autonomy level, from every change waiting on your approval through to fully autonomous inside agreed guardrails. Every proposed change carries the evidence behind it, a measurement plan, and a rollback trigger before it runs.

We do not sell, resell or replace product content management. If your catalogue data is the bottleneck, buy that first and come back to media afterwards — and we would rather write that sentence than take a media budget that was never going to work.

Read the contract, not the feature grid

For quote-only software the terms of service decide more of your exposure than any demo. Most vendors in this space do not publish theirs. Quartile does, and it is the clearest worked example available, so use it as the template for what to ask even though it is a different product.

Quartile's published terms set a one-year initial term that "shall automatically renew on each anniversary of the Effective Date for successive one-year periods", with written notice of non-renewal at least sixty days before expiry. Fees are "due in advance of Services rendered" and the client "shall not be entitled to any refund in connection with any termination". There is a sixty-day Evaluation Period from the effective date in which the client can terminate via a designated button, and outside it early termination means paying the fees that would have been due for the remainder of the term. Month-to-month exists only as a right Quartile "may, in its sole discretion, grant certain Clients", with thirty days' notice.

Nothing there is improper. It is a normal enterprise contract and publishing it openly is more than most of the category manages. The point is the shape: a one-year auto-renewing term with sixty days' notice gives you about 305 days a year in which you cannot act. Diary the notice date the week you sign, whoever the vendor is.

The checklist for any PXM or media vendor, ours included:

• Every meter named, and what a 30% increase in each does to the fee.
• Implementation and migration quoted separately, in writing.
• Term, renewal, notice period, and the address notice must go to.
• Written notice of any fee change, from any vendor including us.
• Data portability on exit — enriched content, taxonomy, mappings, assets, in a named format.
• Change of control, and any price protection attached to it.

Two places to go next, and only if the description fits. If you are still deciding which category you are shopping in, our page on Salsify alternatives separates the three different jobs that get shortlisted as one. And if your product pages already convert and the open question is whether display is adding sales at all, that is a media purchase and the measurement design should come before the budget.