Description

DabDash Sync connects a WooCommerce store to a
DabDash tenant so storefront-facing flags stay honest:

ID / profile / email / phone verification timestamps
Loyalty balance and coupon eligibility
Marketing consent (email and SMS) with a most-restrictive merge — an
unsubscribe on either side always wins

DabDash is canonical. WooCommerce may propose contact edits; it cannot forge
verification or profile compliance state. Sensitive fields (ID images, regulated
profile identifiers, date of birth) never land in wp_usermeta.

Runtime API calls use the official Packagist package
shadow-software/dabdash-php-sdk.

This plugin is free and open source. It is developed and maintained by
Shadow Software LLC, and its full source code is
public on GitHub.

Documentation and source code

Platform: https://dabdash.com/
API reference: https://dabdash.com/docs/api
TypeScript SDK: https://github.com/shadow-software/dabdash-sdk
Plugin page: https://dabdash.com/integrations/woocommerce
Documentation: https://github.com/shadow-software/dabdash-for-woocommerce#readme
Source code and releases: https://github.com/shadow-software/dabdash-for-woocommerce
Report a bug or request a feature: https://github.com/shadow-software/dabdash-for-woocommerce/issues

How it works

Enter your DabDash tenant API base URL (a *.dabdash.com host) and access
token under Settings DabDash Sync.
Review the field-map diagnostics (canonical / contact / consent / never).
Enable sync. Confirm you understand customer fields will be sent to DabDash.
An hourly background job pulls customers, links them to WooCommerce users,
applies DabDash-owned fields, and queues contact/consent proposals upward
when WordPress holds a newer local edit.

What it does not do

It does not store ID document images, sensitive profile documents, or date of birth in
WordPress. It does not invent verification state. It does not send passwords.

External services

This plugin connects to your DabDash tenant API — a host you configure under
*.dabdash.com or *.dabdash.app (local hosts only when WP_DEBUG is on).
Nothing is sent until an API base URL and access token are saved and Enable
background sync is checked.

1. Tenant API (your DabDash host, via shadow-software/dabdash-php-sdk)

What it is for: keeping WooCommerce customers in step with DabDash
verification, loyalty, and marketing consent. DabDash is the source of truth
for verification and loyalty; consent merges most-restrictive.
When it is called: on an Action Scheduler / WP-Cron pull (hourly by
default) and when a tracked local profile field changes (push proposal).
What is sent (contact / consent proposals only): name, email, phone;
email / SMS marketing opt-out flags. The plugin never pushes ID documents,
regulated profile identifiers, dates of birth, or passwords.
What is received: verification timestamps, loyalty / coupon flags,
consent state, and the DabDash customer id linked on the WordPress user.
Transport: HTTPS JSON via the Packagist SDK (Guzzle). Tokens are stored with
autoload disabled.

Terms and privacy

DabDash Terms: https://dabdash.com/terms-of-service
DabDash Privacy Policy: https://dabdash.com/privacy-policy
Shadow Software Terms: https://shadowsoftware.com/terms
Shadow Software Privacy Policy: https://shadowsoftware.com/privacy

Screenshots

Settings — connect a DabDash tenant and review field-map diagnostics.

Installation

Install from the WordPress.org directory (or a GitHub Release ZIP), then activate. WooCommerce must be active.
Go to Settings DabDash Sync.
Enter your tenant API base URL and access token.
Enable sync when ready.

FAQ

Does this send customer passwords or ID documents to WordPress?: No. Passwords, ID images, sensitive profile documents, and date of birth are classified
never and are not mirrored.
What happens if someone unsubscribes in WooCommerce?: Consent is a ratchet. When a customer updates their account, checks out, or
their marketing meta changes, the plugin stamps a local-modified time and the
next sync proposes the opt-out upward to DabDash so both platforms converge on
the restrictive value.
Do I need WooCommerce?: Yes. This plugin requires WooCommerce 8.2+.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“DabDash Sync for WooCommerce” is open source software. The following people have contributed to this plugin.

Shadow Software LLC

Translate “DabDash Sync for WooCommerce” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.1.6

Remove remote writes to WordPress user identity fields, correct public legal URLs, and exclude OpenAPI generator metadata from the distribution archive.

1.1.5

WordPress.org readme: neutral compliance/profile language in directory copy.

1.1.4

Strip OpenAPI SDK dev artifacts (git_push.sh, etc.) from release ZIPs; enforce
vendor prune in CI Plugin Check and deploy builds.

1.1.3

Updated bundled shadow-software/dabdash-php-sdk to 6.3.0.

1.1.2

Updated bundled shadow-software/dabdash-php-sdk to 6.2.1.

1.1.1

Updated bundled shadow-software/dabdash-php-sdk to 6.1.1.

1.1.0

Usermeta keys use the dabdash_woo_ prefix family (_dabdash_woo_*) for
WordPress.org uniqueness; legacy _dabdash_* keys still read/uninstall.
External services section expanded; Plugin Review sandbox guidance on settings.
Host allowlist messaging includes *.dabdash.app.

1.0.1

Updated bundled shadow-software/dabdash-php-sdk to 6.1.0.

1.0.0

Production sync loop via Action Scheduler (or WP-Cron) using
shadow-software/dabdash-php-sdk from Packagist.
WooCommerce hooks stamp local edits for upward contact/consent proposals.
Host allowlist for API base URLs; token stored without autoload.
WordPress.org packaging (slug dabdash-for-woocommerce).