Actinic Link - Can individual attributes be mapped to seperate part numbers?

[domino1]

I have products in Actinic that have size attributes. eg:

Jacket - Size 1
Jacket - Size 2
Jacket - Size 3

In Actinic this is one product so only has a single reference.

In Quickbooks this is listed as three products, one for each size. It has to be done this way for stock control reasons.

Can Actinic Link be configured to map the different sizes to individual product codes? eg:

Jacket Size 1 mapped to Product code J001
Jacket Size 2 mapped to product code J002
Jacket Size 3 mapped to product code J003

Many Thanks

Dave

[Darren B]

Dave you need to do this by componants, then select the corresponding product to this size

[Darren B]

this image might explain

[domino1]

Thanks Darren.

I have the actinic side worked out. I have a 'size' component with a buy button for each size. It's the Link to Quickbooks part that I'm stumped with.

If I generate an order containing 'Jacket size 1' and 'Jacket size 2' I need each size to be mapped into its own part number on Quickbooks.

Its the 'Jacket' that has the product reference in Actinic and not the individual sizes so 'Size 1' and 'Size 2' both have the same product reference.

[peblaco]

You can use permutations and associated hidden products.

[Darren B]

Dave

Simple terms

Create the 3 products as they are in QB, you can hide these in actinic so they are not shown online, then associate them to it as in the picture

D

[domino1]

Thanks Louise, nice one. I think this solves my problem (although I have a lot of work ahead to generate all these hidden products.)

Dave

[domino1]

Darren. Thanks mate, understand what you mean now.

Dave

[Darren B]

No Probs

[domino1]

Have now implemented the above on a few products and succeeded in generating unique product references for 'sizes' of a main product.

It works for sure but there are a few drawbacks:

1) It's quite 'messy' and increases the complexity of the product catalog.

2) It's harder to maintain. (Changes will potentially need to be done in two places. One for the component and one for the dummy product).

3) It's very time consuming for a catalog that has many products with many sizes.

4) When a product of a particular size is added to the basket, it appears in the basket as plain text and not as a clickable link back to that product listing. This (in my opinion) is a usability drawback. In the scenario where a customer has added the wrong size, there's no easy way back to the product to correct the error. The only way to include the link back to the main product is to uncheck "NO ORDER LINE FOR MAIN PRODUCT", but if you do this you'll end up with two products (one for the main product and one for the size) referenced in your Quickbooks import for a single product.

If you've only got a few products that need to be configured this way then I think it's fine but if you've got hundreds of products each with many sizes I forsee it becoming a nightmare.

WISHLIST:

1) Make the component entry in the basket a clickable link.

2) Provide a check-box for attribute 'choices' (eg size) that specifies that a unique product reference is to be generated. (This bypasses the need to create a dummy product.)

Dave

[peblaco]

Might want to post in the Wish List here.

[domino1]

Thanks for the quick reply Louise, you're a lot sharper than I am at this time of morning!

I will add this to the wishlist. Would be interested if anyone has any comments before I do though.

[TraceyHand]

just post it straight into wishlists, Dave

It's all ground that's been covered before so I'm sure plenty of people will second, third and fourth it!

I posted recently about the lack of link back to the catalogue for the associated products. I understand why there isn't, but it would be nice if it could like to the "main" product this way too

As for a checkbox to generate these associated products...sure, that'd be nice too! If we could give these choices properties such as weight/stock etc, even better.

[domino1]

Tracey,
Agreed. Properties on Choices would be very useful. But it might break Actinic's product model. It works for single attribute products but what if you have two attributes (size and colour maybe)? You then have an array of unique products but there will be no single entity in the product catalog where you could assign properties correctly.

For example you might have red and blue jackets in sizes S, M and L.

Product would be 'Jacket'. Size and Colour would be attributes of 'Jacket'. But there would be no way to set the properties (eg weight) of 'Large Red Jacket'.

I keep trying to think of a better way to model products and every time I go full circle and end up with what Actinic have already done.

Dave

[TraceyHand]

yep, I know
BTDT lol
and so we end up back with lengthy lists of hidden products and all the work that involves..

ahhh...one day..