Problem Statement Pelcro’s portal payment page currently supports only credit card payments, which limits flexibility for customers who prefer alternative payment methods such as PayPal. This can lead to lower conversion rates and a suboptimal user experience for customers who rely on PayPal for online transactions. User Story As an admin, I want to offer PayPal as a payment option, So that I can increase payment success rates and provide more flexibility to customers. Definition of Done (DoD) PayPal is available as a payment option on the portal payment page. Customers can select PayPal alongside credit card. Payment flow via PayPal is fully functional (redirect, authorization, confirmation). Successful transactions are correctly recorded in the system. Failed or canceled PayPal transactions are handled gracefully. UI clearly displays PayPal as a payment option. Tested across supported browsers and devices. Documentation updated accordingly.

Rana Haleem 2 days ago

Problem Statement Payments failing with “PayPal Buyer Revoked Pre-Approved Payment Authorization” are currently treated as generic failures, leaving subscriptions in a past due state. This message may instead indicate a user-initiated cancellation via PayPal, but no clear confirmation or automatic handling exists. Current Behavior Failure treated as standard payment error Subscription marked as past due No explicit signal of user cancellation Proposed Improvement Confirm if PayPal/Braintree sends revocation notifications If not, treat this specific failure message as a cancellation trigger Automatically terminate the subscription on first occurrence

Daniele 4 days ago

Problem Statement Pelcro currently supports only a limited set of default transactional emails. Clients must rely on external webhook + Postmark setups, creating fragmented workflows and inconsistent branding. User Story As a Pelcro client, I want a centralized page to manage automated emails tied to Pelcro events, So that I can enable and preview system emails without external setup. Proposed Solution Introduce an Email Center in the dashboard: Predefined, hardcoded email templates mapped to webhook events Toggle per email (enable / disable) Preview (read-only) Automatic branding (logo + colors from platform config) Emails triggered directly from Pelcro events Definition of Done (DoD) UI Email Center page listing all system emails Each email includes: Name Enable/disable toggle Preview API GET /email-templates PATCH /email-templates/{id} Event-driven email trigger layer Email Templates (Default List) System must include, at minimum, emails for: Billing & Payments Invoice Created Invoice Paid Invoice Payment Failed Refund Issued Subscriptions Subscription Created Subscription Renewed Subscription Updated Subscription Canceled Dunning / Recovery Payment Failed (retry notification) Card Expiring Soon Customer / Account Account Created Password Reset Optional (if present in webhook scope) Donation Created Order/One-time Purchase Confirmation Behavior Email is sent when: Corresponding event is triggered Email is enabled Branding Apply platform color configuration Apply client logo dynamically

Michael Ghattas 7 days ago

Problem Statement The current invoice PDF displays billing and shipping addresses in a compressed and inconsistent format (e.g., city/state/ZIP combined in a single line with formatting issues). This reduces readability and does not align with standard postal formatting, which can lead to confusion and a less professional presentation. User Story As an admin, I want invoice PDF addresses (billing and shipping) to follow a clean, standardized postal format, So that invoices are more readable, professional, and aligned with mailing standards. Current Format Name Street + City combined in one line ZIP code formatting is incorrect or duplicated Poor spacing and structure Expected Format Addresses should follow this structure: Full Name Street Address City, State ZIP+4

Rana Haleem 7 days ago

2

Problem Statement The current subscription activity logs lack visibility into key user actions, making it difficult to track changes, ensure accountability, and audit subscription-related updates. User Story As an admin, I want the subscription activity logs to capture key actions performed on subscriptions, So that I can track who made changes, understand the history of a subscription, and ensure transparency and accountability. Scope / Requested Enhancements Include the following actions in the subscription activity logs: Scheduled renewal created New subscription created Expiry date changed Shipment details changed

Rana Haleem 7 days ago

Problem Statement Currently, Pelcro does not support embedding magic links directly within SendGrid templates. This limits the ability to provide seamless, passwordless experiences (e.g., login, account access, or payment actions) through transactional or automated emails. User Story As a platform user, I want to include secure magic links within SendGrid email templates in Pelcro, So that end users can seamlessly access their accounts or complete actions without needing to manually log in.

Rana Haleem 8 days ago

🔍 Problem Statement The Customer Profile page currently does not display the user’s currency. This lack of visibility can cause confusion when viewing financial data, payment methods, or transactions. 💡 User Story As an admin, I want to see the currency on the Customer Profile page so that I can clearly understand the monetary values associated with the account. 🎯 Definition of Done (DoD) A feature is done when: The user’s currency is displayed on the Customer Profile page. Currency is shown in a clear and visible location. Currency format follows standard conventions (e.g., USD $, EUR €, etc.). The displayed currency matches the user’s configured/default currency. If no currency is set, a fallback state is shown (e.g., “Not set”). The UI aligns with the updated design system.

Rana Haleem 10 days ago

