The orders module exports eligible sales orders from NetSuite to Amazon MCF as fulfillment orders. It includes an optional Fulfillment Preview flow, the main Order Export flow, and a Release Hold flow for orders submitted in a held state.
Flow 1: NetSuite to Amazon MCF Orders Fulfillment Preview (Optional)
The fulfillment preview flow calls the Amazon Get Fulfillment Preview API for each eligible NetSuite sales order and writes estimated shipping fees and earliest delivery dates back to the order. This allows your team to review costs and delivery options before committing an order to Amazon MCF.
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. Runs in delta mode to pick up newly created orders.
- 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.
Note: The fulfillment preview flow is optional. If skipped, orders are submitted to Amazon using the default shipping speed configured in Settings > Orders. Amazon's available shipping speeds are Standard and Expedited. Priority shipping has been discontinued and is not supported.
Flow 2: NetSuite Order to Amazon (MCF) Order Add
This is the primary order flow. It exports eligible NetSuite sales orders to Amazon as MCF fulfillment orders on a scheduled basis.
How the flow works
- Get Amazon MCF Sales Orders from NetSuite (Export): Uses the NetSuite 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). Returns sales order records with all required fields: shipping address, items, quantities, shipping speed, fulfillment action, and feature flags.
- Create MCF Order in Amazon (Import): Calls the Amazon createFulfillmentOrder API (POST /fba/outbound/2020-07-01/fulfillmentOrders) with: sellerFulfillmentOrderId (NetSuite order number), displayableOrderId (Document Number), displayableOrderDate, destinationAddress (from the NetSuite order shipping fields), shippingSpeedCategory (Standard or Expedited from the Amazon Shipping Speed field), fulfillmentAction (Ship or Hold from the Amazon Fulfillment Action field), Items (sellerSku, quantity, sellerFulfillmentOrderItemId per line), featureConstraints (BLANK_BOX, BLOCK_AMZL, SIGNATURE_CONFIRMATION from the respective checkboxes), and fulfillmentPolicy (from the Amazon Fulfillment Policy field).
Important: The NetSuite saved search (ID 5777) must include all required columns: Document Number, Date Created, Shipping Address fields (Address 1–3, Addressee, Attention, City, Country Code, State/Province, Zip, Phone), ShipMethod, Memo, Amazon Blank Box, Amazon Block AMZL, Amazon Signature On Delivery, Amazon Fulfillment Action, Amazon Fulfillment Policy, Amazon Shipping Speed, and Line ID.
Flow 3: NetSuite to Amazon MCF - Release Order Hold
When orders are submitted to Amazon in hold status, this flow releases the hold and begins fulfillment. It monitors NetSuite for orders flagged for hold release and calls the Amazon updateFulfillmentOrder API to change the status to Ship.
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 (PUT /fba/outbound/2020-07-01/fulfillmentOrders/{sellerFulfillmentOrderId}) with fulfillmentAction = Ship, releasing the order for fulfillment.
Tip: The hold/release pattern supports any approval workflow in NetSuite: time-based delays, manual review queues, multi-step approvals, or fraud detection integrations. Celigo only handles the API call to Amazon; all logic for when to release is in NetSuite.
Orders settings
Access and configure all settings from the Integration tile > Settings > Orders before enabling the order flows.
| Setting (field label) | Type | Required | Description |
|---|---|---|---|
| NetSuite Saved Search For Syncing Orders | Export Select (Saved Search picker) | Yes | Select the NetSuite saved search that controls which sales orders are exported to Amazon MCF. The template ships pre-configured with saved search ID 5777, which filters for orders where the eTail Channel checkbox is checked and the order has not yet been exported. Customize the saved search in NetSuite to add additional filters (e.g., by location, warehouse, or order source channel). |
| NetSuite Order ID field | Text | No | Provide the internal ID of the NetSuite field that will hold the ID of the MCF Order after it is created in Amazon (e.g., custbody_celigo_amzmcf_etailorderid). This field is written back to the sales order after successful order creation in Amazon. |