Softwr

Email Marketing · head to head

SAP Emarsys vs Ortto

SAP Emarsys logo

SAP Emarsys

Email Marketing

Retail-focused engagement platform now sold and contracted through SAP

From
On request
Rated
-
Ortto logo

Ortto

Email Marketing

Australian marketing automation with a customer data platform and analytics included rather than sold separately

From
On request
Rated
-

The short version

  • Each has a real cost: SAP Emarsys core modules including analytics, recommendations and loyalty are licensed separately, so the platform fee in the first quote is rarely the number you eventually sign.; Ortto contact-based pricing counts everyone stored, including unsubscribed and long-inactive records, so the bill rises with list decay unless someone owns a pruning routine.
  • They diverge on capability: SAP Emarsys covers Tactics library, Ortto covers Customer data platform.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which SAP Emarsys and Ortto actually diverge.

Attributes where SAP Emarsys and Ortto differ
AttributeSAP EmarsysOrtto
PlatformsWeb, iOS, Android, REST APIWeb, REST API

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated), category (Email Marketing).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in SAP Emarsys

  • Tactics library
  • Cross-channel campaigns
  • Smart Insight
  • Predict
  • Loyalty
  • SAP Commerce integration

Only in Ortto

  • Customer data platform
  • Journeys
  • Talk
  • Dashboards and reports
  • Playbooks
  • Capture

What people use each for

The jobs each tool is most often brought in to do.

SAP Emarsys

  • A retailer that needs standard lifecycle programmes live in weeks rather than building them from scratchnot Ortto
  • An SAP Commerce Cloud customer that wants engagement contracted on the same paper as the commerce platformnot Ortto
  • Consolidating email, SMS, push and paid audience suppression for a catalogue retailernot Ortto
  • Teams that want per-programme revenue reporting without building attribution logic themselvesnot Ortto

Ortto

  • A SaaS company that wants trial and onboarding lifecycle plus product analytics without buying two toolsnot SAP Emarsys
  • A small team replacing a stack of email tool, chat widget and dashboard product with one subscriptionnot SAP Emarsys
  • Reporting on revenue by campaign and cohort without exporting events to a warehouse firstnot SAP Emarsys
  • Teams already on Autopilot that need a supported migration path rather than a replatform to a US vendornot SAP Emarsys

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

SAP Emarsys

  • Core modules including analytics, recommendations and loyalty are licensed separately, so the platform fee in the first quote is rarely the number you eventually sign.
  • Licensing counts stored contacts, so a database retained for years costs money every month regardless of whether those contacts are still mailable.
  • Since the SAP acquisition, contracting and support escalation follow SAP processes, which lengthens procurement noticeably for buyers who are not already SAP customers.
  • The product is built around retail patterns, so B2B, media and subscription use cases sit awkwardly on a data model designed for orders and products.
  • Implementation normally involves a partner and runs to a quarter, so the speed advantage of the tactics library only applies after the integration work is finished.

Ortto

  • Contact-based pricing counts everyone stored, including unsubscribed and long-inactive records, so the bill rises with list decay unless someone owns a pruning routine.
  • Each bundled component is shallower than the specialist it replaces, and the email template editor in particular is behind the ecommerce-focused competitors.
  • Deliverability guidance and reputation tooling are thinner than at dedicated email providers, which matters most in the first months of a sending domain.
  • The partner and agency ecosystem outside Australia and New Zealand is small, so hiring contractors with real Ortto experience is harder than for the larger platforms.
  • Support hours follow Australian business time, so European and American teams often wait a working day for a substantive answer on complex issues.

Pricing, plan by plan

SAP Emarsys

On request
  • SAP Emarsys Customer Engagement$undefined/year
    • Licensed on stored contact volume with send allowances
    • Smart Insight, Predict and Loyalty modules licensed separately
    • Annual contract through SAP procurement

Ortto

On request
  • Ortto$undefined/month
    • Priced by number of contacts held, with separate email and SMS send allowances
    • Talk live chat and additional seats charged separately
    • Monthly and annual terms available

Which should you pick?

Choose SAP Emarsys if

  • You need tactics library.
  • You work on Web, iOS, Android, REST API.
  • You also want cross-channel campaigns.

Choose Ortto if

  • You need customer data platform.
  • You work on Web, REST API.
  • You also want journeys.

Questions people ask

Is SAP Emarsys or Ortto better?
Neither clearly leads. SAP Emarsys starts at On request and Ortto at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, SAP Emarsys or Ortto?
SAP Emarsys starts at On request and Ortto at On request.
Does SAP Emarsys or Ortto run on more platforms?
SAP Emarsys runs on Web, iOS, Android, REST API. Ortto runs on Web, REST API.
What is SAP Emarsys best used for?
SAP Emarsys is most often used for a retailer that needs standard lifecycle programmes live in weeks rather than building them from scratch, an sap commerce cloud customer that wants engagement contracted on the same paper as the commerce platform, consolidating email, sms, push and paid audience suppression for a catalogue retailer, teams that want per-programme revenue reporting without building attribution logic themselves. Of those, a retailer that needs standard lifecycle programmes live in weeks rather than building them from scratch and an sap commerce cloud customer that wants engagement contracted on the same paper as the commerce platform are not what Ortto is typically brought in for.
What can SAP Emarsys do that Ortto cannot?
SAP Emarsys covers Tactics library, Cross-channel campaigns, Smart Insight, Predict. Ortto covers Customer data platform, Journeys, Talk, Dashboards and reports.

Answered from the vendors’ own pages

SAP Emarsys: Do we need to be an SAP customer?

No, it is sold standalone. But the contracting, legal and support processes are SAP processes, which is a real cost for smaller buyers.

Ortto: Is Ortto the same product as Autopilot?

It is the successor from the same company, rebranded in 2022 and substantially rebuilt. Older Autopilot tutorials no longer match the interface.

SAP Emarsys: What is actually included in the base licence?

Contacts, channels and the tactics library. Smart Insight, Predict and Loyalty are commonly assumed to be included and are not.

Ortto: Do inactive contacts cost money?

Yes. Pricing counts contacts stored, so unsubscribed and dormant records consume allowance until they are deleted.

SAP Emarsys: Is it suited to B2B?

Not really. The data model and the tactic library assume retail orders, products and repeat purchase behaviour.

Ortto: Can it replace a BI tool?

For campaign, funnel and cohort reporting on its own event data, usually yes. For joins against finance or support data it cannot.

Share

Related pages

Other head to heads