Newcraft Marketplace Sync for Bol.com

Newcraft Marketplace Sync for Bol.com helps WooCommerce store owners connect their store to the Flowwise service from the WordPress admin for marketplace workflows. After the administrator confirms the connection, the plugin creates a WooCommerce REST API key and sends the credentials to Flowwise through a signed connection flow. The actual order sync and marketplace workflow configuration runs in Flowwise. This plugin handles onboarding, connection status, local activity logs and WooCommerce API key revocation. Bol.com orders imported by Flowwise include a tracking panel in the WooCommerce order editor. Add the carrier and track-and-trace code, then complete the order. When tracking sync is enabled in Flowwise, Flowwise submits that shipment to Bol.com. A Flowwise account is required to use this plugin. Open the Flowwise app at app.flowwise.dev. This plugin is developed by Newcraft and connects to the Flowwise service. It is not affiliated with, endorsed by, or sponsored by bol.com, WooCommerce, or Automattic.

0.2.17 Share one WooCommerce REST connection safely with other compatible Newcraft plugins, including owner-aware disconnect and migration of existing connection metadata. Keep Bol.com tracking controls active while that WooCommerce connection is shared with compatible Newcraft plugins. 0.2.16 Add carrier, track-and-trace and tracking URL controls to Flowwise Bol.com orders in both classic and HPOS order editors. 0.2.15 Show Flowwise bol.com imports in a user-hideable WooCommerce order-list origin column, with support for both classic orders and HPOS. Load the Flowwise Crisp support chatbox on the plugin admin page. Give Flowwise support the current administrator, site, software version and connection context in Crisp without sending order or customer data. 0.2.14 Deactivate legacy Flowwise plugin packages during activation and preserve the WordPress return nonce throughout the connection flow. 0.2.13 Show the Flowwise workspace owner email in the connected WordPress admin state. 0.2.12 Return merchants to the exact Flowwise Commerce setup after WooCommerce is connected. 0.2.11 Rename the plugin to "Newcraft Marketplace Sync for Bol.com" and identify Newcraft as the plugin publisher while documenting Flowwise as the external service. 0.2.8 Use separate plugin and author URIs in the plugin headers for WordPress.org submission validation. 0.2.7 Notify Flowwise when the plugin is disconnected or uninstalled, and revoke the generated WooCommerce API key during uninstall cleanup. 0.2.6 Document the Flowwise terms of service for the external SaaS connection. 0.2.5 Harden the Flowwise return step by requiring the WordPress return nonce and by using the configured Flowwise app URL for the credential callback. 0.2.4 Replace the technical checks card with a support contact card in the WordPress admin screen. 0.2.3 Allow the signed Flowwise return step to create a pending confirmation without a WordPress URL nonce. The final credential creation remains protected by the WordPress confirmation form nonce. 0.2.2 Address WordPress Plugin Check feedback for tested WordPress version, admin query nonce handling, safe redirects and documented WooCommerce API key table writes. 0.2.1 Hide the Flowwise app URL field and route new WooCommerce connect users through one Flowwise email flow for sign-in or account creation. 0.2.0 Rename the plugin package for WordPress.org submission, add external service disclosure, improve translation readiness and keep a legacy loader for existing pre-0.2.0 installs. 0.1.1 Clarify the connected state and add clearer activity feedback. 0.1.0 Initial companion plugin for Flowwise WooCommerce connections.