Description
Connect WooCommerce to AYBABTU to configure supplier feeds and synchronize selected product and variation inventory. The plugin provides in-admin Sandbox signup with email verification, manual API key entry, and a link to the separate AYBABTU dashboard. Signup begins only after an administrator clicks Start Sandbox.
An AYBABTU account and API key are required. AYBABTU’s Sandbox plan includes 1,000 requests per month and automatic inventory syncs every 15 minutes. Scheduled syncs are not counted against the monthly request allowance.
AYBABTU is not affiliated with or endorsed by SanMar Corporation. SanMar is a trademark of its owner.
External services
This plugin connects to AYBABTU, operated by Epic Force LLC. Its API origin defaults to https://aybabtu.app. An administrator can set AYBABTU_SYNC_API_BASE in wp-config.php to a validated HTTPS origin for staging. AYBABTU_SYNC_APP_URL continues to control dashboard and documentation links.
When an administrator with the manage_options capability views the AYBABTU Sync settings page and an API key is saved, WordPress makes a server-side GET request to https://aybabtu.app/api/dashboard/jobs/active, or to the same path at the configured service origin. This read-only route uses the same API-key authentication as the dashboard and works before a WooCommerce connection is configured. The saved key is sent only in the Authorization: Bearer header. The URL does not include the key, WordPress site URL, or other site settings. The plugin uses the HTTP status to display connection status and does not display the response body. Results are cached per site and key for about 10 minutes. Clicking Check connection clears the cache and redirects to the settings page, where the check runs again. This authenticated read request can count toward the AYBABTU API request allowance. WordPress sends ordinary network information such as the server IP address and HTTP headers with this request.
The optional agency partner ID is saved in WordPress settings and is not included in the connection check.
No request is made to aybabtu.app when the plugin is activated or when the Get your key page is viewed before consent. The plugin may queue setup events locally until consent is given. When an administrator clicks Start Sandbox, the plugin saves aybabtu_sync_telemetry_optin=1 and sends the entered email address, a site hash, and plugin version from the WordPress server to the AYBABTU signup endpoint. The site hash is SHA-256 of the WordPress home URL and the WordPress auth salt. AYBABTU creates or looks up the account on the Sandbox plan as applicable, generates a short-lived email code, and sends that code to the submitted address. The signup endpoint records the request IP with the code for abuse prevention.
When the administrator submits the email code, WordPress sends the email, code, and site hash server-to-server. AYBABTU returns an API key in the response, and WordPress saves it in the same option used by manual key entry. The API key is not put in a browser URL.
After opt-in, the plugin sends setup events to aybabtu.app: plugin activation, key-screen views, code sent, key saved, first successful stock sync, and deactivation. Event requests contain only the site hash, plugin version, event names, client timestamps, and (for deactivation) the selected reason and optional text. They do not contain an email or WordPress site URL. The deactivation prompt is shown only after opt-in; selecting a reason sends the event before deactivation, while Skip & deactivate sends no reason event. Setup events are sent from the WordPress server. If consent has not been given, queued events remain local and are not transmitted.
When an administrator connects a WooCommerce store in the AYBABTU portal, the store URL and WooCommerce REST API consumer key and secret are sent to AYBABTU. The AYBABTU service uses those credentials to read and update product and variation SKUs, stock quantities, backorder settings, optional prices, and the _aybabtu_supplier product-selection field during configuration and inventory synchronization. The plugin exposes _aybabtu_supplier as WooCommerce REST product metadata for that selection flow.
The plugin also registers the WooCommerce REST route /wp-json/wc-aybabtu/v1/stock/increment. AYBABTU can send a receipt ID and product or variation stock adjustments to this route after a receipt is marked received. The route requires a timestamped HMAC proof associated with a WooCommerce read/write API key and applies each receipt adjustment once.
The optional storefront link to https://aybabtu.app is disabled by default. If enabled, it adds a link to product pages; a visitor’s browser contacts AYBABTU only if the visitor follows that link.
The plugin does not load third-party scripts, styles, fonts, or analytics, and it does not contact supplier services directly. If an administrator configures a supplier such as SanMar, AYBABTU’s service may contact that supplier using the feed credentials and product information provided to AYBABTU.
Terms of Service: https://aybabtu.app/terms
Privacy Policy: https://aybabtu.app/privacy
Installation
- Install and activate WooCommerce.
- Install and activate this plugin.
- In wp-admin, open AYBABTU Sync > Get your key, enter an email address, and select Start Sandbox. Enter the emailed code to save the API key, or paste an existing key on the settings page.
- Confirm the connection status, then select Open AYBABTU dashboard to connect your store with WooCommerce REST API consumer credentials with read and write access.
- Configure a supplier feed in the AYBABTU dashboard and choose which products to synchronize.
FAQ
What does this plugin synchronize?
The AYBABTU service synchronizes selected WooCommerce product and variation inventory using the supplier feed and matching rules you configure. Depending on your settings, it can update stock quantities, backorder settings, and prices.
Where do I manage my AYBABTU connection?
Use Get your key to create an account and verify your email inside wp-admin, or paste an existing key on the AYBABTU Sync settings page. Use Open AYBABTU dashboard to open the separate AYBABTU portal in a new tab and manage the WooCommerce connection and supplier settings there.
When does setup send my store URL and administrator email?
WordPress sends the email address to aybabtu.app only after you click Start Sandbox. Signup and email verification happen inside wp-admin.
Does the plugin contact supplier services directly?
No. The plugin connects to AYBABTU. If you configure a supplier such as SanMar, AYBABTU’s service may contact that supplier using the credentials and feed settings you provide to AYBABTU.
Is AYBABTU affiliated with SanMar?
No. AYBABTU is not affiliated with or endorsed by SanMar Corporation.
Is the storefront link enabled by default?
No. The optional Inventory synced by AYBABTU link is off until an administrator enables it on the plugin settings page.
What information is sent to AYBABTU?
The plugin’s server-side connection check sends the saved API key in an Authorization header. The AYBABTU service also communicates with WooCommerce to read and update products when you configure a store connection. See External services for details.
Screenshots
Changelog
1.4.0
- Added first-run account setup with email verification and one-time API key handoff.
- Added a manual API key connection option for existing accounts and documented setup data flows.
1.5.0
- Added in-admin Sandbox signup and email code verification with one-time API key delivery.
- Added opt-in setup telemetry, first-sync reporting, and the deactivation feedback prompt.
- Documented signup requests, telemetry fields, and consent behavior.
1.3.0
- Replaced the wp-admin dashboard embed with a native settings page and external AYBABTU dashboard link.
- Added a server-side, cached API key connection check and scoped, persistent settings notices.
- Removed the browser-side API key handshake and made storefront-link configuration available in plugin settings only.
1.2.0
- Added an authenticated, idempotent receipt stock increment endpoint for AYBABTU ordering.
- Added atomic marker and stock updates for simple products and variations.
1.1.0
- Prepared the readme and package checks for WordPress.org directory review.
- Clarified the AYBABTU service data flows and optional storefront link.
- Retained the existing WooCommerce compatibility declarations and prefixed settings.


