External Products in GT Extensions for FluentCart
External Product keeps a normal FluentCart listing and product page while sending the buying action to another website. Your store still holds the product’s title, media and description; the external destination handles the purchase.
Use it for an affiliate listing, marketplace product or external booking page. It is different from a service product, which is paid for inside your own FluentCart checkout.
Set Module Defaults
Enable External Product in GT Extensions. Configure the default button text, same-tab or new-tab behavior, link attributes and whether to hide the FluentCart price. These defaults are copied when a product is configured; an individual product can override them.
Configure a Product
The destination belongs to the product, not to the entire store.
- Open the product in FluentCart → Products.
- Choose External Product from its product menu.
- Enable external purchase.
- Enter the full destination URL, including https:// or http://.
- Set the button text and link target.
- Review nofollow, sponsored and price visibility, then save.
For example, View on Marketplace is a clearer label than Add to Cart when the customer is leaving your site. Use sponsored where appropriate for a paid or affiliate relationship. New-tab links include noopener and noreferrer.
Storefront and Checkout Behavior
The module replaces supported local purchase controls on cards, product pages and standalone purchase blocks. It also guards older instant-checkout URLs and rejects an external product found in a local cart or checkout.
- The local product page remains available for descriptions and media.
- Price hiding applies to that external product’s FluentCart price display.
- External products should not create a local order through the guarded purchase paths.
- The destination website is responsible for payment, delivery and returns.
Check the Destination
Test a card, the product page and any embedded purchase button you use. If you duplicate a product, review its copied external settings before publishing the duplicate. Use the external redirect action for custom tracking rather than changing the destination handler directly.