Arc XP Subscriptions Retail
Arc XP Subscriptions Retail empowers your marketing team to manage subscription products, launch targeted offers, and build effective campaigns, all without relying on developer support. The Retail vertical provides tools to configure and promote subscription offerings that drive audience engagement and business growth.
Retail includes four core components: Products, Offers, Campaigns, and Group Packages. These tools are interdependent and designed to work together, helping you move quickly from product creation to campaign execution.
Products: Defining what you sell
The Products page is the foundation of the Retail vertical. Here, you define the items your subscribers can purchase, including pricing and access entitlements. Each product is identified by a unique SKU and can support multiple price points, allowing for flexible subscription tiers and targeted promotions.
We recommend keeping your product catalog lean. Use Offers and Campaigns to create tailored promotions rather than duplicating products for each scenario.
See Managing products.
Offers: Tailoring your pitch
The Offers page lets you turn products into compelling promotions. Offers define how a product is marketed, including its messaging, pricing, duration, and target audience. Offers are essential for seasonal deals, customer win-back strategies, and tiered pricing models.
See ???.
Campaigns: Monitoring and optimizing
The Campaigns page helps your team manage performance across multiple live offers. With customizable table views, you can compare current and past campaigns, monitoring engagement, and identify opportunities.
See Viewing campaigns.
Group Packages: Expanding access
The Group Packages page lets you offer enterprise and shared subscriptions, like for a corporate office, educational institution, or household, as well as gift subscriptions. You can define access by email domain, IP address, or individual invite.
Prerequisites for Accessing Applications
To access and use the Subscriptions Retail application, ensure you have the following permissions:
Access Subscriptions - allows users to see a link to Subscriptions in the Arc XP navigation bar and dashboard and access the application.
Subscriptions: Retail - allows users to view and search offers and libraries, as well as manage user data.
Prerequisites for Paid Subscriptions Migration
User Account Migration
Before the Subscriptions application will accept a migration request for a paid subscription, it must be able to assign an owner to that subscription. This means that an account — one to which the user can sign in — must already exist in Arc Identity.
During an account migration, Arc XP issues an ID to each account. This ID is required when migrating a paid subscription.
You can learn more about the technical requirements for paid subscriptions migrations at Migrating to Arc XP Subscriptions.
Product Catalog and Pricing
You must configure your product catalog and pricing in the Arc Subscriptions admin UI before migrating paid subscriptions.
As a best practice, use a small number of products (fewer than 10) with many price points per product. In the product catalog:
Each product is assigned a SKU.
Each price is assigned a price code.
Both the SKU and price code are required for each paid subscription being migrated.
A subscription's SKU is also used to entitle the subscription owner to bypass the paywall. For this reason, you should plan your paywall strategy at the same time you configure SKUs in your product catalog.
You are expected to provide valid payment tokens for the gateway type under which paid subscriptions are being migrated. If payment tokens need to be migrated between providers before subscriptions are migrated to Arc, you may need to coordinate with your current provider.
Payment Gateway Setup
You must configure your product catalog and pricing in the Arc Subscriptions admin UI before migrating paid subscriptions. The following gateway types are supported:
Stripe Intents
Braintree
PayPal, Paypal Classic, Paypal via Stripe
PayU Latam* (Colombia and Peru only)
IFX (custom implementation)
Note
*PayU Latam was recently acquired by Rapyd. This may require a re-migration of paid subscriptions within Arc XP for publishers using PayU Latam as their gateway, if a direct integration is supported in the future.
Dunning Rules
You should also configure the dunning rules associated with your payment gateway, which is also done in the admin portal.
Payment Tokens
You are expected to provide valid payment tokens for the gateway type under which paid subscriptions are being migrated. If payment tokens need to be migrated between providers before subscriptions are migrated to Arc, you may need to coordinate with your current provider.
Note
Arc XP is not able to participate in a token migration between providers.
The table below shows the expected token format for each gateway type:
Gateway Type | Sample Token |
|---|---|
Stripe Intents |
|
Braintree |
|
PayPal |
|
PayPal Classic |
|
PayPal via Stripe |
|
PayU Latam |
|
IFX | Publisher-specific |
Validating Migration Simulation Data
Before executing a live migration, your development team will run a migration simulation. You should review the simulation results to validate that subscription data, expected revenue, and renewal schedules are accurate before proceeding.
Getting started
To start working with the Retail application, refer to the following documentation: