🟢 Platform: Subscription Activity Logs Added to Subscription Details Page

We’ve improved subscription visibility by surfacing activity logs directly within the Subscription Details page, making it easier to understand changes and investigate issues without leaving the context of the subscription.

✅ What’s New:

• A new Activity Logs section is now available on the Subscription Details page.
• Admins can view a chronological history of subscription-related events and changes in one place.

🎯 Impact:

This enhancement simplifies troubleshooting, improves transparency, and allows support, operations, and finance teams to quickly answer questions about a subscription’s history without navigating across multiple views.

🟢 Platform: Currency Added to Subscription Export

We’ve enhanced the Subscription Export to include currency information, making it easier for finance and operations teams to accurately interpret monetary values—especially in multi-currency environments.

✅ What’s New:

• A new currency field has been added to each subscription record in the export.
• The currency reflects the billing currency of the subscription.
• The field is included consistently across all export formats (e.g., CSV).
• The new column is appended to the end of the subscription export, ensuring backward compatibility.
• Existing export behavior and fields remain unchanged.

🎯 Impact:

This update removes ambiguity around monetary values in exports, simplifies reconciliation and reporting, and reduces the risk of errors when working with multi-currency subscription data.

🟢 Platform: Membership Seat Utilization & Subscription Visibility Enhancements

We’ve introduced clearer, subscription-level visibility for membership-based plans, making it easier to understand seat usage, capacity, and validity without manual cross-checking between pages.

This update connects the billing view (Subscriptions) with the access view (Memberships), giving admins a complete picture of how memberships are being used.

✅ What’s New:

Subscription-Level Seat Allocation

• Membership subscriptions now expose:
  • Seat Capacity
  • Seats Used
  • Seats Available
• Seat capacity is derived from the membership plan and snapshotted on the subscription.
• Seat usage is computed automatically based on active members (read-only).

Subscriptions Page Enhancements

• New toggleable columns:
  • Seat Capacity
  • Seats Used
  • Seats Available
  • Subscription Type (Membership / Standard)
• New filters:
  • Subscription Type = Membership
  • Seats Available > 0
  • Seats Used = Seat Capacity
• Enables quick assessment of membership utilization and health at a glance.

Memberships Page Enhancements

• New toggleable columns:
  • Membership Subscription
  • Subscription Status
  • Seat Capacity (reference)
  • Seats Used (reference)
• New filters:
  • Membership Subscription
  • Subscription Status
  • Seat Status
  • Membership Owner
• Helps admins clearly see which members belong to which subscription and their inherited validity.

Membership Validity Behavior

• Member access now clearly reflects the status of the owning subscription.
• If a membership subscription expires:
  • Members remain visible
  • Members are flagged as inactive / requiring attention
  • Pending members do not consume seats

🎯 Impact:

These enhancements eliminate guesswork around membership utilization, reduce operational friction, and allow teams to quickly answer key questions about seat usage, validity, and access — all without changing billing behavior or existing membership assignment logic.

🟢 Platform: Support for Backdating Subscription Start Date (Pelcro Billing Only)

We’ve added support for backdating subscription start dates to help admins accurately align subscription timelines when correcting data or initializing entitlements. This capability is available only for accounts using Pelcro’s billing engine.

✅ What’s New:

• Admins can now backdate a subscription’s start_date to a past date.
• The Subscription Create API supports an optional start_date parameter for backdating.
• This applies to all plan types (time-based and shipment-based).

🔒 Important Constraints & Guardrails:

• Backdating only — future start dates are not supported.
• Available only for accounts using Pelcro’s billing engine.
• Start date changes do not affect:
  • Invoice start dates
  • Invoice line-item periods
  • Historical invoice data
• Backdating is allowed only when:
  • The subscription is not set to auto-renew, and
  • No renewal phase or future renewal event is scheduled.
• The operation is blocked if renewal logic depends on the existing start date.

📌 Key Use Cases

• Align subscription periods retroactively for shipment-based plans (e.g., institutional or seasonal cycles like Jan–Dec).
• Issue retroactive shipments when entitlements should have started earlier.
• Correct subscription timelines when renewals occur late but access or fulfillment should begin in the past.
• Replace legacy workarounds (such as shortening end dates) that are no longer supported due to stricter revenue-recognition rules.

🎯 Impact:

This enhancement allows teams to correct or align subscription timelines safely and accurately—without impacting billing, invoices, or historical financial data—while maintaining strict controls to prevent unintended side effects.

🟢 Platform: New Shipments & Returns Report

We’ve added a new Shipments & Returns report to give finance teams clearer visibility into shipment and return activity based on when fulfillments were actually created—supporting more accurate monthly revenue recognition.

✅ What’s New:

• A new Fulfillment & Returns report is now available under
  Accounting → Reports.
• The report exports a ZIP file containing two CSV files:
  • Sheet 1: Shipments
  • Sheet 2: Returns

📄 Report Logic & Structure:

Shipments

• Fulfillment Date = fulfillment created_at
• Uses the existing Fulfillment Export as the base dataset.
• Includes all existing fulfillment fields.

Returns

• Fulfillment Date = the associated fulfillment’s created_at date
• Includes the following fields:
  • customer_name
  • customer_id
  • return_created_at
  • return_quantity
  • return_rate
  • total

🎯 Impact:

This report simplifies financial reporting by aligning shipments and returns to the same fulfillment-based timeline, helping teams recognize revenue in the correct accounting period with less manual reconciliation.

🟢 Platform: Delivery Date Support for Shipments & Returns Reporting

We’ve enhanced fulfillment, shipment, and return workflows by introducing a Delivery Date, ensuring reports and rate calculations reflect when deliveries actually occurred—not just when records were created.

✅ What’s New:

• A new optional Delivery Date field is available during fulfillment creation.
• When set, the Delivery Date:
  • Determines the rate applied to all shipments in the fulfillment when using AI plans. Note: The Delivery Date is especially used when using AI plans (available only on Pelcro’s billing engine) with rates that vary by specific days, as it determines which rate is applied.
  • Is used as the primary date in:
    • Shipments reports
    • Returns reports
  • Drives the unit_rate calculation in both shipments and returns reports.
