What CrossUp decides

You display; CrossUp picks what, for whom and at which moment. It learns from your catalog, your orders and what each shopper does, and hands back a recommendation ready to show.

What goes in

The catalog and orders arrive through the app or a connector, translated into a common model. Signals arrive from your store, with what the shopper did.

What comes out

What CrossUp returns is a recommendation: the products for that moment, in order, with title, price, stock and image. In the API that object is called Decision, and decision_id is the recommendation’s id.

If there’s nothing to recommend, the recommendation comes back empty, with a reason.

What CrossUp decides, and what stays on your side

CrossUp decides	Stays on your side
Which products to show, and in what order	How they look: design, placement, copy
When a response is empty, and why	What to do with an empty result (usually nothing)
Which recommendation each signal belongs to	Reporting signals as they happen

Your key identifies your store

With the storefront key you create in the CrossUp admin (Settings → Keys for your storefront) you request the recommendations you’ll show in your store. You don’t need to say which store you are: the key already knows. That’s why nobody can request recommendations or read products from another store by changing a field in the request. A product from another store answers the same as one that doesn’t exist: 404.

What you will see

Data, not HTML. Each product in results is enough to render it without another call. This is how the POST /v1/recommendations response travels for a product page, trimmed to one result. Optional fields the catalog doesn’t have are left out.

Response

{
  "decision_id": "dec_demo_001",
  "request_id": "req_4f1c2a9b8d7e6f50",
  "store_id": "st_demo",
  "connection_id": "cn_demo",
  "placement_key": "pdp-related",
  "surface": "pdp",
  "visitor": {
    "visitor_id": "vis_Q2x9mT4pL7rK1sV8",
    "session_id": "ses_Hn3bW6yZ0cF5dJ2e"
  },
  "context": {
    "shooter": {
      "item_id": "itm_demo_remera"
    },
    "cart_items": []
  },
  "results": [
    {
      "item_id": "itm_demo_pantalon",
      "variant_id": "var_demo_pantalon_azul_m",
      "position": 1,
      "reason_codes": [
        "related_item"
      ],
      "product": {
        "item": {
          "item_id": "itm_demo_pantalon",
          "store_id": "st_demo",
          "connection_id": "cn_demo",
          "external_id": "1002",
          "title": {
            "es": "Pantalón Demo"
          },
          "status": "active",
          "primary_media": {
            "url": "https://cdn.example.test/pantalon-demo.jpg",
            "alt": {
              "es": "Pantalón Demo azul"
            }
          },
          "urls": {
            "es": "https://tienda.example.test/productos/pantalon-demo"
          },
          "source_version": "2026-08-26T09:00:00Z"
        },
        "variants": [
          {
            "variant_id": "var_demo_pantalon_azul_m",
            "item_id": "itm_demo_pantalon",
            "external_id": "2101",
            "sku": "PAN-AZU-M",
            "title": {
              "es": "Azul / M"
            },
            "status": "active",
            "price": {
              "amount": "18900",
              "currency": "ARS"
            }
          }
        ],
        "availability": [
          {
            "variant_id": "var_demo_pantalon_azul_m",
            "sellable": "in_stock",
            "quantity": 6,
            "as_of": "2026-08-26T09:00:00Z"
          }
        ],
        "refresh_revision": 3
      }
    }
  ],
  "reason_codes": [],
  "generated_at": "2026-08-26T09:00:01Z"
}

And this is how your store reads it:

decision.decision_id   // signals will cite it
decision.results       // the recommended products, in order
decision.results[0].product.item.title     // { en: "Demo Pants" }: by language
decision.results[0].product.variants[0].price // { amount: "18900", currency: "USD" }
decision.reason_codes  // why, if the list came back empty

type Decision struct {
    DecisionID  string   `json:"decision_id"`  // signals will cite it
    Results     []Result `json:"results"`      // the products, in order
    ReasonCodes []string `json:"reason_codes"` // why, if it came back empty
}

The six moments

Where a recommendation shows up and what each moment needs.

How your store connects

App or connector: it depends on where your store runs.

Get started

Operate

What CrossUp decides

What goes in

What comes out

What CrossUp decides, and what stays on your side

Your key identifies your store

What you will see

The six moments

How your store connects

​What goes in

​What comes out

​What CrossUp decides, and what stays on your side

​Your key identifies your store

​What you will see

The six moments

How your store connects

What goes in

What comes out

What CrossUp decides, and what stays on your side

Your key identifies your store

What you will see