CARTBRIDGE CHECKOUT LINKS FOR WOOCOMMERCE
CartBridge Checkout Links for WooCommerce compatibility with REEID Translate
CartBridge Checkout Links for WooCommerce compatibility with REEID Translate is being reviewed using official plugin documentation. Fills the WooCommerce cart automatically when customers arrive from a Meta (Facebook or Instagram) shop checkout URL. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What CartBridge Checkout Links for WooCommerce does
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
CartBridge Checkout Links for WooCommerce is documented in the WooCommerce category with 5 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How CartBridge Checkout Links for WooCommerce compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Fills the WooCommerce cart automatically when customers arrive from a Meta (Facebook or Instagram) shop checkout URL.
- Configures a Meta Commerce Manager “Checkout URL” so the plugin reads a `products` query parameter, adds the specified products and quantities to the cart, and redirects the customer to the checkout page.
- Supports product ID formats including `wc_post_id_123:2`, `wc_post_id_123_variation_456:2`, and `123:2` (plain WooCommerce post ID fallback).
- Optionally applies a coupon code via `coupon=CODE` and forwards UTM and Meta attribution parameters (e.g., `utm_source`, `utm_medium`, `utm_campaign`, `utm_content`, `utm_term`, `fbclid`, `cart_origin`) to the checkout URL for analytics.
- Validates product IDs against the WooCommerce catalogue and skips non-existent or non-purchasable products; caps quantities at 99 per item and caps item count at 50 per request.
TRANSLATION BOUNDARY
CartBridge Checkout Links for WooCommerce capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- No visitor-facing translation surface was established for this integration.
FREQUENTLY ASKED QUESTIONS
CartBridge Checkout Links for WooCommerce and REEID Translate FAQ.
What does CartBridge Checkout Links for WooCommerce do?
CartBridge Checkout Links for WooCommerce has 5 documented features listed in its official documentation. See the Plugin Information section for details.
Does CartBridge Checkout Links for WooCommerce have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from CartBridge Checkout Links for WooCommerce?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate CartBridge Checkout Links for WooCommerce in a multilingual WordPress workflow.
REEID documents CartBridge Checkout Links for WooCommerce functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.