• For returns, the Delivery Date always matches the delivery date of the original fulfillment, regardless of when the return is created.
• The Delivery Date is now included at the end of file in:
  • Fulfillment exports
  • Shipments reports

🔄 Fallback Behavior:

• If no Delivery Date is provided, the system automatically falls back to the existing created-at date logic.

🎯 Impact:

This update improves financial accuracy and clarity by aligning shipment and return reporting with real-world delivery timing—supporting more reliable revenue recognition and operational reporting.

🟢 Platform: Member Webhooks Now Include First & Last Name

We’ve enriched membership webhooks by including first name and last name in the payload, making it easier to capture complete customer details and generate more meaningful insights.

✅ What’s New:

The following membership-related webhooks now include:

• first_name
• last_name

Supported events:

• member.created
• member.updated
• member.activated
• member.deleted

🎯 Impact:

This enhancement improves downstream data quality for reporting, segmentation, and analytics by ensuring member records include essential identity fields.

🟢 Platform: Clearer Dispute Handling in Payment Reconciliation Reports

We’ve improved how disputes are represented in accounting and reconciliation reports to provide clearer financial insight and eliminate confusion between refunds and dispute-related activity.

✅ What’s Changed:

• The Payment Reconciliation Report now separates dispute data into distinct sections:
  • Refunds (excluding dispute-related refunds)
  • Won Disputes
  • Lost Disputes
  • Pending Disputes
• Dispute amounts are no longer included in standard refund totals.
• Dispute calculations now clearly reflect their current status (won, lost, pending).
• Historical data has been updated to align with the new dispute logic.
• Dispute exports now correctly export actual dispute records (not underlying charges).

🎯 Impact:

These enhancements provide clearer financial reporting, improve reconciliation accuracy, and allow finance teams to better understand dispute outcomes and performance without changing underlying transaction data.

🟢 Platform: Added last_active Timestamp to Customer Export

We’ve enhanced the Customer Export to include a last_active timestamp, giving teams clearer visibility into customer engagement directly from exported data.

✅ What’s New:

• A new last_active column has been added to the Customer Export.
• The field represents the most recent customer activity, such as:
  • Login activity
  • Subscription actions
  • Invoice-related events
  • Other defined customer interactions
• The timestamp is formatted in ISO 8601 (UTC) for consistency.
• The new column is appended to the end of the export, ensuring backward compatibility.

🎯 Impact:

This update makes it easier to identify inactive or dormant customers, analyze engagement and churn trends, and perform lifecycle segmentation — all without relying on external data sources or custom processing outside of Pelcro.

🟢 Platform: Full Country Name Added to Fulfillment Export

We’ve enhanced the Fulfillment List Export to better support USPS and vendor mailing requirements by including the full country name.

✅ What’s New:

• A new country_name column has been added to the Fulfillment export.
• The field contains the fully spelled-out country name (e.g., United States instead of US).
• The existing country code remains unchanged.
• No manual modification is required for USPS mail file submissions.

🎯 Impact:

This update ensures fulfillment exports meet USPS and vendor formatting requirements, reducing manual work and preventing export rejections.

🟢 Platform: Modernized Subscription Details Page for Faster, More Intuitive Management

We’ve fully modernized the Subscription Details page to align with current UI/UX standards, making it easier to view, update, and manage subscriptions with greater clarity and efficiency.

This update delivers a cleaner layout, improved consistency, and streamlined actions across key subscription workflows.

✅ This update includes:

• A fully redesigned Subscription Details page built with Pelcro’s latest UI components.
• An upgraded Update Subscription form with improved usability.
• Enhanced Renew Subscription and Quick Renew flows.
• A refreshed Cancel Subscription modal (reusing the existing logic with a modernized UI).
• Improved Change Plan experience.
• Updated Manage Subscription Metadata interface for clearer editing and visibility.

🎯 Impact:

This modernization reduces friction, improves navigation, and allows teams to manage subscription data more quickly and confidently — all while maintaining existing functionality and behavior.

🟢 Integrations: Mailchimp Sync Stability Improvements

We’ve improved Mailchimp sync reliability by limiting concurrent jobs and extending retry behavior to prevent rate limits and firewall blocks.

• Mailchimp jobs are now limited to 10 concurrent connections.
• Excess jobs wait and retry instead of failing.
• Retry window extended to handle longer Akamai blocks.
• No breaking changes, though syncs may process more slowly during peak periods.

This ensures steadier Mailchimp syncing with fewer failures and less manual intervention.

🟢 Platform: New Organizations View for Grouped Customer & Invoice Management

We’ve introduced a new Organizations view to give teams better visibility into customers and invoices grouped at the organization level, making it easier to manage accounts with multiple related customers.

✅ What’s New:

• A new Organizations tab is now available in the platform.

Organization List View

The Organizations list displays:

• Organization name
• Number of customers under the organization
• Number of invoices
• Total invoice net due (summed across all customers in the organization)

Organization Detail View

Each organization now has a dedicated details page that includes:

• Organization name
• A table of all associated customers, showing:
  • Customer name
  • Customer email
  • Shipping address
• A table of open and past-due invoices linked to the organization, including:
  • Invoice ID
  • Invoice created date
  • Invoice status
  • Invoice amount due

🎯 Impact:

This new Organizations view provides clearer insight into customer relationships and outstanding balances at the organization level, helping finance, operations, and support teams manage grouped accounts more efficiently.

🟢 Platform: New “Pay Invoices” Workflow for Organizations (Offline Payments)

We’ve introduced a new Pay Invoices workflow at the organization level to make reconciling offline payments faster and more accurate when multiple invoices are involved.

✅ What’s New:

• A “Pay Invoices” button now appears on the Organization view when the organization has unpaid invoices.

• Clicking the button opens a guided Pay Invoices modal that:

  • Lists all open invoices under the organization
  • Allows users to select all or choose specific invoices

• After selecting invoices, users are prompted to enter offline payment details, including:

  • Payment category (e.g., bank transfer, check, cash)
  • Payment reference
  • Payment amount (automatically calculated as the sum of selected invoices and not editable)

