top of page
Search

Pelcro Releases 1.97 & 1.98: Enhanced Reporting, Payments, and User Management





🟢 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 support@pelcro.com 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.



 
 
 
bottom of page