#__lemonadestand-best-practices

1 messages ยท Page 1 of 1 (latest)

fleet pivot
#
  1. Typically Checkout is used for one off purchases.
  2. Which report are you running here?
warped mauve
#

Started to review sigma, and seems like that might be a viable option. We're not live with this integration yet, but just reviewing how we'd answer the question : "How many of X product was purchase between A and B dates?"

-- Then revenue generated from that etc.

#

Thanks for the insights on product types. These were examples for this conversation (since it was posted publicly) -- our rep is reviewing our integration to ensure we're compliant ๐Ÿ‘

fleet pivot
#

Thank you for the clarification. Looking in to what we have build for this.

sharp thorn
#

๐Ÿ‘‹ Hello! I'm hopping in since @fleet pivot has to head out - just to confirm, are you planning on using Checkout for users to purchases your products?

#

I ask because there are a few different ways you can get this - but it does depends on your integration

warped mauve
#

Correct, either checkout or invoicing

#

I don't see an easy way to associate PaymentIntent to line items / products

sharp thorn
#

Yeah so Payment Intents have no awareness of what line items/products were tied to the payment - that line item information is stored on the Checkout session or Invoice. I don't have a lot of visibility into what is stored in each report, but if you wanted this information available on the Payment Intent itself you could add it to the metadata yourself and reference it from there

warped mauve
#

got it, we are adding it to the metadata as well -- but my main concern was best practices & seeing if we can link products specifically (so we can hopefully report on it)

#

we'll try with the checkout session, seems to be the most aligned with our approach

ember viper
#

Yea that sounds good -- this isn't supported directly on the payment intent today