WooCommerce Buy X Get Y: Same-Product vs. Cross-Product BOGO

Most store owners think of BOGO as a single thing: “buy one, get one.” In practice there are two quite different structures that both go by that name, and conflating them causes real problems at configuration time.

The first structure — same-product BOGO — is about quantity. A customer buys two units of one product and the second unit is discounted. The buy and the get come from the same product pool. The second structure — cross-product Buy X Get Y — is about pairing. A customer buys a defined set of “buy” products and gets a different defined set of “get” products at a discount. The buy and the get are explicitly separate.

Same-product BOGO has been the standard interpretation in most WooCommerce plugins for years. Cross-product Buy X Get Y requires a more sophisticated discount engine because it needs to evaluate two independent product pools simultaneously. Smart Cycle Discounts treats them as distinct discount types — same-product BOGO in the free tier, cross-product Buy X Get Y in Pro. This guide covers what each one is, when each one makes sense, and what to watch out for when setting them up.

What same-product BOGO actually is

Same-product BOGO is the classic “buy two of something, get one cheaper” deal. The qualifying products for the “buy” side and the discounted products for the “get” side come from the same eligible pool. When a customer adds enough units of a qualifying product, the discount fires on the additional units.

In Smart Cycle Discounts, same-product BOGO is configured with three values:

• Buy quantity — how many units the customer needs to add before the discount applies
• Get quantity — how many units get discounted once the threshold is reached
• Discount percentage — what percentage comes off the “get” units, from 1% to 100%

A classic Buy One Get One Free is buy quantity 1, get quantity 1, discount 100%. A Buy Two Get One Free is buy quantity 2, get quantity 1, discount 100%. You can also do partial discounts: buy quantity 2, get quantity 1, discount 50% gives you one unit at half price after every two full-price units.

The mechanics operate entirely within a single product scope. The campaign can apply to all products, a specific list of products, or a category. But the buy units and the get units always come from the same qualifying pool — there’s no concept of a separate “get” product list.

What cross-product BOGO (Buy X Get Y) actually is

Cross-product Buy X Get Y is a structurally different mechanism. Instead of working within a single product pool, it maintains two separate product pools — a “buy” pool and a “get” pool — and evaluates them independently. A customer must meet a minimum quantity threshold from the buy products before the discount applies to items from the get products.

In Smart Cycle Discounts, the cross-product Buy X Get Y strategy (available in Pro, introduced in version 1.9.0) is configured with six values:

• Buy product IDs — the specific products (or variations) the customer must purchase
• Buy quantity — how many buy-side units are required to trigger the deal
• Get product IDs — the specific products (or variations) that will be discounted
• Get quantity — how many get-side units receive the discount
• Discount percentage — the percentage off the qualifying get-side units
• Get discount target — whether the discount applies to the cheapest or most expensive matching get-side items (by price rank)

There is also an optional max applications cap, which limits the number of times the deal fires per cart. Without a cap, a customer who adds ten buy-side units could trigger the deal multiple times if they also have enough get-side units. The cap lets you bound that exposure.

Side-by-side comparison

When to use same-product BOGO

Same-product BOGO earns its place when you want to move more units of a single product — or a category of similar products — and the customer’s incentive is to stock up rather than to discover something new.

Consumables and replenishables

Coffee beans, protein powder, skincare, cleaning products, pet food — anything a customer uses regularly and will eventually need more of. When a customer leaves with four bags instead of two, they’re not buying from a competitor for twice as long. Same-product BOGO is one of the cleanest retention tools in a consumables store because the margin cost is real but so is the loyalty value. The customer feels like they got a deal; you extended the repurchase window.

Inventory clearance on a specific SKU

If you need to move a specific product fast — approaching end-of-season, excess stock, a new version incoming — same-product BOGO lets you apply the deal to a fixed product list rather than your whole catalog. Set the buy and get quantities, run it for two weeks, and let it expire automatically. The deal is targeted; it doesn’t accidentally discount everything.

Simple social-sharing moments

The phrase “buy one get one free” is memorable and shareable in a way that “buy product A and get product B at a discount” rarely is. If word of mouth matters for your store, a clearly-stated same-product BOGO on a popular product is a stronger signal to share. The psychology of “free” removes hesitation in a way that percentage discounts don’t — though that same psychology can anchor expectations if you run the deal too often. The full treatment of when BOGO free outperforms 50% off is covered in the guide on Smart Cycle Discounts’ BOGO capabilities.

When to use cross-product Buy X Get Y

Cross-product Buy X Get Y is a cross-selling tool. Its defining characteristic is that the buy products and the get products are different. You’re using a product the customer already wants as leverage to get a different product into their cart at a reduced price.

Product discovery for items that don’t sell on their own

This is the strongest case for cross-product Buy X Get Y. You have a product that gets overlooked because customers don’t search for it directly — a complementary accessory, a newer model of something, a product that requires the customer to already know why they need it. Pairing it as the “get” product against a bestselling “buy” product gives it a runway it wouldn’t otherwise have. The popular product does the traffic acquisition; the overlooked product gets the trial.

Accessories and complementary pairings

A camera and a memory card. A skincare cleanser and a matching toner. A pair of running shoes and a set of insoles. These are product pairings that make intuitive sense to the customer and that benefit your AOV because the get-side product has meaningful margin. Cross-product Buy X Get Y is the natural structure here because you want the discount to be specific and intentional — “buy the main product, get the accessory cheaper” — not a general volume deal.

Choosing cheapest vs. most expensive on the get side

