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.

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.

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.

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.

A Dopigo account and suitable plan/module are required. Its WooCommerce page states that this module may be purchased in addition to the monthly/yearly plan. Product IDs, variations, stock ownership and sync directions must be mapped.

A suitable Entegra plan, store access and the selected ERP/carrier credentials are required. Define the stock source and data priorities. ERP versions and custom fields require separate compatibility checks.

A BirFatura account, suitable credits/plan and store API access are needed. Its current e-commerce page says product and stock data are not yet fully reflected in the panel; full bidirectional inventory sync is not promised. Tax fields must be mapped.

A KolayBi account, integration access under the selected plan and store permissions are needed. Invoice types, VAT fields, stock source and data direction are agreed, with e-document onboarding completed separately.

A Fatura Entegratör account, suitable plan/credits and access to the selected e-document provider are required. Available connections include Mysoft, E-Logo, Uyumsoft, QNB E-Finans and Sovos; actual account scope is checked. The plugin alone does not create an e-document subscription.

A Shipink account and suitable carrier/service access are needed. Your own carrier agreement or an eligible Shipink rate can be used. Cash on delivery, returns and international routes are checked separately; no fixed discount is promised.

A Kargo Entegratör account and the required carrier agreements/API permissions are needed. Select suitable supported carriers such as Yurtiçi, Aras, DHL eCommerce, HepsiJET, PTT and UPS. SMS notifications also need an appropriate SMS account.

This provides tracking records and customer notifications; it must not be sold as automatic shipping-label purchase or carrier booking. Netgsm/Kobikom SMS needs a separate account. Dokan permissions and split-order flows are checked if used.

A separate agreement and API credentials for each chosen bank/PSP are required. The free edition covers selected partner providers; all banks and advanced features may require PRO. Provider names describe connection options, not Bolcal partnerships.

A SanalPosPRO panel account and chosen bank/PSP API credentials are required. Listed connections include Garanti BBVA, Paratika, Moka United and Paycell. Bank fees, installments and currency permissions depend on the merchant agreement; a free plugin does not make processing free.

A Craftgate account, at least one virtual POS and relevant provider agreements are required. The official plugin API lists version 1.0.13, tested through WordPress 6.0.17, so modern-store compatibility needs verification; current API scope may be considered. Not every Craftgate feature is assumed to exist in the plugin.

A Tami account, merchant/terminal details and API key are required. Sandbox and production are configured separately. 3D, hosted checkout and installment access depend on the account; callbacks, failures and refunds are tested on the current store version.