Connect your tools. Keep business moving.

Account eligibility, access and licensing are scoped per project. Listing a provider does not imply an official partnership.

Account eligibility, access and licensing are scoped per project. Listing a provider does not imply an official partnership.

Account eligibility, access and licensing are scoped per project. Listing a provider does not imply an official partnership.

Account eligibility, access and licensing are scoped per project. Listing a provider does not imply an official partnership.

Account eligibility, access and licensing are scoped per project. Listing a provider does not imply an official partnership.

Account eligibility, access and licensing are scoped per project. Listing a provider does not imply an official partnership.

Account eligibility, access and licensing are scoped per project. Listing a provider does not imply an official partnership.

An eligible merchant account in a supported country is required. Payment methods depend on country and account approval; capture and refund flows are tested during setup.

The business must qualify for a Stripe account in a supported country. Currencies, methods, webhooks and refunds are validated for the project.

An eligible business based in the EEA, Switzerland or the UK and a qualifying bank account are required. Enabled methods depend on the Mollie account's eligibility.

An active Klarna agreement, HTTPS and regional API credentials are required. Options depend on customer, country and account eligibility; approval is not guaranteed.

An Amazon Pay merchant account in a supported country and HTTPS are required. A standard Amazon selling account is insufficient; region, currency and notification flows are tested.

A Sendcloud account and an appropriate plan are required. Carriers and delivery options depend on country; order, product and customs fields are mapped.

A seller account, developer access and OAuth authorization are required. Categories, SKUs and policies are mapped; editing restrictions for API-managed listings are considered.

A Brevo account, an appropriate plan and communication permissions are required. The documented plugin syncs from the store to Brevo; full two-way sync and custom-field support are not assumed.

Account eligibility, country scope, licences and the exact supported data flow are verified in the project plan.

Account eligibility, country scope, licences and the exact supported data flow are verified in the project plan.

Configured alongside shop tax settings for customer VAT numbers, VIES validation and eligible tax exemptions. This extension does not validate UK VAT numbers; UK workflows need separate assessment.

Account eligibility, country scope, licences and the exact supported data flow are verified in the project plan.

Account eligibility, country scope, licences and the exact supported data flow are verified in the project plan.

Account eligibility, country scope, licences and the exact supported data flow are verified in the project plan.

Account eligibility, country scope, licences and the exact supported data flow are verified in the project plan.

An approved Adyen merchant account is required. The documented WooCommerce connection uses the Woosa partner plugin; licensing, merchant-country eligibility and enabled methods are verified before implementation.

The merchant must be based in the SEPA area and approved by Unzer. Invoice, instalment and local methods depend on country, customer and contract; not every method is available everywhere.

An active merchant account on the compatible Worldline platform, API credentials and webhooks are required. Methods depend on the contract. Subscription support is not assumed for this WooCommerce plugin.

This Nexi Checkout product lists Germany, Austria, Denmark, Norway and Sweden. An approved merchant account and HTTPS are required; enabled methods, currencies and subscription scenarios are verified for the account.

The Tehster connector requires a licence and suitable GLS account. Origin countries are DE, FR, IE, AT, BE, HR, CZ, HU, RO, SI, SK and RS; availability is not Europe-wide.

A Packlink PRO account is required. Origin country, carriers and services are verified in the account. Plugin access and shipment charges are separate; customs and delivery conditions depend on the route.

This documented connection is DPD Netherlands. A suitable account, depot and enabled services are required; compatibility with DPD contracts in Germany or other countries is not assumed.

In the current package structure, store connectivity requires ERP Handel. The account, master data, sync directions and custom fields are defined; local invoicing and tax scenarios are checked separately.

An appropriate easybill Connect plan, API access and tax mapping are required. Import scheduling and API version are verified; older Legacy API instructions are not applied to current stores without review.

A licence matching the required features is selected. VIES validation and tax-exemption rules depend on the business; a validated VAT number does not automatically exempt every order.

An active Trusted Shops membership is required. Trustbadge, buyer protection and product reviews depend on the contract; installing the plugin does not automatically certify or approve the store.

A CleverReach account and suitable plan are required. Consent, double opt-in and unsubscribe workflows are configured for the business; customers are not automatically added to marketing lists.

A Cookiebot account, suitable domain plan and script review are required. Consent management alone does not guarantee GDPR or complete legal compliance; legal content is supplied by your adviser.