Skip to main content

Checkout Integration SOP

This document outlines the configuration and management of Checkout integrations. These integrations are the backbone of our conversion optimization tools, specifically driving the automated recovery of lost sales.


1️⃣ Overview​

Scope​

This SOP covers the integration of third-party checkout accelerators and cart management tools with the BusinessOnBot (BoB) ecosystem.

Objectives​

  • Recover Lost Revenue: Systematically target users who leave the purchase journey.
  • Streamline Cart Sync: Ensure real-time data flow between the checkout partner and the messaging engine.
  • Onboarding Accuracy: Correctly configuring webhooks to avoid duplicate or missed notifications.

2️⃣ Checkout Integration Details​

a. Purpose of Checkout Integration​

The sole purpose of integrating checkout partners into BoB is to facilitate Abandoned Cart Messaging.

  • When a user drops off at the checkout page, the integration captures the cart metadata (products, price, user details).
  • BoB then triggers a WhatsApp/Instagram nudge to recover the sale.
  • Note: There are currently no other use cases for these integrations beyond recovery logic.

b. Supported Checkout Partners​

We support the following primary partners:

  • Shopify (Default native integration)
  • GoKwik
  • Cashfree Checkout
  • Shiprocket Checkout
  • Shop Flow
  • Magic

c. Standard Checkout Flow​

  1. The Cart: The checkout partner replaces the default storefront cart.
  2. The Payload: Once a user enters their phone number/email and exits, the partner sends the "Abandoned Cart" payload.
  3. The Gateway: If the user continues, the payment is handled by a gateway (Razorpay/PayU).

3️⃣ Partner-Specific Configurations​

a. Shopify-Based Integrations (GoKwik, Shop Flow, Magic)​

Partners like GoKwik, Shop Flow, and Magic are deeply integrated with the Shopify ecosystem.

  • Logic: These tools push abandoned cart data directly into the merchant's Shopify "Abandoned Checkouts" section.
  • Integration Rule: Because BoB already listens to the Shopify API, no separate integration is required in our dashboard for these partners. As long as Shopify is connected, BoB will capture the data they push.

b. Shiprocket (Fastrr) Checkout Integration​

Unlike the partners listed above, Shiprocket (Fastrr) Checkout requires a manual webhook-based setup. This is because Shiprocket (Fastrr) does not push checkout or cart data to Shopify in a way that BusinessOnBot (BoB) can natively detect.


⚙️ Step-by-Step Configuration​

1️⃣ Webhook Access​

Log in to the Shiprocket (Fastrr) Dashboard and navigate to: Settings → Webhooks

2️⃣ Trigger Selection​
  • Trigger: Select the Abandoned Cart event.
  • Timing: Set the trigger time to exactly 10 minutes. This allows sufficient time for customers to complete their order naturally before being marked as abandoned.
3️⃣ Additional Info Configuration​

In the Additional Info section of the webhook, configure the following key-value pair:

KeyValue
Endpointhttps://(client_id).bobot.in/abancart
Mandatory Action

Ensure the (client_id) is replaced with the actual merchant identifier while configuring the webhook.

4️⃣ Dashboard Switch​

In the BoB Admin Panel, you must perform the following:

  1. Go to Checkout Settings.
  2. Manually change the checkout partner from Shopify → Shiprocket (Fastrr).

Reference Screenshot​

The image below shows the Webhook configuration screen in the Shiprocket (Fastrr) dashboard for reference:

Shiprocket (Fastrr) Webhook Configuration


✅ Important Notes​

  • Trigger Check: Only the Abandoned Cart trigger should be enabled to avoid data noise.
  • Status: Ensure the webhook is marked as Active and saved successfully.
  • Accuracy: Any misconfiguration in the endpoint URL or trigger timing will result in cart drop-off automation failures.

Support & Escalations​

If the webhook pings are not being recorded in the BoB dashboard after configuration, please raise a CRB with the client's Shiprocket credentials for a technical audit.

4️⃣ Security & Best Practices​

  • Webhook Health: Periodically check the Shiprocket Webhook logs to ensure a "200 OK" status is being returned.
  • Partner Switching: Never switch the internal dashboard partner (e.g., Shopify to Shiprocket) without first confirming the webhooks are active, as this will stop all recovery messages.
  • Data Integrity: Ensure the checkout partner is capturing the Country Code; otherwise, WhatsApp messages will fail to deliver.

5️⃣ Action Items​

  • Identify if the partner is Shopify-native (GoKwik/Magic) or requires a Webhook (Shiprocket).
  • For Shiprocket: Configure the Webhook with a 10-minute trigger delay.
  • Update the internal BoB dashboard to reflect the correct Checkout Partner.
  • Test the flow by intentionally abandoning a cart on the merchant's site.

Was this page helpful?