Best way to add a one time setup fee to a per-piece item

-- HikaShop version -- : 2.6.4 AND 3.1.1
-- Joomla version -- : 3.7.4

Hello -

After reading the recommendations in this thread: www.hikashop.com/forum/install-update/88...checkout.html#249359 ...

We tested out that solution by creating:
- A setup fee product with 1 characteristic variant only of $45. The quantity allowed on this product is set to a maximum of 1.
- Added that setup fee product as an option to the main product.
- The main product is sold by the piece, with different prices by quantity range (for example, 50 - 60 units is $6.35 vs. 60 - 70 units is $6.10 vs. 70 or more is $5.95, etc.).

BUT - what we get in the checkout is the per item price is added together with the setup fee of $45 so we end up with crazy huge unit prices of ($45 + $6.35) each X the main product quantity ordered.

Hmmm, not what we had in mind at all.

What is the best approach for creating an addon (mandatory), flat setup fee to a product that is sold in bulk quantities and priced per piece?

A bit more background:

This is for screen printed items. The setup fee covers the cost of the time to setup the design art and it's the same $45 whether you buy 50 or if you buy 99. It is a mandatory fee.

We considered adding the $45 setup fee into a special Shipping Method but that would be horrible for cart abandonment. No matter how well we call attention to the setup fee, the customer will feel like it was a bait & switch to not see that price added until they get most of the way through the checkout. Not to mention we want to promote "free shipping" and it will look bad to see such a large fee listed as shipping on the checkout and invoice when shipping itself is actually free.

Lastly, we also need to make sure the customer can't delete the setup fee from the cart separately from the main product.

Ideas and advice welcomed.

Hi, Jerome -

Would you please provide a documentation link or small code example of what you mean. There's nothing about how to properly use that method in the API documentation.

Thanks,
~ Deb