Amazon Personalisation
Some products in our inventory require personalisation … eg. A mug with your name printed on it, or a Chocolate bar with a “Happy Birthday Gary” printed on the wrapper.
When ordering these product from Amazon – before checkout, the customer has to complete the requested customisation – on a popup form. These customisation options are configured through the Amazon Seller administration module.
When fulfilling the order, the customisation data has to be downloaded from the Amazon Seller portal. This process is currently manual and, as you can imagine, when we have tens or hundreds of customised orders, this can take a significant amount of time.
Once the data is downloaded (it’s provided as a zipped archive) we combine it with data from corresponding Storefeeder order and then generate whatever output is required.
Requirement
We are aware that Amazon provide an API to enable us to do what we need – however – (1) it requires a development account, (2) it would be simpler to go to a single API to get all data, rather that synchronising between the two.
There are a number of ways that we envisage the integration could work.Either of these mechanisms would work for us …
1) On-demand … We would call a SF WebAPI – with a Storefeeder order Id, the web response would provide the Amazon personalization package (the zip) in a response stream.
2) We provide a Dropbox account. When retrieving order data from Amazon, test if the order has personalisation data – if it does, then download the corresponding personalisation data – and write it to the dropbox.
In addition, with option 2, if the Storefeeder Order was serialised into a JSON document and then stored with the same name as the Amazon package (but different file extension) – then our process could be simplified. We would not require the existing API. We would simply enumerate through our dropbox – using the JSON documents to provide the Order data.
Gary
shared this idea
We would like to update you in this.
You are now able to download the customisation information from StoreFeeder directly on the order or you can also get the information as it comes from Amazon using the folowwing API call.
https://rest.storefeeder.com/Help/Api/GET-orders-ordernumber-customisation
Thanks,
SF
-
Kelly
commented
I also agree with the users above. We sell a lot of personalised photo products and it is very time consuming having to click into the StoreFeeder order, then into the Customisations tab to then download the zip file onto our computer (currently it is a slightly quicker process to do this directly on Amazon as SF seems slower to load in comparison).
It would be great if all the files were saved onto a server that we could search. We currently use Google Drive to save our files with the order number, other staff members simply search our Google Drive folder on their computer to find the exact photo that they need and insert into our design software to make the order.
Having the files and photos automatically save to a searchable folder or site would be really helpful and speed up the process massively. Whilst I appreciate a lot of work will have gone into making the Amazon Customisation possible on StoreFeeder, I don't think it adds much benefit at present (mainly as it's the same view as on Amazon but takes longer to load, the details cannot currently be printed onto our invoices and we still have to find and download each file we need individually for each order, like we did before on directly on Amazon).
Thank you
-
Charles Ranson commented
Thank you for the updated and adding the feature. Unfortunately it's not much use to us in the way it's displayed in the Customisation Tab. Are you planning on a feature to allow us to download the raw Amazon data from within StoreFeeder? Will either of these from the original post be addressed?
"There are a number of ways that we envisage the integration could work. Either of these mechanisms would work for us …
1) On-demand … We would call a SF WebAPI – with a Storefeeder order Id, the web response would provide the Amazon personalization package (the zip) in a response stream.
2) We provide a Dropbox account. When retrieving order data from Amazon, test if the order has personalisation data – if it does, then download the corresponding personalisation data – and write it to the dropbox.In addition, with option 2, if the Storefeeder Order was serialised into a JSON document and then stored with the same name as the Amazon package (but different file extension) – then our process could be simplified. We would not require the existing API. We would simply enumerate through our dropbox – using the JSON documents to provide the Order data."
Thanks.