Straight answers for Shopify merchants.

YieldCart is a Shopify revenue workspace for margin-aware gifts and cart offers, BuyWhen shopper recovery, and evidence-led analytics. It guides merchants from private configuration through preview and activation while keeping modeled opportunities, paid orders, refunds, and retained outcomes distinct.

BuyWhen is YieldCart's shopper-recovery feature. It connects one purchase blocker to a safe path back to checkout. For example, a shopper can say they will buy a sofa if it arrives before Friday. The condition stays linked to the shopper, sofa configuration, readiness, and deadline; the merchant can confirm a qualified delivery option; and BuyWhen can return the shopper to Shopify checkout and track the order or refund outcome.

A contact form or inbox captures text and leaves the commercial outcome unclear. BuyWhen keeps a structured buying condition connected to the shopper, product or cart, readiness, deadline, merchant resolution, checkout, order, cancellation, and refund outcome.

Not primarily. Reminder apps react to a cart or checkout that was left behind. BuyWhen captures the specific condition blocking a purchase, helps the merchant resolve that condition, and returns the shopper to checkout when the response is feasible.

No. Price is only one possible buying condition or merchant response, and price commitments require merchant control and live safety checks. Delivery, availability, fit, compatibility, product assurance, service, procurement, and other non-discount resolutions can come first.

On an eligible product page, the shopper sees a contextual BuyWhen action and focused condition choices for that product. They provide the required details, see a plain-language summary of what BuyWhen understood, and review or edit the condition before submitting it.

BuyWhen records the exact merchant response, prepares customer-bound and expiring terms, and revalidates live Shopify state before opening checkout. It then links the condition to checkout, paid order, cancellation, refund, and retained outcome evidence where available.

Shoppers can review and edit a condition before submission. After submission, supported shopper controls let them withdraw the request or revoke optional communication choices; a merchant can also decline or revoke an active response. Already-recorded evidence is retained as an append-only audit history.

No. BuyWhen does not silently change a product's public storefront price. When a merchant approves private price terms, those terms stay customer-, product-, quantity-, currency-, and expiry-bound and are revalidated before Shopify checkout.

It is the merchant's tenant-scoped queue of conditional purchase requests, including product context, potential value, commitment, confidence, expiry, ownership, evidence, and decision history.

Price, exact stock or variant, need-by delivery date, and a purchase-blocking question. Bundle and custom/quote activation are intentionally coming later.

No. Requests and offers remain private between the shopper and the merchant. BuyWhen does not publish bids or create cross-merchant exchanges.

No, unless the merchant explicitly communicates a time-bounded reservation. Otherwise inventory is checked again before checkout.

No. BuyWhen does not silently retain and charge an ordinary card. The shopper explicitly reviews terms and completes payment in Shopify checkout.

Manual approval is the default. A decision checks exact currency, cost and margin evidence, inventory, quantity, identity, discount compatibility, market, and active hard rules.

The workflow fails closed: it stays waiting, requires manual review, or offers a safe next action instead of creating a commercial promise.

Each offer has an explicit expiry chosen under merchant policy. It can also be revoked, and every open performs live revalidation.

Public-price terms can use a Shopify Storefront Cart. Approved private-price terms can use a Shopify Draft Order. Taxes, shipping, duties, and payment stay in Shopify.

A durable evidence chain links the request, decision, offer, checkout, and paid order. Refunds and cancellations append negative corrections instead of erasing history.

It supports deterministic treatment and holdout assignment, attribution windows, minimum-sample warnings, and separate treatment and holdout reporting. Attributed sales are never automatically labelled incremental.

Only data needed for the enabled request and its lifecycle, such as product context, condition, contact channel, consent, and limited order evidence. Direct identifiers are encrypted.

No. Transactional permission for request updates and optional marketing consent are separate. Marketing is never preselected.

English, French, German, and Spanish are supported across contracted customer-facing request, offer, portal, email, and checkout-validation surfaces.

Yes. BuyWhen includes merchant roles, store invitations, organization views, and an OIDC SSO foundation with domain enforcement and audited sessions.

Processing stops, sessions are removed, active offers are revoked, and retention-aware cleanup begins while required billing and audit evidence follows documented policy.

The product includes tested provider contracts and guarded adapters. Paid external providers remain visibly Coming soon until credentials, budgets, and provider-specific acceptance are complete.