The get discount target setting — cheapest or most expensive — is worth thinking through carefully before launch. Discounting the cheapest qualifying get-side item protects your margin on higher-priced items; the customer gets a discount on a lower-value product. Discounting the most expensive is more generous and creates a stronger perceived value (“the most expensive thing in my cart just got cheaper”) but costs more per triggered deal. Neither is universally right — it depends on your price spread across the get-side products and what you want the deal to feel like to the customer.

How Smart Cycle Discounts handles both

Smart Cycle Discounts treats same-product BOGO and cross-product Buy X Get Y as separate campaign types rather than variations of the same setting. This is the architecturally correct decision — they have different configuration fields, different eligibility rules, and different edge case behaviors. Conflating them into a single “BOGO” setting is how configuration errors get introduced.

Same-product BOGO (free tier)

The BOGO campaign type in Smart Cycle Discounts is available in the free version and has been since version 1.0.0. You configure buy quantity, get quantity, and discount percentage. The product scope can be all products, specific products, or a category — the buy and get units always come from the same eligible pool. Setting the discount percentage to 100 gives a true “free” unit; any value below 100 gives a partial discount on the get units.

Same-product BOGO runs as a scheduled campaign with defined start and end times, activating and deactivating automatically. It’s incompatible with the cart-total apply_to mode, which is expected behavior — BOGO applies to specific units, not to the cart value as a whole.

Cross-product Buy X Get Y (Pro)

The Buy X Get Y campaign type is a Pro feature, introduced in version 1.9.0. You define the buy product IDs, the buy quantity, the get product IDs, the get quantity, the discount percentage, and the get discount target (cheapest or most expensive). Both product pools must be fixed lists — random and smart selection modes are incompatible because the engine needs stable, deterministic pools to evaluate the buy/get pairing correctly.

The optional max applications cap lets you limit how many times the deal fires per cart. Without a cap, a customer with ten buy-side units and ten get-side units could trigger the deal multiple times. For most promotions you’ll want to set a cap of one or two applications to keep the discount exposure predictable.

Like same-product BOGO, Buy X Get Y runs as a scheduled campaign and is incompatible with cart-total apply_to. The Campaign Intelligence system evaluates both types at launch time — checking for priority conflicts with other active campaigns, flagging low-stock risks on the buy or get products, and identifying configuration issues before they reach customers. The full setup walkthrough for both types is in the discount types documentation.

Edge cases and things that trip stores up

Both structures have edge cases that are easy to miss during configuration and only surface when a customer hits an unexpected cart state.

Variable products and which ID to use

For cross-product Buy X Get Y, both the buy and get product pools accept either parent product IDs or variation IDs. Using a parent product ID qualifies all variations of that product for the relevant pool. Using a specific variation ID qualifies only that variation. If you want “any size of Product A” to qualify as a buy-side product, use the parent ID. If you want only the 500ml version to qualify, use the variation ID. Getting this wrong is a common source of “the deal didn’t apply” complaints.

Overlapping campaigns and priority conflicts

If a product is eligible under both a same-product BOGO campaign and a cross-product Buy X Get Y campaign simultaneously — say, Product A is the “get” product in a Buy X Get Y deal, and there’s also an active BOGO campaign covering all products — you have a conflict. Smart Cycle Discounts handles overlapping campaigns through its campaign priority system: the higher-priority campaign applies, the lower-priority one does not stack. Always check priority settings when running multiple discount campaigns during the same window.

The max applications cap and bulk orders

Without a max applications cap on a cross-product Buy X Get Y campaign, a customer placing a large order could trigger the deal many times in a single cart. For B2C retail this is usually fine (most customers won’t add ten of everything), but if your store handles any wholesale or bulk purchasing, the cap becomes important. Set it before launch, not after reviewing an unexpectedly large discount on a single order.

Cart-total apply_to is not compatible with either type

Both same-product BOGO and cross-product Buy X Get Y apply discounts at the product unit level, not at the cart total level. Setting the apply_to field to cart_total for either campaign type will produce an error or unexpected behavior. These discount types operate on specific items in the cart, so the cart-total mode is not a valid scope for them. This is by design — a “buy X get Y” deal doesn’t make conceptual sense at the cart-total level.

The “cheapest vs. most expensive” setting and mixed-price get pools

The get discount target setting on cross-product Buy X Get Y only becomes meaningful when your get-side product pool has products at different price points. If all get-side products are priced identically, it makes no difference. If you have a mix of $20 and $80 products in the get pool, the setting determines which one the customer gets discounted — and which outcome is better for your margin depends on whether you want the discount to protect your high-margin products (choose cheapest) or create a more compelling customer-facing offer (choose most expensive).

Frequently asked questions

Choosing the right structure starts with the right question

Before picking same-product BOGO or cross-product Buy X Get Y, it’s worth pausing on a single question: do you want the “buy” and “get” products to be the same thing, or different things?

If they’re the same — a customer adds more of one product and the extra units get cheaper — same-product BOGO is the natural fit. It’s simpler to configure, available in the free tier, and works across flexible product scopes including categories and all-products modes.

If they’re different — a customer buys Product A and gets Product B at a discount — cross-product Buy X Get Y is the right structure. It requires fixed product pools and the Pro upgrade, but it enables a genuinely different promotional mechanic: using a product the customer already wants as leverage to move a product they hadn’t yet considered.

The two structures can coexist in the same store during the same promotional window. They serve different goals. And as with any discount, the margin math should run before launch — not after you’ve seen what the discount actually cost you.