Introduction: Why clean order reconciliation matters
When affiliate tracking and merchant order systems operate asynchronously, gaps arise: missing matches, manual follow‑up, incorrect commission payments or unwanted false positives. A structured order reconciliation prevents loss of commissions and protects against incorrect payouts. This guide shows how to reconcile missing or delayed orders cleanly with Affilentra conversion IDs, order imports, webhook logs and recon rules.
Brief overview: Roles and tools
Before getting into practical details: Affilentra clearly separates platform operators, merchants and affiliate partners. Four elements are relevant for reconciliation:
- Conversion ID – unique identifier provided by Affilentra in tracking or conversion events.
- Order Import – merchant-side import of order data (CSV or API) for reconciliation.
- Webhook Logs – records of incoming events and the merchant system's responses.
- Reconciliation Rules – prioritized matching logic and tolerances that prevent incorrect assignments.
- Embedding: Pass the Conversion ID to the order confirmation (for example as a hidden field, a URL parameter on the thank-you page, or in the API response). This ensures the ID is stored in your merchant order record.
- Persistence: Store the Conversion ID with the order even if payment is confirmed later. This keeps mapping possible regardless of payment status.
- Partner Links: Partners should receive personalized tracking links that reliably transmit Conversion IDs or reference variables.
- Mandatory fields: order_id, order_date (UTC), order_total, currency, order_status, conversion_id (if available), customer_email_hash (optional).
- Format: Use machine-readable formats (CSV with UTF-8 or JSON via API). Consistent date formats (ISO 8601) make time-window comparisons easier.
- Idempotency: Mark import jobs uniquely so repeated imports do not create duplicates.
- Partial imports: Support updates (e.g., status changes from pending to paid) instead of only full new records.
- Immediate logging: Record every received webhook including headers, payload, recipient response and timestamp.
- Retry mechanism: Document all delivery attempts with status codes. 5xx responses require different actions than 4xx.
- Error analysis: Search for patterns: recurring 409/422 (data conflicts), timeouts, or missing conversion_id in payloads.
- Audit trail: Webhook logs should be linked with order imports and reconciliation decisions to understand cause and effect.
The self-hosted PRO & NETWORK editions allow full control over these elements without revenue sharing.
1. Use Conversion IDs correctly
The Conversion ID is your central key for matching. Used correctly, it drastically reduces incorrect mappings.
2. Order Import: Structure and required fields
The order import is the bridge from the merchant ERP into Affilentra. Ensure a consistent data picture:
3. Webhook logs as a diagnostic tool
Webhooks are primarily real-time notifications — their logs are your first diagnostic tool for asynchrony issues.
4. Reconciliation rules: priority, tolerances, fallbacks
A clear, prioritized cascade of rules reduces false positives. Suggested practical match order:
- Exact match: conversion_id + order_id → match immediately. This is the most reliable mapping.
- Timestamp check: If conversion_id is missing, check whether order_timestamp is close to conversion_timestamp within a configurable window (e.g. 0–72 hours, adjustable).
- Amount tolerance: If amount and currency match (optionally with a small tolerance for rounding), a match can be confirmed.
- Hash fallback: If an email hash is present and stored in a GDPR‑compliant way, use it as an additional indicator.
- Partner reference: If the partner uses an external reference variable, this can serve as a last fallback — but only after manual verification.
Important: Each rule should have a configurable weight and a risk score. If the score exceeds a threshold, an automatic match is created; otherwise the case goes to the manual review queue.
5. Handling common problem cases
Asynchronous payments, cross‑device journeys or cookie loss are primary reasons for missing matches. How to address them:
- Later payment reconciliation: Keep order imports with status updates available so cancellations and later payments are considered.
- Cross‑device: Use server‑side tracking and persistent conversion IDs to bridge devices.
- Cookie loss: Include conversion parameters in the order confirmation or email templates as well, so partner references are preserved.
- Multiple conversions: Implement duplicate checks and policies determining which conversion is prioritized (e.g. last valid conversion before the order).
6. Monitoring, alerts and reporting
Operationalize reconciliation with metrics and alerts:
- Share of unlinked conversions per day/week
- Average time to match
- Proportion of manual reviews and their turnaround time
- Error categories from webhook logs (e.g. missing conversion_id, auth errors)
Set alerts for sudden increases in unlinked conversions or high retry rates on webhooks — these are early indicators of integration issues.
7. Role‑based responsibilities
A clean reconciliation requires clear ownership:
- Platform operators: Provide platform features (log retention, retry, rule engine) and operate infrastructure monitoring.
- Merchants: Implement order import/API endpoints, store the conversion ID in orders and provide timely status updates.
- Partners: Use tracking links correctly, report discrepancies and supply additional references when needed.
Practical checklist (short)
- Store the conversion ID in the order confirmation
- Set up order import with idempotent updates
- Log webhook records completely and make them searchable
- Configure reconciliation rules with priorities and tolerances
- Define monitoring dashboards and alerts
- Provide manual review processes for uncertain matches
Conclusion and next steps
Order reconciliation is not a one‑off project but an iterative process. With Affilentra, conversion IDs, structured order imports, meaningful webhook logs and a flexible rule engine can be combined so that asynchronous orders are matched reliably and false positives are minimized. Start by consistently passing the conversion ID and implementing an idempotent import workflow; build monitoring and prioritized recon rules on top of that.
Act now: Choose your entry point to operate reconciliation transparently and under control. Choose entry: https://affilentra.de
Next step
Try Affilentra yourself
A unified platform that transparently brings together product provisioning, tracking, conversion validation, commission calculation and payout along clearly separated roles; option for a self‑hosted installation with a perpetual license without revenue sharing; merchants retain control over products, terms and creatives; partners receive personal tracking links and a transparent payout history.