🔒 Validation & Rules:

• At least one invoice must be selected to proceed.
• Partial payments are not supported — the offline payment amount must fully cover the selected invoices.

🚀 Impact:

This new workflow significantly reduces manual effort when reconciling offline payments for organizations, ensuring cleaner records, faster processing, and more accurate financial reporting.

🟢 Platform: New Auto-Uncollectible Settings for Invoices Without Due Dates

We’ve introduced clearer and more flexible controls for how invoices are automatically marked as uncollectible, especially for invoices without due dates (most of the time they are charge auto invoices). This update improves transparency, prevents unintended cancellations, and gives teams explicit control over automation behavior.

✅ What’s New:

• A new dedicated setting for invoices without a due date:
  • “Cancel subscription and set invoice as uncollectible if invoice has no due date and was created more than:”
• Clear tooltips added to explain how each setting behaves.

🔒 Behavior Changes:

• A configurable new toggle now allows teams to enable or disable this behavior explicitly.
• When disabled:
  • Invoices without due dates are not automatically marked uncollectible.
  • Subscriptions are not auto-canceled.
• When enabled:
  • Invoices follow the configured rules and thresholds.

⚠️ Backward Compatibility:

• All existing accounts are defaulted to the disabled state to prevent regressions or unexpected subscription cancellations.

🎯 Impact:

This enhancement provides safer defaults, clearer configuration, and better control over auto-uncollectible logic — aligning invoice handling with real-world billing scenarios and accounting best practices.

🟢 Platform: Clearer File Naming for Accounting Report ZIP Downloads

We’ve improved the naming convention for files included in Accounting report ZIP downloads to make exported data easier to identify and manage.

✅ What’s New:

• Each file inside an accounting ZIP download now includes:
  • The report type (e.g., recognized_revenue, deferred_revenue)
  • The selected date range
  • A timestamp indicating when the export was generated
• File names are now human-readable and self-descriptive, reducing confusion when handling multiple exports.

🔧 Technical Impact:

• Update applies to the Accounting Export Service (ZIP generation logic).
• All generated reports are still included in the ZIP (no change to report selection behavior).

⚠️ Notes & Limitations:

• Existing integrations or workflows that rely on previous file naming conventions may need to be updated.

🎯 Impact:

This enhancement improves clarity, traceability, and usability of accounting exports — especially for finance teams managing multiple reports across different time periods.

🧪 Platform: Subscription Churn Prediction Score — Beta (Simple Model)

We’re introducing an early Subscription Churn Prediction Score to help Pelcro clients identify at-risk subscriptions directly within the platform — without relying on external exports or manual analysis.

This feature is currently in Beta and powered by a simple predictive model based on subscription and user data from Pelcro’s core database.

✅ What’s Included (Beta):

• A new churn prediction score attached to each subscription.
• Churn score included in:
  • All subscription API responses
  • All subscription-related webhooks

🖥️ UI Preview (Feature-Flagged):

• Subscription List Page
  • A new column or badge displays the churn score per subscription.
• Subscription Detail Page
  • The churn score appears on the subscription view.

⚠️ Beta Notes & Enablement:

• This feature is controlled by a feature flag.
• If you would like the Churn Prediction Score enabled for your account, please contact [email protected].
• Scores are informational only and do not trigger actions by default.

🎯 Impact:

This Beta feature provides early insight into churn risk, helping teams prioritize retention efforts and prepare for more advanced automation in future releases.

🟢 Platform: Fully Modernized Customers Details Page for Faster, More Intuitive Management

We’ve completely redesigned the Customers experience to align with modern UI/UX standards — reducing friction and making it easier to manage customer details with confidence.

This update delivers a cleaner, more consistent interface across customer workflows, improving efficiency for support, operations, and admin teams.

✅ This update includes:

• A fully modernized Customer Show page built with Pelcro’s latest UI components.
• A new, structured global layout with improved visual hierarchy and clarity.
• Redesigned header and tab-based navigation for quicker access to customer data.
• A dedicated details sidebar for key customer information.
• Enhanced views and layouts for better readability and usability.

⚙️ Improved Global Actions (Now Modal-Based):

Key customer actions have been streamlined and moved into modals for a smoother experience:

• Reset Password
• Delete Customer
• Change Password (converted from full page)
• Manage Fraud Actions
• Assign Agency Customer ID
• Redeem Gift
• Create Newsletter (converted from full page)
• Adjust Customer Balance

🎯 Impact:

This modernization significantly improves navigation, reduces unnecessary page loads, and provides a more intuitive way to manage customer data — all while maintaining consistency across the Pelcro platform.

🔧 Hotfix: Refund Modal Issue Resolved on Customer Details Page

We’ve deployed a hotfix to address an issue where the Refund modal was not functioning correctly from the Customer Details (Show) view.

✅ What’s Fixed:

• Refund actions from the Customer Details page now open and function as expected.
• Users can successfully initiate and complete refunds without needing to navigate to other views.

This fix restores the expected refund workflow and improves reliability for customer support and operations teams.

🟢 Platform: Gift Message Added to Fulfillment Export

We’ve enhanced the Fulfillment Export to include gift messages for gift subscriptions, making it easier for fulfillment teams to process shipments accurately and efficiently.

✅ What’s New:

• A new gift_message column has been added to the Fulfillment Export CSV.
• For gift subscriptions, the column displays the exact message entered by the purchaser.
• For non-gift subscriptions or orders without a message, the column remains blank.
• This change applies only to the Fulfillment Export and does not affect other exports.

🎯 Impact:

This update eliminates the need for manual lookup of gift notes, reduces fulfillment errors, and ensures gift messages are reliably included in shipments.

🟢 Platform: Improved Customer Search Tolerance for Middle Names & Initials

We’ve enhanced the Customer Search experience to make finding customers faster and more forgiving — even when middle names or initials are present in the customer record.

✅ What’s Improved:

• Searching by first and last name now returns results even if the stored customer record includes:
  • A middle initial (e.g., John A. Smith)
  • A full middle name (e.g., John Adam Smith)
