iFrame or cross-site listings?
I operate two related websites, for the same brand. Can I keep Fluent Cart on Site 1, but put checkout buttons or product listings on site 2, and then run checkout and delivery from site 1? Is there a best practice for doing that?
(site 1 has fluent cart plus fluent community for courses on it, site 2 is the public-facing site with about, services, contact, blog, etc)
Do you need the entire product display on site 2, or is a link to the product display on site 1 sufficient?
William Beem Mostly each instance will be a landing page on the main site for one course or product, so it can be simple, like a link back to the cart/community site. But ideally it's a link that begins a 1-click checkout, and not linking to a product page that then requires additional clicks to choose it again and then go to a cart... Because that's more friction.
Lee Busch I think there is an option on the product editor, it copies a direct checkout link. Maybe that is what you want?
Lee Busch In that case, what Natascha says, you can go into your product editor and click the 3 dots next to a variation or product and select the direct checkout link. You then just build you landing page and use that link on a buy now button. Downside to this is there's no cart on the shop side so you can't add a few purchases before going to the cart, but maybe you don't need that?
I can't speak for if it's simple to do out of the box, but all of the functionality is there to do what you're describing. There's pretty comprehensive webhooks and an API that would let your shop site fetch and display products and to send the checkout process back to the cart site.
I'd definitely look at pulling the products in via API rather than an iframe.
Ross FCA I see what you're saying, but that sounds like a lot of work when we own both the sites, it's the same domain, and I'm merely trying to post a few course products on the public site that are housed on the FluentCommunity site, all on the same domain (www domain and subdomain)
What you're describing sounds more like something to be undertaken to build an affiliate network, and more worth doing if that programming can be leveraged against a large catalog of products (not the 2-3 we've got).
Lee Busch The webhooks aren't so bad. I use that a lot with Fluent Forms and FluentCRM automations.
Natascha Vantuykom and William Beem thank you. The docs chatbot did not think of that.
Now, to take advantage of that, I just need to wait for Fluent to fix the direct checkout bug that I reported and that their support verified. (It fails to present a subscription or multi-part payment option correctly)
Lee Busch Chatbots aren't good at innovative thinking or knowing when to pivot. I find that they get buried in the weeds of the current issue and often fail to look at the big picture.