Is there a way to upload the Quantity on hand for inventory via an API call or file upload automatically?
Can the file upload function be automated? Passing a csv, xml, etc that would then load the updated QOH numbers?
The real time inventory functionality is not sufficient for some third party feeds like google merchant.
Inventory QOH Upload
-
cyoung
- Posts: 147
- Joined: Wed Nov 09, 2016 11:01 am
Re: Inventory QOH Upload
Product XML upload API specifications is in the docs, as is documentation for the Custom Inventory Tracking Add-on API (to have ShopSite make a call to a different source for inventory information instead of using its Quantity On Hand numbers).
https://www.shopsite.com/developer_tools.html
https://www.shopsite.com/developer_tools.html
-
Danscan
- Posts: 4
- Joined: Wed Mar 15, 2023 6:28 pm
Re: Inventory QOH Upload
I built out the call and I am using the upload1 url from the authentication but I am receiving the following error:
I am calling the following url:
https://mydomain/cgi-myname/sb/dbupload.cgi?clientApp=1&dbname=Product&uniqueName=SKU&signature=-=&token=-=×tamp=1683156130&nonce=26236363
<html><body><h1><center>Error</center></h1><hr><p>
Your User Name could not be determined. You should have been prompted by your browser to authenticate by entering a username and password.<p>
Solution:<p>
ShopSite is designed to use your webserver's built-in authentication system via the Apache .htaccess file method. If you are seeing this error message, many times the solution is to edit your webserver's httpd.conf file (or other config file) and allow the use of .htaccess files in your cgi-bin by defining 'AllowOverride All' in a <Directory> directive for your particular cgi-bin path.<p>
If you are unfamiliar with how to configure your webserver to use .htaccess authentication, your hosting service provider should be able to help you. The following links provide general information on setting up the use of .htaccess authentication for Apache-based webservers:<p>
<a href="http://httpd.apache.org/docs/mod/core.html#allowoverride">
AllowOverride directive</a><br>
<a href="http://httpd.apache.org/docs/howto/htaccess.html#troubleshoot">
Troubleshooting</a><p>
The ShopSite CGI Directory (containing the admin cgis like start.cgi) must be password protected in order to use the ShopSite admin tools. Do not put a password on the Shopping Cart CGI Directory or your customers will be unable to use the shopping cart.<p>
<hr></body></html>
I am calling the following url:
https://mydomain/cgi-myname/sb/dbupload.cgi?clientApp=1&dbname=Product&uniqueName=SKU&signature=-=&token=-=×tamp=1683156130&nonce=26236363
<html><body><h1><center>Error</center></h1><hr><p>
Your User Name could not be determined. You should have been prompted by your browser to authenticate by entering a username and password.<p>
Solution:<p>
ShopSite is designed to use your webserver's built-in authentication system via the Apache .htaccess file method. If you are seeing this error message, many times the solution is to edit your webserver's httpd.conf file (or other config file) and allow the use of .htaccess files in your cgi-bin by defining 'AllowOverride All' in a <Directory> directive for your particular cgi-bin path.<p>
If you are unfamiliar with how to configure your webserver to use .htaccess authentication, your hosting service provider should be able to help you. The following links provide general information on setting up the use of .htaccess authentication for Apache-based webservers:<p>
<a href="http://httpd.apache.org/docs/mod/core.html#allowoverride">
AllowOverride directive</a><br>
<a href="http://httpd.apache.org/docs/howto/htaccess.html#troubleshoot">
Troubleshooting</a><p>
The ShopSite CGI Directory (containing the admin cgis like start.cgi) must be password protected in order to use the ShopSite admin tools. Do not put a password on the Shopping Cart CGI Directory or your customers will be unable to use the shopping cart.<p>
<hr></body></html>
-
Danscan
- Posts: 4
- Joined: Wed Mar 15, 2023 6:28 pm
Re: Inventory QOH Upload
I have started to try a different method using a different url. This gives me a success but does not actually change anything what am I missing?
https://www.mywebsite.com/cgi-mywebsite/bo/dbupload.cgi
Non Authentication info
clientApp:2
dbname:products
uniqueName:SKU
newRecords:no
The xml is sent as a stream.
The response back is 200 but nothing changes.
https://www.mywebsite.com/cgi-mywebsite/bo/dbupload.cgi
Non Authentication info
clientApp:2
dbname:products
uniqueName:SKU
newRecords:no
The xml is sent as a stream.
The response back is 200 but nothing changes.