Start building

Last updated

Build and review a COD form

Releasit COD Form & Upsells

Build and review a COD form

Releasit COD Form & Upsells is a native CartWhizz addon. It is disabled by default. It does not connect to a Releasit account or assert an official provider affiliation. Enable it for a store only when its COD shipping and payment rules are ready.

Create the form

Open Releasit COD → Create form. Set an internal name, customer title, button label and optional description. Choose Popup for an opening button, or Embedded for an inline product-page form. Leave the form in Draft while configuring it.

Leave the product scope empty for every eligible physical product, or search and add specific products. Stock, product options and variant requirements are validated by the normal checkout service. Existing Add to Cart and checkout actions remain available.

Customize field labels and optional address details. Full name, real email, phone, street, city, postal code and country are required for delivery and the store's checkout policy. The postal-code, country, state and city controls remain grouped for consistent address entry. The store's email-verification policy still applies. Optional terms require an unchecked, explicit acceptance.

Set the form to Published and save when ready. Publishing a form does not enable the addon. Disabling the addon hides its placements and blocks new addon checkout requests.

Optional offers

Use Add offer to select an exact product, variant, quantity and percentage discount. Give the offer a clear name that describes the item and variant. Every offer starts unchecked; customers choose extra items and then review the server-calculated total.

  • Pre-purchase and One-tick offers are optional choices before confirmation.
  • Downsell appears after the shopper explicitly declines its configured parent offer.
  • Quantity becomes eligible when the main product meets its minimum quantity.
  • Post-purchase appears after a successful order. Choosing it begins a separate follow-up COD order. The shopper must review its own items, shipping, tax and total and explicitly confirm it. The original order is already confirmed and is not modified.

Enable A/B assignment and choose A, B or both for each offer. The server assigns an intent to one group and keeps that assignment for its lifetime. Results compares started intents, placed COD orders and order value. These metrics measure order placement; they do not represent collected cash or statistical certainty.

Review and currency

A shopper starts the form, enters delivery details, chooses optional offers and requests a review. CartWhizz calculates prices, discounts, tax, available shipping and COD eligibility. Changing details or offer selections requires a fresh review. Price changes may also require refreshing the quote before confirmation. Retrying the same order submission reuses its server result.

The final confirmation displays the actual amount and store collection currency. A selected local display currency is only an estimate; COD is collected in the store's primary currency. CartWhizz stores money with a fixed two-place storage scale and uses each currency's display precision when formatting it.

A private checkout capability stays in browser memory and is sent in a request header. Closing the popup or reloading discards the capability; it is never placed in a URL or browser storage. The optional hosted handoff route is /releasit/FORM_ID?product_id=PRODUCT_ID and accepts variation_id, unified_variation_id and quantity for a selected item. Choose all required product options before starting.

Verification, postal rules and notifications

Phone OTP requires the existing OTP addon plus a working SMS or WhatsApp delivery route. Enable Require phone verification only after configuring that route. The customer requests and verifies a code during order review. Changing the phone or delivery address invalidates phone verification; a follow-up order uses a fresh verification scope. Email verification follows the store's existing checkout policy independently.

Postal allowlists and blocklists use one COUNTRY:PREFIX per line, such as US:90 or GB:SW. Empty allowlists permit every area otherwise supported by checkout. IP restrictions accept exact addresses or CIDR ranges, one per line. Server validation remains authoritative.

Order confirmations and abandoned-checkout recovery use the existing enabled CartWhizz notification and recovery facilities and configured delivery providers. Configure those settings separately; this addon does not create provider credentials or start an additional recovery campaign.

Google Sheets

Create a merchant-owned Google service account with Sheets API access. Create a spreadsheet and a dedicated empty tab, then share the spreadsheet as Editor with the service-account email.

In Integrations, enter the spreadsheet ID, tab name and service-account JSON. The JSON is encrypted at rest and never returned to the editor. Leave the credential input blank to keep saved credentials; use the explicit remove switch to clear them. Saving a new destination or credentials requires another access check.

Review and explicitly allow exporting COD order items, totals, customer contact information and delivery addresses to that spreadsheet. Save settings, then select Check Google access. This check reads metadata and the dedicated tab; it does not write order data. After enabling sync, consenting and passing the check, the worker initializes managed headers and exports placed COD orders to deterministic managed rows. Other tabs are not used. Failed rows can be queued again with Retry failed exports once the connection is ready.

Use a dedicated tab exclusively for this integration. Existing unrelated data is rejected. No Google credentials or spreadsheet are supplied by CartWhizz. See Google service-account guidance and the Sheets API.

Google address suggestions

Configure a merchant-owned browser API key with Maps JavaScript and Places access, billing, and HTTP-referrer restrictions for the storefront origins. This key is intentionally public. The new Place Autocomplete widget supports current Google projects; legacy Autocomplete is not available to new customers. The SDK loads only after the customer selects Use Google address suggestions. Selected address components fill the normal address controls. Manual entry remains available if suggestions fail or are not configured. See Google's current autocomplete documentation.

Marketing tracking

Meta Pixel, GA4, Google Ads and GTM use their existing store configuration. The additional TikTok, Pinterest and Snapchat switches require valid merchant-owned public pixel IDs. Their fixed vendor SDKs load only when the network is configured and enabled and the store's consent rules allow marketing tracking. Contact and address details are not included in the addon pixel events.

Checkout and purchase events use the actual server quote/order totals and primary collection currency, never a local estimate. Purchase here means a COD order was placed, not that cash was received. Meta's count COD on delivery policy remains authoritative; when enabled or unavailable, the addon does not emit a browser Meta Purchase. Normal canonical event IDs and order deduplication are retained.

TikTok uses current InitiateCheckout and Purchase events; Pinterest uses InitiateCheckout and checkout; Snap uses START_CHECKOUT and PURCHASE. Pinterest’s published Tag currency list contains USD, GBP, CAD, EUR, AUD and NZD. Its money events are skipped for other collection currencies, with an admin warning; other configured networks retain the actual store currency. Check each network's supported currencies and event diagnostics after configuring a test environment. See TikTok standard events, Pinterest tag documentation and Snap Pixel installation.

Changing consent prevents subsequent addon pixel event calls. A vendor script already loaded in the current page cannot be removed from the browser runtime; use the store's consent controls and vendor settings for their broader cookie behavior.

Permissions

Forms can be read with View settings or Manage settings. Form changes and integrations require Manage settings. Results require View orders or Manage orders. The addon module and entitlement gate apply on both admin and storefront APIs. Provider checks require actual merchant configuration; an unconfigured integration is not connected or tested.

Mobile apps

The admin app lists forms and results according to the same permissions. Open the same-store web editor to change forms and integrations. The buyer product app opens the hosted COD review in the browser with the selected unified variant and quantity. Products with custom options or unresolved legacy variants open the product page first so the shopper can complete its selections.

App sign-in is not transferred to the browser. Signed-in app shoppers are asked to use the same account in the browser before confirming so account-specific eligibility is preserved. Links contain product selections only; no access token or checkout capability is transferred. The private checkout capability is created in browser memory.