We are still using EDI to get orders from Amazon, Walmart, Costco, etc... I want to move to API. I believe that all the "big" players have API. Now, should we write the code or use an existing application like Celigo or RF-smart ? My only concern with Celigo and / or RF-Smart or any other, is that it's an endless cost. If we write it, it will be one time. Just want to know what you think ?

Do you mean Netsuite’s API? Like dumping EDI data to a Netsuite RESTlet?

No connecting directly to Amazon. They sent us the documentation. It will be quite easy. I'm just wondering what other people did ?

oh gotcha, sorry we just do strictly EDI, didn’t realize trading partners offered another option

No problem

@Simon are you 1P or 3P with Amazon?

I would go with developing your own to connect to the APIs. It will take some time especially if you haven't done it yourself or your team doesn't have any experience with connecting to those APIs.

1P

We’re 1P, too. I’d be interested in using their API vs. EDI, but I hadnt’ heard anything about an API for 1P.

I know it's available with Amazon, they sent me the documentation and want me (us) to use id

what’s your product category?

but I believe that I will write everything instead of RF-Smart or Celigo or Anything else like that

You might have to rethink your strategy of writing everything if you're 1P because that will still have to go through EDI. Compared to being 3P where Amazon has an API for that.

You can use Celigo's integration platform interator.io to create integration on your own. it would be very easy and quick.

I agree , but we are looking at the cost. Celigo is an ongoing cost, IF we write it, it will be a one time cost and it's over. That's what they think. I'm looking for an answer to that 🙂

the traditional integration option is to use webservices to create your integration

In terms of cost, compare it to what you're going to pay to develop it and maintain it say over a 5 yr period versus going with integrations like Celigo, SPSCommerce, or TrueCommerce. If you lose the team members who developed it and know how to support it, it may end up being more expensive overall.

Thanks. It's great information.