Helping Your ecommerce Developer
When integrating eCommerce into your stores there can be a lot of toing and froing between the eCommerce developer, the stock controller and the EPOS provider. For this blog I’m focusing mainly on how the stock controller can understand what the eCommerce developer can see when using the TRIMS API, and how the stock controller can check and advise the eCommerce developer without needing the help of the EPOS provider.
The image that accompanies this blog shows a tool that we have added into TRIMS specifically for this job. This tool calls the TRIMS API in exactly the same way that your eCommerce developer would, it shows the raw JSON results (just think of JSON as the language software communicates in) in the lower window, and formatted in a tree view for your ease of use in the upper window.
To reiterate, what you see in this window is what your eCommerce developer sees. When you realise that an important bit of data in your TRIMS system is not on your website, you can use this view to help explain to your web developer where they can find it, because they can see the same info as you can see on this view.
When your website says you have 5 items in stock, but you only have 4 - check this view to see what the web developer can see, if it’s 4 but the website says 5, they have a problem that needs correcting. You can also use this same method to check that you have TRIMS configured correctly, if the number looks incorrect on TRIMS, you may not have all of your locations toggled for sending stock to your website.
In most cases this tool can help bridge the gap between the stock controller who knows their stock and the web developer who knows how to build websites. All without going through the EPOS provider.
Just because something is displayed in the API, doesn’t mean that the web developer is using it, or has the functionality in their system to take advantage of it. Depending on your web developer, it may not be possible, it may be chargeable, or it may be included already. Never expect functionality and always check well in advance of wanting to implement functionality.