What Are Customer Generated Offers? The Negotiated Commerce Primer.
Chris Daly, Founder, I Want That! | 25 years in retail, worked with 40+ ecommerce brands.
Every year, 65% of shopping carts worth over $4 trillion are abandoned e-commerce globally. Merchants respond with exit intent popups, retargeting ads, and email sequences offering 10% off. The customer already told you what they wanted to do. They wanted to negotiate. You gave them a coupon code instead.
The most expensive thing in ecommerce is a customer who wanted to make a deal and found a store that wouldn't.
What Customer Generated Offers Are
Customer Generated Offers (CGOs) are offers that a customer initiates to purchase from your business. In digital commerce, a CGO may be an offer on an abandoned cart, a product page, a clearance item, or as the normal course of buying from your store. The customer names a price, or proposes terms and the merchant decides to approve, decline, or counter. CGOs are not a discount mechanism. They are a negotiation infrastructure that reveals true willingness to pay at the individual customer level and enables merchants to close transactions that fixed pricing cannot.
How Customer Generated Offers Work
CGO infrastructure has four components. All four must work together for the system to function at scale.
Points of Engagement are where the customer initiates the offer. Before purchase — on a product page before adding to cart — or during purchase, after a product is in the cart. Before-purchase CGOs typically require manual handling at most merchants today; during-purchase CGOs are where automation creates scale.
Points of Processing are the decisioning layer. Every incoming offer receives one of three outcomes: approval, decline, or counter offer. Automation handles all three against your defined BATNA (Best Alternative to a Negotiated Agreement).
Approvals fire when the offer lands within your maintained markup (MMU) target. Declines fire when the offer is so far outside your MMU that the path to agreement is not realistic — but a decline is never a hard no. It is a "that discount is outside our range; feel free to make another offer." That response captures what the customer was willing to pay, which is valuable data regardless of outcome.
Counter offers are where the system earns its margin. The counter mechanics include incremental units at the offered discount, bundle additions that justify the discount, bounce-back offers that apply the savings to a second purchase, and shipping concessions. Every lever your pricing already built in becomes a counter offer tool.
Consumer-Facing Pricing is the analytical foundation. Most retail pricing is product-facing cost plus margin plus allowances equals selling price, full stop. CGO pricing adds the customer dimension: what does your portfolio data tell you different customers actually pay for this product? AOV, AUR, and discount rate by customer segment inform what offers to accept, counter, and decline before a single offer comes in.
Financial Goal Setting closes the loop. MMU targets, contribution margin floors, and weekly revenue goals by portfolio segment define your BATNA for every product and every customer type. Without defined financial goals, CGO processing becomes reactive. With them, it becomes a system.
Why Customer Generated Offers Matter Now
Fixed-price commerce was built for mass production and mass distribution, a world where a merchant could say "here is the product and here is the price, take it or leave it." The economics of that model assumed the customer's BATNA was to not buy at all or to buy from a competitor at a similar fixed price.
That assumption is gone. The customer's BATNA now includes AI buying agents constructing offers across multiple merchants simultaneously, marketplace alternatives with immediate price transparency, and a generation of buyers who negotiated for everything from cars to concert tickets and see no reason their online shopping should be different.
The infrastructure gap is closing. The merchant mindset gap is not. The myth that customer generated offers cheapen a brand persists despite being mathematically wrong. IMU pricing already bakes discounts into the selling price. There is no difference between a merchant offering 30% off and a customer asking for 30% off. The only difference is who initiates, and one of those options reveals what the customer actually values.
How Customer Generated Offers Differ from Discount Codes
Discount codes are merchant-initiated, uniform, and margin-blind. A 20% off code applies to every customer equally regardless of their willingness to pay, their portfolio value, or whether they needed the discount to convert. They train customers to wait for sales, anchor expectations to the discounted price, and surrender margin to customers who would have bought at full price anyway.
CGOs are customer-initiated, individual, and margin-aware. A customer making an offer reveals their actual price point. A merchant countering that offer against an MMU floor retains margin that a blanket code would have given away. A customer who negotiated a deal feels ownership over the transaction in a way that a coupon code never produces, and that emotional ownership drives repeat purchase and referral behavior that discounts do not.
How to Apply Customer Generated Offers to Your Store
- Set your BATNA before you accept a single offer. Know your MMU target for each product or category. Know the contribution margin floor below which a transaction does not serve the business. These numbers define what the system can approve, counter, and decline automatically.
- Map your customer portfolio to offer strategy.
- New customers need basket formation –\> incremental unit counters that build AOV.
- Declining customers need repeat purchase —\> more generous acceptance thresholds to restore cadence.
- Reactivated customers are fully amortized —\> counter harder and protect margin.
- Defected customers represent 100% incremental revenue —\> aggressive re-entry offers are justified.
One offer policy for all six portfolio segments is the same mistake as one discount code for all customers. Customer generated offers solve the last leg of personalization, the deal itself.
- Automate the decisioning layer. Manual CGO processing does not scale. The system approves offers within MMU automatically, fires counter offers against pre-set levers, and declines outliers with a response that keeps the door open and captures the data. The customer gets a response in seconds. The merchant retains margin without a human in the loop.
The Bryden Road Case Study
Bryden Road had 4,000 pre-lit Christmas trees to move. The trees were a category favorite for Stable and Defected customers. Rather than markdown the inventory, they ran a CGO campaign targeting Q1 and Q2 Defected customers from the prior fiscal year.
Audience: 28,000 email, 2,000 direct mail. Offer: Make Us An Offer We Cannot Refuse. Target MMU: 75%. Target Response: 1.5%.
Results: 2.4% response rate with a customer-yield of 672 buyers. AOV of $565.42. Discount rate of 29.6%. MMU of 78.1%, well above target. The campaign reactivated 672 defected buyers at a margin that exceeded the goal, on inventory that would otherwise have gone to clearance at a lower MMU.
The markdown alternative would have moved the same inventory at a lower margin to customers who did not need the negotiation to convert. The CGO campaign moved it at a higher margin to customers whose return to the brand was worth more than the transaction.
FAQ
What are customer generated offers in ecommerce? Customer Generated Offers (CGOs) are offers that a buyer initiates to purchase from a merchant on a product, a cart, or a category. The merchant responds with an approval, decline, or counter offer. Unlike blanket discount codes, CGOs reveal each customer's true willingness to pay, enable margin-aware decisioning, and create the negotiated transaction experience that builds stronger customer relationships than fixed-price commerce can.
Are customer generated offers the same as make-an-offer buttons? A make-a-deal button is the customer-facing entry point for a CGO, the interface where the offer is submitted. The CGO system is everything behind it: the BATNA logic, the approval and decline thresholds, the counter offer mechanics, the portfolio-aware pricing, and the financial goal structure that determines what the system does with each incoming offer. The button is the door. The CGO infrastructure is the building.
Do customer generated offers hurt brand perception? No. The math explains why. IMU pricing already includes discounts as a line item in the selling price. A merchant who prices at $279 from a $100 cost has already allocated room to negotiate. A customer asking for 30% off is operating within the margin structure the merchant already built. What CGOs change is who initiates and a customer who negotiated a deal has more emotional ownership over the purchase, higher satisfaction, and stronger repeat purchase intent than one who used a coupon code.
How do you automate customer generated offer responses? Automation requires three inputs: an MMU floor for each product or category, a set of counter offer levers (incremental units, bundles, bounce-backs, shipping), and a decline threshold below which the margin gap is too large to bridge. With those inputs defined, the system approves offers within the floor automatically, fires the appropriate counter offer lever for near-misses, and declines outliers with a response that captures the customer's price point data and keeps the conversation open.
How do customer generated offers connect to customer portfolio management? Portfolio classification: New, Growth, Stable, Declining, Reactivated, Defected determines the right CGO strategy for each customer. New customers need incremental unit counters to build basket behavior. Declining customers need lower friction acceptance to restore purchase cadence. Reactivated customers are amortized acquisition costs, counter harder. Defected customers represent 100% incremental revenue, aggressive re-entry offers are justified. The portfolio is the context. The CGO is the instrument.
What is BATNA in the context of customer generated offers? BATNA stands for Best Alternative to a Negotiated Agreement, the point below which a merchant is better off not making the deal. In CGO management, BATNA is defined by your MMU target and contribution margin floor. An offer that lands above your BATNA gets approved or countered toward closure. An offer that lands below it gets declined, not as a hard rejection but as an opening for a revised offer. Knowing your BATNA before processing begins is what separates margin-aware CGO management from reactive discounting.
Which Shopify stores benefit most from customer generated offers? Any store with meaningful inventory exposure, customer repeat purchase potential, or cart abandonment above 60% benefits from CGO infrastructure. Stores with product margins that support a negotiation range like apparel, home goods, jewelry, furniture, specialty retail all see the strongest results. Commodity products with thin margins and no negotiation room are the exception. If your IMU pricing includes a discount allowance, you already have the margin architecture for CGOs. The question is whether you are activating it or leaving it on the table.
Start building your CGO infrastructure, see how the negotiation space in your current pricing maps to your customer portfolio →
Codex handoff notes:
- This is a migrated post — original publish date 2023-08-19, preserve in frontmatter for authority signal
- 301 redirect required:
https://iwantthat.io/how-to-use-customer-generated-offers-to-power-commerce/→https://useiwantthat.com/blog/what-are-customer-generated-offers - Canonical tag on new URL must point to itself:
https://useiwantthat.com/blog/what-are-customer-generated-offers - Submit to Search Console immediately on go-live
- External citation slot: $4 trillion abandoned cart stat — source and link needed, flag for Codex
- Sibling links: /blog/dtc-playbook-broken, /blog/agentic-commerce-offer-layer, /blog/six-customer-portfolios-framework
- Hub confirmation: /negotiated-commerce
- Image: replace old WordPress DALL-E image with new pillar OG image at /images/blog/what-are-customer-generated-offers-hero.png
- Asset cut: the BATNA diagram from the original post — recreate as a clean SVG in brand colors and commit to repo. Best LinkedIn asset from this post.
- FAQ schema: true — 7 entries
- sitemapPriority: 0.9 — this is the definitional anchor for the Negotiated Commerce pillar