Introduction
Onboarding merchants involves more than filling out a form: products must be made available, tracking configured, conversions validated and commission rules defined. Affilentra links these steps in a self-hosted environment where operators, merchants and partners have separate roles. This article shows concretely how to configure webhooks, validation rules and automated test orders in Affilentra (PRO & NETWORK) so that merchants are integrated into your partner network quickly, securely and without errors.
Why webhook-driven onboarding?
Webhooks allow external systems (shop, ERP, payment provider) to be event-driven integrated with Affilentra. Instead of manual entries or scheduled imports, you react immediately to relevant events such as merchant creation, product updates or order events. Combined with automated validations and test orders, this reduces the error rate, shortens lead times and increases traceability for merchants and partners.
Preparatory steps (checklist before technical implementation)
- Install a self-hosted Affilentra instance (PRO or NETWORK).
- Ensure: HTTPS, access for software operators and administrators, up-to-date PHP/MySQL environment.
- Clarify available merchant information: shop URL, API access, product catalog, desired commission models.
- Define which events should trigger webhooks (e.g. merchant.created, product.updated, order.created, order.status_changed).
- Outline roles and permissions: which actions merchants, partners and operators are allowed to perform.
Configuring webhooks in Affilentra
Affilentra provides the ability in PRO & NETWORK to configure webhooks for system-wide and merchant-specific events. Proceed as follows:
- Create a webhook endpoint: Register a new webhook in the admin area and enter the destination URL of the external system.
- Event selection: Choose events deliberately, e.g. merchant.created, merchant.updated, product.synced, order.created. Limit the selection to what is necessary to reduce traffic.
- Configure security: Enable HMAC signatures with a shared secret. Affilentra signs payloads and external systems verify the signature before processing.
- Retry strategy: Specify the number of retry attempts and backoff strategy so that temporary outages do not lead to data loss.
- Idempotency: Use unique event IDs in the payload so recipients can detect repeats and avoid duplicate processing.
Practical notes
Document the expected payload structure for your shop or ERP team. Common fields are merchant_id, shop_url, products (with SKU, price, availability) and signatur_meta. Clear field names and data types reduce coordination effort.
Validation rules: Configure field and business rules
Validation rules protect your network from incorrect or incomplete data. Affilentra allows configurable checks on multiple levels:
- Schema checks: Required fields, data types and length limits (e.g., shop_url must be a valid HTTPS, SKU must not be empty).
- Business rules: Example: commission types must match the products, selected payout methods must be enabled for the merchant.
- Context‑dependent validation: Rules that apply only to specific merchant categories or markets (e.g., minimum conversion value for certain partner programs).
Implement validations as part of the webhook processing flow. For invalid inputs, Affilentra automatically sends feedback to the source systems (webhook response) and logs the error message in the user interface for operators and merchants.
Automated test orders: Validate tracking and commission logic
Test orders are central to verifying tracking paths and commission calculations before a merchant goes live. You should implement test orders in Affilentra as follows:
- Enable test mode: Set a test status for the merchant in which orders are marked as tests and do not trigger real payouts.
- Simulation payloads: Create standardized test orders that cover various scenarios: successful conversion, cancellation, partial refund, chargeback.
- Automated triggering: Trigger test orders via webhook from the shop or via the Affilentra API. Test orders should include the same tracking parameters as live orders (e.g., affiliate_id, campaign_id, click_id).
- Reporting and tracing: Test orders appear in the order history including validation status and commission calculation so that merchants and operators can spot discrepancies.
Introduce a short test procedure: send test order → check validation → verify commission calculation → reset the test order or promote it to live if everything is correct.
Role mapping and permissions
A central element in onboarding is the clear separation of roles. Affilentra distinguishes software operators, merchants and partners. Configure roles as follows:
- Software operator: Full access to system configuration, webhook management, license administration and global validation rules.
- Merchant: Control over products, prices, promotional assets, terms and merchant‑specific webhooks; insight into commission settlements for their own programs.
- Partner (Publisher/Creator): Personal tracking links, transparent conversion and payout history, access to promotional materials.
Mapping rules define which default permissions a newly created merchant receives. In PRO & NETWORK you can create templates that are automatically assigned together with webhook events (e.g. merchant category A → a specific commission model + restricted API access).
End-to-End Onboarding Pipeline: Example Flow
A typical automated flow with Affilentra looks like this:
- Shop sends merchant.created → Affilentra creates the merchant and checks basic data (schema checks).
- Affilentra triggers merchant.validation_failed/merchant.validation_passed to the shop system and the operator.
- If the check passes, product syncs are initiated via product.synced; validation rules for products run.
- Test orders are automatically generated (order.created with test_flag); tracking and commission logic are checked.
- After a successful test, the merchant receives live status; partners receive personalized tracking links and can start campaigns.
Monitoring, Logs and Error Handling
Use the logging in Affilentra: webhook events, validation errors and test orders should be visible in the dashboard. Create alert rules for recurring errors (e.g. failed product syncs) and define escalation rules to the operator.
Practical Example: Quick Start for a New Merchant
Concrete procedure in a few steps:
- Send merchant data to Affilentra via the merchant.created webhook.
- Affilentra validates required fields; if data is missing the shop API receives a detailed error object in response.
- On successful checks, product data is synchronized and a series of test orders are automatically generated.
- Test results are displayed in the merchant portal; the operator reviews approval and sets the merchant to live.
- Partners automatically receive tracking links for the new merchant program and see test and live conversions in their history.
Conclusion and Recommendations
Webhook-driven onboarding reduces manual steps and enables transparent, reproducible processes. With Affilentra you ensure that validation rules and test orders are an integral part of onboarding — and that roles remain clearly separated. Practically, this means fewer booking errors, faster time-to-market and traceable payouts for all parties involved.
Next step: Review your onboarding checklist, define the required webhook events and create standardized test orders. If you want to use Affilentra, choose the appropriate entry for your organization.
Next step
Try Affilentra yourself
A unified platform that transparently brings together product provisioning, tracking, conversion validation, commission calculation and payout across 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 traceable payout history.