Amazon MCF – NetSuite implementation guide

Just getting started? Start here

If you want the core Amazon Multi-Channel Fulfillment loop up and running — inventory sync, order submission, and shipment tracking — you only need a handful of flows. Follow the sections in order: Prerequisites → Install → Configure Settings → enable the core flows. You can add returns and cancellations later.

1. Prerequisites
2. Install the template
3. Configure settings
4. Core flows
5. Enable and schedule

What this template does

The Amazon MCF – NetSuite template integrates Amazon Multi-Channel Fulfillment (MCF) with NetSuite through Celigo's integrator.io platform. It automates the full fulfillment lifecycle: inventory sync, order submission, fulfillment tracking, returns, and cancellations — keeping inventory, orders, and shipment records automatically in sync between the two systems.

Amazon MCF lets merchants use Amazon's fulfillment network to ship orders that originate from any sales channel — Shopify, Walmart, your own website, or any other storefront, not just Amazon.com. This template connects that fulfillment network to your NetSuite ERP.

The template is delivered as an unmanaged solution. Unlike a managed integration app, it gives you full control: you can directly modify flows, mappings, settings, and business logic to align the integration with your operational requirements. It ships as eight pre-built flows that you install, configure, and enable — no custom development required for standard MCF operations.

What you gain

• Operations teams stop submitting orders to Amazon by hand. Eligible NetSuite sales orders are exported to Amazon MCF as fulfillment orders automatically.
• Warehouse and inventory teams keep NetSuite item quantities aligned with what is physically fulfillable in Amazon's fulfillment centers.
• Customer service sees tracking numbers and fulfillment status flow back into NetSuite as Item Fulfillment records the moment Amazon ships.
• Finance and support get a clean returns and cancellations trail: NetSuite RMAs create Amazon return requests, and cancelled orders are withdrawn from Amazon before they ship.

Who this guide is for

This guide is written for:

• Operations and fulfillment teams who are setting up the integration themselves or overseeing an implementation.
• Support teams who need to understand how each flow works in order to diagnose issues and answer questions.
• NetSuite administrators who are preparing NetSuite for the integration (bundle installation, roles, saved searches, and eTail custom fields).

All eight flows at a glance

The template ships with eight flows organized into five functional modules. All flows are disabled by default after installation: you enable them in a specific order after completing setup. The Enable flows and schedule section walks through the exact sequence.

Prerequisites

Before installing the template, ensure that all prerequisites are met across your NetSuite, Amazon Seller Central, and Celigo accounts. Skipping prerequisites is the single most common cause of errors on new installations.

NetSuite requirements

Amazon Seller Central requirements

You must have an active Amazon Seller Central account with Multi-Channel Fulfillment (MCF) enabled. Ensure the following before configuring the Amazon SP-API connection in Celigo:

• An Amazon Seller Central account with MCF activated.
• Your Marketplace ID (for example, ATVPDKIKX0DER for the US).
• SP-API credentials: client ID, client secret, and refresh token (obtained via the Amazon developer console).
• At least one FBA/MCF-enabled ASIN with inventory at an Amazon fulfillment center.
• Seller SKUs in Amazon must match (or be mappable to) item identifiers in NetSuite.

Celigo requirements

• An active integrator.io subscription with a valid Amazon MCF – NetSuite template license.
• Account owner role in integrator.io to authorize the Amazon SP-API and NetSuite connections.
• Both connections (Amazon SP-API and NetSuite) must be configured and online before enabling any flows.

Install the template

Once every prerequisite is met, install the template from the integrator.io Marketplace. You must be signed in as an account owner.

Post-installation sequence

Complete the following steps in order before relying on the integration for production traffic. Each step is expanded in later sections.

Configure settings

Settings are grouped by module and configured from the Integration tile > Settings. Configure each module's settings before enabling that module's flows. This section documents every setting field, its type, whether it is required, and how it affects flow behavior.

Inventory settings

Access and configure all inventory settings from Settings > Inventory before enabling the inventory flow. The settings are split across two tabs: Inventory and Location.

Tab: Inventory

Tab: Location

Quantity fields reference

Amazon reports inventory across several quantity buckets. Use this reference to decide which buckets to include in the fulfillable and unfulfillable totals.

The unfulfillable multiselect also exposes finer-grained buckets — Customer Damaged (customerDamagedQuantity), Warehouse Damaged (warehouseDamagedQuantity), Distributor Damaged (distributorDamagedQuantity), Carrier Damaged (carrierDamagedQuantity), Defective (defectiveQuantity), and Expired (expiredQuantity) — for merchants who track damage reasons separately.

Item matching

The Specify the Amazon field to search for matching items in NetSuite setting controls how each Amazon SKU is resolved to a NetSuite item.

Orders settings

Access and configure all order settings from Settings > Orders before enabling the order flows.

Fulfillments settings

Access and configure all fulfillment settings from Settings > Fulfillments before enabling the fulfillment flows.

Cancellations settings

Access and configure the cancellations setting from Settings > Cancellations before enabling the cancellations flow.

Flows: Inventory

The inventory module keeps NetSuite item quantities aligned with what is physically available for fulfillment in Amazon's fulfillment centers.

How the flow works

• Export Inventory from Amazon. Calls the SP-API getInventorySummaries endpoint. Runs in delta mode by default, using the Offset time setting to control the look-back window. Returns fulfillable and unfulfillable quantity fields per seller SKU.
• Lookup Items from NetSuite. For each Amazon SKU returned, searches NetSuite for the matching item using the configured item-matching field (sellerSku, fnSku, asin, or productName).
• Lookup Item Aliases from NetSuite. If Search for Item Alias is enabled, performs an additional lookup in the NetSuite item alias table when the primary lookup does not return a match.
• Adjust Inventory in NetSuite. Creates a NetSuite Inventory Adjustment record for the sellable-quantity location, setting the item's quantity to match the Amazon value based on the configured fulfillable quantity fields. Damaged quantities post to the damaged location if configured.
• Update Amazon Quantities into NetSuite Item. If Update Amazon Quantity fields into NetSuite Item is enabled, writes the raw Amazon quantity field values (fulfillable, unfulfillable, and so on) back to the NetSuite item record.

Flows: Orders

The Orders module exports eligible sales orders from NetSuite to Amazon MCF as fulfillment orders. It includes an optional Fulfillment Preview flow, the primary Order Add flow, and a Release Hold flow for orders submitted in a held state.

How the flow works

• Get Amazon MCF Sales Orders for Fulfillment Preview (Export). Uses a NetSuite saved search (Search ID 5745, record type salesorder, delta mode) to retrieve sales orders flagged for MCF that have not yet been submitted.
• Get Amazon Fulfillment Preview Data (Lookup). For each order, calls the Amazon createFulfillmentPreview API (POST) with the order's items, quantities, and destination address. Returns available shipping speeds, estimated delivery windows, and fulfillment fees per speed option.
• Update Sales Order with Amazon Fulfillment Preview Data (Import). Updates the NetSuite sales order with the Fulfillment Preview – Standard Fee, Fulfillment Preview – Expedited Fee, and Fulfillment Preview – Earliest Delivery fields.

How the flow works

• Get Amazon MCF Sales Orders from NetSuite (Export). Uses the saved search configured in Orders settings (Search ID 5777, record type salesorder, once mode using the custbody_celigo_amzmcf_order_exported boolean field to prevent re-export). Runs in batches of 100 records.
• Create MCF Order in Amazon (Import). Calls the Amazon createFulfillmentOrder API with the seller fulfillment order ID, displayable order ID and date, destination address, shipping speed category, fulfillment action, line items, feature constraints, and fulfillment policy.

How the flow works

• Get Amazon MCF Sales Orders to Release HOLD (Export). Uses a NetSuite saved search (Search ID 6389, record type salesorder, delta mode by lastmodifieddate) to find sales orders where the Amazon Remove Hold checkbox is checked.
• Update Amazon MCF Order to remove Hold (Import). Calls the Amazon updateFulfillmentOrder API with fulfillmentAction = Ship, releasing the order for fulfillment.

Flows: Fulfillments

The Fulfillments module polls Amazon for completed shipments and creates Item Fulfillment records in NetSuite. The template includes two fulfillment flows: the standard flow, and a variant that also retrieves per-package tracking data. Enable only one of them for a given fulfillment stream.

How the flow works

• Amazon MCF List Fulfillment Export (Export). Calls the Amazon listFulfillmentOrders API in delta mode. Returns MCF fulfillment orders with status changes since the last run.
• Amazon MCF Get Fulfillment Export (Lookup). For each fulfillment order ID, calls getFulfillmentOrder to retrieve the full fulfillment record including fulfilled items, quantities, shipment details, and tracking numbers.
• Create ItemFulfillment in NetSuite (Import). Creates a NetSuite Item Fulfillment record linked to the originating sales order with the items shipped, quantities, tracking numbers, carrier information, and ship date.

How the flow works

• Amazon MCF List Fulfillment Export_HTTP (Export). Calls the same listFulfillmentOrders API in delta mode.
• Amazon MCF Get Fulfillment Export (Lookup). Retrieves the full fulfillment order record per order ID.
• Amazon MCF Get Package Data (Lookup). For each package in the shipment, calls the Amazon tracking API to retrieve per-package tracking detail.
• Create ItemFulfillment in NS (Import). Creates the NetSuite Item Fulfillment record with all package-level data included.

Partial fulfillments

Both flows fully support partial fulfillments at the line-item level and at the quantity level.

Flows: Returns and cancellations

These two flows close the reverse-logistics loop. Returns move accepted RMAs from NetSuite into Amazon's returns network; cancellations withdraw orders from Amazon before they ship.

How the flow works

• Get NetSuite Returns (Export). Uses a NetSuite saved search (Search ID 6387, record type returnauthorization, once mode) to fetch return authorization records not yet exported to Amazon.
• Create Amazon Fulfillment Return (Import). For each RMA, calls the Amazon Returns API with the return items and quantities.

How the flow works

• Get NetSuite Amazon MCF Order Cancellations (Export). Uses a NetSuite saved search (Search ID 6390, record type salesorder, once mode) to find cancelled sales orders with a corresponding Amazon MCF fulfillment order.
• Cancel MCF Order in Amazon (Import). Calls the Amazon cancelFulfillmentOrder API to cancel the fulfillment order if it is still in a cancellable state.

Cancellability by Amazon MCF order status

Returns and cancellations decision guide

Enable flows and schedule

Enabling flows in the wrong order is the most common cause of errors on new installations. The post-installation sequence lists the order in which to switch flows on; this section explains the dependencies behind that order and how to schedule each flow for production.

Dependency order

Each flow depends on records or settings created by an earlier step.

Scheduling best practices

Most flows filter source records by a modification or creation timestamp. Choose an interval that balances data freshness against API volume on both platforms.

Troubleshooting

For each issue, the fastest path to diagnosis is to open the failing record in the Celigo flow dashboard, examine both the source payload and the error response, and identify which step failed (export, lookup, or import).

Orders not exporting to Amazon MCF

• Confirm the eTail fields are set. The order saved search (ID 5777) only returns orders where the eTail Channel checkbox is checked.
• Check the "already exported" flag. The export runs in once mode using custbody_celigo_amzmcf_order_exported. Clear it to force a re-export.
• Verify the saved search columns. If saved search 5777 is missing any required column, the generated payload is incomplete and Amazon rejects the order.
• Check SKU eligibility in Amazon. Each line's seller SKU must correspond to an FBA/MCF-enabled ASIN with inventory at an Amazon fulfillment center.
• Confirm the Amazon connection is online. A 403 from SP-API means the connection is offline or the refresh token is invalid.

Inventory not adjusting in NetSuite

• Check the item lookup. Verify the Specify the Amazon field to search… setting and the NetSuite Item field ID that matches the Amazon SKU setting point at the right fields.
• Verify the required IDs. The NetSuite Adjustment Account Internal ID and the sellable Warehouse location Internal ID are required.
• Serialized / lot-numbered items. If the item is Serialized or Lot Numbered and Auto-assign number is off, the adjustment errors. Enable auto-assignment.
• Widen the offset for backfills. Temporarily raise the Offset time to re-capture a missing window.

Fulfillments not creating in NetSuite

• Confirm the originating sales order exists. The Item Fulfillment is linked to the NetSuite sales order created by the Order Add flow.
• Check the delta window. Use Add shipments updated after, or the on-demand Amazon Seller Fulfillment Order Id setting, to reprocess a specific shipment.
• Set the inventory location. If Select inventory location present in NetSuite is blank and inventory detail is required, the Item Fulfillment can fail.

Cancellation rejected by Amazon

• Check the Amazon order status. Orders can only be cancelled while in Received or Planning status. See the cancellability matrix.
• Confirm the eTail Order ID is populated. If the eTail Order ID is empty, the order was never successfully created in Amazon and there is nothing to cancel.
• Cancel earlier. Shorten the cancellation flow's schedule so requests reach Amazon before the order enters Processing.

Returns not processing

• Verify the original fulfillment. The originating sales order and its Item Fulfillment must exist in NetSuite before the RMA can be sent.
• Check the "already exported" state. The returns export runs in once mode. A return authorization already marked as exported will not be re-sent.

Amazon SP-API authentication and throttling

• 403 authentication failures. Only a Celigo account owner can reauthorize the Amazon SP-API connection. A connection outage cascades into errors across every Amazon-bound flow at once.
• Rate limiting. If flows report throttling, lengthen the schedule interval and reduce concurrency so requests spread out over time.
• Sandbox limitations. Real-time inventory event notifications are not available in the Amazon MCF Sandbox.

NetSuite connection issues

• Token-Based Authentication errors. Confirm Token-Based Authentication is enabled in NetSuite and that the Token ID and Token Secret in the connection are current.
• Permission errors. Verify the cloned Celigo eTail SmartConnectors role retains all required permissions and is assigned to the integration user.

General debugging approach

1. Find the failing record. In the Celigo flow dashboard, open the run that contains the error and locate the specific record(s) that failed.
2. Identify the failing step. Export failures usually indicate a connection or saved-search issue; lookup failures indicate a missing or non-matching record; import failures indicate a payload, eligibility, or permission problem.
3. For lookup failures, preview the saved search. Open the referenced NetSuite saved search with the same values the flow used. If it returns nothing, the problem is the underlying data.
4. For import failures, inspect the payload. Copy the generated payload from the error log and compare it against the target API's requirements.
5. Fix before retrying in bulk. Resolve the underlying issue first, then retry. Retrying against an unresolved root cause only generates noise and partial records.