AffiliPartnerCS / Support
Find the problem before you change anything.
Start with System Status and read-only Diagnostics. Preserve the affected records, use the smallest relevant repair, and share sanitized evidence that makes the issue reproducible.
WooCommerce partner-commerce software · Customer Reference 1.3.9
A safe support sequence
Work from evidence to the smallest useful change.
01
Inspect System Status
Record product, WordPress, PHP, and WooCommerce versions; encryption support; routes; optional dependencies; scheduled work; and required record structures.
02
Run read-only Diagnostics
Review partner/plan, commission/payout, paid-state, reference, ownership, access, marketing, lifecycle, and queue consistency. A failed check is uncertainty—not a healthy result.
03
Use a targeted repair
Repair only what the finding supports: required structures, schedules, routes, missing safe references, expired temporary records, or specifically paused work.
04
Reproduce with controlled logging
Enable optional WooCommerce diagnostic logging only long enough to reproduce the operation. Match timestamp, component, non-identifying request reference, and sanitized error.
05
Recheck the original workflow
Confirm the affected operation and related state before closing the issue. Do not delete financial rows or create another payment to see whether the first one worked.
06
Send a bounded report
Provide expected/actual behavior and the smallest safe reproduction sequence with relevant versions and sanitized references.
Trace the record before changing it
- Identify
Program, partner and affected order.
- Inspect
Current commission or payout state.
- Compare
Expected result and recorded explanation.
- Resolve
Use the smallest supported corrective action.
Common questions
The boundary is often the answer.
Why is a final balance not being paid?
Pending Payout means commission is final, not that every payout condition is satisfied. Check the partner/currency group, configured at-least/strictly-above minimum, method minimum, usable recipient profile, currency support, tax status, and retained-liability review. Balances below the minimum carry forward.
Why did a scheduled task not send PayPal or Stripe?
Schedules can discover eligible batches and reconcile existing payments. Native PayPal and Stripe sends require authorized human review. Creating an off-cycle batch bypasses only the calendar date, not the finance checks.
The provider shows success, but the ledger is still open. What next?
Reconcile the existing verified provider reference. Provider Paid – Recover Ledger finishes local closure against that success without another transfer. A timeout or unclear local response is not proof that no payment moved.
Why is Store Credit unavailable or not marked paid?
Confirm compatible credit services, enabled method, supported currency, beneficiary account, frozen amount, tax/lifecycle clearance, and the durable source reference. AffiliPartnerCS closes the payout only after matching credit is confirmed. If issuance succeeded before interruption, reuse its reference and finish accounting; do not issue again.
Does the commission hold block a customer refund?
No. WooCommerce remains responsible for the customer refund. Eligible merchandise refunds can affect provisional commission within its captured window. Final or payout-frozen commission is not automatically reopened by a late refund, chargeback, or provider reversal.
Why can an account log in but not use partner tools?
A customer login alone does not grant partner access. Check the linked organization, seat membership, role, partner lifecycle, and required program. Suspended or terminated partners retain permitted history but cannot make new operational changes.
Why does a copied member coupon not unlock the discount?
Protected member coupons require a current verified pricing session for the correct active partner. Check signed state, timing, one-use identity, authorized secure origin, partner/plan/coupon setup, and the supported server connection. A public affiliate code is not membership proof.
Why is an affiliate referral not attributed?
Check an enabled affiliate plan, operational partner, usable referral context, configured window, and self-referral policy. Verified member pricing takes priority, then a linked public coupon, then an affiliate referral. First/last click does not move affiliate credit above those other sources.
Why do plan expectations and checkout discounts differ?
WooCommerce controls actual coupon amounts, dates, eligibility, limits, and compatibility. Inspect Codes & Coupons mismatch warnings and the native coupon editor. Changing the plan’s expected discount is not an override of those native rules.
Why is an email notice missing?
A saved application or confirmed payout remains its own record even when mail fails. Check configured transport and use authorized test/resend tools. A local mail handoff is not independent proof of inbox delivery, and resending a notice never creates another award.
Does disabling enhancement or deactivating the plugin erase data?
No. Normal PHP pages and forms remain the functional baseline when enhancement is off. Deactivation preserves stored records. Uninstall retention/deletion and Factory Reset are separate choices.
Maintenance is not reset
Keep destructive operations separate from troubleshooting.
| Tool | Purpose |
|---|---|
| System Status | Environment, routes, services, scheduled work, and required structures. |
| Diagnostics | Read-only integrity findings with warnings, critical states, and visible failures. |
| Safe Repair / maintenance | Scoped structural, scheduling, route, reference, cleanup, and paused-work repairs. |
| Diagnostic logging | Temporary redacted troubleshooting details, separate from material audit history. |
| Factory Reset | Explicit permanent clearing of AffiliPartnerCS-owned data/settings—not an ordinary repair. |
| Uninstall choices | Retain Data or selected Delete Data behavior; WooCommerce commerce records remain under WooCommerce. |
Sample removal follows the sample registry and protects samples that gained business history. Factory Reset requires appropriate maintenance and administrator authority plus the exact confirmation process. Do not use it to fix a missing image, theme layout, or uncertain payment.
Contact support
Send enough context to investigate safely.
- AffiliPartnerCS version and relevant WordPress, PHP, WooCommerce, theme, and extension versions.
- The affected operation, expected result, actual result, timestamp, and site timezone.
- The smallest safe reproduction sequence and whether the issue repeats.
- System Status and Diagnostics findings, with sanitized error codes or messages.
- A safe request, commission, batch, or provider reference when it is relevant—never the secret or full payload.
Keep sensitive material out of the report.
Do not send passwords, signing keys, cookies, tokens, raw provider payloads, complete database exports, or unredacted customer records. For an existing payment, preserve its reference and history rather than trying another send.
For purchase, account, download, or license questions, include the relevant order/account reference through the appropriate support channel. Keep plugin-program records separate from the license package you purchased.
Your programs. Your partners.
One connected way to manage them.
Choose the license package that fits your sites. Existing AffiliPartnerCS packages and purchase terms remain on the pricing page.