OpenCart Community

straightlight wrote: ↑

Sun Mar 17, 2019 5:47 am

In OC v3.x releases (and perhaps prior), the bestsellers extension is based on the highest prices being sold which provides the vision on noticing the ordered products that have been purchased with limited results. However, since Opencart v3.0.2.0 and above has a customer search method built-in, I thought of the idea on migrating the customer search with the ordered product results - including the updates of product options within the customer search table whenever an order has been created.

These changes now involves Demand Management with the Service Strategy as it should be. Based on the customer's service request, in this case the customer search results, store owners can now filter by total or by the most recent search queries which makes much more sense. Demands will keep increasing by customers and, in this case, for a good cause. Each products involving changes with the product options will automatically be updated in the customer search based on the last time the identical product was purchased which will only require a low amount of resource. This methodology will allow store owners to keep track of the demands vs. the sales all in the same place as for customers having an account will be able to notice the change (if not, then later on with an extension).

Edit: From now on, see from my GitHub namespace all files called: bestseller.php, catalog/model/account/search.php and catalog/model/catalog/product.php files: https://github.com/straightlight/openca ... ter/upload

Lastly, FAQ: viewtopic.php?f=176&p=739789#p718325

It would be a great feature to have among the core.

This approach is very interesting. If I understand the concept well, does this approach AI? Or also a type of internal remarketing?

Could it be extended to the other modules (latest, featured, etc)?

diegospm wrote: ↑

Sat May 11, 2019 9:03 am

Sorry, I made a little confusion, I think I got it now.

About my suggestion, what I envisioned was related to an attempt to buy / buy and customer search. For example: if the client is logged and search iphone term, posteriorly during in store navigation, the modules automatically displays iphone related products.

If the customer buys, would be listed products related to the purchase. Not necessarily latest or featured modules, I used these just as an example...

straightlight wrote: ↑

Sat May 11, 2019 9:28 pm

There's no need to re-invent the wheel by using an API. Simply use this example: viewtopic.php?f=202&t=203512&p=720446#p720446 . Then, once the token gathered at the bottom, use the custom codes as you see fits to return the results to your jQuery response.

diegospm wrote: ↑

Sun May 12, 2019 7:41 am

straightlight wrote: ↑

Sat May 11, 2019 9:28 pm

There's no need to re-invent the wheel by using an API. Simply use this example: viewtopic.php?f=202&t=203512&p=720446#p720446 . Then, once the token gathered at the bottom, use the custom codes as you see fits to return the results to your jQuery response.

maybe you did not understand to my suggestion or I did not understand the proposal of the topic you mentioned.

The purpose of the api would be to connect the OC in external sites / apps (erps, marketplaces, payments provider, shippings provider, etc) and not the other way around.

In some countries (such as mine), the OC is not yet extensively exploited by external providers and api could simplify to developers create extensions.

It would not be necessary to create a curl function to connect to each app and I thought about the guzzle to be able to use requests async/promise (when necessary).