Yes, we have many clients who work with Amazon as a vendor (EDI/API) and as a seller we connect only through the API.

Of course. The use of a third-party provider like Edicom is not mandatory. I can confirm however that we have been working with Amazon to connect to their APIs for a long time now and it is a process that requires advanced knowledge and programming skills. In saying that, if you have the internal resources, it can be done. 

By leveraging a third-party provider like Edicom, you can speed up the process and connect automatically without any hassle. 

This is a really common question that unfortunately never results in the answer people what to hear. This depends a lot on the information you as a vendor wish to receive, your workflow, internal processes etc. It is something that would have to be discussed 1:1 in order to come to a concrete and individual conclusion.  
Bear in mind, Amazon are continuously developing different API calls and EDI has been around for a long time now. Either way, Edicom can help you connect. 

Yes, as a Vendor, you can integrate with Amazon using both EDI & Amazon's Selling Partner (SP) API.

As a seller, you can only integrate using Amazon SP API. 

If you’re working with Amazon in Spain and wish to also work in Germany, this would require configuring the connecting and testing, but the workflows and integrations remain the same. 

If however you wish to start selling in the US, it may require a new mapping as X12 is the format most often used in the US whereas Edifact is what’s used in Europe. 

We have a large variety of EDI messages that we can exchange with Amazon. The exact ones you need will depend on your specific workflow. 

For example, if you’re a Vendor, shipping your products directly to the customer from your warehouse, you must include a mandatory EDI message called an IFTSTA (Status Report).

If Amazon is delivering the products for you, the IFTSTA message isn’t necessary. 

Here are some of the commonly used EDI messages our clients exchange with Amazon:
Purchase Order, Purchase Order Response, Advance Shipment Notice/Dispatch Advice (ASN), Invoice, 820 Payment Order/Remittance Advice, Inventory Availability Advice, Label Request (XML), Label Response (XML), Status Report (IFSTA).

The workflows we spoke about during the webinar are specific to Europe. Direct Fulfilment is not available in all marketplaces. Brazil is one of them where only Retail Procurement is available for vendors. 

For Sellers, FBA was only recently introduced (late 2020).

Most of the EDI functions can be developed by API. Nevertheless, Edicom will suggest the best way to integrate according to your integration requirements and expectations.

Amazon’s API allows developers to create new products in Amazon's catalog. The “CreateProduct” operation allows developers to programmatically create a new product.

The "CreateProduct" operation allows developers to submit information about new products to Amazon's product catalog. This operation can be used by developers who have the necessary permissions to create new products in Amazon's catalog on behalf of their organization or business.

Seller Central can only be used by utilizing the Selling Partner API developed by Amazon, using the JSON format.

Yes, you can outsource your API connection to EDICOM, and you will benefit from EDICOM's expertise and experience in API development, which can result in faster implementation and reduced costs. Leveraging EDICOM as your third-party API provider can avoid the need to hire and train local IT staff, so you can benefit from our economies of scale and expertise in API development.

The time required to integrate an order confirmation using an API with EDICOM as the service provider will depend on various factors, such as the complexity of the integration, the availability of resources, and the level of expertise of the technical team involved. It is important for the company to have a clear understanding of their business requirements, have a well-defined plan for the integration, and have dedicated resources to work on the integration in order to speed up the integration process with you ERP. Furthermore, it is important to work closely with EDICOM's technical team to ensure a smooth and successful integration.

It is true that APIs will have more functionalities in the future and are constantly being developed and updated. Nevertheless, Edicom will suggest the best way to integrate according to your integration requirements and expectations.

Yes, Edicom helps with this prior configuration in Vendor Central in all of our integration projects.

EDICOM can connect to various e-commerce platforms through our integration solutions. We have connections with platforms such as Amazon, eBay, Shopify, Magento, and Mercado Libre, among others. 

EDICOM's integration solutions use various technologies such as APIs, web services, and EDI standards such as EDIFACT and XML. These technologies enable seamless integration with e-commerce platforms, providing businesses with real-time data exchange and automated order processing. 

EDICOM's pricing model is based on price per message. As the volume of transactions processed through the platform increases, the price per transaction decreases. This pricing model is beneficial for EDICOM's clients because they can save money over time. Additional pricing considerations for the implementation of EDICOM's EDI solution depends on numerous factors, such as the specific EDI services and features required, the volume of transactions, the complexity of the project, and the level of customer support and maintenance required.

The actual timeline and process may vary depending on the specific requirements and scope of your project, but this should give you an idea of what to expect.

Phase 1: Analysis and Planning (1-2 weeks)

During this phase, you'll work with Edicom to define the scope of the project, identify the specific data exchange needs, and establish the technical requirements. This may include mapping out the data formats, defining the business rules, and selecting the appropriate communication protocols. Edicom will work with you to develop a project plan and timeline.

Overall, the time frame for implementing an EDI project with Edicom can range from a few weeks to a few months, depending on the complexity and scope of the project. By following these phases and working closely with Edicom, you can ensure a smooth and successful implementation that meets your business needs.

