Dropleather for WooCommerce

Opis

Dropleather for WooCommerce connects your WooCommerce store to Dropleather, a premium leather goods fulfillment platform. Push products from your Dropleather catalog to your store, automatically receive orders, and sync fulfillment status — all without manual work.

Features

  • One-click connection — Enter your Dropleather email and you’re set up
  • Product sync — Push Dropleather products to your WooCommerce store with full details, images, and variants
  • Order sync — New WooCommerce orders are automatically sent to Dropleather for fulfillment
  • Fulfillment tracking — Order status and tracking numbers sync back to WooCommerce automatically
  • Dashboard — View order stats, recent orders, and net profit right in your WordPress admin
  • Status monitoring — Check endpoint health, webhook status, and environment compatibility
  • Error logging — Full log with copy-to-clipboard for easy support

Requirements

  • WordPress 6.0 or higher
  • WooCommerce 8.0 or higher
  • PHP 8.0 or higher
  • A Dropleather seller account (sign up free)

Privacy

This plugin exchanges data with api.dropleather.com only after the site administrator explicitly connects a Dropleather account. No tracking, analytics, or data collection happens before connection.

Sent from your store to Dropleather:

  • Store URL, domain, WordPress and WooCommerce version numbers
  • Auto-generated WooCommerce REST API keys with read/write permissions for products and orders
  • Product catalogue data synced via the REST API: titles, descriptions, prices, images, SKUs, inventory levels
  • Order data for orders containing Dropleather products: order number, customer name, email, phone, shipping address, payment status

Sent back from Dropleather to your store:

  • Fulfillment status, tracking numbers, and carrier details to update the matching WooCommerce orders

Retention:

  • Integration credentials (OAuth / API tokens) and synced product records are deleted within 48 hours of disconnecting the store
  • Order records containing customer personal data are retained for 7 years for tax and legal compliance (German HGB §257, AO §147), then anonymized
  • On-demand deletion requests under GDPR Article 17 are honored within 30 days regardless of the 7-year window
  • Database backups are automatically deleted after 30 days

Sub-processors:

Dropleather uses AWS and Supabase for cloud hosting, and Stripe / PayPal / Adyen for payment processing. A current list of sub-processors is available on request at privacy@dropleather.com.

Disconnecting: revokes all API access and stops further data transmission immediately.

Full privacy policy: https://dropleather.com/legal/privacy-policy

A suggested privacy-policy block is registered via WordPress’s Privacy Policy Guide (Settings Privacy Policy Guide) for admins to paste into their site policy.

Snimke zaslona

  • Dashboard — order stats and recent orders
  • Settings — connection and sync configuration
  • Status — endpoint health and environment info
  • Support — error logs with copy and contact

Instalacija

  1. Upload the plugin folder to /wp-content/plugins/ or install via the WordPress plugin installer
  2. Activate the plugin through the ‘Plugins’ menu
  3. Go to Dropleather > Settings in your admin sidebar
  4. Enter your Dropleather account email and click Connect
  5. Done! Your store is now connected

ČPP

Do I need a Dropleather account?

Yes. Sign up at app.dropleather.com — it’s free to create an account.

How are orders fulfilled?

When a customer places an order on your WooCommerce store containing Dropleather products, the order is automatically sent to Dropleather. Dropleather handles production and shipping, then syncs the tracking number back to your store.

Can I disconnect my store?

Yes. Go to Dropleather > Settings and click Disconnect. All webhooks and stored credentials will be removed.

Recenzije

Pročitajte 1 recenziju

Suradnici i Programeri

“Dropleather for WooCommerce” je softver otvorenog koda. Sljedeće osobe su doprinijele ovom dodatku.

Suradnici

Dnevnik promjena

1.1.5

  • Improved: heartbeat now runs via Action Scheduler instead of wp_schedule_event so the connection-status badge stays accurate on quiet/dev/staging stores where WP-cron silently skips fires (Action Scheduler runs via its own background processor, independent of visitor traffic). Same library used by Stripe, Klaviyo, MailPoet etc.
  • Added: lifecycle webhook on plugin deactivation/uninstall — Dropleather now learns within seconds when a seller deactivates or deletes the plugin, instead of waiting on the 2-hour heartbeat-stale threshold. Fixes the “I uninstalled and the dashboard still says Connected” UX gap

1.1.4

  • Added: 5-minute liveness heartbeat (wp_schedule_event) so the Dropleather dashboard’s /integration page can show a real 3-state health badge (active / idle / stale) instead of a stale “Connected” pill that lies after the plugin is deactivated or the WP server goes offline. One ping fires synchronously on activation and after a successful pair so the seller is shown active immediately
  • Added: dashboard orders table now refreshes via WordPress Heartbeat API delta tick — new WooCommerce orders appear within ~15 s without reloading the WP-admin tab. Steady-state cost on the api side is one indexed since lookup per tick when nothing changed
  • Fixed: stable-tag mismatch in the WP.org submission (Stable tag now matches the plugin header Version)

1.1.3

  • Internal: bumped to ship the orders auto-refresh code path

1.1.2

  • Added: WP 6.5+ Requires Plugins: woocommerce header for native WooCommerce dependency check
  • Fixed: setup wizard redirect now fires only once on activation (one-shot transient) instead of on every admin page load — addresses WordPress.org Guideline 11
  • Fixed: Plugin URI now points to a live page (/integrations/woocommerce)

1.1.1

  • Fix: webhook registration now purges every webhook pointing at the Dropleather delivery URL before creating new ones — prevents accumulation across reconnects, plugin delete/reinstall, or manual DB edits

1.1.0

  • WordPress.org submission prep: removed the bundled GitHub update checker (plugins on WP.org are updated through WP.org’s own update channel)
  • Migrated every log-table query to the native %i identifier placeholder introduced in WordPress 6.2
  • Bumped minimum WordPress requirement to 6.2 and tested-up-to to 6.9
  • Removed redundant load_plugin_textdomain() — translations are auto-loaded for WP.org-hosted plugins since WP 4.6
  • Slug renamed to dropleather-for-woocommerce (WordPress trademark policy requires the “for woocommerce” pattern)

1.0.4

  • Verification release for the GitHub-based auto-update channel

1.0.3

  • Hardened PHPCS compliance — escaped version-requirement notices, prefixed global variables in uninstaller + dashboard template, renamed $order loop variable to avoid colliding with WooCommerce’s global
  • Resolved PHPCS errors reported by the WordPress-Extra + WordPress.Security rulesets so CI runs clean
  • Whitelisted WooCommerce’s manage_woocommerce capability in phpcs.xml.dist
  • No runtime-visible changes — purely code-quality + CI hygiene

1.0.2

  • Hardened logger DB queries (centralised table-name validation, back-ticked identifiers, DELETE in place of TRUNCATE for broader hosting compatibility)
  • Added pre-connect privacy disclosure aligned with the full Dropleather Privacy Policy — lists every data field exchanged, two-way (store Dropleather and Dropleather store), retention periods (48h / 7y / 30d), sub-processors, and GDPR Article 17 handling
  • Registered a suggested privacy-policy snippet via WP’s Privacy Policy Guide (Settings Privacy Policy Guide)

1.0.1

  • Health check auto-disconnect when token is revoked on the Dropleather dashboard
  • Added GitHub-based auto-update mechanism (plugin-update-checker)

1.0.0

  • Initial release
  • Store connection via API key pair
  • Order sync via WooCommerce webhooks
  • Product push from Dropleather catalog
  • Fulfillment status sync with tracking numbers
  • Dashboard with stats and orders table
  • Status page with health checks
  • Support page with error logs