Wp-calypso: Billing History: Woo products appearing in WordPress.com receipts

Created on 8 Sep 2016  路  7Comments  路  Source: Automattic/wp-calypso

Steps to reproduce

  1. On an account with at least one WordPress.com purchase and one WooCommerce purchase, starting at URL: https://wordpress.com/me/billing
  2. Note that the receipts section includes WooCommerce purchases
  3. Open the "All Apps" filter for the receipts, and select "WordPress.com"

    What I expected

I was surprised that WooCommerce products appeared in my Billing History on WordPress.com at all, but I expected that selecting "WordPress.com" would limit the receipts to only WordPress.com products.

What happened instead

The WooCommerce products remained in the list after selecting "WordPress.com."

The Woo product names also had unexpected prefixes ("themes" and "plugins")

Browser / OS version

Mac OSX 10.11.6, Chrome 53.0.2785.89

Screenshot / Video

screen shot 2016-09-08 at 2 51 22 pm

Context / Source

dogfooding

Billing [Type] Bug

Most helpful comment

The endpoint only considers connect products as Woo, and returns them as Store Services.

Yep - those products (currently) represent shipping label purchases from both self-hosted WooCommerce Services and the Store functionality on WordPress.com, hence the genericized "Store Services" name.

Any changes to the behavior of connect products needs to involve @Automattic/hydra - thanks!

All 7 comments

@rachelmcr do you know what filters should appear under the "ALL APPS" dropdown?

I'm not sure what filters are expected here, but personally I'd expect them to match the various services in Payments Admin.

The Woo product names also had unexpected prefixes ("themes" and "plugins")

These product names are assembled in a very fragile way; related to #112 .

Ok, I've tracked down what goes wrong where.
The endpoint only considers connect products as Woo, and returns them as Store Services.

Though, normally, Woo products have the woo slug, which is not mapped in the endpoint and is returned as WordPress.com.

At this point I can do two things:

  • Map woo products as WooCommerce, and display them in Calypso's billing history (the filtering by "All Apps / WooCommerce" would come for free).
  • Filter out woo聽products in the endpoint.

@Automattic/payments what should I do here?

The endpoint only considers connect products as Woo, and returns them as Store Services.

Yep - those products (currently) represent shipping label purchases from both self-hosted WooCommerce Services and the Store functionality on WordPress.com, hence the genericized "Store Services" name.

Any changes to the behavior of connect products needs to involve @Automattic/hydra - thanks!

For context: I've updated D11598-code to the first option:

  • Map woo products as WooCommerce, and display them in Calypso's billing history (the filtering by "All Apps / WooCommerce" would come for free).

Fixed in D11598-code!

Was this page helpful?
0 / 5 - 0 ratings