Show Shipping category name instead of temp controlled in packing reports

[gracejam]

:warning: before starting this papercut we need to ask instance managers if they use this field in integrations.

Context

The enterprise manager for Enterprise ID#3604 needs the best way to differentiate between refrigerated & frozen items so this can be considered when packing orders. After every order cycle the manager downloads the packing reports to begin packing. Packing reports show if a product is 'Temp Controlled' - which is set by Shipping Category - but this will display the same whether the product has the Shipping Category selected as 'Refrigerated' or 'Frozen' Discussion in slack here

Description

- As a: enterprise user or superadmin - On page: /admin.reports/packing- all sub reports Other reports will be dealt in different issues - I want to be able to do: see the shipping category name instead of "Yes/no" in temp. controlled column.

Currently we have:

We want to have:

Acceptance Criteria & Tests

1. Log in as enterprise manager
2. Check all packing reports: you should see the name of the shipping category instead of the usuall temp controlled yes/no
3. Check it's accurate with the product line items

Repeat as super admin

[gracejam]

Reports where the Shipping Category would be most valuable to this user:

• Order Cycle Supplier Totals
• Pack by Customer

Extra detail from the enterprise:

'Report that I can see valuable of fridge / freezer /  default :

• Order cycle supplier totals – particularly with our variety of products increasing, this would help our (newer) volunteers place incoming goods into the right place and have it within the list when in doubt.
• Packing report – (prob all variations – but mostly by customer) this will be particularly helpful when packing ½ the orders for delivery.'

[RachL]

@gracejam thanks for this wishlist.

I'm also struggling with shipping methods and pack by customer so I often merge the report with OC customer total. It made me think of another solution: adding temperature to OC customer totals. In this case, would you still have use cases in AU where Pack by customer would be needed?

[RachL]

Papercut confirmed

[lin-d-hop]

"Show instead of" in reports is a recipe for disaster.

But maybe we're thinking about this wrong... I would say that blocking this is the feature to save report display options. Once that is in place we should be looking at adding missing fields to reports on a mass scale but by default showing the old report settings.... then no integrations would be impacted and we could explode functionality of reports quickly.

[audez]

hi! thanks for this @gracejam ! @RachL we have a producer who is also struggling and asking to add the "Shipping method" column in the "Pack by customer" report. Having this data would allow him to directly sort/group the orders by shipping method in his export file. For now he manually adds the Shipping methods to the export file.

@gracejam thanks for this wishlist.

I'm also struggling with shipping methods and pack by customer so I often merge the report with OC customer total. It made me think of another solution: adding temperature to OC customer totals. In this case, would you still have use cases in AU where Pack by customer would be needed?

[RachL]

@audez just to detail a bit my thinking: a lot of data of pacing reports are shared with Orders & fulfillments reports. If users can hide columns in Total OC by customers, see the temperature columns there and save that rendering, do we still need the Pack by customer report?

I'm not questioning the fact that shipping methods are useful for packing, just commenting on the fact that increasing the columns on one report, start to make it look a lot like another one... and this can also confuse users when they start using the software: they don't know which reports to choose and often end up merging them.

[RachL]

then no integrations would be impacted and we could explode functionality of reports quickly.

Agreeing for now. But on the long run we will need to make tough decisions on cleaning a bit the reports section so that we have fewer reports, more performant, and easier to maintain that the patchwork we have today. This will impact integrations. The longer we wait, the more integrations will be impacted by this change. So we need to keep it in mind to not end up with something we are afraid to release.

[drummer83]

This one is now unblocked because #9189 has been solved in #9999.