How to Measure Shopify Manual Cross-Sells Without a Paid Analytics App

Measure the pairing decision, not a fictional app-attribution number

Start with the right measurement question. If a product page recommends a charger next to a device and an order later contains both items, that order tells you the pairing exists in completed demand. It does not prove the recommendation block caused the second purchase. The shopper might already have intended to buy the charger, arrived from a bundle page, used search, or added it from another product page. A manual cross-sell review should therefore begin with basket association and merchandising quality rather than pretending every paired order is attributed revenue.

That distinction keeps a free workflow honest. Your first goal is to discover which hand-picked relationships show up in real orders often enough to deserve product-page space. Later, if causal attribution or controlled experimentation becomes essential, you can evaluate software built for those jobs. Do not buy that complexity before the basic pairings are good.

Step 1: create a cross-sell scorecard before looking at reports

Build a small table with one row for each priority base product and one column for each companion you intentionally recommend. Record the date the pairing went live, the reason for the pairing, and any compatibility rule that matters. A camera and its exact battery can have a stronger relationship than a camera and a generic cleaning cloth, even if the cloth happens to sell more often. Your scorecard should preserve that merchandising context so a high-volume but weakly relevant item does not automatically win.

Keep the first review set small. Start with perhaps the products that generate the most orders or the pairings where accessory choice affects customer success. The point is not to create a warehouse of metrics. It is to make each recommendation answerable: what relationship did we choose, what basket behavior followed, and what should we change next?

• Base product and SKU or variant identifier.
• Recommended companion and its compatibility rule.
• Date the pairing was added or changed.
• Orders containing the base product in the review window.
• Orders containing both base and companion in the same window.
• Notes for stockouts, launches, promotions, returns or catalogue changes.

Step 2: use Shopify's Items bought together report when it is available

Shopify's current Help Center documents an Items bought together report that shows common product combinations purchased together from processed orders. It can switch between product and variant combinations and supports filters around the number of products or variants bought together. If that report is available in your Shopify admin, it is the cleanest place to begin because the question already matches the merchandising problem: which products are actually appearing in the same processed orders?

Open Analytics, go to Reports, filter to the Orders category, and look for Items bought together. Compare the combinations in the report with the companions you intentionally selected. A recommended pair that also appears naturally among common purchased combinations is a useful positive signal. A pair that never surfaces is not automatically bad, especially at low volume, but it deserves a closer look at relevance, visibility, price and stock availability.

Step 3: fall back to the order CSV when you need a simple manual check

If you do not have the report you need, Shopify also documents order exports from the Orders page. The current order CSV places additional line items from the same order on separate rows and includes fields such as order name, financial status, created date, line-item name, quantity, SKU, refunded amount and cancellation date. That structure is enough to reconstruct whether a base item and its companion appeared inside the same order without installing a separate analytics app.

Choose a date range, export the relevant orders, and group rows back to the order identifier. Then flag each order that contains the base product and separately flag whether that same order contains the recommended companion. Keep your inclusion rule consistent across periods. For example, do not compare a clean paid-order sample in one month with a mixed sample containing cancelled or refunded orders in another month. The spreadsheet is only useful when the denominator means the same thing every time.

Step 4: calculate a merchant-defined attach rate, then label it correctly

A practical score is companion attach rate: orders containing both the base item and the chosen companion divided by orders containing the base item. If 80 qualifying orders contain the base product and 12 of those orders also contain the companion, your merchant-defined attach rate is 15 percent for that review window. This is a useful internal merchandising measure, not a Shopify-defined attribution metric and not proof that the recommendation block generated those 12 additions.

Track the same calculation before and after a pairing change when you have enough comparable orders to make the comparison meaningful. Keep promotional context beside the number. A free gift, sitewide discount, bundle campaign, inventory shortage or major traffic-source change can move basket composition even if the cross-sell block itself did nothing differently. The score is a compass, not a courtroom verdict.

Step 5: measure variants when compatibility lives below the product level

Product-level reporting can hide a bad recommendation when only some variants fit. A phone case may belong with one device generation but not another. A replacement part may fit the 220-volt version but not the 110-volt version. A cushion insert may need to match a specific cover size. Shopify's Items bought together report currently supports a variant dimension, and the order export includes line-item SKU, so use variant or SKU-level analysis when the relationship depends on exact compatibility.

This is also where a manual app earns its keep. Öneri Kiti lets the merchant choose the recommendations rather than relying on a behavioral algorithm, but manual control does not remove the need to verify the product relationship. If a recommendation is safe only for certain variants and the storefront presentation cannot make that boundary obvious, do not force the cross-sell. A smaller number of correct recommendations beats a higher attach rate built on confusing compatibility.

Step 6: separate availability problems from merchandising problems

A weak attach rate can have nothing to do with the pair. Check whether the companion was actually purchasable during the review period. If the recommended refill was out of stock for half the month, the result cannot fairly evaluate the recommendation. The same applies when a product was archived, a key variant sold out, a price changed sharply, or the companion was hidden from the sales channel.

Add a simple availability note to the scorecard. When a recommendation underperforms, first ask four questions in order: was it in stock, was it compatible, was it understandable, and was it placed where a shopper could act on it? Only after those checks should you replace the pairing. This prevents the spreadsheet from becoming a machine that punishes good merchandising for operational problems elsewhere in the catalogue.