Phase 2: Development and Testing (4-12 weeks)

In this phase, Edicom will configure and customize the software and infrastructure to meet your specific needs. This may involve setting up the necessary connections to your partners' systems, configuring data mapping, and creating custom workflows. Once the solution is developed, it will be tested thoroughly to ensure it is working as expected.

Phase 3: Implementation and Go Live (1-4 weeks)

During this phase, the solution will be deployed to production and any necessary configurations will be made to the production environment. Edicom will work with you to test the solution in the production environment to ensure it is working as expected. Any necessary training or support will also be provided to your team.

Phase 4: Ongoing Support and Maintenance

Once the solution is live, Edicom will continue to provide ongoing support and maintenance to ensure the solution remains up to date and meets your evolving business needs. This may include troubleshooting issues, updating configurations, and making any necessary modifications to the solution.

Yes, at EDICOM, support is available in 7 languages: English, Spanish, French, Italian, Dutch, German, and Portuguese.

We also offer a web interface available in the above languages.

Yes, our software is ERP agnostic which means we can connect to all the major ERPs on the market, including SAP Business One.  We currently have multiple clients using this ERP. 

Yes, EDICOM's platform can integrate invoices and other related documents generated by Amazon Vendor Central and Seller Central into the ERP system. EDICOM's platform can automatically convert the invoices generated by Amazon Vendor Central and Seller Central into the required format for your ERP system and can transfer the data between the systems. This process can help to streamline the invoicing process, reduce errors, and improve the accuracy of financial reporting. 

EDICOM has developed a solution called iPaaS (Integration Platform as a Service) which is a cloud-based integration platform that can help businesses connect different systems and applications, including Power Automate. This platform provides businesses with a range of integration services and tools that connect different systems, applications, and data sources. iPaaS allows businesses to integrate their internal systems (for example ERPs or CRMs) with external systems (like e-commerce platforms or supply chain partners).

As an ERP system, you can use EDICOM to connect your clients to Amazon and Mercado Libre. EDICOM provides a wide range of services and solutions that can help you integrate your ERP system with such marketplaces and other trading partners.

EDICOM provides integration services that can connect ERP systems, such as JD Edwards and Oracle, with Amazon Vendor and Seller Central. EDICOM has extensive experience integrating different types of systems and formats, including EDI, XML, and other formats used by different ERP systems.

EDICOM will never enter your ERP or management systems to extract data. The client will always push data to us by exporting it.

EDICOM works with them to build the data extract they need to send us to be mapped to the required format.

ERP integration refers to the process of connecting an ERP system with other software systems within an organization or with external systems, such as third-party software, to share data and streamline processes. ERP integration can help organizations to improve their operational efficiency, reduce manual effort and errors, and gain better visibility and control over their business processes.

There are different methods for this integration. It could be an API-based integration, or we could use our middleware integration etc.

Our client exports structured data from their ERP. Once this arrives on our platform, we map it into the format required, carry out syntactical validations and route the message to the correct destination. 

All handling units (pallets, cartons, packages..) need to be labelled so they can be tracked and processed by carriers or Amazon FCs

If you want to send information to Amazon using EDI or ASN, you can but you will need to label each item according to Amazon's guidelines.

It's important to check Amazon's Vendor Central or Seller Central portal regularly for any updates on their labeling requirements and guidelines, so that you can remain compliant.

There is no label information in orders. The Shipping Label workflow comes separately from the Purchase Order reception and acknowledgment.

it’s a separate process that varies based on whether you are a Seller, a Retail Vendor, or a Direct Fulfillment Vendor.

In the Gs1-128 standard, the SSCC (Serial Shipping Container Code) is a mandatory element that must be included in the barcode.

If you are sending inventory to Amazon's fulfilment centres, you will need to use an SSCC label to identify and track your shipments, as this is a requirement of Amazon's labelling and packaging guidelines.

No, an AMZNCC (Amazon Container Code) does not substitute a SSCC (Serial Shipping Container Code). These two codes serve different purposes in the supply chain and are used by different parties to identify and track shipments.

The SSCC is a globally recognized barcode standard that is used to identify and track shipping containers. It is a unique identifier assigned to a specific shipping container or pallet, and is used by carriers, logistics providers, and other supply chain partners to track the movement of goods.

The AMZNCC, on the other hand, is a code that is used by Amazon to identify and track shipments within its own supply chain. It is not a globally recognized standard and is only used by Amazon and its partners. The AMZNCC is used to track shipments within Amazon's warehouses and fulfilment centres, and is not intended to replace the SSCC for tracking shipments through the wider supply chain.

If you are using Amazon's fulfilment services to store and ship your products, you may be required to use the AMZNCC in addition to the SSCC to ensure that your inventory is tracked accurately within Amazon's systems.

It's important to note that Amazon's labelling requirement may vary depending on the specific fulfilment centre and the type of products you are shipping. You should check with Amazon directly.