🔍 Problem Statement The Payment Method Creation page uses an old UI/UX that no longer meets current design standards. It should be updated using new Preline templates to improve usability, consistency, and overall user experience. 💡 User Story As an admin, I want a modern and intuitive payment method creation experience so that I can add payment details easily and confidently. 🎯 Definition of Done (DoD) A feature is done when: Updated Payment Method Creation UI is implemented using Preline templates. Validation should fail on UI first and then from backend. UI is reviewed and approved by design/product stakeholders. Responsive behavior is verified across supported screen sizes. Form validation and error handling are implemented and tested. Accessibility basics are covered, including labels, keyboard navigation, and readable contrast. Existing payment method creation functionality continues to work as expected.

Rana Haleem 10 days ago

🔍 Problem Statement Currently, lists and order exports display country values as abbreviations or codes instead of full country names. This can create confusion for users reviewing exports, especially for reporting, operational workflows 💡 User Story As a user exporting lists or order data, I want countries to appear as full country names instead of abbreviations, so that the exported data is easier to read, understand, and share. 🎯 Definition of Done (DoD) A feature is done when: Full country names are displayed in lists/fulfillment/order exports instead of country codes or abbreviations. Exported country values match the correct country associated with each record. The output is validated for common countries and edge cases.

Rana Haleem 13 days ago

Problem Statement: Currently, cart functionality does not fully support subscription products. This creates friction in the purchase flow and may prevent users from managing subscription-based items in the same way as regular products. We need to extend the cart experience so subscription products can be added, viewed, updated, and purchased seamlessly. User Story: As a customer, I want to add subscription products to my cart and manage them like other products, so that I can complete my purchase smoothly in a single checkout flow.

Rana Haleem 13 days ago

🔍 Problem Statement As a Pelcro admin, I experience the restart-expired-membership flow restricting plan selection to the original plan only, which forces customers to cancel-and-resubscribe if they want a different plan and causes unnecessary churn. 💡 User Story As an admin, I want to select any active plan when restarting an expired membership, so that customers can upgrade, downgrade, or switch without losing their history. 🎯 Definition of Done - Given an expired membership, when an admin initiates the restart flow, then a plan selector is shown allowing any active plan. - This change impacts the UI (restart membership modal) and API (subscription restart endpoint). - Limitations: same proration rules apply as mid-cycle plan changes. Problem Statement Currently, when restarting an expired membership, admins are restricted to the original plan and cannot select a different one. This limits flexibility and creates friction, especially for customers who want to upgrade, downgrade, or switch plans based on their current needs. As a result, users may abandon the restart flow or require manual intervention. User Story As an admin restarting an expired membership, I want to be able to select a different plan during the restart process, so that I can choose a plan that better fits my current needs without extra steps or support involvement.

Rana Haleem 14 days ago

🔍 Problem Statement As a finance admin, I experience the refunds export lacking billing information, which prevents direct reconciliation with original transactions and requires manual cross-referencing. 💡 User Story As a finance admin, I want billing details (name, address, last 4 of payment method) included in the refunds export, so that I can reconcile refunds without pulling a second report. 🎯 Definition of Done - Given the refunds export, when downloaded, then it includes billing name, billing address, and payment method (last 4 / type). - This change impacts the API (refunds export endpoint). - Limitations: fields are appended to the existing format; no existing columns are removed. Problem Statement Currently, the refunds export does not include billing information, which makes it difficult to reconcile refunds with original transactions and customer records. This creates gaps in financial tracking and increases manual effort for teams trying to match refunds with their corresponding billing details. User Story As a finance or operations user, I want billing information to appear in the refunds export, so that I can accurately reconcile refunds with the original transactions and maintain consistent financial records without manual lookup.

Rana Haleem 14 days ago

🔍 Problem Statement As a collections admin, I experience past-due invoice exports missing the billing email address, which forces time-consuming manual cross-referencing with other reports to identify who to contact. 💡 User Story As an admin, I want the billing email included in the past-due invoice export, so that I can reach the right contact immediately without a secondary data pull. 🎯 Definition of Done - Given the past-due invoices export, when downloaded, then a billingEmail column is included for each row. - This change impacts the API (invoice export endpoint). - Limitations: billing email may differ from the account email; both can be included if applicable. Presently, when we run an export of the past-due invoices, we cannot get the billing email on the same report, which is who we need to contact regarding the past-due invoices. While we can cross-reference other exports and ID numbers, this is extremely time consuming and does not need to be, when the addition of the Billing Email could be added to the invoice exports.

hallesarner 14 days ago

1

Problem Statement The Customer Summary Balance Report currently includes customers whose transactions within the selected reporting period sum to zero. Although these customers may have activity, a net total of zero provides little analytical value and unnecessarily increases the size of the report. User Story As an admin, I want customers whose Sum of Transactions is 0 during the reporting period to be excluded from the Customer Summary Balance Report, So that the report is more concise and focused on customers with meaningful financial activity. Definition of Done Customer records with a "Sum of Transactions" equal to 0 for the selected reporting period are excluded from the report Customers with non-zero transaction sums (positive or negative) are included Report output remains accurate and consistent with existing balance calculations

Rana Haleem 15 days ago

