Appstle Subscriptions

The dunning in Appstle is very basic. So many apps have better dunning features. One thing that would be really helpful would be silent retries that don't count against your dunning settings for soft failures. Here's just one example: I had a customer's payment method fail with the reason "There was a problem with Shop Pay". Something like this should not trigger a notification to the customer and should be retried maybe 2-3 times in the same day a few hours apart. This error resolved itself with no action by the customer. All it did was create confusion for them. Like what are we expecting the CUSTOMER to do if there's a problem with SHOP PAY? There's no reason to involve them. I have my dunning set up as 4 tries 1 day apart. But even with these settings it should allow for 2-3 silent retries per day for soft failures. Other soft failures might include issuer/network issues, insufficient funds, activity limit exceeded, etc. None of these should involve the customer and none of them should count toward my dunning limit. Only hard failures should count toward the limit.

Merchant wants a subscription plan wise breakdown for the quantity of products in the contracts.

would be great to have a monthly build your own subscription box appear as a product in a collection

we would like to request a simplified flow for customers to pause or take a break from their subscriptions. Currently, the process involves multiple steps: first, the customer selects the subscription type (pause or take a break), then chooses the duration, followed by acceptance. The merchant would like the flow to be more intuitive: Step 1: Customer selects the pause or break option. Step 2: A message informs the customer that they can take a break for a set period. Step 3: The customer selects the pause duration in a drop-down menu. Step 4: Dynamic Button (Pause Button Instead of cancel) This change will make the process clearer and more straightforward for customers.

I noticed that when I go to the build-a-box page that Appstle provides, it autoselects the first product. I do not want it to do that. Do you know how i can change this? ​ https://onitathlete.com/apps/subscriptions/bb/lc8r1coi

I'd like an option to have digital subscription items sent only to ACTIVE members as I cannot create a new listing every time (defeats a subscription listing), I currently update the files on the subscription but notice that all previous purchasers receive the update so it is not fair to people who have active subscriptions, and those who should not be receiving it are exploiting this issue.

Currently, customers can only be presented with one option at a time when they attempt to cancel their subscription. It would be incredibly beneficial to have the ability to create multiple retention options within a single flow. This would allow customers to be offered various alternatives (e.g., changing subscription frequency, skipping shipments, or receiving discounts) in a seamless, multi-step process before they finalize their cancellation. This feature would help improve retention by providing customers with more choices, ultimately reducing cancellations and increasing customer satisfaction.

Description: In the customer portal, when a customer with an active multi-pack (bundle/volume) discount updates the variant of an item within their subscription, the displayed price does not immediately reflect the applicable discount. Instead, the correct discounted price is only shown after the page is manually refreshed. Proposed Enhancements: Real-Time Price Update in Portal: Ensure that whenever a variant is changed within the customer portal, all applicable discounts (including multi-pack discounts) are recalculated and reflected instantly in the displayed price. User Guidance (Fallback Option): If real-time updates are not feasible in certain cases, display a clear inline message such as: “Discounts will be applied after refreshing the page.” This helps set the right expectation and avoids confusion. Dynamic Feedback Indicator: Introduce a brief loading or recalculation indicator when a variant is changed, signaling that the system is updating the pricing.

It's really hard to tell how many people skip or renew per selling plan. Further analytics, sorting features, and easier methods of organizing data is sorely needed

We offer prepaid subscriptions (e.g. 3, 6, or 12 issues) where customers pay upfront and are entitled to receive all issues purchased. However, the current system treats a cancellation as an immediate stop to the subscription. This means that when a customer cancels after subscribing, they are marked as “cancelled” and no longer appear as active — even if they still have remaining issues that have already been paid for. As a result, we lose visibility of customers who still need fulfilment, creating a risk that paid issues are not dispatched. What is needed: The system must allow a subscription to remain active for fulfilment purposes until all prepaid issues have been delivered, even if the customer cancels renewal immediately after subscribing. Cancellation should only prevent future renewals, not stop fulfilment of already paid issues.