Connecting Amazon, Kaufland, Zalando, eBay or any other marketplace to your ERP is rarely hard because of the API itself. It gets hard because of the decisions around it: which system owns which data, what happens when something fails, and who notices.
Use this checklist when planning a new integration, or when reviewing one that keeps causing trouble.
1. Decide the source of truth for each type of data
Write down which system owns each type of data, and make the integration follow it:
- Stock: usually the ERP or warehouse system.
- Prices: the ERP, a pricing tool or a repricer, but only one of them.
- Product data: the ERP, a PIM or supplier feeds.
- Orders: the marketplace creates them; the ERP processes them.
Most data conflicts come from two systems both believing they own the same field.
2. Map identifiers properly
Marketplaces identify products by ASIN, EAN, their own IDs and your SKU. Keep an explicit mapping table between your ERP item numbers and each marketplace's identifiers, including variants and bundles. Never rely on matching product titles.
3. Make order import idempotent
Network errors and retries are normal. Importing the same order twice must not create two orders in your ERP. Store the marketplace order ID (or order line ID) and check it before creating anything.
4. Import by "last updated", not just "created"
Orders change after they are placed: payment completes, an address is corrected, the customer cancels. Fetch orders by last updated time so you catch changes, not only new orders.
5. Use stock buffers across channels
When the same item is sold on several marketplaces, stock updates are never instant. Keep a safety buffer per channel or per item for low-stock items, so you do not oversell between syncs.
6. Sync deltas often, reconcile fully on a schedule
Send stock and price changes frequently. Run a full reconciliation less often, for example nightly, that compares every item and corrects drift caused by missed updates.
7. Respect rate limits and use bulk operations
Every marketplace API limits how fast you can call it. Use bulk feeds and reports for large catalogs, queue and pace requests, and retry with backoff when you are throttled. One call per SKU does not scale.
8. Prefer events to polling where the marketplace supports them
Amazon, for example, can push notifications for order changes and finished reports. Event-driven integrations react faster and use far less API quota. Keep a slower scheduled sync as a fallback.
9. Handle shipping confirmations and returns
Sending tracking numbers back late hurts your seller metrics on every marketplace. Make shipment confirmation part of the integration, not a manual step. Bring returns and cancellations back into the ERP so stock and accounting stay correct.
10. Get taxes and currencies right
Selling across European marketplaces means different VAT rates, currencies and sometimes marketplace-collected taxes. Agree with your accountant how orders, fees and settlements should be booked, and map them explicitly.
11. Log errors where someone will see them
A failed product upload or rejected order hidden in a log file is a lost sale. Collect errors in one place, with the reason and the affected item, and review them daily.
12. Monitor and alert
The most important alert is the simplest: no orders received from a marketplace for longer than usual. Add alerts for rising error rates and syncs that fall behind. Most integration failures are found by customers because nobody was alerted.
Bonus: plan for change
Marketplace APIs change constantly: new versions, deprecated endpoints, new required attributes. Budget time for maintenance, or have someone responsible for it. An integration without an owner will eventually break.
Want a second opinion on your integration?
We review marketplace integrations in an Integration Health Check: we go through your current setup against this checklist and give you a prioritized plan. See our marketplace ERP integration service, or describe your setup below.