Therefore, I and the developer Codinginspect jointly planned and developed the "Product Shipping Method & Payment Method (Batch Modified Based On Customer Groups)" module.
Although we are currently only in the planning stage of programming code operation logic, I can guarantee that if this customized development project is completed, we can avoid the misuse of products that are not suitable for supermarket pickup and payment.
Not to mention, only one-time batch modifications can be made for a single customer group to avoid setting conflicts caused by the shipping and payment methods of multiple customer groups. (Of course, it can also be edited for a single product)
Module development concept diagram
Catalog > Products > Link, here you can set settings for a single product.
In the future, a "Product Shipping Method & Payment Method" menu may be added directly in Catalog, And different rule settings for each customer group will be displayed in the "Product Shipping Method & Payment Method" tab of each product.
Use selection methods for each rule to determine which shipping products and payment methods should be applied to which product category?
After selecting, click the [Batch Modify] button to complete the settings. After the settings are completed, you can make settings for other customer groups or product categories.
Data table structure:
Code: Select all
CREATE TABLE `oc_product_method_ci` (
`product_method_id` int(11) NOT NULL,
`customer_group_id` int(11) NOT NULL,
`product_id` int(11) NOT NULL,
`product_shipping_method` varchar(2550) NOT NULL,
`product_payment_method` varchar(2550) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=utf8;Code: Select all
INSERT INTO `oc_product_method_ci` (`product_method_id`, `customer_group_id`, `product_id`, `product_shipping_method`, `product_payment_method`) VALUES
(1, 1, 1, 'flat,category_product_based', 'bank_transfer,pp_standard'),
(2, 2, 1, 'item,category_product_based', 'pp_standard'),
(3, 3, 1, 'category_product_based', 'bank_transfer'),Therefore, I hope to ask two friends to help share the remaining development costs, and the sharing ratio is $75*2=150.
Payment can be made through the website of Codinginspect.
Promise from Codinginspect.
Fully compatible with:
OpenCart 3.0.4.0
OpenCart 4.0.2.3
Journal 3.2.0-rc.101 (including the above versions)
PS. This custom development fundraiser is made possible with the permission of Daniel Kerr. (Please understand)