• Users no longer need to enter names exactly as stored to get accurate results.
• Existing partial and fuzzy search behavior remains supported (e.g., “John Smi”).
• An optional middle name field is now supported in the customer profile (not required for search).

🎯 Impact:

This improvement reduces guesswork and friction for support, fulfillment, and operations teams, allowing them to reliably locate customers without worrying about exact name formatting or hidden middle names.

🟢 Platform/ API: Select Payment Method During Subscription Plan Changes

We’ve improved the subscription change experience by giving subscribers more control over which payment method is charged when updating their plan.

✅ What’s New:

• You can now select an existing saved payment method before confirming a subscription change on the platform.
• The Change Subscription API now accepts an optional source_id parameter.
• If a source_id is provided, the selected payment method is charged.
• If no source_id is provided, the system safely falls back to the subscription’s current default payment method.

🎯 Impact:

This update helps prevent failed payments and unintended past-due subscriptions during upgrades or plan changes, improving payment success rates and overall customer experience.

🟢 SDK: Address Collection Added to Subscription Upgrade Flow

We’ve improved the subscription upgrade experience to prevent failures when upgrading to plans that require an address through the SDK.

✅ What’s Improved:

• During the upgrade flow, users are now prompted to select an existing address or add a new address when upgrading to a plan that requires one.
• The upgrade no longer fails if the user does not already have an address on file.

🎯 Impact:

This update eliminates upgrade failures caused by missing address data, improves conversion during plan changes, and ensures users can successfully upgrade to address-required plans without interruption.

⚠️ Important Note:

• This feature is available only in the latest version of Pelcro React Elements.
• Please contact [email protected] if you need assistance upgrading.

🟢 Platform: Modernized API Key Management & Shift to Non-Expiring Keys

We’ve improved API key management to reduce unexpected expirations, minimize support overhead, and provide a more reliable integration experience across all environments.

✅ What’s Changed:

• Enhanced and modernized the API Key Management UI/UX for clearer visibility and easier administration.
• Standard API keys are now created with no expiration date by default, improving stability while maintaining security best practices.
• Expiring and expired API key events and webhooks have been deprecated, and related documentation has been updated accordingly.
• Post-release update: All existing API keys across all environments have been updated to ensure expires_at = NULL.

🎯 Impact:

These changes eliminate unexpected API key expirations, reduce integration-related incidents, and ensure Pelcro and partner teams can operate with greater confidence and continuity when using API keys.

🟢 Platform Enhancement: Improved Auto-Uncollectible Setting Behavior

We’ve introduced an enhancement to how Auto-Uncollectible logic is applied across the platform.

✅ What’s Changed:

• If an invoice has a Due Date, the platform now uses that date to determine when the invoice becomes uncollectible.
• If no Due Date exists, the invoice’s Created Date is used as the effective due date.
• The invoice is marked uncollectible only after the configured Auto-Uncollectible Days have elapsed based on the applicable date.

🎯 Impact:

This enhancement improves accuracy, aligns with accounting best practices, and ensures more predictable and consistent handling of uncollectible invoices.

🟢 Platform: New Payment Reconciliation Report

We’ve added a new Payment Reconciliation Report to help finance teams easily reconcile Pelcro transactions with their payment processor’s monthly summaries — reducing manual work and improving accuracy.

✅ What’s New:

• A new Payment Reconciliation tab under Accounting → Reports.
• Monthly report with a YYYY-MM selector and currency filter.
• Simple, structured table showing:
  • Payments (received)
  • Refunds
  • Disputes
• Each row includes:
  • Online Total
  • Offline Total
  • Total
• Export to CSV for each report view, matching on-screen data.
• Online vs. offline classification aligns with Pelcro’s existing payment source logic.

🎯 Impact:

This report enables clean, one-to-one monthly reconciliation with payment processors, helping teams validate totals faster, reduce errors, and maintain consistent financial records.

🟢 Platform: Added Last Active Tracking for Better Engagement & Segmentation

We’ve introduced Last Active tracking to give you clearer visibility into recent user activity, enabling smarter engagement and churn-prevention strategies.

✅ What’s New:

• A new last_active_at timestamp is now recorded for authenticated users.
• The timestamp updates whenever a user interacts with your website.
• Last Active is now:
  • Visible in the platform UI alongside Last Login
  • Available on the JS SDK user object
  • Exposed via the API
  • Included in customer-related webhooks

🔒 Limitations:

• Activity is tracked only for authenticated users with valid sessions.
• Anonymous or unauthenticated activity is not recorded.

This update helps teams identify inactive users, build engagement segments, and trigger timely re-engagement campaigns with greater accuracy.

🟢 Platform: Enhanced Payment Method Management via Direct URLs

We’ve improved the payment method update experience to support direct URL access, clearer user flows, and better error handling — making it easier for users to manage their cards without navigating the full dashboard.

✅ What’s New:

• Direct payment method updates via URL

  • ?view=payment-method-update&source_id={id} opens the update modal for a specific payment method.
  • Automatically redirects unauthenticated users to login.
  • Ensures the payment SDK is fully loaded before rendering the form.

• Payment methods list accessible via URL

  • ?view=payment-method-update&list=all or ?view=payment-method-update opens the payment methods list modal.
  • List displays all saved payment methods with edit and delete actions.

• Graceful handling of invalid or outdated links

  • Invalid source_id values show an in-modal error message (no broken or empty states).
  • Users are given a clear path to recover via a “View all payment methods” action.

🎯 Impact:

These enhancements enable seamless card updates from email links, improve transparency when issues occur, and give users faster access to their payment methods — all without leaving their current context.

🟢 Platform: Improved Sign-In Button Handling to Prevent Plugin Interference

We’ve improved the Pelcro Sign In experience to prevent third-party WordPress plugins or scripts from incorrectly intercepting the login action and redirecting users to search results pages.

✅ What’s Improved:

• The Pelcro Sign In button now reliably triggers the correct authentication flow, even on sites with form- or search-intercepting plugins.
• Updated event handling within the Pelcro React Elements SDK ensures login requests are executed as intended.
• Users can now complete sign-in without unexpected redirects caused by external plugin behavior.

⚠️ Notes & Limitations:

• This update does not override any custom code that explicitly targets Pelcro elements.
• Conflicts from plugins injected after Pelcro events complete may still require integration guidance.
• Sites that dynamically rewrite button DOM nodes may need additional configuration.

This enhancement improves login reliability across WordPress environments while maintaining compatibility with existing integrations.

🟢 Platform: New Subscription Health Report for Retention & Churn Insights

We’ve introduced a comprehensive Subscription Health Report that helps you better understand historical subscription behavior and project retention and churn trends over time.

This new reporting tool gives clear visibility into subscription activity, enabling smarter forecasting and more informed business decisions.

✅ Key Features:

• New Subscription Health Report accessible from the Pelcro platform.
• Clients can select a custom date range and reporting interval (e.g., monthly, weekly).
• Automatically generates a detailed interval-based table containing:
  • Opening Actives (OA)
  • New Starts (NS)
  • Churned — Opening Cohort (CO)
  • Churned — In-Period (CI)
  • Closing Actives (CA)
  • Closing Actives — Opening Cohort (CAO)

📊 New Retention & Churn Metrics:

The report calculates essential performance rates, including:

• Subscription Retention Rate: (OA - CO) / OA
• Total Retention Rate: CA / (OA + NS)
• Subscription Churn Rate: CO / OA
• In-Period Churn Rate: CI / NS
• Total Churn Rate: (CO + CI) / (OA + NS)

🎯 Impact:

This new report empowers Pelcro clients to track subscriber behavior with precision, audit retention and churn.

🟢Natural-Language Plan Creation for Complex Billing Logic - Beta Release

We’re introducing an early Beta version of Advanced Billing, featuring an interactive chat-based experience that helps Billing and Product Admins create complex billing plans through natural language.
This functionality is still under development and available only to selected abstracted accounts.

🧠 What’s New (Beta Release):

• A new “AI Plan” option is available when creating a plan.
• Instead of manual configuration, you can describe billing logic in natural language (e.g.,
  “Bill $5 for the first month and increase by $1 each month.”).
• The system enters an interactive chat flow where the chat:
  • Parses your prompt
  • Identifies missing configuration details
  • Asks clarifying questions
  • Suggests valid billing structures
  • Ensures the plan meets all required rules before generation

💬 Interactive Experience Highlights:

• Multi-turn conversation to refine plan logic
• Automatic detection of incomplete or conflicting billing rules
• Real-time prompts to fill gaps (e.g., “What should the renewal price be after month 12?”)
• Built-in validation before plan creation

This feature aims to simplify how complex or non-standard billing plans are created — helping teams launch sophisticated pricing models faster and with a guided, conversational experience.

🎯 Who Gets Access

• Currently available only to accounts using Pelcro's billing engine.

🟢Platform: Introduce Accounts Payable (AP) — Beta Release

We’ve launched the first Beta version of Pelcro’s Accounts Payable module, giving admins the ability to manage vendors and bills directly from the platform.

✅ What’s Included (Beta):

• New Vendors section with full CRUD and searchable list.
• New Bills section under Accounts Payable, supporting CRUD, line items, and PDF generation.

🎯 Impact

This Beta introduces the foundation for full AP functionality:

• Reduces manual vendor/bill tracking
• Centralizes AP records within Pelcro

The AP module is still in active development, and your feedback will shape upcoming enhancements.

🟢 Platform: New Accounts Receivable (AR) Aging Report

We’ve launched a fully featured AR Aging Report to help finance and AR teams accurately track overdue invoices, segment balances into industry-standard aging buckets, and strengthen their collections and cash-flow management processes.

This report follows established accounting best practices and provides all essential customer, invoice, subscription, and plan-level details needed for financial audits and reconciliation.

✅ Key Features:

• New AR Aging Report available under Accounting → Reports.
• A single “As of Date” filter determines:
  • Which invoices are considered open.
  • How aging buckets are calculated.
• Displays only invoices created on or before the selected date and still open as of that date.
• Aging buckets calculated dynamically:
  • Not Yet Due
  • 1–30 Days
  • 31–60 Days
  • 61–90 Days
  • 91–120 Days
  • Over 120 Days

📊 Data Included in the Report:

Each row includes comprehensive fields such as:

• Invoice details (ID, number, created date, status, total, due date)
• Customer information (ID, name, email, title, organization)
• Subscription lifecycle details (created at, started, period start/end, status)
• Product/Plan metadata (product name, plan ID, name, term, amount)
• Accounts Receivable and all aging bucket amounts
• Plan Auto Uncollectible Days (pulled from the Plan associated with the invoice)
• Sales rep name tied to the originating subscription

🎯 Impact:

This marks a major upgrade for finance workflows and brings Pelcro’s accounting capabilities fully in line with industry standards.

🟢 Platform: Coupons Can Now Be Edited — Including Max Redemptions & Expiration Date/Time

We’ve introduced long-requested improvements to coupon management, allowing you to update key coupon fields without needing to recreate codes. This provides greater flexibility for managing promotions, reduces operational overhead, and ensures cleaner analytics across campaigns.

✅ Key Enhancements:

• Coupons can now be edited through both the Platform UI and the API.
• New editable fields include:
  • Maximum Redemptions
  • Expiration Date & Time

🎯 Impact:

This update streamlines promotional workflows, eliminates the need to recreate coupons for small adjustments, and provides precise scheduling control for marketing and subscription teams.

🟢 Platform: Modernized Products Page for a Cleaner, Faster Browsing Experience

The Products page has been fully updated with a modern UI/UX design — offering a cleaner interface, improved performance, and a more intuitive product-management flow.

This enhancement brings greater clarity and consistency across the platform, helping users browse, understand, and manage products more efficiently.

✅ This update includes:

• A modernized Products page built using Pelcro’s latest UI components.
• A cleaner, more intuitive layout with improved responsiveness on all devices.
• Enhanced performance, accessibility, and load speed for smoother interactions.

🟢 Platform: New Bundle Tops PDF Report for Fulfillment

We’ve added a new Bundle Tops PDF that can be generated directly from the fulfillment screen, giving Pelcro clients a printer-ready format for distribution workflows.

✅ What’s New:

• A new “Bundle Tops.pdf” is now available after creating a fulfillment and selecting View Fulfillment.
• The PDF is optimized for printing and bundling operations.

📄 PDF Contents (in order):

1. Customer Name
2. Address
3. City / State / Zip
4. Product Name
5. Distribution Date
6. Quantity

This update streamlines fulfillment processes by providing a clear, standardized, print-ready bundle top format.

🟢 Platform: Modernized Customers Page for a More Streamlined Management Experience

The Customers page has been fully refreshed with a modern, intuitive UI/UX — making it easier and faster to view, search, and manage customer information.

This update brings improved clarity, consistency, and performance across the platform, helping teams navigate customer data with greater efficiency.

✅ This update includes:

• A modernized Customers page built using Pelcro’s latest UI components.
• A cleaner, more organized layout with enhanced responsiveness across all devices.
• Improved performance, accessibility, and loading speed for a smoother management experience.

🟢 Platform: Added Informational Warning to Prevent Duplicate Subscription Purchases

To help subscribers avoid unintentionally purchasing plans they already own, the checkout flow now includes a clear informational banner for logged-in users with active subscriptions.

This improvement ensures transparency during the plan selection process and reduces the likelihood of duplicate or unnecessary purchases.

✅ This update includes:

• A new informational banner displayed at the top of the product/plan selection modal.
• Message shown: “You are already subscribed to: Active Plan Name”
• Automatically displays only for logged-in users with at least one active subscription.
• If multiple active subscriptions exist, the banner shows the most recently created active plan.
• Fully non-interactive banner — checkout behavior and plan selection remain unchanged.

🎯 Benefits:

• Reduces accidental duplicate subscription purchases.
• Adds clarity and transparency to the checkout experience.

🧩 Available now in the latest React Elements version. Please reach out to [email protected] to upgrade to the newest UI.

🟠 Platform: Prevent Partially Paid Invoices from Being Marked Uncollectible or Voided

To protect financial accuracy, the platform now blocks users from marking partially paid invoices as uncollectible or voided, avoiding scenarios where applied payments disappear from customer balances.

✅ Key Improvements:

• New validation prevents uncollectible/void actions on invoices with applied payments.
• Clear error message guides users to issue a credit note instead.
• Admin Dashboard disables/hides the “Mark as Uncollectible” option for partially paid invoices.

🟢 Platform: Refund Customer Balances Directly to Original Payment Cards

You can now refund customer balances directly to their original payment cards — streamlining refund workflows and eliminating the need for manual intervention or external processing.

✅ What’s New

• Added support for refunding payments originally credited to a customer balance back to their card.
• The “Refund” button now appears for eligible payments directly in the Admin Dashboard.
• Supports full or partial refunds, up to the original charge amount.
• Refunds are processed via the same payment method and gateway as the original transaction.

💡 Why It Matters This enhancement reduces refund handling time, ensures accounting accuracy, and delivers a smoother refund experience for both customers and administrators.

🟢 Default UI: Self-Serve “Switch Plan” Experience for Subscribers

Subscribers can now upgrade their plans directly through a self-serve interface, allowing them to explore and switch to higher-tier products without contacting support — improving upsell opportunities and customer autonomy.

✅ What’s New

• Added a “Switch Plan” button to the subscriber dashboard for all active subscriptions.
• Displays only eligible plans with an equal or higher amount than the current plan.
• Subscribers receive immediate confirmation (“You’ve successfully upgraded to Plan X”).
• Updated plan details are reflected instantly in the user’s account.

💡 Why It Matters This update empowers subscribers to manage their own upgrades, reducing support overhead and driving faster conversions to higher-value plans — all through a seamless, intuitive interface.

🧩 Available now in the latest React Elements version. Please reach out to [email protected] to upgrade to the newest UI.

🟢 Platform: Introduce Returns Management for Fulfillments

Pelcro now supports tracking and managing fulfillment returns directly within the fulfillment workflow — giving collaborators full visibility into returned quantities, reasons, and history for each shipment.

✅ What’s New

• New Returns Section under Subscription → Fulfillments displaying:
  • Returned Quantity
  • Reason for Return (optional)
  • Creation Date and User
• Introduced a “Process Return” option in the Fulfillment section — accessible via the three-dot menu on each shipment.
• Built-in validation ensures users cannot return more items than were originally delivered.

💡 Why It Matters This enhancement introduces a structured and auditable way to manage product returns — improving operational accuracy, reducing manual tracking, and ensuring that fulfillment data remains consistent across the platform and reporting.

🟢 Integrations: New “Bypass Marketing Contacts” Flag for SendGrid

We’ve introduced a new configuration option for the SendGrid integration to improve flexibility for accounts without marketing permissions.

✅ What’s New

• Added a Bypass Marketing Contacts flag to the SendGrid settings.
• When enabled, Pelcro will skip all marketing contact operations while still allowing transactional emails (e.g., invoices, receipts, password resets) to be sent successfully.
• This should be enabled if your SendGrid API key doesn’t include Marketing Campaigns permissions.

💡 Why It Matters This update prevents permission-related errors for customers using restricted API keys while ensuring that all essential emails continue to send without disruption.

🟢 API: Performance Optimization for Customers List Endpoint

We’ve optimized the Core API’s Customers List endpoint to deliver faster response times — especially when retrieving large datasets or using default ordering by user_id.

This enhancement reduces latency and improves scalability for bulk data retrieval and integrations that rely on customer listings.

💡 Why It Matters Developers can now fetch customer lists significantly faster, improving the responsiveness of dashboards, exports, and connected applications.

🟢 Platform: Membership Export Now Includes Organization and Shipping Address

We’ve enhanced the Membership Export to include additional context for each record — making it easier to analyze member data.

✅ What’s New

• Added Organization field to identify the member’s associated organization.
• Added Shipping Address field for better fulfillment and reporting accuracy.

