Skip to content

Pelcro Release 3.6: Smarter Billing, Native Support & Better Integrations

Release 3.6 adds automated carrier and vendor billing, native support ticketing, structured coupon errors, Mailchimp merge tags, and richer webhooks.

Merhan Amer3 min read

Release 3.6 (Tech Release 1.30)

🟢 Platform: Automated Bills for Carriers & Vendors

The platform now enables automated calculation of carrier and vendor payouts based on actual delivery performance data, replacing manual processes.

Billing Cycles list under Payable, with a Run Billing button and cycles showing reference, cycle window, vendors, bills, total payable, and status

✅ What's New:
  • Select billing cycles and generate one bill per carrier in a single operation
  • Net payable formula: (Delivered Quantity × Delivery Rate) − (Missed Issues × Missed Issue Rate)
  • Pricing rules defined as plain-language text without specialized configuration screens
  • Bills include cycle window, carrier, applied rates, quantities, deductions, and net amounts
  • Fulfillments are recorded and auditable; duplicate bills are prevented on repeated runs
  • Fulfillments attributed to carriers assigned at delivery time

🎯 Impact:

Operations teams get accurate, repeatable, auditable carrier payouts tied directly to delivery performance.

Billing Cycle CBR-0008 detail with a per-vendor table of delivered and missed quantities, gross, deductions, net payable, and bill status

🟢 Platform: Native Support Ticketing

Support workflows now operate natively within Pelcro, reducing dependency on external systems.

✅ What's New:
  • Inbound support emails auto-create tickets assigned to configurable default agents
  • Internal notes remain agent-only, never visible to clients
  • Per-ticket priority levels (Low/Medium/High/Urgent) for queue management
  • Status options: Open, Pending, On-hold, Solved; auto-reopen when clients reply

🎯 Impact:

Support teams can triage, collaborate, and report on SLAs directly in Pelcro.

Support ticket #590 "Issue in Paywall" with a conversation timeline, an inbound customer email, and an internal note marked not visible to the customer

🟢 Platform: Modernized Taxes & Analytics Reports Pages

The Taxes and analytics report pages now use the current dashboard design system.

Analytics Reports page on the modernized dashboard showing a New Customers line chart with a date range and export

✅ What's Improved:
  • Both pages render on the modern dashboard layout consistent with Analytics
  • All existing report functionality and metrics are preserved

🎯 Impact:

A consistent, modern admin experience with no change to how reports or taxes work.

Taxes summary page on the modernized dashboard with a jurisdiction table showing Canada and Quebec tax rates and amounts

🟢 Open API: Structured Coupon Validation Errors

Coupon validation now returns enumerated error codes at fixed locations instead of inconsistent text messages.

✅ What's New:
  • Endpoints POST /api/v1/sdk/order, POST /api/v1/sdk/subscription, and POST /api/v1/sdk/subscription/change return structured errors including:
    • error.failure_reason_code — stable, never-renamed enumeration
    • error.failure_reason_detail — object with description and code-specific fields
    • error.param — always coupon_code
    • error.coupon_code — echoes submitted code
  • GET /api/v1/sdk/campaign validates coupon.valid against the campaign plan; returns codes and details when invalid

Reason codes include: coupon_not_found, coupon_type_mismatch, coupon_inactive, coupon_expired, coupon_max_redemptions_reached, coupon_currency_mismatch, coupon_plan_not_eligible, coupon_customer_not_eligible, coupon_customer_redemption_limit_reached, and coupon_incompatible_with_subscription.

🎯 Impact:

Integrators can map coupon errors directly to subscriber-facing messaging and support tooling, without parsing free-text.

🟢 Platform: Per-Product Active-Subscription Merge Tags for Mailchimp

Customer segmentation in Mailchimp now supports product-level active subscription flags.

Create Product form with the new Product code field and a tooltip explaining the per-product ACT_ Mailchimp merge tag, plus a Suggest button

✅ What's New:
  • New Product code field (up to 6 characters) on product forms with auto-suggested values
  • Per-product active flags (e.g., ACT_DEB) synced to Mailchimp, valued 1 or 0
  • Flags reflect aggregated status across all subscriptions and recalculate on lifecycle events
  • "Active" includes active, trialing, and extended subscriptions

🎯 Impact:

Marketers can build product-level segments and campaigns from a single, always-current boolean per product.

Mailchimp integration settings showing merge tags and Product Subscription Flags such as ACT_ACCOUN and ACT_AYMANI, each set to 1 when the customer has an active subscription

🟢 Platform: Additional Fields in Webhook Payloads

Webhook payloads now include payment and membership data previously requiring supplementary API calls.

✅ What's New:
  • Payment method status (chargeable/pending/failed) on subscription webhooks
  • Institutional member and seat status fields for membership/seat holders
  • All changes are additive; no existing fields renamed, removed, or retyped

🎯 Impact:

Downstream ESP and CRM integrations can map payment health and seat state directly, cutting extra API calls, latency, and rate-limit pressure.

Webhook events log with a payload panel highlighting the new seat_status field set to active

🟢 Platform: Higher Limit for Paywall Exclude URL Patterns

The paywall's exclusion pattern field capacity has been significantly increased.

✅ What's Improved:
  • Capacity increased to roughly 25 entries (~300 characters)

🎯 Impact:

Publishers can target paywall exclusions more precisely without hitting the previous ceiling.

Ready to monetize your audience?

Get a personalized demo and see how Pelcro can replace the patchwork of tools running your subscription business today.

By submitting your email, you agree to opt in to marketing emails.