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 DHL business contract, customer number and eligible product permissions are required. Available services depend on origin country and contract.

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

A Shipcloud account, eligible carrier access and a plugin compatibility check are required. Labels, service selection and status flows are tested for your store.

A Billbee account and authorized store REST API access are required. Fields and statuses are mapped; plugin-specific custom fields require separate assessment.

Billbee and sevdesk accounts are required. API version and tax cases are checked; the current V2 bridge has an OSS limitation, so cross-border scope requires separate validation.

Billbee and Lexware Office accounts, authorization and eligible records are required. Invoice, customer and tax fields, OSS, warehouse country and exceptions are validated with your accountant.

An eligible Xentral account and Connect access are required. Master data ownership, sync directions and custom plugin fields are assessed; the current Connect flow replaces the legacy connector.

An eligible JTL version, Connector license and compatible hosting are required. Initial transfer, data priorities and plugin compatibility are checked; JTL-Wawi leads ongoing data maintenance.

Billbee, an activated DATEV data service and your accountant's adviser/client numbers are required. Transfer scope and account mappings are agreed together; tax advice is excluded.

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

An approved seller account, API keys and product data suitable for the target country are required. Scope includes category and SKU mapping, error handling and playground testing.

OTTO seller approval, a contract and an API user through OPC are required. A technical connection does not imply seller admission; data quality and scenarios are validated in the sandbox.

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.

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.

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.