2 results found

1. API extension: Make trial status for plugin rentals queryable

   For extensions with usage-based features (e.g., character quotas, API limits, etc.), it would be very helpful to be able to query the current trial status of a plugin rental via API.

   Specifically, the following scenario applies:
   For plugins that unlock the full range of functions during the trial month (e.g., a translation plugin that can translate almost the entire shop), we are increasingly observing that users take advantage of the free month to translate the entire shop once and then cancel. Without a technical way to recognize the trial month, it is difficult to limit this fairly.

   A simple flag would be desirable, e.g., isTrialActive, which can be queried via API. This would allow us to activate a transparent limitation during the trial period and automatically unlock full functionality after it expires.

   Example application:
   During the trial month:
   - quota of, for example, 100,000 characters.
   - All functions can be tested realistically.
   - However, the free trial month is not used as a full “free full version.”

   After the end of the trial: Automatic release of the full quota/scope with active rental
   Such a trial flag would make it possible to design fair trial periods – both for merchants (realistic testing) and for developers (protection against abuse) – without complicated workarounds or external billing logic.

   For extensions with usage-based features (e.g., character quotas, API limits, etc.), it would be very helpful to be able to query the current trial status of a plugin rental via API.

   Specifically, the following scenario applies:
   For plugins that unlock the full range of functions during the trial month (e.g., a translation plugin that can translate almost the entire shop), we are increasingly observing that users take advantage of the free month to translate the entire shop once and then cancel. Without a technical way to recognize the trial month, it is difficult to limit this fairly.

   A simple flag… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  In-App Purchases  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Enhanced in-app purchase API for usage-based models

   We want to develop extensions that are billed entirely via IAP (comment from Shopware: IAP stands for In App Purchases) – without our own subscription logic or external billing. Typical use cases are usage-based features such as quotas (e.g., search volume per month), limits, or activations with periodic renewal.

   Currently, Shopware.InAppPurchase.isActive(‘MyExtensionName’, ‘my-iap-identifier’) only returns a Boolean (purchased: true/false).
   However, for usage-based models, we lack the specific billing period, e.g., to reliably reset quotas when transitioning to the new period.

   Our request/feature request:
   In addition to isActive(), minimal contract information would be helpful, e.g.:
   - Purchase or start date of the current billing period
   - Billing interval (e.g., monthly, annually)
   - Flag indicating whether it is a wildcard/stage environment

   This would allow usage-based features (such as search volume, API quotas, free requests, etc.) to be implemented correctly, transparently, and fairly— without having to implement a parallel subscription or billing solution alongside Shopware IAPs.

   We want to develop extensions that are billed entirely via IAP (comment from Shopware: IAP stands for In App Purchases) – without our own subscription logic or external billing. Typical use cases are usage-based features such as quotas (e.g., search volume per month), limits, or activations with periodic renewal.

   Currently, Shopware.InAppPurchase.isActive(‘MyExtensionName’, ‘my-iap-identifier’) only returns a Boolean (purchased: true/false).
   However, for usage-based models, we lack the specific billing period, e.g., to reliably reset quotas when transitioning to the new period.

   Our request/feature request:
   In addition to isActive(), minimal contract information would be helpful, e.g.:
   - Purchase or start date of the… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  In-App Purchases  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating