wrong price in transaction report

[tulipsonmars]

i have some items where the product price is set at zero because the price is setup as a component. for example, a pair of ice skates - junior size £47 and senior size £41.70 the junior sizes are configured to point to a hidden product that i have called "vat exempt". the senior sizes are taxed.

check out this link http://actinic.dnetsltd.com it has snapshots from my actinic catalog to help clarify what i have described here.

my problem is - any product that has a zero price on the product itself (because it is using component pricing) shows as zeros in the transaction report.

is there a way around it without me re-designing the whole site and with spending lots of extra money on crystal reports?

thank you so much for your help.

tony.

[cdicken]

If you associate the components with actual products in the store that have prices, then these products and prices will appear in the transaction reports.

[tulipsonmars]

RE: wrong price in transaction report

thanks chris,

but whatever i do to the permutations in the component, the transaction report always picks up on the fact that the product price is set to zero, even if i make a dummy/hidden product and put the price in that.
my problem is only with the transaction report, the customers are charged correctly when they checkout, i find this confusing because it shows that actinic knows how to deal with the various pricing models. i have put some more screen dumps at http://actinic.dnetsltd.com

thanks,

tony.

[cdicken]

Online, all the pricing models work fine, but the problem just seems to be with the transaction reports showing the product price as zero. I would have that if you had the components associated with hidden products in your store, then the hidden product would be included in the transaction report.

I'll ask Jan Strassen to comment here as she knows a lot more about the reports than I do.

[cdicken]

I've just done a test and it worked fine for me.

Check out the attached screenshot and you'll see that when a product has components, the price shown in the shaded area against the main product name should be the price of the first product/component combination in the list. The report then lists all the individual component selections, and gives the total product/component price against each one. These prices are then totted up at the bottom.

I think you need someone to look at your store data to find out why this is happening. Why not register an email support query at http://www.actinic.co.uk/support/register.htm and the team there will be able to look at your data.

[tulipsonmars]

thanks again chris, i will register an email support query. i just want to point out one more detail with my problem - in the component tab of a component there is an option "Component As Separate Order Line" if this box is unchecked, then yes, my transaction reports work fine. but i need this box to be checked so i can make use of the "Tax from Associated Product" option in the permutations tab of the component.

ok, i'll leave it at that, and thanks again chris for your help, i will register a query with the support team.

tony

[Jan]

Sorry for the slow response, I've been on holiday.

I have taken a look at the 6.1.3 transaction report and uses the order cost details that are recorded in the order table. There is no reference to the original product at all and no reference to component flags. So if the report is showing the wrong results is it likely that the stored order somehow also has wrong results.

Can you confirm that changing the original product details changes the output on the report or do you mean that new orders show differnet results?

Can you check the results you are seeing against the values you see in the order details dialog and report back please.

Transaction reports don't take adjustments into account but this doesn't seen to be the problem here.

Regards,

[tulipsonmars]

i gave up trying to work it out and ended up redesigning the layout of my site to get around my problem.

"Can you confirm that changing the original product details changes the output on the report or do you mean that new orders show differnet results?"

i found that once an order had been placed on the web site, the way it was then displayed to me in actinic remained the same even after i made changes to the structure of my products. but thats ok, i wasn't really worried about it, i just wanted my future orders to display correctly in my transaction report.

i'm not sure if i just answered your question correctly, sorry

my problem is - my product (for example a hockey jersey) that has a taxable and a non-taxable price depending on if the size chosen is a junior or senior size, i can't make the correct prices be displayed in the transaction report. eventually i gave up and just split the product into 2 products, junior non-taxable and senior taxable.

chris mentioned, near the top of the thread "If you associate the components with actual products in the store that have prices, then these products and prices will appear in the transaction reports." but this only works if the "Component As Separate Order Line" option is unchecked, but you see my problem here? if that box is unchecked then the "Tax from Associated Product" option becomes unavailable, i need this option available to me so i can differentiate between taxable and non-taxable choices on my product.

well, it seems i'm just repeating myself in this thread now.

if you can help me it would be great

tony.