Step 7: review reversals before celebrating a high-attach pair

A companion can appear frequently in orders and still create poor business quality if it is often removed, refunded or returned. Shopify's current Orders and reversals by product report distinguishes ordered quantity from reversed quantity and defines reversals broadly enough to include refunds, returns, cancellations or edits. Use that information as a sanity check when a pairing looks unusually successful.

Imagine a cable appears with a device in many orders, but support repeatedly learns that shoppers selected the wrong connector and the cable is later reversed. A raw attach-rate chart would call the recommendation a winner. A merchandising review should call it a warning. The best manual cross-sell is not the item that enters the most baskets; it is the companion that makes the original purchase more complete without creating avoidable confusion afterward.

Step 8: change one merchandising variable at a time

When a pair is weak, do not replace all three recommendations, move the block, change the base-product copy and launch a discount on the same day. You will lose the ability to understand what improved. Start with the highest-confidence correction. If the item is relevant but poorly explained, improve the relationship in the product copy. If the pair is clear but buried, revisit placement. If the companion is simply wrong, replace that one recommendation and leave the rest of the setup stable for the next review window.

Öneri Kiti is intentionally narrow enough to support this style of merchandising. The official listing says you can choose up to three recommendations per product by hand and the shopper can add one from the product page without a reload. There is no claim of built-in A/B testing or attributed-revenue analytics, so keep the test design outside the app and describe the result as a store-data comparison rather than an app experiment.

A concrete example: stop recommending the bestseller and recommend the missing piece

Suppose a coffee-machine page recommends a bestselling mug, cleaning tablets and the correct water filter. The mug sells well across the store, so it appears in many baskets, but its base-product attach rate barely changes when shown beside the machine. The filter appears in fewer orders overall, yet a much larger share of machine buyers add it. The filter also solves a maintenance need specific to the purchase. That is the stronger manual cross-sell even if the mug wins on total unit sales.

Now imagine the cleaning tablets are out of stock for two weeks. Do not drop them permanently because their monthly attach rate falls. Mark the stock interruption, restore availability, and review the next comparable period. This is why a small human-maintained scorecard can outperform a dashboard full of isolated numbers: it preserves the reason the products belong together.

Where Öneri Kiti fits in a no-monthly-fee measurement workflow

Use Öneri Kiti when you want the storefront job to stay focused: choose up to three product-page companions yourself, let shoppers add them to cart from the page, and avoid another recurring app subscription for that manual cross-sell layer. The current Shopify App Store listing shows Free pricing and says there is no monthly fee, revenue share or usage limit; the owner confirms there is no paid plan. Re-check the live listing for future budget decisions rather than turning today's pricing into a permanent guarantee.

Available in English: Öneri Kiti can be used by English-speaking merchants despite its Turkish product name. ShopRadar uses the authentic `oneri-kiti` App Store slug with `locale=en`; that parameter requests the English App Store listing locale and does not change the installed app language. The live listing checked on September 15, 2026 currently presents English title and copy while its Languages metadata still says Turkish and 'not translated into English.' That is a listing-metadata mismatch, not a reason to rewrite the product as Turkish-only against the owner's confirmed English availability.

Recommendation: buy analytics only when the measurement question truly outgrows this workflow

For a small or mid-sized catalogue with deliberate product relationships, start free. Build the recommendation map, use Öneri Kiti for the product-page cross-sell, inspect Items bought together when available, and use order exports for a manual attach-rate check when you need more detail. That combination can answer the foundational merchandising question without pretending the app contains attribution features it does not advertise.

Move to a paid analytics or experimentation system when you genuinely need functionality this workflow does not provide, such as controlled A/B testing, placement-level attribution across several funnel stages, automatic optimization across a very large catalogue, or reporting that must be maintained without spreadsheet work. If you are still building your pairings, start with `/blog/how-to-add-related-products-shopify-manually-free`. For catalogue maintenance, continue with `/blog/shopify-related-products-audit-manual-cross-sells`. For a no-tracking merchandising model, see `/blog/shopify-cross-sells-without-customer-tracking`.

Apps mentioned in this guide

Frequently asked

Can I measure Shopify cross-sells without paying for an analytics app?

Yes. Shopify documents an Items bought together report for common product or variant combinations in processed orders, and it also lets merchants export orders as CSV. Those sources can support a manual basket-association and attach-rate workflow without claiming app-level attribution.

What is a useful attach rate for a manual Shopify cross-sell?

There is no universal target. A useful internal measure is orders containing both the base product and companion divided by qualifying orders containing the base product. Compare the same pairing across comparable periods and keep stockouts, promotions, refunds and catalogue changes in context rather than inventing a benchmark.

Does Öneri Kiti include cross-sell analytics or A/B testing?

The current official listing does not advertise attributed-revenue analytics or A/B testing. It describes a focused manual product-page cross-sell workflow. Use Shopify order data or another verified analytics tool if you need measurement beyond that scope.

Is Öneri Kiti free or a temporary trial?

The current Shopify App Store listing shows Free pricing, and the owner confirms Öneri Kiti has no paid plan. It is not being described as a trial or limited starter tier. Re-check current pricing before making future budget assumptions.

Is Öneri Kiti available in English?

Yes. The owner confirms Öneri Kiti is available in English. ShopRadar links to the authentic oneri-kiti Shopify App Store slug with locale=en; that selects the listing locale and does not change the installed app's language settings.