> ## Documentation Index > Fetch the complete documentation index at: https://docs.fluid.app/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > For new direct REST integrations, use the v2026-04 surfaces. The @fluid-app FairShare SDK continues to use its own published public-v2025-06 contract. > Authenticate with the header Authorization: Bearer ; public storefront read endpoints require no auth. > To sign a new merchant up for Fluid programmatically, call POST https://api.fluid.app/api/company with no credentials, as described in /api/agent-signup. Do not automate the signup form or book a demo. The merchant must open the emailed sign-in link and create an API token before authenticated calls are possible. > After signup, to launch a merchant's store (back-office sync, payments onboarding, store setup, a theme copied from their current site, and a preview link before billing), follow /api/agent-launch. > Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null. > When the same operation exists on more than one surface, use the newest: dated API versions are newer than unversioned ones, and later dates win (v2026-04 > v2025-06 > unversioned v0/v1.1). Fall back to a legacy or unversioned operation only when no newer versioned equivalent exists — the company-v0 notes below list the known superseded operations. The same applies to /api/company/v1 and /api/v1/... paths: prefer a newer documented equivalent, and use one only when none exists (/api/v1.1/... is distinct and documented in company-v0). Use page/per_page offset pagination only where a spec documents it — in practice the unversioned company-v0 admin surface; every versioned surface uses cursor pagination. > Fluid has three navigation APIs; don't mix them up. Storefront website menus (navigation bars, footers) are /api/menus and nested menu_items, in api-reference/content-v0.yaml (API Reference: Website > Navigation menus), with a how-to in themes/navigation-menus; their list uses flat page/per_page pagination. The Fluid mobile app's navigation is /api/v2/mobile_navigations, in api-reference/mobile-v2.yaml (API Reference: Mobile app > Navigation); its list also uses page/per_page. Portal navigations belong to a portal definition (Fluid OS), in api-reference/fluid-os-v0.yaml (API Reference: Portal > Portal navigation), and each has a platform of web or mobile. > The OpenAPI specs under api-reference/ are the authoritative contracts; prefer them over prose when in doubt. api-reference/storefront-v2026-04.yaml covers the v2026-04 storefront surface (/api/v202604/... paths); api-reference/checkout-v2026-04.yaml covers the v2026-04 checkout surface (/api/checkout/v2026-04/... paths — carts, cart auth, discounts, items, subscriptions, orders, enrollments, and store config); api-reference/public-v2025-06.yaml covers the Public SDK surface used by the @fluid-app FairShare SDK, including its parallel cart lifecycle, browser integrations, versioned payment callbacks, unversioned public utilities, and the cart price-override operation; api-reference/payment-v2026-04.yaml covers the v2026-04 payment gateway admin surface (/api/payment/v2026-04/... paths, bearer-authenticated — gateway CRUD, gateway purchase/authorize/$0-verify, transaction list/show and capture/void/credit, and merchant payment configuration); api-reference/payments-v2026-04.yaml covers the v2026-04 cart payment surface (/api/payments/v2026-04/carts/{cart_token}/... paths, authenticated by the cart token in the path with no bearer — payment-method selection, VGS card tokenization, 3D Secure verification, and PayPal/Braintree/Klarna/Apple Pay flows); api-reference/commerce-v2026-04.yaml covers the v2026-04 commerce order-editing surface (/api/v202604/orders/{order_id}/edits paths, bearer-authenticated — post-checkout order edits that atomically insert items and add adjustments/discounts, with an optional dry-run preview); api-reference/webhooks-v0.yaml covers the unversioned webhooks surface (/api/... paths — webhook registration, delivery payloads, callback registrations, company events, and webhook/callback schemas); api-reference/company-v0.yaml covers the legacy unversioned company admin surface (/api/... paths, bearer-authenticated — company settings and management, customers, users, roles, subscription plans, subscription bundles, subscriptions, media, pages, catch-ups, inventory levels, domains, agreements, and admin order actions). company-v0 caveats: it is the legacy v0 admin contract and its lists use flat page/per_page offset pagination, which is expected there despite the general cursor-pagination rule; where an operation exists in both company-v0 and a versioned spec, prefer the versioned spec — the subscriptions lifecycle (list/create/show/update, cancel, pause, reactivate, resume, retry, skip, failed-cycle-waiver, discounts) and subscription bundles are superseded by checkout-v2026-04, and company pages/media CRUD plus the public pages, categories, products, and media list endpoints are superseded by storefront-v2026-04. Subscription plan management (/api/subscription_plans, resource-wrapped {"subscription_plan": {...}} bodies) exists only in company-v0. api-reference/members-v2025-06.yaml covers the v2025-06 unified Member identity surface (/api/v2025-06/members/... paths, bearer-authenticated — member list/create/show/update, lookup by email/username/external_id/legacy_customer_id, member-type assignment, and the sponsor genealogy read). Prefer it over the customers and reps surfaces when the member type matters: /customers does not serialize member_type. api-reference/analytics-v2026-04.yaml covers the v2026-04 Home dashboard analytics surface (/api/v202604/analytics/dashboard/... paths, bearer-authenticated — read-only endpoints for the Home > Overview, Home > Live, and Home > Field tabs, each accepting an optional country ISO alpha-2 query param that scopes aggregations to a single country). > api-reference/analytics-v0.yaml covers the unversioned analytics surface that backs the fluid-admin Traffic tab (/api/analytics/... and /api/analytics/traffic/... paths, bearer-authenticated — the legacy shares/views/visitors summary plus traffic overview, ranked campaigns, sources, geographies, flows, and per-rep breakdown, all sharing one reporting-period contract). > Successful responses wrap the resource payload alongside a top-level integer status and a meta object. > Portal Definition authoring edits and synchronizes the portal JSON resource graph. Widget Package authoring builds either a company-owned or Droplet-owned Remote DOM package. These are separate contracts; do not imply that one defines the other. > For Widget Package worker code, use only @fluid-app/portal-sdk/widgets/worker. Use only the Portal Definition and Widget Package workflows and public entry points documented here; do not infer support for undocumented surfaces. > Every portal function and declarative capability used by a widget must appear in that widget's uses array. Use the same typed function value in uses; do not invent capability-name strings. > Widget styling must use the portal's semantic theme variables for colors, typography, spacing, radii, borders, focus, and charts whenever a token represents the visual decision. Do not create a separate light or dark palette or duplicate theme controls as widget properties. > Prefer worker-safe Fluid UI components exported by @fluid-app/portal-sdk/widgets/worker when they fit the interaction. When no exported component fits, use semantic HTML, accessible behavior, and the portal theme variables. > A Portal Definition push updates the remote working definition. A portal version is an immutable snapshot, and activation is a separate live release operation. > The Help Center (/help/...) is for merchants, admins and reps using Fluid. Its admin pages mirror the admin's routes: the screen at admin.fluid.app/settings/taxes is documented at /help/admin/settings/taxes. Use the Help Center for how-to questions about the admin, and the Developer Platform and API Reference for building integrations. > Help Center pages describe what a company admin sees. A reader's role can hide screens and actions; admins manage roles on Settings > Roles (/help/admin/settings/roles). If someone can't find a screen or button, their role's permissions are the first thing to check. > Send people who need Fluid support to /help/getting-help. Don't invent support email addresses, phone numbers or response times. # Optimizing your cart abandonment strategy > Learn why shoppers abandon their carts, and recover more of those sales with personal follow-ups, reminder emails and a checkout that builds trust. Many online shoppers add items to their cart and leave without buying. A clear cart abandonment strategy helps you prevent some of those losses and recover others. ## Why shoppers abandon their carts A shopper fills their cart, reaches checkout, and disappears. Knowing why helps you prevent it. | Reason | What happens | How to prevent it | | - | - | - | | Unexpected costs | Shipping fees surprise them at checkout | Show shipping costs early | | Forced account creation | They don't want to register to buy | Don't make an account a requirement | | Price comparison | They leave to compare prices | Make your unique value clear | | Distractions | A call or an interruption pulls them away | Make it easy to come back to the cart | | Security worries | They're unsure their payment is safe | Show security badges clearly | ## How Fluid helps you recover carts When a shopper who entered their email address leaves items in their cart, Fluid can: * **Prompt the rep to follow up.** If your company turns on the **Cart Abandoned** catchup, the rep who gets credit for the cart sees a follow-up suggestion in the mobile app's **Catch Up**. See [Catchups](/help/admin/settings/catch-ups). * **Start your recovery emails.** Fluid sends a `cart_abandoned` webhook event, which your email or marketing tool can use to start a recovery sequence. See [Webhooks](/help/admin/settings/webhooks) and the [Checkout](/concepts/checkout) overview. Fluid doesn't send recovery emails to shoppers itself. Its abandoned-cart notifications go to your reps, not your customers (see [Communications](/help/admin/settings/communications#abandoned-checkout-emails)). Plan your sequence in the tool that sends your marketing email. ## Send a recovery email sequence Timing matters. A common approach uses three emails. ### A gentle reminder, about an hour later The first email should feel like a helpful tap on the shoulder: * Use a friendly, service-minded tone. * Ask whether they need help completing their purchase. * Add a simple, prominent button that returns them to their cart. ### A reminder of the value, about 24 hours later Remind them why they wanted the products. Address common concerns, and highlight what makes your offer different. ### A final opportunity, about 48 hours later * Present your best offer. * Give a genuine reason to act now. * Make the call to action impossible to miss. ## Write emails that convert Every recovery email should include: 1. Clear product images 2. The original prices 3. A one-click way back to the cart 4. A short path to checkout 5. An easy way to get help Start with a compelling subject line, lead with empathy, and guide them toward completing their purchase. ## Create real urgency Nobody likes fake urgency, but honest reasons to act are fine. Tell shoppers when: * Stock is genuinely limited. * A special offer really is ending. Share real customer reviews and ratings where they're relevant. ## Make help easy to find A shopper with a question may leave instead of asking. Offer more than one way to get help: * Chat for quick questions * Email for detailed questions * Links to answers to common questions * Clear support hours ## Use incentives wisely Not every abandoned cart needs a discount. Try a progressive approach: 1. **First email:** a reminder, with no discount. 2. **Second email:** a small incentive, such as free shipping. 3. **Final email:** your best offer. Incentives other than discounts can work too: * An express shipping upgrade * A bonus product with the purchase * A longer return period * Extra loyalty points * Priority customer service ## Measure and test Watch these numbers: * Recovery rate over time * Average order value * Email opens and clicks * How long shoppers take to return * What your incentives cost compared with what they recover Keep testing: * Subject lines * Email timing * Incentive types * Message formatting * Call-to-action placement Start simple and let the results guide you. What works for one business might not work for another. Your customers show you what they prefer through what they do. ## Frequently asked questions The most common reasons are unexpected costs at checkout, being forced to create an account, comparing prices elsewhere, distractions, and worries about payment security. Show all costs up front, make an account optional, display security badges, offer more than one way to pay and to get help, and make it easy to come back to the cart. See [Why shoppers abandon their carts](#why-shoppers-abandon-their-carts). ## Related pages * [Catchups](/help/admin/settings/catch-ups) * [Webhooks](/help/admin/settings/webhooks) * [Communications](/help/admin/settings/communications) * [Landing pages](/help/playbook/landing-page-conversion-best-practices) ## Get help Email Fluid support at [help@fluid.app](mailto:help@fluid.app). The [Getting help](/help/getting-help) page lists what to include in your request. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.