SKU services not showing up at checkout

VTEX in your native language 🌎 Portuguese
,
1

I have SKU services registered and, when the respective SKU was added to the cart, they used to show up at checkout in an HTML select so the customer could choose whether or not to add them to the cart, but now they’re no longer appearing.

Can anyone help me?

2

Hey @tiago.freire, how’s it going?

In the most common case, it’s some customization that might be preventing this from happening.

Have you checked if it shows up after removing custom styles and JS?

Did you check in the Orderform if they’re there when entering the checkout?

Hope this initial info can be useful for debugging.

Cheers,
Estevão.

3

Thanks for the response @estevao_santos

I’ve already done the following tests and couldn’t identify the cause of the problem:

  • Removing custom CSS and JS from the checkout, without success
  • Inspecting the DOM on the checkout screens and finding no mention at all of the services, offerings, etc., that could be hidden with display: none
  • Examining the vtexjs.checkout.orderForm object and seeing that the cart item has the offerings key with an empty array as its value

I’ve already verified that the services are in fact associated with the SKU in question through the “Get SKU and context” endpoint described at Catalog API

Is there any endpoint I can use to check the services linked to a cart item?

4

@tiago.freire No problem!

Got it, makes sense.

You might want to try dissociating and re-associating the Service on the SKU to see if that changes anything: Catalog API

If that doesn’t work, based on what you’ve already done in terms of debugging — confirming that the Attachment/Service is linked to the SKU and that the SKU has been reindexed and is active — I’d suggest opening a support ticket with VTEX and sending a .HAR file from the checkout.

Also include the SKU ID and the Service ID that are both associated.

Best,
Estevão.

5

@estevao_santos, I just found out that the SKU associated with the services in question belonged to a VTEX seller (the store is a marketplace). For the default seller’s SKUs, the services work normally at checkout (image below)

Quase-lá-Finalizar-compra
Quase-lá-Finalizar-compra863×435 36.8 KB

In this case, would it be necessary to register services and associate them with the SKU in the seller’s account? Is it possible to sell the seller’s services on the marketplace?

Thanks in advance!

6

Hey @tiago.freire, perfect. Glad you found the reason. I hadn’t considered that the seller could interfere with the display of services for a SKU. But it actually makes sense, since seller configuration also defines how and what you display for a given product.

Yes, the seller must register the services in their own VTEX account, through the admin.

After registering the services, the seller must associate them with the SKUs of the products for which they want to offer those services.

Since the SKU belongs to the seller, the main store (marketplace) cannot manage the services of partner sellers. Each one is responsible for registering and configuring their own services on the VTEX platform.

So go ahead and test it — when you add a SKU from a seller that has associated services to the cart, those services should appear at checkout so you can choose whether or not to add them.

Cheers,
Estevão.