Release 3.6 (Tech Release 1.30)

🟢 Platform: Automated Bills for Carriers & Vendors

Carrier and vendor payouts can now be calculated automatically from actual delivery data, replacing manual off-platform calculation.

✅ What's New:

Select a billing cycle and generate one bill per participating carrier in a single run
Net payable calculated as (Delivered Quantity × Delivery Rate) − (Missed Issues × Missed Issue Rate)
Rates defined as plain-language pricing rules — no new configuration screens
Each bill shows cycle window, carrier, rates applied, delivered/missed quantities, deductions, and net payable
Included fulfillments are recorded and retrievable for audit
Duplicate bills prevented on reruns; fulfillments attributed to the carrier assigned at the time of delivery

🎯 Impact:

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

🟢 Platform: Native Support Ticketing

Core support workflows are moving into Pelcro, reducing reliance on external ticketing tools.

✅ What's New:

Inbound emails to the support inbox auto-create a ticket, assigned to a configurable default agent
Internal notes visible to agents only, never to the client
Per-ticket Priority (Low / Medium / High / Urgent) for queue triage
Open / Pending / On-hold / Solved statuses, with auto-reopen when a client replies to a solved ticket

🎯 Impact:

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

🟢 Platform: Modernized Taxes & Analytics Reports Pages

The Taxes and Reports → Customer/Subscription analytics pages have been upgraded to the current dashboard design, completing the Analytics section refresh.

✅ What's Improved:

Both pages now render on the modern dashboard layout, consistent with the rest of Analytics
Existing functionality preserved across all report metrics

🎯 Impact:

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

🟢 Open API: Structured Coupon Validation Errors

Coupon validation failures now return a stable, enumerated error code at a fixed location, replacing generic, inconsistently-placed error text.

✅ What's New:

On POST /api/v1/sdk/order, POST /api/v1/sdk/subscription, and POST /api/v1/sdk/subscription/change, the error object now includes:
- error.failure_reason_code — stable enum, never renamed
- error.failure_reason_detail — object; always carries description, plus code-specific keys (expiry date, allowed plan IDs, redemption counts, segment names)
- error.param — always coupon_code, identifying the failing input
- error.coupon_code — echoes the submitted code
error.message text is unchanged for every case
GET /api/v1/sdk/campaign: coupon.valid is now computed against the campaign plan (not the stored flag); when false it returns coupon.failure_reason_code and a failure_reason_detail.description. As a public endpoint, it deliberately returns no coupon configuration.

📋 Reason codes (precedence order — first failing rule wins):

#	Code	HTTP
1	`coupon_not_found`	404
2	`coupon_type_mismatch` — code belongs to an e-commerce coupon	404
3	`coupon_inactive`	404
4	`coupon_expired`	404
5	`coupon_max_redemptions_reached`	404
6	`coupon_currency_mismatch`	404
7	`coupon_plan_not_eligible`	404
8	`coupon_customer_not_eligible` — segment restriction	400
9	`coupon_customer_redemption_limit_reached`	404
10	`coupon_incompatible_with_subscription` — plan change blocked by a `once` coupon on an existing invoice	404

🎯 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

Campaigns can now segment by whether a customer currently holds an active subscription to a given product, via a boolean flag synced to Mailchimp — powered by a new Product code field on the product form.

✅ What's New:

New Product code field on the product create/edit form — a short code (up to 6 characters) that identifies the product in merge tags. The form suggests a code automatically (derived from the product's internal name); the code is editable and must be unique per account.
Mailchimp sync can now send a per-product active flag (for example ACT_DEB), valued 1 when the customer has at least one currently active subscription to that product and 0 otherwise.
The flag reflects the customer's aggregated status across all their subscriptions for that product — not a single subscription — and recalculates on every relevant lifecycle event (create, renew, reactivate, cancel, expire).
- A renewal, or a cancellation scheduled for end of term, keeps the flag at 1 while any subscription stays active; it drops to 0 only once the customer has no remaining active subscription to that product.
"Active" counts active, trialing, and extended subscriptions.

🎯 Impact:

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

🟢 Platform: Additional Fields in Webhook Payloads

Webhook payloads are being extended with payment and membership fields that previously required a supplementary API call.

✅ What's New:

Payment method status (chargeable / pending / failed) now included on subscription webhook payloads
Institutional member and seat status fields being surfaced for membership/seat holders
Additive only — no existing field 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.

🟢 Platform: Higher Limit for Paywall Exclude URL Patterns

The paywall's Exclude URL Pattern field now holds significantly more entries.

✅ What's Improved:

Capacity increased to roughly 25 entries (~300 characters)

🎯 Impact:

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