Release 1.98 (Tech Release 1.111)

🟢 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.