Upcoming releases

Note: This is the initial version of the documentation, published early to provide partners with visibility into upcoming changes. The documentation will be updated as additional details become available. The expected release dates are indicative only and may change.

Local currency support

Expected release: November 2026

Local currency support introduces country-specific price lists through the existing Fetch Price List API. The pricing and currency rules for each country take effect on its cutover date. The cutover date is the date on which the country-specific price list becomes available and takes effect.

Important: Local currency support will be rolled out in phases. The first phase introduces country-specific pricing in USD. The second phase introduces CAD for Canada and MXN for Mexico. Follow official communications from Adobe for information about the releases.

What changed?

• Country-specific prices can differ from regional prices for the same offer, currency, and price list month. Each offer's firstOrderDate for each order indicates when the country-specific price takes effect for orders.
• New orders use the applicable country-specific price list and currency, subject to commitment exceptions. Existing subscriptions transition to the new currency at anniversary renewal, while active 3YC and HGO commitments retain the existing currency until the commitment ends.
• Subscriptions in both the old and new currencies can remain active for the same SKU. At renewal, eligible quantities from the old-currency subscription are consolidated into the new-currency subscription, excluding quantities that were renewed early. Partners can disable auto-renewal for the old-currency subscription to prevent consolidation.
• Existing flexible discount codes are carried over during consolidation.
• API requests to create orders or previews using the old currency are rejected after the currency change, subject to commitment exceptions.
• Eligible early renewals in the new currency cannot reference an old-currency subscription.

Why it matters

Partners can quote country-specific prices and manage currency transitions without losing subscription history or counting early-renewed seats twice.

Action required

For more information, see Local currency support.

Adobe Instant Deal Registration

Expected release: November 2026

Adobe Instant Deal Registration is an automatically applied, codeless reseller credits, removing the need for a manual registration step on qualifying orders. There is no code to request, submit, or track. Partners see the intant deal registration amount directly in any qualifying orders and can view information on the deal through two discovery APIs. For more information see, Adobe Instant Deal Registration overview.

What changed?

• The Flexible Discounts API introduces a DEAL_REGISTRATION discovery category that provides descriptive details, validity dates, status, qualification criteria, and instant deal registration outcomes without exposing a code or identifier. Partners must explicitly request this category during discovery.
• The Recommendations API introduces the includeDealRegistrations request parameter. The value defaults to false. When set to true, the response includes a discounts.dealRegistrations section and prioritizes opportunities whose eligible products intersect with products already owned by the customer.
• Preview Order, Create Order, Get Order, Get Order History, Preview Renewal, and Return responses include isDealRegistered when Instant Deal Registration was auto-injected for a line item. The field value indicates whether the deal registration amount was successfully applied.
• For requests with fetch-price=true, qualifying line items include per-unit earnedDealRegPerUnit and line item-total earnedDealRegAmount; pricingSummary includes the aggregated totalEarnedDealRegAmount.

For more information, see Discover and verify Adobe Instant Deal Registration using APIs.

Why it matters

Partners can identify Instant Deal Registration opportunities in advance through Order Preview, Get Recommendations, or the Flexible Discounts API. When a qualifying order is placed, the applicable deal registration amount is applied automatically and is reflected immediately in the order results.

Unlike a traditional deal registration rebate, the deal registration amount appears as an upfront line item in the recon file, reported separately from lineItemPartnerPrice, discountedPartnerPrice, and totalLineItemPartnerPrice.

Partner actions

Testing Adobe Instant Deal Registration in Sandbox

Sandbox provides predefined scenarios that simulate both qualifying and non-qualifying Instant Deal Registration outcomes while remaining contract-compatible with production responses. See Test Adobe Instant Deal Registration in Sandbox.

Churn and seat expansion propensity are now surfaced in the Recommendations API

Expected release: November 2026

Partners can now see churn risk and seat expansion signals for each customer through the existing Fetch Recommendations (POST /v3/recommendations) API.

What changed?

Set the request parameter includePropensity to ["churn"], ["seatExpansion"], or ["churn", "seatExpansion"] to retrieve the corresponding churn and seatExpansion propensity signals. Each contains a probability rating (HIGH, MEDIUM, or LOW), a refreshDate, and a reasons array with up to seven leading indicators ordered by relevance.

Seat expansion also includes predictedAddonSize with the expected number of additional seats.

Important: An empty object {} for either node means propensity data is not available for that customer. Do not interpret {} as LOW risk or LOW expansion potential.

Why it matters

Partners can now identify at-risk customers and high-growth opportunities using data-driven signals, rather than relying on anecdotal indicators or waiting for account-manager outreach.

Action required

For more information, see Propensity Intelligence.

Testing Propensity Signals in sandbox

A set of 13 predefined test seeds is configured in the Sandbox so you can exercise every combination of rating level and empty-array behavior during integration testing. Each seed returns a fixed response.

For more information, see Testing Propensity Signals in sandbox.