Sync Membership Address with Customer Default Shipping Address
🔍 Problem Statement Customers currently cannot update the address associated with their active memberships when they change their default shipping address, particularly when the custom UI does not expose the memberships view. This requires customers to contact Customer Service to make the change. 💡 User Story As a user, I want active memberships to automatically use the customer’s default shipping address when it is changed, so that customers can update their membership address without needing to contact Customer Service. 🎯 Definition of Done (DoD) ✔ ️When a customer changes their default shipping address, the new address is automatically assigned to their active membership(s). ✔ The behavior can be enabled/configured through the appropriate Pelcro setting.
Nada Shoukry 5 days ago
Sync Membership Address with Customer Default Shipping Address
🔍 Problem Statement Customers currently cannot update the address associated with their active memberships when they change their default shipping address, particularly when the custom UI does not expose the memberships view. This requires customers to contact Customer Service to make the change. 💡 User Story As a user, I want active memberships to automatically use the customer’s default shipping address when it is changed, so that customers can update their membership address without needing to contact Customer Service. 🎯 Definition of Done (DoD) ✔ ️When a customer changes their default shipping address, the new address is automatically assigned to their active membership(s). ✔ The behavior can be enabled/configured through the appropriate Pelcro setting.
Nada Shoukry 5 days ago
In Progress
Consumer Data Platform/CDP
🔍 Problem Statement As a publisher, I experience paywall targeting as a fixed attribute list set inside each individual paywall, which results in audiences I cannot express — anonymous readers with more than five page views in the last 30 days, for instance — receiving the same meter and gate as everyone else. 💡 User Story As a publisher, I want to define paywall targeting as a Pelcro segment rather than per-paywall attributes, so that an audience is described once and reused across paywalls. As a publisher, I want every attribute available in today's paywall targeting to also exist as a segment condition, so that deprecating paywall-level targeting costs me no capability I have now. As a publisher, I want to select a segment when I create a paywall, so that the paywall applies only to readers in that segment. [TBD: one segment per paywall, or several] As a publisher, I want to build segments over anonymous visitors from referral source and page-view frequency, so that I can target readers I know nothing else about. 🎯 Definition of Done (DoD) ✔ Given the segment builder, when a publisher creates a segment, then every attribute usable in paywall targeting today — country, platform, tag, URL, adblock — is available as a condition. ✔ Given a paywall, when a publisher configures targeting, then they select a segment, and the per-paywall attribute fields are deprecated in the UI. ✔ Given a reader in a targeted segment, when they load an article, then that paywall's frequency_limit and type_of_paywall apply instead of the untargeted paywall. ✔ Given each segment condition type, we should make sure the data will be available and can be evaluated client-side at paywall time. ✔ Given a paywall is displayed, when Paywall Displayed is logged, then the matched segment ID and applied meter limit are recorded. ✔ This solution will include the following limitations: anonymous identity is per-browser and resets on cookie clear; activity events are logged-in only and retained 3 months; geo is country-level at decision time; per-segment products, plans and campaigns out of scope.
Rana Haleem 5 days ago
In Progress
Consumer Data Platform/CDP
🔍 Problem Statement As a publisher, I experience paywall targeting as a fixed attribute list set inside each individual paywall, which results in audiences I cannot express — anonymous readers with more than five page views in the last 30 days, for instance — receiving the same meter and gate as everyone else. 💡 User Story As a publisher, I want to define paywall targeting as a Pelcro segment rather than per-paywall attributes, so that an audience is described once and reused across paywalls. As a publisher, I want every attribute available in today's paywall targeting to also exist as a segment condition, so that deprecating paywall-level targeting costs me no capability I have now. As a publisher, I want to select a segment when I create a paywall, so that the paywall applies only to readers in that segment. [TBD: one segment per paywall, or several] As a publisher, I want to build segments over anonymous visitors from referral source and page-view frequency, so that I can target readers I know nothing else about. 🎯 Definition of Done (DoD) ✔ Given the segment builder, when a publisher creates a segment, then every attribute usable in paywall targeting today — country, platform, tag, URL, adblock — is available as a condition. ✔ Given a paywall, when a publisher configures targeting, then they select a segment, and the per-paywall attribute fields are deprecated in the UI. ✔ Given a reader in a targeted segment, when they load an article, then that paywall's frequency_limit and type_of_paywall apply instead of the untargeted paywall. ✔ Given each segment condition type, we should make sure the data will be available and can be evaluated client-side at paywall time. ✔ Given a paywall is displayed, when Paywall Displayed is logged, then the matched segment ID and applied meter limit are recorded. ✔ This solution will include the following limitations: anonymous identity is per-browser and resets on cookie clear; activity events are logged-in only and retained 3 months; geo is country-level at decision time; per-segment products, plans and campaigns out of scope.
Rana Haleem 5 days ago
In Progress
Trigger Renewal/Expiration by Shipments Remaining for Print Subscriptions
🔍 Problem Statement As a publisher managing shipment-based print subscriptions, renewal and expiration are tied to end_date/renewal_date, which don't reflect actual shipments remaining. 💡 User Story As a publisher, I want auto-renewing (or scheduled-phase) shipment-based subscriptions to activate renewal automatically once shipments remaining hits 0, so subscribers aren't held to an unrelated date. As a publisher, I want non-auto-renewing shipment-based subscriptions to be marked expired once shipments remaining hits 0, so expiration reflects actual fulfillment status. 🎯 Definition of Done (DoD) Given a print subscription is auto-renewing or has a scheduled renewal phase, when shipments remaining reaches 0, then renewal activates regardless of end_date or renewal_date. Given a print subscription is non-auto-renewing with no scheduled renewal phase, when shipments remaining reaches 0, then the subscription is marked expired. Given an existing print subscription currently tracked by end_date/renewal_date, when this change ships, then it is migrated to shipment-count-based renewal/expiration logic. This change will impact API / SDK, specifically shipment-based subscription renewal and expiration logic. This solution will include the following limitations: applies only to pure print subscriptions (no print+digital combined pricing plans); end_date and renewal_date are not used as renewal/expiration triggers for shipment-based subscriptions; manual early-activation override is out of scope (superseded by automatic shipment-count trigger).
Rana Haleem 5 days ago
In Progress
Trigger Renewal/Expiration by Shipments Remaining for Print Subscriptions
🔍 Problem Statement As a publisher managing shipment-based print subscriptions, renewal and expiration are tied to end_date/renewal_date, which don't reflect actual shipments remaining. 💡 User Story As a publisher, I want auto-renewing (or scheduled-phase) shipment-based subscriptions to activate renewal automatically once shipments remaining hits 0, so subscribers aren't held to an unrelated date. As a publisher, I want non-auto-renewing shipment-based subscriptions to be marked expired once shipments remaining hits 0, so expiration reflects actual fulfillment status. 🎯 Definition of Done (DoD) Given a print subscription is auto-renewing or has a scheduled renewal phase, when shipments remaining reaches 0, then renewal activates regardless of end_date or renewal_date. Given a print subscription is non-auto-renewing with no scheduled renewal phase, when shipments remaining reaches 0, then the subscription is marked expired. Given an existing print subscription currently tracked by end_date/renewal_date, when this change ships, then it is migrated to shipment-count-based renewal/expiration logic. This change will impact API / SDK, specifically shipment-based subscription renewal and expiration logic. This solution will include the following limitations: applies only to pure print subscriptions (no print+digital combined pricing plans); end_date and renewal_date are not used as renewal/expiration triggers for shipment-based subscriptions; manual early-activation override is out of scope (superseded by automatic shipment-count trigger).
Rana Haleem 5 days ago
Customizable Invoice Due Date
🔍 Problem Statement The default due date for subscription invoices is currently fixed at 30 days and cannot be customized. We need the ability to set a different default due date for all future subscription invoices. 💡 User Story As a user, I want to configure the default due date for subscription invoices so that I can choose a payment period that fits our billing workflow. 🎯 Definition of Done (DoD) ✔ ️ Add an option to configure the default due date for subscription invoices, with options such as 30, 60, or 90 days. ✔ The selected setting should apply to all future subscription invoices.
Nada Shoukry 6 days ago
Customizable Invoice Due Date
🔍 Problem Statement The default due date for subscription invoices is currently fixed at 30 days and cannot be customized. We need the ability to set a different default due date for all future subscription invoices. 💡 User Story As a user, I want to configure the default due date for subscription invoices so that I can choose a payment period that fits our billing workflow. 🎯 Definition of Done (DoD) ✔ ️ Add an option to configure the default due date for subscription invoices, with options such as 30, 60, or 90 days. ✔ The selected setting should apply to all future subscription invoices.
Nada Shoukry 6 days ago
Add Test Send Option for Automation Emails
🔍 Problem Statement The Send Email (via Pelcro) automation currently only provides a basic preview and does not offer a test-send option using a real customer from the segment. This makes it difficult to verify how dynamic variables, such as {{customer.magic_link}}, will render before activating the automation for a live segment. 💡 User Story As a user setting up an automation email, I want to send a test email using a real sample customer from the segment so that I can validate the email's final rendering and dynamic variables before activating the automation. 🎯 Definition of Done (DoD) ✔ Add a test-send option to the Send Email (via Pelcro) automation that allows users to send a test email using a selected/sample customer from the segment.
Nada Shoukry 6 days ago
Add Test Send Option for Automation Emails
🔍 Problem Statement The Send Email (via Pelcro) automation currently only provides a basic preview and does not offer a test-send option using a real customer from the segment. This makes it difficult to verify how dynamic variables, such as {{customer.magic_link}}, will render before activating the automation for a live segment. 💡 User Story As a user setting up an automation email, I want to send a test email using a real sample customer from the segment so that I can validate the email's final rendering and dynamic variables before activating the automation. 🎯 Definition of Done (DoD) ✔ Add a test-send option to the Send Email (via Pelcro) automation that allows users to send a test email using a selected/sample customer from the segment.
Nada Shoukry 6 days ago
Allow Partial Refunds for Prepaid Invoices / Advance Payments
🔍 Problem Statement Pelcro currently only supports full refunds for future phases/prepaid invoices. This prevents users/admins from applying a partial refund when they need to retroactively discount a future order. As a workaround, we have been processing these refunds directly through Stripe, but refunds processed outside Pelcro do not create the corresponding credit note and therefore are not reflected correctly in the deferred revenue accounting. 💡 User Story As a user, I want to be able to issue partial refunds on prepaid invoices/future orders directly through Pelcro so that I can apply partial discounts or refunds while keeping the related accounting records accurate. 🎯 Definition of Done (DoD) Users can issue a partial refund against a prepaid/advance invoice through Pelcro. The partial refund creates the appropriate accounting records, including the corresponding credit note and deferred revenue adjustment.
Nada Shoukry 6 days ago
Allow Partial Refunds for Prepaid Invoices / Advance Payments
🔍 Problem Statement Pelcro currently only supports full refunds for future phases/prepaid invoices. This prevents users/admins from applying a partial refund when they need to retroactively discount a future order. As a workaround, we have been processing these refunds directly through Stripe, but refunds processed outside Pelcro do not create the corresponding credit note and therefore are not reflected correctly in the deferred revenue accounting. 💡 User Story As a user, I want to be able to issue partial refunds on prepaid invoices/future orders directly through Pelcro so that I can apply partial discounts or refunds while keeping the related accounting records accurate. 🎯 Definition of Done (DoD) Users can issue a partial refund against a prepaid/advance invoice through Pelcro. The partial refund creates the appropriate accounting records, including the corresponding credit note and deferred revenue adjustment.
Nada Shoukry 6 days ago
In Progress
Support Tax Rates With Plan Bundling
🔍 Problem Statement As a publisher, I need to apply different tax rates to individual line items within a bundled plan based on the product type, customer billing country, and VAT ID status. For example, a publisher may create a bundled plan priced at $100, consisting of: Print: $50 — 7% tax Digital: $50 — 5% tax The applicable tax rate for each line item must be dynamically resolved based on the customer's billing country, VAT ID, and the line item's content code/product type. Certain tax scenarios also require specific legal text to be dynamically added to the invoice. The tax calculation mechanism may be implemented through AvaTax or Pelcro's AI Tax module. 💡 User Story As a publisher, I want each line item within a bundled plan to have its tax calculated independently so that Print, Digital, and other components can follow their applicable tax rules. As a publisher, I want tax rates to be dynamically determined based on the customer's billing country, VAT ID status, and the line item's content code so that the correct tax treatment is applied. As a publisher, I want the appropriate legal text to be dynamically added to invoices when a transaction qualifies for a tax exemption or reverse-charge treatment. As a subscriber, I want the correct tax to be calculated for each component of my subscription so that my checkout total and invoice reflect the applicable tax treatment. 🎯 Definition of Done (DoD) A feature is done when: Tax Calculation per Line Item ✔ Given a bundled plan contains multiple line items, tax is resolved independently for each line item. Example: Create a bundled plan for $100: $50 Print $50 Digital The Print and Digital components can receive different tax rates depending on the applicable tax rules. ✔ Tax resolution takes into consideration: vat_id billing_country content_code / product type ✔ The resolved tax is calculated against the amount of the corresponding line item rather than against the bundle as a single taxable amount. ✔ For bundled Digital & Print products, Print and Digital are evaluated independently whenever the applicable rules require different rates.
Rana Haleem 6 days ago
In Progress
Support Tax Rates With Plan Bundling
🔍 Problem Statement As a publisher, I need to apply different tax rates to individual line items within a bundled plan based on the product type, customer billing country, and VAT ID status. For example, a publisher may create a bundled plan priced at $100, consisting of: Print: $50 — 7% tax Digital: $50 — 5% tax The applicable tax rate for each line item must be dynamically resolved based on the customer's billing country, VAT ID, and the line item's content code/product type. Certain tax scenarios also require specific legal text to be dynamically added to the invoice. The tax calculation mechanism may be implemented through AvaTax or Pelcro's AI Tax module. 💡 User Story As a publisher, I want each line item within a bundled plan to have its tax calculated independently so that Print, Digital, and other components can follow their applicable tax rules. As a publisher, I want tax rates to be dynamically determined based on the customer's billing country, VAT ID status, and the line item's content code so that the correct tax treatment is applied. As a publisher, I want the appropriate legal text to be dynamically added to invoices when a transaction qualifies for a tax exemption or reverse-charge treatment. As a subscriber, I want the correct tax to be calculated for each component of my subscription so that my checkout total and invoice reflect the applicable tax treatment. 🎯 Definition of Done (DoD) A feature is done when: Tax Calculation per Line Item ✔ Given a bundled plan contains multiple line items, tax is resolved independently for each line item. Example: Create a bundled plan for $100: $50 Print $50 Digital The Print and Digital components can receive different tax rates depending on the applicable tax rules. ✔ Tax resolution takes into consideration: vat_id billing_country content_code / product type ✔ The resolved tax is calculated against the amount of the corresponding line item rather than against the bundle as a single taxable amount. ✔ For bundled Digital & Print products, Print and Digital are evaluated independently whenever the applicable rules require different rates.
Rana Haleem 6 days ago
In Progress
Introduce Bundle Manifest Report
Problem Statement The client uses a Truck Manifest every print day to determine the number and size of newspaper bundles required for distribution. The required bundle size varies by print day. Their standard bundle sizes are 30 copies on Sundays and 50 copies on Wednesdays, with the ability to change the size when the publication is heavier due to large or heavy inserts. Currently, there is currently no report that converts these quantities into the number of bundles and remaining copies required for distribution. The legacy manifest performs this calculation using total draw and standard bundle size. User Story As a Distribution Manager, I want to generate a Bundle Manifest for a selected print day, so that I can see how many bundles and remaining copies need to be prepared for each route. Definition of Done A new Bundle Manifest Report is available under Reports. The user can select a fulfillment creation/delivery date. The report is grouped by Vendor/Carrier → Route. Delivery points within each route are ordered by their existing Delivery Sequence. For each delivery point, the report displays: Delivery Sequence Subscriber / Account Name Delivery Address Phone Number Total Draw / Copies Bundle Size Number of Full Bundles Remaining Copies A default Bundle Size can be configured by delivery day: Sunday: 30 copies Wednesday: 50 copies Users can override the bundle size for a specific print/delivery date when needed for heavy or large inserts. Bundle quantities are automatically calculated based on the Total Draw: Full Bundles = Total Draw ÷ Bundle Size Remaining Copies = Total Draw % Bundle Size Existing Pelcro data is reused for Vendor/Carrier, Route, Delivery Sequence, Subscriber, Address, Phone Number, and Total Draw. The report displays totals per Route and Vendor/Carrier. The report can be exported/downloaded. Insert mix, returns, ad zones, and other legacy manifest fields are out of scope for V1.
Rana Haleem 6 days ago
In Progress
Introduce Bundle Manifest Report
Problem Statement The client uses a Truck Manifest every print day to determine the number and size of newspaper bundles required for distribution. The required bundle size varies by print day. Their standard bundle sizes are 30 copies on Sundays and 50 copies on Wednesdays, with the ability to change the size when the publication is heavier due to large or heavy inserts. Currently, there is currently no report that converts these quantities into the number of bundles and remaining copies required for distribution. The legacy manifest performs this calculation using total draw and standard bundle size. User Story As a Distribution Manager, I want to generate a Bundle Manifest for a selected print day, so that I can see how many bundles and remaining copies need to be prepared for each route. Definition of Done A new Bundle Manifest Report is available under Reports. The user can select a fulfillment creation/delivery date. The report is grouped by Vendor/Carrier → Route. Delivery points within each route are ordered by their existing Delivery Sequence. For each delivery point, the report displays: Delivery Sequence Subscriber / Account Name Delivery Address Phone Number Total Draw / Copies Bundle Size Number of Full Bundles Remaining Copies A default Bundle Size can be configured by delivery day: Sunday: 30 copies Wednesday: 50 copies Users can override the bundle size for a specific print/delivery date when needed for heavy or large inserts. Bundle quantities are automatically calculated based on the Total Draw: Full Bundles = Total Draw ÷ Bundle Size Remaining Copies = Total Draw % Bundle Size Existing Pelcro data is reused for Vendor/Carrier, Route, Delivery Sequence, Subscriber, Address, Phone Number, and Total Draw. The report displays totals per Route and Vendor/Carrier. The report can be exported/downloaded. Insert mix, returns, ad zones, and other legacy manifest fields are out of scope for V1.
Rana Haleem 6 days ago
In Progress
Introduce Fulfillment Activity Report
Problem Statement District Managers need a daily operational report to review and follow up on circulation changes, including starts, stops, vacation pauses/restarts, and missed deliveries for each print day. Pelcro’s Bundle Tops already capture this delivery activity at the fulfillment level, including the associated vendor/carrier and route. However, there is currently no consolidated report that presents this information across fulfillments in an operational format similar to the existing District Manager Report. A generic Fulfillment Activity Report is needed to consolidate daily fulfillment activity and group it by Vendor/Carrier for all vendors. User Story As a District Manager, I want to view the circulation activity for a selected print day, grouped by Vendor/Carrier and Route, so that I can review and follow up on starts, stops, vacation pauses/restarts, and missed deliveries with the responsible carriers. Definition of Done A new Fulfillment Activity Report is available under Reports. The report is generic and is not tied to a specific fulfillment. The user can select a fulfillment creation/delivery date. Activity is consolidated across the relevant fulfillments and Bundle Tops for the selected date. The report is grouped as: Vendor/Carrier Route Subscriber activities Each vendor/route displays the applicable: Starts Stops Vacation Pauses Restarts Missed Deliveries Each subscriber activity displays: Subscriber Delivery address Phone number Quantity/Copies Activity type Effective/Delivery date Resume date, when applicable Totals are displayed per route for the supported activity types, following the approach of the existing District Manager Report, which provides starts/restarts/stops/complaint totals after each route/vendor. Totals are displayed per Vendor/Carrier across its routes. Existing Bundle Top data is reused for starts, stops, pauses, routes, carriers and resume dates. Missed deliveries are included using Pelcro's existing applicable delivery issue data. The report can be exported/downloaded. Legacy District → Zone → Region → Area rollups and legacy source/reason codes are out of scope for V1. Legacy District/Zone/Region hierarchy, source/reason codes, complaint-per-1,000 calculations and other legacy District Manager Report fields are out of scope for V1.
Rana Haleem 6 days ago
In Progress
Introduce Fulfillment Activity Report
Problem Statement District Managers need a daily operational report to review and follow up on circulation changes, including starts, stops, vacation pauses/restarts, and missed deliveries for each print day. Pelcro’s Bundle Tops already capture this delivery activity at the fulfillment level, including the associated vendor/carrier and route. However, there is currently no consolidated report that presents this information across fulfillments in an operational format similar to the existing District Manager Report. A generic Fulfillment Activity Report is needed to consolidate daily fulfillment activity and group it by Vendor/Carrier for all vendors. User Story As a District Manager, I want to view the circulation activity for a selected print day, grouped by Vendor/Carrier and Route, so that I can review and follow up on starts, stops, vacation pauses/restarts, and missed deliveries with the responsible carriers. Definition of Done A new Fulfillment Activity Report is available under Reports. The report is generic and is not tied to a specific fulfillment. The user can select a fulfillment creation/delivery date. Activity is consolidated across the relevant fulfillments and Bundle Tops for the selected date. The report is grouped as: Vendor/Carrier Route Subscriber activities Each vendor/route displays the applicable: Starts Stops Vacation Pauses Restarts Missed Deliveries Each subscriber activity displays: Subscriber Delivery address Phone number Quantity/Copies Activity type Effective/Delivery date Resume date, when applicable Totals are displayed per route for the supported activity types, following the approach of the existing District Manager Report, which provides starts/restarts/stops/complaint totals after each route/vendor. Totals are displayed per Vendor/Carrier across its routes. Existing Bundle Top data is reused for starts, stops, pauses, routes, carriers and resume dates. Missed deliveries are included using Pelcro's existing applicable delivery issue data. The report can be exported/downloaded. Legacy District → Zone → Region → Area rollups and legacy source/reason codes are out of scope for V1. Legacy District/Zone/Region hierarchy, source/reason codes, complaint-per-1,000 calculations and other legacy District Manager Report fields are out of scope for V1.
Rana Haleem 6 days ago
Add Ability to Write Off Debit Customer Balances
🔍 Problem Statement Payment processors such as Stripe accept payments when the amount received is short by $0.50 or less, which results in the invoice being marked as paid. Pelcro then adds the remaining amount as an outstanding debit balance on the customer's account, which is carried over and included as an amount due on the customer's next invoice. Currently, the write-off functionality does not support writing off these debit balances. This can leave small outstanding balances on customer accounts, including test accounts that may never have another invoice to which the balance can be applied. It can also cause confusion for customers when these small balances appear on their accounts or are carried over to a future invoice. The client would like the ability to write off these debit balances when appropriate. 💡 User Story As a finance/accounting user, I want to be able to write off small debit customer balances, so that I can clear immaterial outstanding balances from customer accounts and prevent them from carrying over to future invoices or creating confusion in customer statements. 🎯 Definition of Done (DoD) Users can write off debit customer balances through the dashboard, clearing the outstanding balance to zero.
Nada Shoukry 7 days ago
Add Ability to Write Off Debit Customer Balances
🔍 Problem Statement Payment processors such as Stripe accept payments when the amount received is short by $0.50 or less, which results in the invoice being marked as paid. Pelcro then adds the remaining amount as an outstanding debit balance on the customer's account, which is carried over and included as an amount due on the customer's next invoice. Currently, the write-off functionality does not support writing off these debit balances. This can leave small outstanding balances on customer accounts, including test accounts that may never have another invoice to which the balance can be applied. It can also cause confusion for customers when these small balances appear on their accounts or are carried over to a future invoice. The client would like the ability to write off these debit balances when appropriate. 💡 User Story As a finance/accounting user, I want to be able to write off small debit customer balances, so that I can clear immaterial outstanding balances from customer accounts and prevent them from carrying over to future invoices or creating confusion in customer statements. 🎯 Definition of Done (DoD) Users can write off debit customer balances through the dashboard, clearing the outstanding balance to zero.
Nada Shoukry 7 days ago
Editorially-placed paywall break within an article body (inline "subscriber break")
🔍 Problem Statement As an editor, I cannot choose where inside an article the paywall appears, which limits me to all-or-nothing gating per article. 💡 User Story As an editor, I want to insert a subscriber-only break at any point in an article, so that non-subscribers read only the content above it. As a publisher admin, I want only articles containing a break to be gated, so that free stories stay open without meter rules. 🎯 Definition of Done (DoD) ✔ Given an article contains a subscriber break marker, when a non-entitled user loads the page, then content below the marker is withheld and the embedded paywall renders at the marker. ✔ Given an entitled subscriber loads a marked article, when the page renders, then the full article displays with no paywall. ✔ Given an article contains no marker, when any user loads the page, then no paywall renders. ✔ Given a search crawler requests a marked article, when the page renders, then the full article body is served, preserving current crawler-bypass behaviour. ✔ Given an editor publishes an article, when they place the break in the CMS editor, then no Pelcro dashboard configuration is required per article. ✔ This change will impact UI, SDK, and API, specifically Pelcro Elements embedded paywall rendering, JS-SDK content gating, and paywall product configuration. ✔ This solution will include the following limitations: one break per article; marker authoring requires a CMS-side plugin or shortcode; client-side content withholding only unless server-side truncation is scoped separately; no A/B testing of break position; interaction with metered paywalls out of scope.
Rana Haleem 7 days ago
Editorially-placed paywall break within an article body (inline "subscriber break")
🔍 Problem Statement As an editor, I cannot choose where inside an article the paywall appears, which limits me to all-or-nothing gating per article. 💡 User Story As an editor, I want to insert a subscriber-only break at any point in an article, so that non-subscribers read only the content above it. As a publisher admin, I want only articles containing a break to be gated, so that free stories stay open without meter rules. 🎯 Definition of Done (DoD) ✔ Given an article contains a subscriber break marker, when a non-entitled user loads the page, then content below the marker is withheld and the embedded paywall renders at the marker. ✔ Given an entitled subscriber loads a marked article, when the page renders, then the full article displays with no paywall. ✔ Given an article contains no marker, when any user loads the page, then no paywall renders. ✔ Given a search crawler requests a marked article, when the page renders, then the full article body is served, preserving current crawler-bypass behaviour. ✔ Given an editor publishes an article, when they place the break in the CMS editor, then no Pelcro dashboard configuration is required per article. ✔ This change will impact UI, SDK, and API, specifically Pelcro Elements embedded paywall rendering, JS-SDK content gating, and paywall product configuration. ✔ This solution will include the following limitations: one break per article; marker authoring requires a CMS-side plugin or shortcode; client-side content withholding only unless server-side truncation is scoped separately; no A/B testing of break position; interaction with metered paywalls out of scope.
Rana Haleem 7 days ago
Multi-Year Coupon Request
Currently, our coupons only support a one-year discount for annual plans, but we have a couple of use cases where we'd want the discount to span multiple years, and then have the coupon fall off so the subscriber renews into the full price of the subscription. We have the ability to do this with monthly plans using the “repeating” coupon duration but this is not an option for annual plans. Some use cases include: Students renewing at a discounted rate for 4 years, then moving to the full price in year 5 A multi-year rate lock campaign, where a subscriber gets a set price for 2-3 years and then renews into the full price. Please let me know if you need additional information. Tagging @Mike Gilbert for any additional technical concerns. Thank you!
Julie S 11 days ago
Multi-Year Coupon Request
Currently, our coupons only support a one-year discount for annual plans, but we have a couple of use cases where we'd want the discount to span multiple years, and then have the coupon fall off so the subscriber renews into the full price of the subscription. We have the ability to do this with monthly plans using the “repeating” coupon duration but this is not an option for annual plans. Some use cases include: Students renewing at a discounted rate for 4 years, then moving to the full price in year 5 A multi-year rate lock campaign, where a subscriber gets a set price for 2-3 years and then renews into the full price. Please let me know if you need additional information. Tagging @Mike Gilbert for any additional technical concerns. Thank you!
Julie S 11 days ago
Allow Scheduled Renewal Phase to Start Early
🔍 Problem Statement For shipment-based subscriptions, a subscription can reach 0 shipments remaining while there is still time left in the current subscription period. The renewal is scheduled to begin once the current period ends, but there is currently no way to activate the renewal early. This prevents the subscriber from being included in an upcoming fulfillment when the publisher needs to start the next shipment cycle before the current period ends. 💡 User Story As a publisher managing shipment-based subscriptions, I want to manually activate the next scheduled renewal before the current subscription period ends, so that subscribers who have exhausted their shipments can be included in an upcoming fulfillment without waiting for the current period to expire. 🎯 Definition of Done (DoD) ✔ Authorized users can manually activate the next scheduled renewal before the current subscription period ends. ✔ The subscription moves to the renewal phase and receives the appropriate shipment allocation when activated. ✔ The subscriber becomes eligible for the next fulfillment/shipment list. ✔ Scheduled renewals continue to activate automatically at the end of the current period when no early activation is performed.
Nada Shoukry 19 days ago
Allow Scheduled Renewal Phase to Start Early
🔍 Problem Statement For shipment-based subscriptions, a subscription can reach 0 shipments remaining while there is still time left in the current subscription period. The renewal is scheduled to begin once the current period ends, but there is currently no way to activate the renewal early. This prevents the subscriber from being included in an upcoming fulfillment when the publisher needs to start the next shipment cycle before the current period ends. 💡 User Story As a publisher managing shipment-based subscriptions, I want to manually activate the next scheduled renewal before the current subscription period ends, so that subscribers who have exhausted their shipments can be included in an upcoming fulfillment without waiting for the current period to expire. 🎯 Definition of Done (DoD) ✔ Authorized users can manually activate the next scheduled renewal before the current subscription period ends. ✔ The subscription moves to the renewal phase and receives the appropriate shipment allocation when activated. ✔ The subscriber becomes eligible for the next fulfillment/shipment list. ✔ Scheduled renewals continue to activate automatically at the end of the current period when no early activation is performed.
Nada Shoukry 19 days ago
In Progress
Saving skills to account settings in AI Agent
🔍 Problem Statement As an AI Agent user running recurring reports, I must re-explain rules and business processes in every new conversation, wasting time and causing inconsistent output. 💡 User Story As an AI Agent user, I want to save reusable rules/processes to a shared project, so that new conversations reuse them automatically without re-explaining. As a teammate, I want access to shared project rules, so that I can run the same reports consistently without rebuilding context. 🎯 Definition of Done (DoD) ✔ Given a saved project with stored rules, when a new conversation starts within that project, then the AI Agent applies those rules without re-entry. ✔ Given a project with multiple members, when a teammate opens the project, then they see and can use the same stored rules.
Ahmed Soliman 20 days ago
In Progress
Saving skills to account settings in AI Agent
🔍 Problem Statement As an AI Agent user running recurring reports, I must re-explain rules and business processes in every new conversation, wasting time and causing inconsistent output. 💡 User Story As an AI Agent user, I want to save reusable rules/processes to a shared project, so that new conversations reuse them automatically without re-explaining. As a teammate, I want access to shared project rules, so that I can run the same reports consistently without rebuilding context. 🎯 Definition of Done (DoD) ✔ Given a saved project with stored rules, when a new conversation starts within that project, then the AI Agent applies those rules without re-entry. ✔ Given a project with multiple members, when a teammate opens the project, then they see and can use the same stored rules.
Ahmed Soliman 20 days ago
Done
Expose payment_method_status, institutional_member & seat_status in webhook payloads
Problem Statement As a Pelcro integration developer, I experience three required fields being unavailable from the Pelcro webhook payloads when building ESP and CRM syncs, which results in either dropping the field from the integration or making an extra authenticated API call per event — added latency, rate-limit pressure, and a per-integration workaround instead of one platform fix. User Story As a Pelcro integration developer, I want payment_method_status, institutional_member and seat_status to arrive on the existing customer and subscription webhook payloads, so that any downstream integration can map them directly with no supplementary API calls. Definition of Done A feature is done when: Given a subscription with a payment method, when a subscription.* webhook fires, then the payload's payment method / source object includes status (chargeable / pending / failed / ...) matching that payment method's actual state in Pelcro. Given a customer holding an institutional or membership seat, when a customer.* or subscription.* webhook fires, then the payload includes institutional_member and seat_status, resolvable without a supplementary API call. [TO BE DETERMINED] — exact semantics pending client clarification, see Open Questions. This change will impact the API (webhook payload serialization in pelcro-core — app/WebHooks/Resources/, including SourceResource). No SDK, UI, or Integration changes in this task. This solution will include the following limitations: additive fields only, no existing field renamed, removed or retyped; no backfill or replay of historical webhook events; seat_status semantics for individual (non-membership) subscriptions remain undefined until the client confirms.
Rana Haleem 20 days ago
Done
Expose payment_method_status, institutional_member & seat_status in webhook payloads
Problem Statement As a Pelcro integration developer, I experience three required fields being unavailable from the Pelcro webhook payloads when building ESP and CRM syncs, which results in either dropping the field from the integration or making an extra authenticated API call per event — added latency, rate-limit pressure, and a per-integration workaround instead of one platform fix. User Story As a Pelcro integration developer, I want payment_method_status, institutional_member and seat_status to arrive on the existing customer and subscription webhook payloads, so that any downstream integration can map them directly with no supplementary API calls. Definition of Done A feature is done when: Given a subscription with a payment method, when a subscription.* webhook fires, then the payload's payment method / source object includes status (chargeable / pending / failed / ...) matching that payment method's actual state in Pelcro. Given a customer holding an institutional or membership seat, when a customer.* or subscription.* webhook fires, then the payload includes institutional_member and seat_status, resolvable without a supplementary API call. [TO BE DETERMINED] — exact semantics pending client clarification, see Open Questions. This change will impact the API (webhook payload serialization in pelcro-core — app/WebHooks/Resources/, including SourceResource). No SDK, UI, or Integration changes in this task. This solution will include the following limitations: additive fields only, no existing field renamed, removed or retyped; no backfill or replay of historical webhook events; seat_status semantics for individual (non-membership) subscriptions remain undefined until the client confirms.
Rana Haleem 20 days ago
Done
Pelcro Tickets vs Zendesk
🔍 Problem Statement As a support engineer, I lack ticket triage, internal collaboration, and SLA visibility in Pelcro, which results in reliance on Zendesk for core support workflows. 💡 User Story As a support engineer, I want inbound emails to support@ to auto-create a ticket assigned to an agent, so that no request is missed or manually re-entered. As a support engineer, I want to add internal notes on a ticket, so that I can coordinate with teammates without exposing context to the client. As a support engineer, I want to set a Priority on each ticket, so that I can triage the queue by urgency. As a support engineer, I want Open/Pending/On-hold/Solved statuses with auto-reopen on client reply, so that ticket state always reflects reality. As a support manager, I want tickets to track first-reply and resolution time, so that I can report on SLA compliance. 🎯 Definition of Done (DoD) ✔ Given a Settings page for Support, when an admin selects a collaborator as the default ticket assignee, then that setting is saved and used for all future auto-created tickets. ✔ Given an email sent to the support inbox, when it's received, then a ticket is auto-created with Source=Email, Status=New, and assigned to the collaborator configured in Settings. ✔ Given an open ticket, when an agent adds a note marked "Internal," then it appears in the ticket timeline but is never sent to or visible by the client. ✔ Given the Create or Edit Ticket drawer, when an agent sets Priority (Low/Medium/High/Urgent), then it saves and displays on the ticket and in the global list. ✔ Given a Solved ticket, when the client replies via email, then the ticket status automatically changes to Open. ✔ Given a ticket, when the first agent email is sent, then first-reply time is recorded from ticket creation to that timestamp; resolution time is recorded from creation to Solved.
Rana Haleem 20 days ago
Done
Pelcro Tickets vs Zendesk
🔍 Problem Statement As a support engineer, I lack ticket triage, internal collaboration, and SLA visibility in Pelcro, which results in reliance on Zendesk for core support workflows. 💡 User Story As a support engineer, I want inbound emails to support@ to auto-create a ticket assigned to an agent, so that no request is missed or manually re-entered. As a support engineer, I want to add internal notes on a ticket, so that I can coordinate with teammates without exposing context to the client. As a support engineer, I want to set a Priority on each ticket, so that I can triage the queue by urgency. As a support engineer, I want Open/Pending/On-hold/Solved statuses with auto-reopen on client reply, so that ticket state always reflects reality. As a support manager, I want tickets to track first-reply and resolution time, so that I can report on SLA compliance. 🎯 Definition of Done (DoD) ✔ Given a Settings page for Support, when an admin selects a collaborator as the default ticket assignee, then that setting is saved and used for all future auto-created tickets. ✔ Given an email sent to the support inbox, when it's received, then a ticket is auto-created with Source=Email, Status=New, and assigned to the collaborator configured in Settings. ✔ Given an open ticket, when an agent adds a note marked "Internal," then it appears in the ticket timeline but is never sent to or visible by the client. ✔ Given the Create or Edit Ticket drawer, when an agent sets Priority (Low/Medium/High/Urgent), then it saves and displays on the ticket and in the global list. ✔ Given a Solved ticket, when the client replies via email, then the ticket status automatically changes to Open. ✔ Given a ticket, when the first agent email is sent, then first-reply time is recorded from ticket creation to that timestamp; resolution time is recorded from creation to Solved.
Rana Haleem 20 days ago
Done
Multi-subscription merge tags for Mailchimp integration
🔍 Problem Statement As an email marketer at Les Débrouillardes, I can't segment or personalize campaigns per subscription when a customer holds multiple subscriptions, since merge tags only hold the most recent one. 💡 User Story As an email marketer, I want per-subscription merge tags for customers with multiple active subscriptions, so that I can build campaigns targeting specific products (DEB, EXP, CURIUM). 🎯 Definition of Done (DoD) ✔ Given a customer with 2+ active subscriptions, when Mailchimp sync runs, then each subscription's data populates its own indexed merge tag set (e.g. PRODNAME_1, PLANNAME_1, SUBSTATUS_1, PRODNAME_2, PLANNAME_2, SUBSTATUS_2). ✔ This change will impact Integration Orchestrator and API, specifically the Mailchimp sync connector and merge tag mapping logic. ✔ This solution will include the following limitations: indexed tags support up to [TBD - clarify max subscriptions to support, e.g. 5] subscriptions per customer; existing single-subscription merge tags remain unchanged for backward compatibility.
Rana Haleem 20 days ago
Done
Multi-subscription merge tags for Mailchimp integration
🔍 Problem Statement As an email marketer at Les Débrouillardes, I can't segment or personalize campaigns per subscription when a customer holds multiple subscriptions, since merge tags only hold the most recent one. 💡 User Story As an email marketer, I want per-subscription merge tags for customers with multiple active subscriptions, so that I can build campaigns targeting specific products (DEB, EXP, CURIUM). 🎯 Definition of Done (DoD) ✔ Given a customer with 2+ active subscriptions, when Mailchimp sync runs, then each subscription's data populates its own indexed merge tag set (e.g. PRODNAME_1, PLANNAME_1, SUBSTATUS_1, PRODNAME_2, PLANNAME_2, SUBSTATUS_2). ✔ This change will impact Integration Orchestrator and API, specifically the Mailchimp sync connector and merge tag mapping logic. ✔ This solution will include the following limitations: indexed tags support up to [TBD - clarify max subscriptions to support, e.g. 5] subscriptions per customer; existing single-subscription merge tags remain unchanged for backward compatibility.
Rana Haleem 20 days ago
Available
Preline Upgrade - Ecommerce
Problem Statement As a publisher admin, I experience an inconsistent dashboard experience because the Ecommerce Orders, Products, and Product SKU pages still run on the legacy Bootstrap-era UI while most of the rest of the dashboard has already moved to Preline, which results in jarring context-switches and duplicated maintenance effort across two design systems. User Story As a publisher admin, I want the Ecommerce Orders, Products, and Product SKU pages rebuilt on Preline, so that I get the same modern, consistent experience I already have on Customers, Subscriptions, and Invoices. Definition of Done A feature is done when: Given a publisher views the Orders, Products, or Product SKU index/create/edit/show pages, when the page loads, then it renders on the Preline layout with full feature parity to the current legacy pages. This change will impact the UI only (Ecommerce\OrderController, Ecommerce\ProductController, Ecommerce\ProductSkuController and their Blade views); no API, SDK, or Integration changes expected. This solution will include the following limitations: legacy views may need to stay reachable via a ?legacy=1 fallback during rollout (same pattern already used for Addresses/Fulfillments); full filter/search parity may require a follow-up pass.
Rana Haleem 20 days ago
Available
Preline Upgrade - Ecommerce
Problem Statement As a publisher admin, I experience an inconsistent dashboard experience because the Ecommerce Orders, Products, and Product SKU pages still run on the legacy Bootstrap-era UI while most of the rest of the dashboard has already moved to Preline, which results in jarring context-switches and duplicated maintenance effort across two design systems. User Story As a publisher admin, I want the Ecommerce Orders, Products, and Product SKU pages rebuilt on Preline, so that I get the same modern, consistent experience I already have on Customers, Subscriptions, and Invoices. Definition of Done A feature is done when: Given a publisher views the Orders, Products, or Product SKU index/create/edit/show pages, when the page loads, then it renders on the Preline layout with full feature parity to the current legacy pages. This change will impact the UI only (Ecommerce\OrderController, Ecommerce\ProductController, Ecommerce\ProductSkuController and their Blade views); no API, SDK, or Integration changes expected. This solution will include the following limitations: legacy views may need to stay reachable via a ?legacy=1 fallback during rollout (same pattern already used for Addresses/Fulfillments); full filter/search parity may require a follow-up pass.
Rana Haleem 20 days ago
In Progress
Make Shipping Address Optional on new checkout UI
🔍 Problem Statement The Shipping Address section on the new checkout UI displays by default and cannot be hidden, even for plans that don't require shipping information. 💡 User Story As a business owner, I want the Shipping Address field to show or hide dynamically based on the shipping requirement configured on the selected plan, so that customers aren't shown irrelevant fields at checkout. 🎯 Definition of Done (DoD) ✔ Given a plan configured without a shipping address requirement, when a subscriber reaches checkout, then the Shipping Address section is not displayed. ✔ Given a plan configured with a shipping address requirement, when a subscriber reaches checkout, then the Shipping Address section is displayed and required. ✔ This change will impact UI, specifically the checkout Shipping Address section.
Nada Shoukry 28 days ago
In Progress
Make Shipping Address Optional on new checkout UI
🔍 Problem Statement The Shipping Address section on the new checkout UI displays by default and cannot be hidden, even for plans that don't require shipping information. 💡 User Story As a business owner, I want the Shipping Address field to show or hide dynamically based on the shipping requirement configured on the selected plan, so that customers aren't shown irrelevant fields at checkout. 🎯 Definition of Done (DoD) ✔ Given a plan configured without a shipping address requirement, when a subscriber reaches checkout, then the Shipping Address section is not displayed. ✔ Given a plan configured with a shipping address requirement, when a subscriber reaches checkout, then the Shipping Address section is displayed and required. ✔ This change will impact UI, specifically the checkout Shipping Address section.
Nada Shoukry 28 days ago
In Progress
AI-Driven Code Customization & Deployment for UI
🔍 Problem Statement As a Pelcro client, I need engineering involvement for every UI customization (paywall, dashboard, member pages), which slows onboarding and blocks self-serve iteration. 💡 User Story As a Pelcro client, I want to describe my site in natural language and get a working, deployable UI, so that I launch and iterate without Pelcro engineers. 🎯 Definition of Done (DoD) ✔ Given a client prompt or uploaded template, when submitted, then the agent produces a working site in the workspace using JS-SDK for all billing actions and Elements where applicable. ✔ Given a workspace build, when the client views it, then a live preview reflects changes without a deploy step. ✔ Given client approval, when Publish is clicked, then the site is served on the client's domain with SSL, and any prior version is restorable in one click. ✔ This change will impact UI, SDK, and API, specifically an agent service, workspace/preview infrastructure, and publish/rollback endpoints. ✔ This solution will include the following limitations: UI only — no integrations or backend logic; billing flows only via JS-SDK; templates must pass validation before use; one production domain per client.
Rana Haleem 29 days ago
In Progress
AI-Driven Code Customization & Deployment for UI
🔍 Problem Statement As a Pelcro client, I need engineering involvement for every UI customization (paywall, dashboard, member pages), which slows onboarding and blocks self-serve iteration. 💡 User Story As a Pelcro client, I want to describe my site in natural language and get a working, deployable UI, so that I launch and iterate without Pelcro engineers. 🎯 Definition of Done (DoD) ✔ Given a client prompt or uploaded template, when submitted, then the agent produces a working site in the workspace using JS-SDK for all billing actions and Elements where applicable. ✔ Given a workspace build, when the client views it, then a live preview reflects changes without a deploy step. ✔ Given client approval, when Publish is clicked, then the site is served on the client's domain with SSL, and any prior version is restorable in one click. ✔ This change will impact UI, SDK, and API, specifically an agent service, workspace/preview infrastructure, and publish/rollback endpoints. ✔ This solution will include the following limitations: UI only — no integrations or backend logic; billing flows only via JS-SDK; templates must pass validation before use; one production domain per client.
Rana Haleem 29 days ago