Connect Amazon Seller Central to your ERP and storefront. Entech builds Celigo-based Amazon integrations for brands and distributors where orders, inventory, and settlements need to move between Amazon and your back-office systems without manual touchpoints — including the parts most connectors leave out.
Talk to an integration expert →Amazon Vendor Central (1P) is not accessible via Seller Central API. Amazon transmits EDI purchase orders to Vendor Central sellers rather than providing a standard connector interface. If you sell wholesale to Amazon rather than through Seller Central, the EDI capability page covers this flow.
Amazon Seller Central orders pulled into your ERP or Shopify as Sales Orders. Order status, line items, quantities, shipping details, and buyer information all mapped. Order source tracked by marketplace (US, UK, CA, EU) where multi-marketplace is in scope. FBA and FBM orders handled with separate fulfillment logic — they are different operational events.
Available inventory quantities pushed from your ERP or warehouse system to Amazon listing inventory on a defined schedule. FBA inventory held in Amazon's fulfilment network is tracked separately from merchant-held stock — both require distinct handling. High-SKU catalogues use delta sync rather than full catalogue refreshes to stay within API limits.
Amazon identifies products by ASIN; your ERP and warehouse use internal SKU codes. Every integration requires a lookup table mapping ASINs to internal item records. This lookup is maintained as a configuration layer in Celigo — product catalogue changes update the mapping without rebuilding the flow.
Where FBA is in use, inbound shipment plans created in Seller Central need to reflect in the ERP as inventory transfers or purchase orders. Received quantities confirmed by Amazon update ERP inventory levels. This flow runs separately from order and settlement flows.
Amazon pays out on a settlement cycle — typically every two weeks — and the settlement report mixes order revenue, FBA fulfilment fees, referral fees, reimbursements, chargebacks, promotional credits, storage charges, and adjustments in a single document. Mapping this to clean journal entries in NetSuite requires line-level parsing and separate GL treatment for each fee and adjustment type. This is the part of Amazon integration that generic connectors either skip or flatten into a single revenue figure that does not reconcile.
Customer return events in Amazon mapped to corresponding ERP records — Credit Memos, return receipts, and inventory adjustments where units are physically returned to stock. Amazon's return disposition status (returnToStock, damaged, customerDamaged) determines the inventory handling logic.
The most common gap in Amazon + NetSuite integrations is treating settlement as an afterthought. Pulling orders into NetSuite as Sales Orders is the straightforward part. Reconciling what Amazon actually paid — net of fees, reimbursements, and adjustments — against those Sales Orders is the operationally critical part. We build settlement parsing as a first-class component of every Amazon + ERP integration, not a phase 2 add-on.
FBA orders are fulfilled by Amazon — inventory depletion happens inside Amazon's network and the fulfillment event flows back as a confirmed shipment. FBM orders require the seller to fulfil and report a shipment back to Amazon. These are fundamentally different operational flows, and treating them identically produces incorrect inventory counts and missed fulfilment confirmations. We configure both paths explicitly.
The ASIN-to-SKU lookup table is not a one-time setup task — it needs to be maintained as the product catalogue changes. New products added to Amazon, bundled ASINs, and parent-child ASIN relationships all require mapping updates. We build the lookup layer to be maintainable by the client without touching the flow configuration.
Sellers active on Amazon US, UK, Canada, and EU marketplaces need per-marketplace configuration. Currency, VAT treatment, fulfilment centre locations, and settlement schedules differ by marketplace. A single Celigo flow cannot serve all marketplaces without marketplace-aware routing logic. We scope this at the design stage.
SP-API rate limits are aggressive at high catalogue volumes — updating inventory for 50,000+ SKUs cannot be processed in a single run without throttling errors. We implement delta sync, request queuing, and back-off retry as standard on high-SKU implementations. If your existing Amazon integration started throwing errors in 2023, MWS deprecation — Amazon's shutdown of their legacy API — is the most likely cause.
Vendor Central sellers receive purchase orders from Amazon as EDI 850 documents rather than through a standard API. Entech implements this flow using Celigo's B2B Manager — the full 850 → Sales Order → 940 cycle with NetSuite, with zero manual touchpoints. See EDI / B2B capability →
A branded consumer goods company selling through major retail partners — including Amazon Vendor Central — needed to eliminate manual processing of retailer purchase orders. Amazon transmits 850 EDI purchase orders to this client; Entech built the full EDI + NetSuite flow on Celigo's B2B Manager. The 3PL now receives warehouse authorisation within two minutes of PO transmission, down from several hours of manual processing. 100% of EDI 997 acknowledgements transmitted within SLA. The full 850 → Sales Order → 940 cycle runs with zero manual touchpoints.
See the EDI / B2B capability page →Entech has delivered Amazon Seller Central integrations across its 200+ Celigo implementations. All developers are Celigo certified. Amazon marketplace integrations — and specifically settlement reconciliation — are among the most technically involved flows we build.
If you are reconciling Amazon settlements manually against your ERP, or managing Amazon inventory separately from the rest of your stock, those are the two problems we solve most frequently in Amazon integrations on Celigo.