🔍 Problem Statement Currently, tickets can only be assigned to collaborators, and there is no option to assign a ticket to a vendor. This limits flexibility when managing issues that are handled by external vendors, making it harder to track responsibility and streamline communication. 💡 User Story As a collaborator I want to assign a ticket to a vendor from the customer profile (similar to assigning it to a collaborator), So that I can track and manage issues that are handled by vendors more effectively. 🎯 Definition of Done (DoD) A feature is done when: Users can assign a vendor to a ticket from the customer profile/ tickets view Vendor assignment is available alongside collaborator assignment in the customer profile/ tickets view The selected vendor is saved and displayed on the ticket details (vendor, vendor id) Users can update or remove the assigned vendor Ticket management workflows remain consistent with existing assignment behavior

Rana Haleem 15 days ago

🔍 Problem Statement Currently you cannot filter support tickets by a specific date range or export results based on applied filters in the tickets list on the platform This limitation: Prevents efficient reporting and analysis of support activity 💡 User Story As a support manager I want to filter tickets by a selected date range and export the filtered results So that I can analyze support activity, generate reports, and share insights with stakeholders 🎯 Definition of Done (DoD) A feature is done when: User can filter tickets by: Created date (from–to) User can export only filtered results or all if nothing selected. Supported formats: CSV (mandatory) Data Integrity Exported data matches exactly what is displayed in UI Includes all relevant fields (e.g., ticket ID, status, customer, created date, resolution time) Performance Filtering responds within acceptable time (<2–3 seconds for typical datasets) Export handles large datasets (with async job if needed)

Rana Haleem 15 days ago

1

If possible, please add all subscription metadata information to the Subscription Details page. We use Metadate to create notes about the subscription as metadata, and having this information display on the Subscription Details page would be helpful.

Mark Beyer 17 days ago

🔍 Problem Statement As an admin, I experience the Next Invoice amount differing from expected without any explanation, causing confusion and unnecessary support escalations when coupons or balance adjustments are applied. 💡 User Story As an admin, I want a tooltip on the Next Invoice amount that explains any adjustments, so that I understand the final amount without contacting support. 🎯 Definition of Done - Given a Next Invoice with adjustments applied, when hovering over the amount, then a tooltip lists each contributing adjustment (coupon, credit balance, etc.). - This change impacts the UI (Next Invoice tooltip) and API (next invoice response — return itemized adjustments). - Limitations: covers applied coupons and credit balance only; tax breakdowns are out of scope for v1. Problem Statement Admins may see a Next Invoice amount that does not match their expectations because it has been adjusted by factors such as applied coupons or existing customer balance . Currently, there is no contextual explanation for these adjustments, which can lead to confusion, support tickets, and reduced trust in billing transparency. User Story As an admin, I want to understand why my upcoming invoice amount is different from the standard price, So that I can clearly see if discounts (coupons) or my account balance have been applied and trust the billing information displayed.

Rana Haleem 21 days ago

Problem Statement Currently, the checkout flow does not explicitly surface or obtain customer acknowledgment of legal policies (terms and conditions, cookie policy, and privacy policy) at the point of purchase. This creates a compliance and legal exposure risk. User Story As a customer completing a purchase on the site, I want to see a checkbox on the checkout modal that lets me acknowledge and agree to the applicable legal policies, So that I can confirm my understanding of the terms before finalizing my purchase. Acceptance Criteria: A checkbox is displayed within the existing checkout/purchase confirmation modal Checkbox label includes plain-language verbiage along the lines of: "I accept the [Terms and Conditions], [Cookie Policy], and [Privacy Policy]" The checkbox must be checked before the purchase can be completed (form validation) Add a new boolean flag in the uiSettings object called enableLegalConsent. Add legalConsentLinks array in the uiSettings object where you can specify the text and the URL of this text as below. window.Pelcro.uiSettings = { enableLegalConsent: true, legalConsentLinks: [ { text: "Terms and Conditions", url:"https://example.com/terms" }, { text: "Cookie Policy", url: "https://example.com/cookies" }, { text: "Privacy Policy", url: "https://example.com/privacy" } ] };

Rana Haleem 23 days ago

Mar 30

Problem Statement The current Segments and Automations interfaces use older UI templates, which are inconsistent with Pelcro’s newer UI standards and reduce usability. The interfaces also lack sufficient helper text, guidance, and clarity, making it harder for administrators to understand how to configure segments and automation workflows. Upgrading these interfaces to the new UI templates and improving instructional clarity will make the features easier to use and more consistent with the rest of the platform. User Story As a Pelcro client administrator, I want the Segments and Automations interfaces to use the new UI templates with clearer instructions and helper text, so that I can more easily create and manage segmentation rules and automation workflows. Definition of Done (DoD) Segments and Automations pages are migrated to Pelcro’s new UI templates. Updated UI includes: improved list views improved creation/edit forms helper text and guidance explaining fields and configuration. All related pages follow current Pelcro UI standards. Existing functionality remains backward compatible. Product documentation is updated to reflect the new UI and workflows.

Rana Haleem 23 days ago

Mar 31