Use a make-an-offer workflow when the commercial problem is specifically negotiable price. Use conditional purchase when the shopper may be blocked by price, stock or variant, delivery, assurance, service, payment or procurement, or a product question and the merchant needs one controlled decision and evidence model. In either case, keep normal full-price checkout primary and make accepted terms private, explicit, expiring, customer-bound, product-bound, quantity-bound, revocable, and live-validated before Shopify checkout.
- Make-an-offer is a price workflow; conditional purchase is a wider condition model.
- Public or unlimited negotiation can train price-seeking behavior.
- Unknown margin, inventory, currency, identity, or compatibility should fail closed.
- An accepted request still requires explicit Shopify checkout and payment.
Diagnose the revenue constraint before choosing a tactic
Determine whether price is actually the recurring blocker and whether the catalog economics and positioning support negotiation. Review gross margin inputs, fees, discount combinations, inventory age, market and currency behavior, quantity, customer eligibility, frequency, and cannibalization risk. If shoppers are also asking for unavailable variants, need-by dates, assurances, services, payment methods, or product answers, a price-only workflow will fragment the evidence and may offer a discount when another fix would have preserved more margin.
Treat profitable sales as a system: qualified traffic multiplied by conversion, order value, repeat behavior, and contribution margin. A tactic that raises one number while damaging another is not durable growth. Segment the evidence by product, variant, device, market, new versus returning customer, and purchase stage before deciding what to change.
A practical merchant playbook
Define eligibility before adding a button. Keep the standard Add to cart path visually primary, state that a request is not a guarantee, capture the exact customer and product context, require merchant approval by default, and show the customer the exact accepted terms and expiry. Generate checkout only after live price, cost, stock, market, currency, identity, quantity, and active-rule validation. Revoke or expire terms without rewriting the decision history.
- Choose price-only negotiation or a broader condition workflow intentionally.
- Set margin, quantity, currency, market, frequency, and compatibility guardrails.
- Bind private terms to one customer and exact merchandise.
- Revalidate live Shopify state before checkout opens.
- Measure paid and refund-adjusted outcomes plus full-price cannibalization.
Where BuyWhen fits—and where it does not
BuyWhen is broader than a make-an-offer widget: it keeps price, stock or variant, delivery, assurance, service, payment or procurement, and product-question conditions in one merchant-controlled Live Order Book. Price and delivery commitments are manually approved by default. A merchant that only wants automatic price haggling with no broader evidence workflow may prefer a narrower product.
BuyWhen is most relevant when a shopper has purchase intent but one explicit active condition is unresolved: price, stock or variant, delivery, assurance, service, payment or procurement, or a product question. Bundle and custom activation remain future-gated. It does not replace acquisition, storefront quality, checkout, customer service, or a sound product.
Measure the change without overstating the result
Measure eligible views, request rate, target-price distribution, qualification, accept and counter rates, response time, checkout, paid orders, net sales, margin, refunds, expiry, abuse, repeat negotiation, and full-price conversion. Use a control or staged rollout before claiming incremental revenue.
Record the full path from eligible shopper to request, qualification, merchant decision, offer, checkout, paid order, refund, and cancellation. Report potential demand, attributed paid sales, net sales, and experimentally estimated lift as separate measures. Document the window and exclusions so a useful signal never becomes an unsupported revenue claim.
Frequently asked questions
Can a Shopify shopper name their own price?
An app can collect a target price, but the merchant should decide whether it is eligible. The request itself must not change price or create a charge, and accepted terms should return through an explicit Shopify checkout.
Does BuyWhen automatically accept every profitable offer?
No. Manual approval is the default for price commitments, and unknown cost, fees, inventory, currency, market, identity, discount compatibility, quantity, or rules fail closed.
When is a make-an-offer app the simpler choice?
It can be simpler when price is the only intended negotiation, the eligible catalog is narrow, and the merchant does not need a unified workflow for other purchase conditions.
Sources and further reading
Product guidance is grounded in BuyWhen's documented behavior. The broader commerce and search principles in this guide also reference these primary sources: