Cs-Cart And Multi-Vendor 4.14.3 Released

So I won't be upgrading. I process phone-in orders manually in the backend all the time.

Yup, I saw the note ahead of time, but thought, they just must be putting this functionality elsewhere, there's no way they removed it right? Really hope I am wrong, CS-Cart please chime in here and let us know what's going on. Why even have the credit card fields on the admin order side if we cannot process the payment?! Please restore this functionality ASAP!

The booking addon has not appeared yet


Booking is alreay available as a separate solution: https://www.cs-cart.com/start/booking-marketplace. We released it that way because there are differences in how booking and non-booking marketplaces work.

P.S. I also noticed the questions about “Save and process payment” above. I'll get back to you witht the answer as soon as I can.


[*] Order management: The “Save and process payment” button was removed from the order creation and editing pages.

I am confused, why remove this?? How do I process an order payment on the admin side when I need to now? Am I missing something obvious?



So I won't be upgrading. I process phone-in orders manually in the backend all the time.



Yup, I saw the note ahead of time, but thought, they just must be putting this functionality elsewhere, there's no way they removed it right? Really hope I am wrong, CS-Cart please chime in here and let us know what's going on. Why even have the credit card fields on the admin order side if we cannot process the payment?! Please restore this functionality ASAP!

First of all, thank you for bringing this up. If you disagree with anything of the below, you're welcome to share your thoughts.

There were a few reasons why this functionality was removed:

- The situation when a customer provides credit card information by phone is rather unusual and not completely safe. Removing this from the admin panel simplified the interface and removed a potentially insecure approach.

- Storing credit card data in CS-Cart is something we don't advise either. The "cc.tpl" template (credit card fields displayed on the CS-Cart checkout page) serves mostly for demonstration purposes.

- Some payment processors (like Stripe) use "cc.tpl" too. But they capture the data themselves, without CS-Cart or the merchant accessing it. This ensures that the sensitive data remains between your buyers and the payment processor.

- Not all payment methods in CS-Cart supported "Save and process payment" on the admin side; that required extensive development.

- There was a workaround that allowed admins to achieve the same result on the storefront.

All these things are what led us to remove this action.

Speaking of the workaround, it is as follows:

You can configure the "Open" (or any other) order status to allow payment for the order again.

After that, an admin will always be able to log in as the required customer, go to the customer's orders on the storefront and make the payment from there.

Please let me know if this workaround works for you.

The workaround doesn't work for me. Some of my customers don't have internet, and others don't like ordering over the internet. So when they call, the order is starting cold. It's not like they start the order online and then call in to have it finished.

Not sure why you think phone-in orders are less secure. Been doing this for years with no problems.

- The situation when a customer provides credit card information by phone is rather unusual and not completely safe. Removing this from the admin panel simplified the interface and removed a potentially insecure approach.

This is a perfect example of why you are becoming very out of touch with your actual end user base, no one asked for this feature to be removed, it was/is instrumental to numerous businesses.

Our use case:

We create a product consulting fee or system design on our cart that customers can checkout on their own, we then design a complex system for them and often create a 10-15 item package that the client has agreed to, we need to then enter those product into an order thru admin. (This is not driven by client as too cumbersome for them or some products may be hidden from online view etc). We then finalize the order in admin and process final payment for the client on admin side.

Many Long time clients, and B2B clients want you to manage their orders, not shop for them online and checkout.

Many orders that are service type installation packages have items that change on the order after the job is finalized, everything is neatly edited on the order page of the admin side and the difference of price processed thru admin to reconcile job, this CANNOT be done using your workaround.

- Storing credit card data in CS-Cart is something we don't advise either. The "cc.tpl" template (credit card fields displayed on the CS-Cart checkout page) serves mostly for demonstration purposes.

Don't Stripe and Auth.Net arguably your 2 biggest processors use this? When entering credit cards into the storefront for purchases become for demonstration purposes, I'm out!

- Some payment processors (like Stripe) use "cc.tpl" too. But they capture the data themselves, without CS-Cart accessing it. This ensures that the sensitive data remains between your buyers and the payment processor.

- Not all payment methods in CS-Cart supported "Save and process payment" on the admin side; that required extensive development.

I have used Stripe (currently) authorize.net and Intuit, which all supported "Save and process payment". It's understandable that developing it for hundreds of processors may be cumbersome, but you already have it working so why remove it? Just hide that option for unsupported processors?!

- There was a workaround that allowed admins to achieve the same result on the storefront.

This workaround is so clumsy and poorly thought out, it also disproves your theory about insecure phone orders since we are just doing the same thing here anyway, its actually much less secure doing it here then on the admin side, where it is all cleanly packaged on one page with order management.

Also, when you use this "workaround" many things are not considered like every purchase you make logged in as your client, registers your IP/Identity with 3rd party chat clients and other add-ons as your client.

At worst, you should have consulted your customers more thoroughly before cutting this major functionality of a working store, I am sure I am not the only one that has many examples of why it should stay, it may even be a deal breaker for us after 12 years of businesses with you.

Please consider re-enabling this feature or at least providing it optionally for those that need it where it already worked, it literally cuts the intelligence of the cart system in half.

Thank you for sharing your use cases and letting us know how use this functionality. If it is indeed used widely, then we may bring it back in one of the future versions. That will depend on the number of requests we receive regarding it.

But for now, I can offer you a way to bring it back in your store. Here is a diff file that will return "Save and process payment" in the admin panel to your store. You can apply it as described in this instruction.

So whats the use of the call request addon then ?

Thank you for sharing your use cases and letting us know how use this functionality. If it is indeed used widely, then we may bring it back in one of the future versions. That will depend on the number of requests we receive regarding it.

But for now, I can offer you a way to bring it back in your store. Here is a diff file that will return "Save and process payment" in the admin panel to your store. You can apply it as described in this instruction.

Is there any improvement planned ahead to customer look and feel ?

So whats the use of the call request addon then ?

For the customer to pick a convenient time when they'd like to be called. To ask questions about the product, shipping terms, cash on delivery, etc.

Is there any improvement planned ahead to customer look and feel ?

The plans for 4.15.1 are listed on this page (you'd have to scroll down to the "Future plans" section). Anything else is TBA ("to be announced") for the moment.

@automatednow can you check out the diff file @ikoshkin posted about above and make sure it works?



[*] Order management: The “Save and process payment” button was removed from the order creation and editing pages.

I am confused, why remove this?? How do I process an order payment on the admin side when I need to now? Am I missing something obvious?

Another feature removed that we use a lot.

@automatednow can you check out the diff file @ikoshkin posted about above and make sure it works?

Yes I am going to do it shortly will let you know.


Thank you for the .diff file option will report back once installed.

Thank you for sharing your use cases and letting us know how use this functionality. If it is indeed used widely, then we may bring it back in one of the future versions. That will depend on the number of requests we receive regarding it.

But for now, I can offer you a way to bring it back in your store. Here is a diff file that will return "Save and process payment" in the admin panel to your store. You can apply it as described in this instruction.

I applied this .diff file but the functionality was not returned, I also cleared cache etc.

For the customer to pick a convenient time when they'd like to be called. To ask questions about the product, shipping terms, cash on delivery, etc.

The plans for 4.15.1 are listed on this page (you'd have to scroll down to the "Future plans" section). Anything else is TBA ("to be announced") for the moment.

I applied this .diff file but the functionality was not returned, I also cleared cache etc.

That's not what I wanted to hear. But thanks for testing and reporting back!

It's possible I did something wrong I will ask support to look at it, but looking at that code it doesnt seem to do much!

UPDATE: Support was able to properly install the .diff and it did restore the save and process payment functionality.

That's not what I wanted to hear. But thanks for testing and reporting back!

In cCs-Cart And Multi-Vendor 4.14.3 stripe payment can t be installed, it doesn t show on payment methods.

The save and process payment is very important to all my stores, I have contacted support and had to restore to the previous version which did not go well. They provided the diff file but have not done it yet, and from what I understand the diff file is only good until version 4.15.1. Not very happy

If you upgrade and want the Create and process payment do the following:

1. Open the update.tpl file, which is located in the following directory: design/backend/templates/views/order_management;

around line 157- 159

Replace this: {hook name="order_management:update_tools_list"}{/hook}

With this: - {hook name="order_management:update_tools_list"}
  • {btn type="list" text=$but_text_ dispatch="dispatch[order_management.place_order]" class="cm-submit" process=true}
  • {/hook}
    Clear the cache or remove the cache directory in var.

    If you upgrade and want the Create and process payment do the following:

    1. Open the update.tpl file, which is located in the following directory: design/backend/templates/views/order_management;

    around line 157- 159

    Replace this: {hook name="order_management:update_tools_list"}{/hook}

    With this: - {hook name="order_management:update_tools_list"}
  • {btn type="list" text=$but_text_ dispatch="dispatch[order_management.place_order]" class="cm-submit" process=true}
  • {/hook}
    Clear the cache or remove the cache directory in var.

    So why did you downgrade, if this mod is possible on the upgraded version?

    So why did you downgrade, if this mod is possible on the upgraded version?

    I downgraded because the Create and process was not there after the upgrade and support did not tell me that this feature had been removed, all I was told is to restore to the previous version which made me think that the upgrade did not go well, after the restore was done I found out that the feature was removed and that is when support provided me with the diff file, they sent me the wrong file first and corrected it and sent me the correct file.