We are in the process of upgrading our 3.x cart to 4.x, in big part driven by rolling out a new POS which will connect to the cs cart API. The problem we are running into is the custom fields. The simplest of which is UPC. Each product has a unique UPC which we use to scan and look up the product on the POS. Adding the field to the database, admin, etc. is easy, but what about modifying the API to we can pass it back and forth through this. I am surprised that in 4.x we don't have custom fields for products. They seem to be pretty popular based on requests on the forum. Any one out there modify the API to add a field or would we have to go to CS Cart services to have them do this one?
We are in the process of upgrading our 3.x cart to 4.x, in big part driven by rolling out a new POS which will connect to the cs cart API. The problem we are running into is the custom fields. The simplest of which is UPC. Each product has a unique UPC which we use to scan and look up the product on the POS. Adding the field to the database, admin, etc. is easy, but what about modifying the API to we can pass it back and forth through this. I am surprised that in 4.x we don't have custom fields for products. They seem to be pretty popular based on requests on the forum. Any one out there modify the API to add a field or would we have to go to CS Cart services to have them do this one?
Since the default fn_update_product php function is used to update/ create products, you can try to extend the API without additional code changes. Just try to add additional parameters to the API request and check
You might want to consider moving your UPC to a product feature. It will then be portable and available via the API. Or alternatively, most people just use the product_code to store UPC since by definition it is unique to a product.
Using the product_code would be an option, but we really need 2 fields, one for single piece UPC and one for case UPC. I created the fields as product features, which makes them accessible if I search (filter) based on product_code, but our issue is we need to "filter" the API based on these new fields. I have a request into CS Cart sales for a customization to allow filtering on the product features fields. This would allow a lot of flexibility for all developers if they do make it part of the production software, which I also asked.