💡 Why It Matters This update gives teams deeper visibility into membership details, streamlining reporting, fulfillment, and integration workflows.

🟢 Accounting: New Customer Balance Summary Report Added

You can now view a consolidated summary of all customer balances directly within the Accounting → Reports tab — no need for manual exports.

This update introduces the new Customer Balance Summary Report, designed to give accounting and finance users a clear, at-a-glance view of customer balances, activity, and outstanding amounts.

✅ This update includes:

• A new Reports section under the Accounting tab, built using Pelcro’s latest dashboard UI template.
• Date filters to view balances as of a specific period.
• Sortable export (descending by highest balance).

🟢 Platform: Modernized Subscriptions List for a Smoother Management Experience

The Subscriptions page has been fully redesigned to align with modern UI/UX standards — making it faster, cleaner, and easier to manage subscriptions.

This update enhances navigation, readability, and consistency across the platform, giving users a more intuitive and efficient experience when reviewing or updating their subscriptions.

✅ This update includes:

• A modernized Subscriptions list page built with Pelcro’s latest UI components.
• Improved layout and responsiveness across desktop and mobile devices.
• Enhanced performance and accessibility for faster load times and smoother interactions.

🟢 Performance: Ultra-Fast Loading for E-Commerce Product Lists

We’ve optimized the E-Commerce List endpoint by offloading it to Cloudflare’s global edge network — the same performance architecture powering our fastest APIs.
Product catalogs now load dramatically faster, reducing wait times and improving the overall browsing experience for your customers.

✅ This update includes:

• Edge Caching for Product Lists: The E-Commerce List endpoint is now cached globally at the Cloudflare edge.
• Lightning-Fast Response Times: Sub-100ms responses, even for large product catalogs.
• Smart Auto-Refresh: Cache automatically refreshes every 5 minutes to ensure up-to-date catalog data.
• Resilient by Design: Product lists remain available even if the origin API experiences downtime.
• Seamless Scalability: Handles surges in traffic with no performance degradation.

⚙️ How It Works

1. The first request fetches data from the origin server and stores it in Cloudflare’s global cache.
2. Subsequent requests are served instantly from the nearest edge location.
3. Cache entries automatically refresh every 5 minutes with the latest catalog updates.
4. Any product updates you make propagate to customers within minutes — no manual clearing required.

💡 What This Means for You

Shoppers now experience instant product list loading, smoother navigation, and reduced latency across all regions — even during peak traffic hours.

🟢 Platform: New Billing Email Field for Customer Records

You can now set a dedicated billing email on customer profiles — ensuring that all invoice and billing-related communications reach the right recipients, such as your finance or accounts payable teams.

Previously, billing notifications were always sent to the customer’s primary email. With this update, businesses can route billing messages directly to a separate billing_email, reducing delays and improving financial communication accuracy.

✅ This update includes:

• New billing_email field on the customer object (available via Platform UI and Create / Update Core API).
• Billing-related webhooks and ESPs (SendGrid, Mailchimp, Mandrill) now use billing_email if available; otherwise, they fall back to the customer’s primary email.
• Supported webhook events include:
  • invoice.created
  • invoice.payment_action_required
  • invoice.payment_failed
  • invoice.payment_succeeded
  • invoice.upcoming
  • invoice.updated
  • charge.failed
  • charge.refunded
  • charge.succeeded
• Non-billing webhooks continue to use the primary customer email.
• billing_email is now searchable in the Customers view.

💡 Why It Matters

This update ensures that billing communications always reach the correct contact, improving payment timeliness, reducing errors, and aligning Pelcro’s billing workflows with enterprise finance processes.

🟢 Platform: First & Last Name Fields Now Optional in Address Form

You can now create or edit addresses on the platform without requiring first or last names.
This aligns the platform behavior with the Core API for more flexible address management.

🟢 Platform & Default UI: Configurable and Required Cancellation Reasons

The cancellation reason field is now required when users cancel a subscription.
Cancellation reasons can be configured directly from the platform and will be reflected on your website through the latest React Elements version.

This ensures consistent data collection and better visibility into why customers cancel their subscriptions.

🟢 Default UI: New Inline Subscription Paywall for Seamless On-Page Conversions

We now support an inline subscription paywall in our new UI version, allowing publishers to display subscription options directly within the content — creating a smoother, higher-converting experience for readers.

This feature helps digital publishers convert engaged, anonymous visitors into paying subscribers without redirecting them away from the page.

✅ What’s New

• Added support for Inline Paywall Display Mode.
• When displayPaywall = true and the paywall type is set to inline, Pelcro renders an embedded paywall over any section wrapped with:
  HTML

  <div id="pelcro-inline-paywall"></div>

🟢 Default UI: Newsletter Opt-In Now Available During Registration

You can now enable newsletter opt-ins directly within the user registration flow — helping publishers grow their mailing lists and improve audience engagement without extra forms or steps.

When configured, visitors will see newsletter options dynamically during sign-up, allowing them to select the topics or newsletters they want to receive.

✅ What’s New

• Added dynamic newsletter opt-in checkboxes to registration flows.
• When Pelcro.uiSettings.newsletters is defined, one checkbox is rendered for each newsletter entry using:
  • label → displayed as the newsletter name
  • id → mapped to backend opt-in tracking
• Introduced a new boolean flag besides label, id:
  • addToRegistration — when true, the newsletter section is automatically displayed during registration.
• Upon successful registration, all selected newsletter opt-ins are sent to Pelcro’s backend and synced with connected ESPs (e.g., Mailchimp).
• If no newsletters are defined in uiSettings.newsletters, the registration form remains unchanged.

💡 Why It Matters

This feature allows publishers to:

• Grow mailing lists organically as part of the sign-up process.
• Offer personalized content preferences right from registration.
• Maintain consistent, automated newsletter management across ESP integrations.

🟢 API: Refunds Endpoint Now Includes charge_id for Easier Reconciliation

We’ve enhanced the /refunds API to include the charge_id field in its response — making it easier for developers and finance teams to trace each refund back to its original transaction.

✅ What’s New

• charge_id Added: Each refund object now includes the related charge identifier.
• Simplified Reconciliation: Quickly match refunds with their originating charges and customers.
• Improved Reporting Accuracy: Enables cleaner data mapping in accounting exports and internal tools.

🟢 API: Added Option to Bypass Address Cleansing on Create/Update Address Endpoints

You can now bypass the Address Cleansing feature if enabled directly through the Core API by using a new optional boolean flag — giving developers more flexibility when creating or updating addresses programmatically.

✅ What’s New

• Added a new bypass_address_cleansing boolean flag (optional) to the following endpoints:
  • POST /addresses
  • PUT /addresses/{id}
• When bypass_address_cleansing: true is passed in the request, Pelcro will skip address validation and standardization, even if the Address Cleansing feature is enabled for the site.
• Default behavior remains unchanged — addresses are cleansed automatically unless this flag is explicitly set.

🟢 Payments: Google Pay Now Supported via Braintree

You can now enable Google Pay for your checkout flows using the Braintree payment gateway — giving Android users a faster, more secure way to complete purchases.

This update includes:

• ✅ Braintree configuration support for Google Pay (API keys and credentials)
• ✅ Seamless front-end rendering of the Google Pay button based on browser/device compatibility
• ✅ Full back-end integration for tokenizing and processing Google Pay transactions via Braintree

Now your customers can enjoy a smoother checkout experience with Google Pay — even when your site uses Braintree.

🟢 Invoicing: Add Purchase Order Field Before Invoice Creation

Accounts using Pelcro’s billing engine can now include Purchase Order (PO) numbers before invoices are generated and sent, ensuring compliance for billing and avoiding rejected invoices.

This update includes:

• ✅ New Purchase Order field in Create, Renew, and Update Subscription flows for self-renew plans.
• ✅ PO values are stored on the invoice record and displayed in invoice PDFs.
• ✅ PO numbers are included in invoice webhooks and SendGrid events.

This enhancement ensures every invoice includes the correct PO from the moment it’s created — no post-send edits needed.

🟢 Platform: Restrict Subscription End Date Changes to Extensions Only

You can now only extend — not shorten — subscription end dates, helping maintain accurate access control and continuous revenue recognition.

This update includes:

• ✅ Admin-side validation preventing end dates earlier than the current period end.
• ✅ Clear UI and API error message (“End date cannot be set earlier than the current period end”).
• ✅ Updated logic in the subscription end date override functionality within the platform.

📘 API Note – Update Subscription Endpoint:
Under the end_date field in the Core API (/subscription/update), the following rules now apply:

• You may only set or change the end date to a time after the current period end.
• Attempts to set an earlier date will be rejected with a clear validation error.

This ensures that admin adjustments to subscriptions never trigger unintended cancellations or disrupt revenue recognition.

🟢 Performance: Ultra-Fast Loading for Site & Plan Info

We’ve supercharged how both site configuration and plan endpoints are delivered. Both are now powered by Cloudflare’s global edge network, ensuring sub-100ms response times worldwide.

• ⚡ Blazing Speed: ~60ms average response times, served from 200+ edge locations.
• 🔄 Smart Caching: Data refreshes automatically every 5 minutes for up-to-date content.
• 🌍 Global Reliability: Content stays available even if the origin server has issues.
• 📈 Consistent Performance: Smooth, predictable response times no matter the traffic.

How It Works

• First request fetches from the origin, then caches globally.
• Subsequent requests are served instantly from the nearest edge.
• Cache auto-refreshes every 5 minutes with the latest data.
• Updates you make are live for users within 5 minutes, with no slowdown.

What this means for you: both site and plan updates go live within minutes, and your visitors always get the fastest, freshest experience possible.

🟢 Enhancement: Subscription Metadata in Co-Pilot

We’ve added support for subscription metadata in Co-Pilot. Platform users can now:

• Export all subscriptions that match a specific metadata key/value.
• List all metadata associated with a given subscription.

This improvement gives businesses greater flexibility to analyze and extract subscription details based on custom metadata.

🟢 Enhancement: Add Invoice Notes in Invoice View

We’ve introduced the ability to add and update invoice notes directly within the invoice view. These notes are saved to the invoice record and will also appear in the PDF version.

This improvement gives you more flexibility to include billing references, legal notes, or custom instructions, ensuring important context is clearly communicated to your customers.

🟢 Enhancement: Expanded Core API Subscription Management

We’ve enhanced the Core API update subscription endpoint to support:

• Plan changes (switching between compatible plan types)
• Address updates via address_id
• Switching to the same plan type without restrictions
• The subscription.changed webhook payload now includes the new plan information instead of the old data

This update streamlines subscription management, reduces manual intervention, and gives developers greater flexibility when integrating with the Core API.

🟢 Enhancement: Carrier Routes in Fulfillments Export

We’ve added the Carrier Routes field to the Fulfillments Export when Address Cleansing is enabled. The field is appended in a way that avoids breaking changes to existing exports.

This improvement helps fulfillment teams provide more accurate delivery instructions and streamline distribution workflows.

🟢 Enhancement: Add Phase Creation Timestamps

We’ve added the campaign phase creation date to the subscription pricing view, displayed next to the campaign key. This timestamp is also included at the end of the Subscriptions Export.

This enhancement gives campaign managers a clear, timestamped record of when renewal campaigns are triggered, helping ensure compliance with required lead times.

🟢 Enhancement: Introduce Wallet Type in Exports

We’ve added a new column (source.wallet) to the payments exports that clearly indicates whether a payment was made using Apple Pay, Google Pay, or a standard card.

This improvement makes it easier for finance teams to accurately track, reconcile, and analyze payment methods without relying solely on the Payment section.'

🟢 Enhancement: Support Offline Plans Without Gateway Restriction

We’ve removed the restriction that prevented creating plans with a price greater than 0 when no payment gateway is connected — if the plan is of type OFFLINE.

This improvement ensures that clients using Pelcro in backend-only mode can create and manage offline plans seamlessly and process offline payments without requiring a payment processor connection.